What nobody else in field service does

Commercial field service has changed. Customers want proof the same day, good people are hard to find, and every new desk in the office comes out of the margin. ServiceProof is a ground-up rethink of how a company scales to meet that, built around three things nobody else in this industry is doing.

A business run on baselines

Every function in a trade company has a standard, and nobody gives you a way to set it. We do: the Balance to Baseline pillars and forty-four free worksheets to define a baseline for every job, and an ERP built to collect the numbers, measure the work against them, put them on every scorecard and celebrate them.

Balance to Baseline →

Proof workflows for the office and the field

Field apps stop at the truck. Here the checklist a tech walks on the roof and the SOP the parts counter, the estimator and billing follow at a desk run on the same engine, and every one of them comes back as proof that the work was done the way you said it would be.

How workflows run →

Code-level intelligence, not a chatbot

Wingman reads the question, and our engine answers it from your trade’s actual code, with your state and county amendments, worked out exactly and with the section cited, on a phone with no signal at all.

See it answer ↓

Why make ServiceProof your system

We’ll say it out loud: this is the best modern ERP in field service. Here is what that means next to the system you run today.

A typical FSM or ERP	ServiceProof
You run it from a desk, one screen at a time.	You run it by talking. Your AI assistant can do anything your people can do, from the truck, the job or the car.
The field app is a form with a camera.	The field app walks your procedure, reads it into the tech’s earpiece, and keeps working with no signal.
The AI is a chatbot that can be confidently wrong.	Wingman answers from your code book, exactly, with its work shown and the section cited.
Courier work is forced into a trades app or a parcel carrier’s system.	Courier is built in: pickups and drop-offs as legs, routes, custody of every bag, fuel surcharges and the customer’s proof of the day.
Office work runs on reminders and somebody’s memory.	Office work runs on your SOPs, and every hand-off starts the next team’s checklist.
The books live in another product.	The general ledger, payroll, payables, commission and sales tax are built in, cut by zone and department.
Six years without a meaningful new feature.	New capabilities ship every week, and your assistant can use each one the day it lands.
Switching is a twelve-month project.	Start beside the system you have in a month, and move the rest over when you’re ready.

Not ready to move everything? You don’t have to. Connect us to the system you run today and step across one crew at a time. How to step in ↓

Talk to your company on the drive in

Connect Claude, ChatGPT or Copilot to ServiceProof once, and the whole company becomes a conversation. Ask how the week is going, then tell it what to do. Anything your people can do in ServiceProof, your assistant can do too, with your permissions.

Ask about the business

“How much did we bill this week, and who’s past thirty days?”
“Which zone actually made money last month?”
“Which of today’s bank stops still have no proof?”
“Where is the estimating queue backing up?”

Tell it to do the work

“Move Marco’s last two stops to Dana.”
“Add Hartman Dental as a customer and book a drain cleaning for Thursday morning.”
“Set up a crew for the Lancaster zone and put Ivan on it.”
“Release this week’s vendor checks.”

It acts as you, never as a robot account. It sees and does exactly what you could, it confirms anything that can’t be undone before it acts, and every call it makes is on the record under your name. It works the same whether you run the whole company here or only sync your jobs in and run a few workflows.

That is how the work grows faster than the overhead. Each year agents can take on more of the office’s routine work, always through your SOPs and under your permissions, so the crew you have carries more of the load and the cost of running the company stops climbing with every new account.

What agents change → Open platform, your data →

Courier, logistics and hotshot

Couriers finally get software built for them

Local and regional couriers have been stuck between trades apps built for four long calls a day and logistics systems built for parcel hubs. ServiceProof runs the day a courier actually has: eighty quick stops, the same rounds twice a week, a bag that has to be accounted for at every hand-off, and a customer who wants proof before the day is over.

Booked on your own website

Clients book a pickup and a drop-off on your site, and it lands on the board as one job with two legs.

Routes that re-plan as the day changes

Every driver’s stops come in driving order with real drive times, and a pickup that drops in mid-day goes where it costs the least.

Custody of every bag

The driver scans the bank’s bag, then the collection bag it rides in, and at the drop scans each one out or hands the lot over for a signature.

Works with no signal

The driver’s phone keeps the whole day and holds every scan, photo and signature until it finds a signal again.

Your customer watches it move

A track-my-pickup map, a lookup on your website by job number or PO, and texts when the driver is on the way, arrives, leaves and delivers.

One proof a day, not ninety

The bank gets one document at the end of the day with every stop, who did it, when, and every photo and signature.

Priced like a courier

Quotes by vehicle class, distance and time, with fuel surcharges that follow the diesel index for your region.

Skip a stop once, or for good

When a client closes for a holiday, turn the stop off just this once or pause it until they’re back, and the record says why.

A courier day on the dispatch board: seven drivers each with their own lane, and the unassigned and parts queues as columns beside them.

A proof of the day document for a bank: eight stops, eight finished, eight with proof, none without, thirty-four answers - each stop with who did it, when they arrived and finished, and every answer with its coordinates.

Way Delivery, with forty cars and box trucks running bank deposits twice a week, is moving its whole operation onto ServiceProof.

Courier on ServiceProof → Routes and day planning →

From a forty-vehicle fleet down to one van

One platform, speaking each trade’s own language. A courier fleet, a plumbing shop with two departments, an HVAC company with rooftop PMs, a marina and a one-person appliance repair business all run the same app, and it is priced per tech, so a one-van shop pays for one.

Courier and logistics

Way Delivery. Forty cars and box trucks running bank deposits twice a week, with chain of custody on every bag.

Plumbing

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

Heating and cooling

Rooftop PMs on agreements with a window to move them in, and what the tech finds on the roof turned into a quote the same day.

Commercial electrical

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

Marine

Tarvin Marine. The thing being serviced moves, so nothing assumes a fixed address.

Appliance repair

One owner, one van. You’re the dispatcher, the tech and the bookkeeper, so let the assistant take two of those jobs off your hands.

Charlie’s Plumbing runs on the app today, and Way Delivery is moving its courier operation onto it. Schoolfield and Tarvin are businesses the platform is being built around, named for their real constraints rather than as references.

Find your trade →

A wingman in every tech’s ear

On a hot roof or under a sink, nobody should be thumbing through a phone. Wingman reads the checklist into any Bluetooth earpiece, listens to the answer, and fills a dozen steps from one sentence, each checked exactly as a typed answer would be.

Drivers get the same help with their day. Start of day, on my way, the pickup, the bank drop and end of day are read to them and answered out loud, so nobody is typing at a red light.

A photo you can’t take with a gauge in each hand is remembered rather than skipped, and the job won’t close until it has been taken. Twenty minutes of paperwork becomes two, done on the drive to the next call.

And none of it needs a signal. The whole day lives on the phone, so in a basement, a crawlspace or a dead spot on a farm road every answer, photo and status change is saved where it was made, then sent by itself, exactly once and with the real time, when the bars come back. How the app works offline →

The Wingman client, idle and ready: 'Say hey wingman any time to start talking, hands-free - or hold (or tap) the button. Say a command - my jobs, todo, menu - or answer the step it reads to you. Say over to send what you've said right away, faster or slower to tune my voice.' A What's owed? control sits in the top bar, and a box to type instead of talk sits above the big HOLD OR TAP TO TALK button.

Meet Wingman → The field app →

Wingman knows the code

Ask the code, not a chatbot

A chatbot guesses, and a guess fails inspection. Wingman’s AI does one thing: it reads the question the way a tradesperson actually asks it and writes it as a formula. Our engine does everything that has to be exact. It looks up the code value for the job’s jurisdiction, does the math, shows its work and cites the section, and when a question doesn’t read cleanly it asks the tech rather than guessing.

It runs on the phone with no internet at all, in a basement, a crawlspace or a hot attic, because the model is our own, built from scratch and small enough to fit in 2 MB. It learned only from the code itself and the way tradespeople talk, never from another AI’s answers.

“is 315° over the limit for a T&P”

→ check 315 <= max temperature(relief_valve)

Not compliant. You have 315 °F; the relief valve maximum temperature is 210 °F.
“um: is 7/16 inch the minimum supply line on a standard bathtub”

→ check 7/16 >= min supply_size(standard_bathtub)

Not compliant. You have 7/16 inch; the minimum supply pipe size is 1/2 inch.
“remind me, which kind for a pop-off”

→ lookup type(relief_valve)

An approved, self-closing (levered) pressure and temperature relief valve … conforming to ANSI Z21.22.
“How much drop over 86 feet at 1/8 per foot”

→ compute 1/8 in/ft * 86 ft

10 3/4 inches of fall.
“hey – what size main at 1/4 inch per foot for 311 fixture units”

→ size building_drain[slope 1/4] for 311 dfu

5 inches (carries up to 480 DFU).
“12 service sinks and 1 vanity sink – how many dfu all together”

→ compute 12 * drain_load(service_sinks) + 1 * drain_load(vanity_sink)

12 × 2 DFU (service sink) + 1 × 1 DFU (lavatory) = 25 DFU.
“question for you – only got 2/32 on the tire, too worn?”

→ check 2/32 >= min tread_depth(tire)

Compliant. You have 2/32 inch; the minimum tread depth is 2/32 inch.
“who won the baseball game tonight”

→ none

Declined: not a code question.

Real questions, word for word, with the formula Wingman read and the answer the engine worked out.

Your experts teach it with a spreadsheet. Every formula lives in a workbook beside the ways people ask for it, so a master plumber can hand back a spreadsheet and the model learns from it, with no programmer in the middle. That is how it goes from the plumbing code and the vehicle inspection to electrical, HVAC and every other trade.

Bring us your trade’s code → How Wingman reads the code →

An office that runs on your SOPs

Write a procedure once and publish it, and it becomes how the work is done, at a desk or in the truck, and every time somebody walks it the run becomes the proof you get paid against. Every column on the board is somebody’s queue: Parts Ordered and Estimate Review are columns too, and a job that lands in one starts that team’s checklist.

The technician finishes

The visit needs a part, so the job moves to the Parts Ordered column.
The parts counter takes over

Their checklist starts by itself, and the purchase order goes out.
The parts arrive

They are received against that PO and onto the truck they belong to.
The job goes back out

It moves to a technician, and the return visit starts its own checklist.

Nobody has to call anybody, and nothing waits on one dispatcher’s memory. Rules and events are data rather than code, your assistant can work every queue the way your team does, and a step you lock stays locked for the screen, the API and any AI alike. That is how you scale the crew you already have.

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 the office runs on SOPs → Rules and events →

One rule. One quote. Same day.

Every service company loses money between “the tech noticed something” and “the customer got a quote.” Here is one job crossing that gap on a rule instead of a phone call, from the find to the commission on the technician’s check.

The tech’s baseline asks them to find 4 a week

Blueprint · Plan

The business sets it on the technician’s scorecard — four finds a week is the example — and each technician can open their own card and see it, with its weight beside it.
A PM comes due and the tech runs Found on PM

Business · Execute Bid · Sell

On the visit the agreement generated: photos, what is failing, what it will take, a rough price on the phone — and the find is stamped with their name the moment they raise it.
A rule fires and the estimator’s queue lights up

Bid · Sell

The find is its own job in the Estimate queue, and a rule you set once, as data, starts the estimator’s review on it. Nobody had to route it or remember it.
The quote is sent and the customer approves

Bid · Sell

Priced from your rate cards, sent under your letterhead, kept exactly as it was sent. The yes moves the job to the dispatcher — same job, same number.
The work is invoiced and paid in full

Billing · Collect

The accepted quote becomes the invoice, with only the lines they took. The payment that brings it to zero marks it paid in full.
Commission lands on the tech’s check and paycard

Betterment · Improve

Earned on that paid invoice by the finder, the estimator and the crew, each on their own plan. And the week’s finds are scored against the baseline, which is kept or adjusted.

…and back to the baseline — set it, execute to it, collect, analyze the variance, adjust, repeat.

BlueprintPlanStep 1 BusinessExecuteStep 2 BidSellSteps 2–4 BillingCollectStep 5 BettermentImproveStep 6 1 Set the baseline 2 Execute to it 3 Collect the data 4 Analyze the variance 5 Adjust the baseline — 6 repeat

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.

The whole flow, step by step → How commission is earned →

One platform, all the way to the books

Working screens with real data in them, not a roadmap. Everything a field service company runs on is one product here, rather than six bought at different times and never quite connected.

The field app

Jobs, the clock, the checklist, photos and signatures, plus each tech’s own numbers and paycard.

The dispatch board

Unlimited saved boards, a lane per technician or driver, and queues as columns.

Service agreements

A quarterly PM and a twice-weekly bank run as one commitment, with a warning before a breach.

Routes and day planning

Each driver’s stops in order, with the drive time between them.

Purchasing and van stock

POs raised at the supply house on a phone and received onto the right truck.

Estimates and invoices

An accepted quote becomes the invoice, priced from your rate cards.

Proof of service

One job or a customer’s whole day as one document, hashed when it is sent.

Finance and the books

A ledger by zone and department, payroll, commission and sales tax, exported to QuickBooks and the rest.

The portal home screen: today counted on every saved board, the queues that are waiting, and the service commitments coming due.

Move in all at once, or a step at a time

Move the whole company over in one go, or plug us into the system you run today and step across one crew at a time. Either way you end up on the same platform, and neither one is a trial.

Adopt — make it your system

Customers, sites, the board, agreements, routes, purchasing, estimating and billing, plus the books: a general ledger, payroll, payables, commission and sales tax, with every export your accountant needs. Your customers and sites come across with you.

What the platform does →

The books, and every export →

Step in — start beside what you run

Already on ServiceTitan, FieldEdge, BuildOps or an on-premise ERP you’ve run for twenty years? Keep it for now. Jobs arrive by webhook, API or batch load, our workflows, rules, events and estimating run on them, and the proof goes back to your system. Then move the next piece over whenever you’re ready.

How stepping in works →

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

Starting beside what you have is a Tuesday. Every step after that moves a little more of the company onto one platform, until the old system is just somewhere you used to look things up.

Meet the baseline. Not more. Not less.

The method behind the software

Every function in a service business has a standard: how long a PM takes, how many finds a tech makes in a week, how fast an invoice goes out. Balance to Baseline gives each one a number, and ServiceProof measures the work against it, job by job, and tells you when a target itself is wrong. Everyone sees their own numbers first.

Kirk E. Barrett has been refining the framework since 2003. The book, five workbooks with forty-four worksheets and the audiobook are all free, with no form and no email address.

Read about the framework → Listen now · 118 minutes

The whole pitch, in one line

Take the driver’s seat

The modern way to scale a field service company: dispatch, the field, the office and the books on one platform that runs lean today, with an assistant that will run any of it while you drive and agents that take on more of the routine work every year. Move everything over, or start beside the system you have with one crew for one month, at $0.25 a job workflow or $75 per tech per month, no term.

See it on your own jobs Pricing →

Run your whole company from the driver’s seat.