Workflows, rules and proof

Keep your system.
Fix how the
work runs.

You already bought a system of record — ServiceTitan, FieldEdge, Procore, Acumatica, ESC. It tells the technician where to go. It doesn’t control what happens after they get there.

That part is ours. Your system holds the record — we run the work. Because we already know the job, the equipment and what the contract promised, the checklist asks the six things that matter on this unit instead of forty that don’t. Run it and it is proof. Publish it and it is your SOP.

It runs in our app, in an earpiece, or turn by turn in a text thread — so the subcontractor who will never install anything still leaves evidence. Every answer is an event: the office is told, the quote goes out, approved before the tech leaves site. And what a person walks, an agent can run — more work, not more people in the middle.

See it on your own data Start where you are →

The ServiceProof home screen on a phone: dispatch, billing, start and end of day, team directory and on-call schedule.

You don’t have to replace anything to start

There are two ways to run ServiceProof, and most shops should take the first one.

🔧

Augment — keep your system of record

Your ERP stays your ERP. Jobs come in over webhooks, an API or a batch load and land on our board. Rules fire. The tech runs the workflow on our app and captures the photos, the scans and the signature. What matters goes back out.

Nobody in your office learns a new system, nobody migrates twenty years of history, and you can stop at the end of any month.

Buy only the workflow seats for your commercial electrical crews and keep Procore. Run Acumatica and our mobile app for your locksmith shops. That is a supported way to own this product, not a workaround.

How augmenting works →

🏢

Adopt — run the whole platform

Dispatch board, customers, sites, equipment, people, crews, zones, recurring commitments, on-call. It is all built and it is all real.

Some shops want one system, and this is that system — but it is the second thing to read, not the first, because it puts back the risk the other one just took away.

What the platform does →

We are deliberately not the source of truth. That is a design decision, not a limitation — it is what lets you start on a Tuesday instead of next year.

One rule. One quote. Same day.

Every field service company on earth loses money in the gap between “the tech noticed something” and “the customer got a quote.” Here is that gap closed with a rule instead of a phone call.

A PM comes due

A recurring commitment — quarterly rooftop inspection — generates the work on its own, inside a window: earliest, target, due-by. Not a fixed date, because when a heat wave lands, PM work is what moves. The system knows what may move and how far, and it records it when a commitment gets breached — which is what an argument with a customer turns on a year later.
The tech runs “Found on PM” on their phone

Photos of the failed part, readings off the nameplate, the condition of the unit. The checklist is contextually aware: it renders one way for a CBRE site and another for a restaurant chain, because the difference between two customers is data, not a different version of the app.
A rule fires

The finding raises an event. No dispatcher decides to route it, nobody remembers to, and it does not depend on the tech texting somebody. An admin bound a workflow to that event once, as data, and it has fired every time since.
The estimator’s column lights up

The job transfers to the estimator on the board with the field evidence already attached — the photos, the notes, the equipment, the whole story of the visit. A board column is a queue with a person’s name on it, and arriving in that queue starts that person’s checklist.
A review flow walks the estimator through the quote In build

Madlib screens, prior-art pricing, and the checks that stop things being missed.
The quote goes out the same day In build

Instead of dying in somebody’s inbox.

The technician's dispatch list showing current jobs, with one marked 16 hours late.

The ServiceProof dispatch board: a zone lane with an unassigned inbox column and a column per technician, each holding live job cards with status, promise window and value.

What’s real today Beats one to four are running now, and we will show you all four on your own data. Five and six are where we are pointed. What makes that credible rather than a promise: every capability in ServiceProof is already an MCP tool, so an agent can do anything a person can do on a screen — and the estimator’s checklist is the same machinery as the technician’s. We are pointing it at estimating first.

How rules and events work →

One engine. Two audiences.

A workflow is a checklist a human walks — on a phone in a truck, in the office beside the screen they are already working in, and next in their ear while both hands are busy. Publish it and it is your standard operating procedure. Run it and it is the proof the work happened. Same engine. What it produces depends on who is holding it.

And when the procedure goes out as a message, the carrier tells us it reached the handset. A delivery receipt is proof the instruction arrived — not proof we sent it. Your ERP cannot produce that, because your ERP does not own the channel. It is the one piece of evidence in this whole product that comes from outside the building.

	The field	The office
What a run produces	Proof — of service, of condition, of custody	Conformance — the step was taken, in order, by the right role
Why you want it	It is the record you get paid against and defended by	Details are not missed, and a new hire is useful on day one
What you end up with	The story of the visit	The SOP, written by doing the job

You build your SOPs by doing your job

Not by writing a binder nobody opens. And the office half is the half that scales you — every competitor has a field app. Nobody automates the plumbing office. That is where the ten-times volume comes from: train agents to do the repeatable tasks that support the staff you already have. Not replace your dispatcher. Support her.

What the office gets → What the tech gets → Paperwork in your ear →

Creating a dispatch by filling in a sentence: customer, building, work and technician.

Rules and events, tied to everything

A job opens. A bag is sealed. A unit fails its check. A signature comes back. Your business turns on moments like these. OnOpen. OnClose. OnAssign. OnUnassign. OnChangeAssignment. Every status a job passes through. An admin binds a workflow to an event — as data, not code — and it fires from then on. Scope it globally, or to one department, one zone, one board, one customer.

A board column is a queue, and every queue can run its own workflow. A job sitting in Parts Ordered has the parts counter’s SOP running on it, exactly as a job on Rudy has the field SOP running on his phone.
Finishing transfers the job, and the transfer starts the next checklist. The tech completes, it hands to Parts, the parts counter’s workflow starts, the parts land, it hands back. A job’s life is a sequence of hand-offs and each one starts somebody’s list automatically.
The lock is opt-in. With no workflows there are no locks and the system is fully usable on day one. Mark a workflow as locking and the edits it governs cannot happen outside it — and it is enforced in the executor, not in the screen, so it holds for the API and the agents too.
The audit stops saying “Dave changed the tax code at 14:02.” It says “under run 4471, step 3 of New Commercial Customer.” The why becomes structural.
The card carries the proof, not just the question. A rich card can ask for a location and get coordinates back — not an address somebody typed. The carrier stamps the time. And a tapped reply returns a token we minted, so Worn arrives as a typed value rather than a word to be parsed. Location, timestamp and data, captured in the exchange itself.
And a reply is an event, which is what makes it scale. Delivered, seen, the suggestion that was chosen — each comes back as its own event, and an event can start the next workflow. So the conversation drives the process forward: the office is told, the quote task is raised and the next step goes out, with nobody sitting in the middle orchestrating it. One dispatcher stops being the limit on how many jobs a day you can run.

The rules screen: each row is an event, a scope, and the published workflow it starts, including a rule that hands a job to the estimating queue.

How rules and events work →

From a CBRE-driven commercial account to a boat in a slip

One platform. Different vocabulary. That is the whole argument for the model — and these are real shops, not personas.

Commercial electrical

Schoolfield Electric. Ten commercial electricians building drone pads for Walmart and conveyor systems for Amazon.

Plumbing

Charlie’s Plumbing. Forty-plus techs, two departments, one dispatch board — billing real work through the app every working day.

Courier and logistics

Way Delivery. Forty cars and hotshot box trucks, bank deposit runs twice weekly, chain of custody on every bag.

Marine

Tarvin Marine. The serviced thing moves, and the platform does not assume a fixed address.

HVAC and the rest

Appliance repair, locksmith, fire and sprinkler, refrigeration — most any field business that runs on trucks and checklists.

And a guy in one truck can run teams and fleets of subcontractors. That is not a slogan — it is what happens when the SOP does the coordinating instead of a person.

Charlie’s Plumbing is live on the app today. Schoolfield Electric, Way Delivery and Tarvin are the work the platform is being built around — named here because they are real businesses with real constraints, not because they are references.

Find your trade →

The whole pitch, in one line

Run it the same way every time

Keep the system you already bought. Put your work on our board, run your checklists on our app, and get the proof and the consistency you cannot buy anywhere else. Priced per tech or per proof.

See it on your own data Pricing →

Keep your system. Fix how the work runs.