I’m trying to think through a field-operations architecture question.
Most CRMs and FSM systems are good at the administrative record:
customer;
work order;
technician;
schedule;
status;
invoice.
But “completed” is often still a self-attestation. The technician presses a button or uploads a photo. The system records that the technician said it was complete, but that is not always the same as independently verifying the completion.
Full disclosure: I’m the founder of LockProof. We’re building a separate verification layer rather than another CRM.
A worker receives a secure text link, opens a live camera, and submits proof tied to the job. There is no worker account or app installation. The record includes server-recorded time and location when shared.
My open question is where that evidence should ultimately live.
Option A: LockProof remains the separate evidence system, and the CRM receives a status, link and summary.
Option B: The full evidence package gets copied into the CRM.
Option C: The CRM triggers the request, but the verified record remains externally stored.
For people who implement or manage CRMs:
Which approach creates the least operational friction?
Would you prefer an API, webhook, native integration or email-based workflow?
Would copying the entire evidence record into the CRM create retention or storage problems?
I’m interested in the architecture more than selling anything. The product is lockproof.com for context.