Site index

ServiceProof

The modern ERP for field service and courier: dispatch, field app, estimating, billing, payroll and books, run by an AI assistant you talk to as you drive.

• What nobody else in field service does
• Why make ServiceProof your system
• Talk to your company on the drive in
• Couriers finally get software built for them
• From a forty-vehicle fleet down to one van
• A wingman in every tech's ear
• Ask the code, not a chatbot
• An office that runs on your SOPs
• One rule, one quote, same day
• One platform, all the way to the books
• Move in all at once, or a step at a time
• The method behind the software

Start beside your system

Start beside ServiceTitan, FieldEdge, BuildOps, Procore or Acumatica: our workflows run on its jobs and the proof goes back. Then move in a piece at a time.

• Step in, then step across
• Keep the system you already bought
• Getting the work in
• Then our rules fire
• And the proof goes back out
• Your event board
• What switching everything at once really costs
• What you get at the end of it
• What a pilot looks like

The field app

The technician's day on one screen: jobs, the clock, the workflow for each job, photos, barcode scans, signatures and readings - assembled as proof.

• Today's work
• The checklist for this job
• The time clock
• Capture: photos, scans, signatures, readings
• Multi-day and multi-tech jobs
• Notes that survive
• Contacts and directions
• Equipment on site
• Every photo, every year
• Their own numbers, in their pocket
• The story of the visit

Safety, and the culture that produces it

Start of day, end of day, break and incident procedures that belong to a person rather than a job - plus near-miss and good-catch reporting where the person who reports is never blamed. Built on the same workflow engine and evidence pipeline as the work itself.

• The day has a start and an end
• Near misses and good catches
• The no-blame rule, and why it is not softness
• A scoreboard that counts catches
• A catch becomes a procedure
• And if something does happen
• What is built today

Wingman: in your ear and on the code

Wingman reads checklists into a tech's or driver's earpiece and captures the answers, and answers code questions from the code itself, with no signal.

• Say “hey wingman.” Talk. Say “over.”
• One sentence, a dozen fields
• Ask the code, not a chatbot
• Your experts teach it with a spreadsheet
• Yes - you can defer the photos
• Four ways to run the same job
• Everything Wingman does, in one place

The office runs on SOPs

Every competitor has a field app. Nobody automates the office. Build SOPs by doing the job, route work by assignee queue, and close the estimating loop that decides whether a shop can grow.

• The SOP writes itself
• The board is a work-routing state machine
• Every column is somebody's queue
• Recurring work, PM or route
• Authoring: madlibs, not a form
• The people on every record
• Augment the office, don't replace it
• Estimating is where a shop stops scaling
• What you get at the end of it

Flows: one checklist, walked

The flagship flow, Found on PM: a baseline, a find, a quote the customer approves, an invoice paid in full and commission on the tech's check. Then how any flow is written, published and walked.

• Found on PM, start to finish
• The six steps, in full
• Write down the job you already do
• Publishing is what makes it a standard
• Then somebody walks it
• What a step is allowed to ask for
• The story of the visit
• The same engine, one floor up
• What this is not

The Balance to Baseline program

A business operating framework that puts a measurable standard on every activity in the company - five pillars, twenty-four disciplines, forty-four workbooks - and a platform that measures them on every job. Meet the baseline. Not more. Not less.

• Five pillars, twenty-four disciplines
• The technician hour problem
• The employees write the SOPs
• The loop that never stops
• The person who finds the bug is the hero
• The balanced scorecard
• One find, traced to the money
• What it looks like when it is running
• What the software already measures
• The pledges - both ways
• Take the whole thing
• How an engagement runs

Rules, events and workflows

Bind a workflow to an event as data, not code. OnAssign, OnComplete, every status a job passes through - scoped globally or to one zone, board or customer.

• Events on everything
• A binding is data, not code
• Scope decides who it applies to
• Contextually alive checklists
• Finishing hands the job on
• The lock is opt-in
• The why becomes structural

Bring your own AI

Plug Claude, ChatGPT or Copilot straight into your business and both ask it anything and tell it to do anything - from the van or from the board room. All 734 capabilities are open to it, and it works even if you only sync your jobs in and run a few workflows.

• Run the company from the driver's seat
• One capability, every door
• How an owner asks
• How a dispatcher asks
• The copilot on every screen
• What it will not do
• Scale the crew you already have
• What is real today

Proof of service

The record of the work is the product. One job, one procedure or a whole day as a single document - stored and hashed when it is sent, and honest about the stops that captured nothing.

• Three grains: a job, a run, a day
• A real one
• It shows what is missing
• The file that was sent is the record
• Why a photograph is evidence, or is not
• And it is a capability, not just a button

Recurring commitments

A quarterly rooftop PM and a twice-weekly bank run are the same object. Cadence, coverage, and a movability window that says what may be pushed and how far - before a promise is broken.

• One object, not two families
• A window, not a date
• What we owe
• Warned before the breach, not after
• Who is covered and who pays

Estimates, quotes and invoices

Courier and trade quoting: pricing profiles that cascade, weekly fuel surcharges, legs measured on the map, one-click pricing and invoices from hours worked.

• Quote a pickup and delivery in one click
• Pricing profiles that cascade
• Fuel surcharges that follow the pump
• Liftgates, wait time, cranes and permits
• The customer says yes, and the work is on the board
• Hourly work, billed from the hours actually worked
• The same engine for HVAC, plumbing and electrical
• One document, two stages
• The catalog and the supply houses
• Won, lost, and why
• The estimator's bench
• Making the PDF, and what was sent
• Your name and your logo, at the top
• Getting paid
• And the field half of it

Finance: the books, payroll and every export

All the accounting a service business runs on - a general ledger by zone and department, AR and AP aging held against the books, payables, payroll with overtime, commission and sales tax - and exports shaped for QuickBooks, Business Central, Intacct and Acumatica.

• A real general ledger
• Who owes you, and whom you owe
• From purchase order to check
• Payroll from the job clock
• Commission, earned from baselines
• Sales tax where the work was done
• Licenses and registrations
• Approved, reviewed, exported once
• Export everything, to whatever keeps your books
• Ask your books anything

The settings are the product

Zones are profit centers. Departments cut across them. A board queue is an employee row. Statuses, work codes, numbering, tax, roles and custom fields - all data, none of it a release.

• A zone is a profit center
• A queue is a person
• Every list you choose from
• Custom fields on anything
• Who may actually do what

Who runs on ServiceProof

Commercial electrical, plumbing, courier and logistics, marine, HVAC and appliance repair. One platform, different vocabulary - which is the proof the model is right.

• From CBRE to a boat in a slip
• Find your trade
• One truck, or forty
• Your techs on the app. Your subs on a text.

Open platform, your data

Every capability is a documented REST route and an MCP tool. Your files live on your own storage. No lock-in as a business strategy.

• One capability, every door
• Which is why an agent can do it
• Your files, on your storage
• Getting your data out
• And you can leave

Map boards

A map board is a saved set of filters over any dataset - sites, jobs, equipment, recurring work, route stops, who pays where. Facets that cascade, two layers at once, and a map that says what it is not showing you.

• A map board is a saved set of filters
• Any dataset, not just today's jobs
• The number narrows, which is the whole point
• Two layers at once, filtered separately
• It tells you what it is not showing you
• And this is how territory actually works

The route plan

Today, this driver, these stops, in this order. A day's execution plan with anchored stops, a released moment, per-leg drive forecasts and the provenance of the order - for a courier run or a technician stacking PMs.

• Two different things get called the route
• What a plan actually holds
• Re-order it - and the record says who did
• What the driver gets
• A route is an API object, not just a screen
• Planned by the machine, adjusted by a person

Commercial electrical

National-accounts intake, multi-state crews and big-project discipline. Keep Procore, buy the workflow seats, and hand the GC a record assembled as the work happened.

• Brokered work should not need a human to triage it
• The SOP is what makes a multi-state crew consistent
• On a Procore job, the proof is the invoice's argument

Plumbing

Charlie's Plumbing runs 40+ techs across two departments on one dispatch board. Commercial and residential, PM agreements, and the callback you win by walking in knowing.

• Two lines of business do not fit on one list
• Ask the plumbing code, not a chatbot
• The checklist in your ear, both hands on the work
• The PM is the schedule's shock absorber
• The callback you win because you walked in knowing

Courier and logistics

Courier software built the way couriers work: online booking, one job with legs, routes that re-plan, bag custody, offline phones and one proof a day.

• Why this one is a different beast
• Your clients book it on their own website
• A pickup and its drop-off are one job
• A route is a day's plan; a commitment is a promise
• Routes that re-plan as the day changes
• Skip a stop just this once, or pause it
• Chain of custody is a workflow, not a subsystem
• Every bank bag, from the door to the counter
• The checklist presses the buttons
• A wingman in the driver's ear
• The whole day works with no signal
• Your customer watches it move
• Prove Tuesday
• Where you compress the photo decides whether it is evidence
• Priced the way a courier charges
• The whole business, not just the driving

Marine service

The serviced thing moves. A boat is equipment with its own history, not an address - so last season's work is still findable when the slip changes.

• The serviced thing is not the place
• Seasonal work is recurring work
• Photos are the conversation

HVAC, appliance and the rest

There is no HVAC edition. The difference between a plumber, a locksmith, an HVAC shop and a courier is vocabulary, custom fields and checklists.

• Custom fields, because every shop is different
• Seasonal peaks are where consistency pays
• Run the rooftop PM with both hands on the unit
• Run a one-van shop from the driver's seat
• Make it your system, or start beside yours

Why switch from your ERP's mobile add-on

A typical ERP's mobile add-on runs $115-$250 per tech, with six years of no meaningful features. ServiceProof is $75 per tech, starts with one crew for a month, and you keep your system.

• The math
• You keep your system
• What switching an FSM really costs
• One crew, working in the first week

Billing and van stock

Parts and labor billed as the tech works, priced from your parts catalog, off the right truck. The invoice is built before they leave the driveway.

• Bill as you go
• Your parts, at your prices
• Labor without the math
• Van stock
• The invoice, before they leave

Purchase orders from the counter

Raise a PO at the supply house, get a real PO number on the spot, photograph the paperwork, and have purchasing know before the tech drives off.

• Raise it at the counter
• Your supply houses
• Photograph the paperwork
• Nothing walks off the job
• And the office side of it
• Purchasing finds out immediately

Create work from anywhere

Raise a dispatch, customer, location or PO from a truck. Your lead tech takes the 9pm call and puts real work in the system without waking the office.

• Fill in the sentence
• The 9pm call
• New customers and buildings
• Send it to somebody
• Who's allowed

Team chat, AI and the on-call schedule

Per-job chat rooms that pull in the whole crew, an AI that answers questions about the job, an on-call schedule, and a tap-to-call directory.

• Chat about the job
• Ask about the job
• Who's on call
• The company directory

Look up anything in your job history

Search years of job history from the truck - by customer, address, job number, phone, or a phrase buried in a note nobody remembers writing.

• Search everything
• The site's whole story
• Why it wins the callback

How the field app works

A field app built for basements, rural roads and steel buildings. It works offline, installs like an app, keeps your data yours, and opens no firewall port for an on-premise ERP.

• When there's no signal
• Your data stays yours
• No hole in your firewall
• It installs like an app
• Getting started

Pricing

$0.25 a job workflow metered, or $75 per tech per month for the whole white-labeled app, against $115-$250 per tech for a typical ERP's mobile add-on. No term - cancel at the end of any month.

• What it costs
• Where the line falls
• Why safety costs a nickel
• What you stop paying
• Your data is yours. Always.
• Buy only what you need
• The honest comparison
• Custom work

ERP Tools

A REST API over the on-premise ERP you already own, cloud hosting, Google Sheets reporting, bulk document export, and online card and ACH payments.

• The ERP API
• ERP Cloud Hosting
• Sheets reporting
• Document Exporter
• Card and ACH payments
• Connectors
• The SQL toolkit

Get started

Tell us about your shop and we'll show you ServiceProof running against your own data. A pilot is one crew, one workflow, one month.

• Talk to us
• What we need from you

Privacy Policy

What svcproof.com records: one page-view line with your IP address. No cookies, no analytics, no third-party code.

Acceptable Use Policy

Conduct prohibited for users of the ServiceProof service.

Copyright Notification

Listrak's designated DMCA agent and how to send a notification of claimed copyright infringement.

Security

How this site is served, what ServiceProof does with a contractor's business data, and how to reach us about security.

Vulnerability Disclosure Policy

How to report a security vulnerability in ServiceProof, what we will do with it, and what testing we ask you not to perform.