How it works — the field app
The field app works where your techs actually are
Your techs work in basements, on rural roads and inside steel warehouses, which are exactly the places phones stop working. ServiceProof was built for those places: it installs like any other app, and your data stays yours.
On the hosted platform the app talks to our API directly, so read that section as true of an on-premise installation rather than as a claim about the platform. What the platform promises about your data →
When there’s no signal
Most field apps are written as though everyone has five bars. Your techs work in the exact places that isn’t true.
ServiceProof keeps the day right on the phone: the route, every stop, each job’s address, contacts, notes and equipment, and the checklists themselves. When a screen opens it paints from that copy immediately, then quietly refreshes in the background if there’s signal to refresh with. And the work itself never waits for a bar.
- Screens open instantly, even on one bar, because nothing is waiting on a server to answer.
- The job is still there in the basement — the address, the contact, the notes, the equipment, the parts catalog.
- The work keeps going. Starting a checklist, every answer and photo, a note, the stop’s status and the truck or bag taken out are all saved on the phone first and wait in an outbox.
- Sent exactly once, with the real time. When the signal comes back, everything goes by itself, in order, stamped with the moment it happened rather than the moment it got through.
- You can see what is waiting. A chip shows anything still on the phone, and one screen lists it, so nobody has to wonder whether a photo made it.
- Nothing goes blank. If a refresh fails the app keeps showing the last good version, rather than wiping the screen to show you an error.
The one thing that waits for a bar is money: billing a part to the invoice or receiving one onto the truck needs a moment of signal, and the app says so plainly rather than pretending it went through.
Painted from the phone, before the network answers.
Your data stays yours
We are not asking you to move your business into our system. There is nothing to migrate, because nothing moves.
- Your system stays exactly where it runs today, owned by you. ServiceProof never copies your whole database.
- What matters goes back into your system on the same job, and the office sees it there as it always has.
- No second record to reconcile. Beside your system, ServiceProof is deliberately not the source of truth, so there is nothing to keep in step with the real one.
- Stop using us tomorrow and your system is untouched, complete and yours, because it never lived anywhere else.
That is what augmenting means: we extend the life of what you already run instead of holding it hostage.
Your jobs, on a phone that behaves.
No hole in your firewall
If your system of record is an on-premise ERP on a server in your building, show this section to whoever looks after your network. It is the part they care about, and the part most vendors get wrong.
- Nothing dials in to your office. There is no port to open, no address to publish, nothing for anyone on the internet to find and try.
- A small piece of software on your side makes an outbound connection out — the same direction as a browser, which your firewall already allows.
- Every request rides an encrypted channel, and every one of them has to be signed in as a real person before it is answered.
- A tech only ever sees what a tech should see. The app can’t be talked into handing over your customer list.
- Your ERP’s login credentials never leave your building.
It installs like an app
A tech opens a link, taps “add to home screen,” and they’re done. It sits on the home screen and behaves like any other app on the phone.
- iPhone and Android — same app, same day.
- No app store. No waiting on a review, no Apple ID, no “ask the office for the password.”
- No device management. It works on the phone the tech already owns.
- They stay signed in. Once, not every morning.
- Updates just arrive. Nobody chases forty people to update anything.
- They pick their truck when they sign in, so van stock and pricing are right from the first tap.
A new hire is working in about ninety seconds. That matters more than it sounds when you hire in the spring.
On the home screen, like everything else.
Pick your truck. Everything else follows.
Getting started
A pilot is one crew, one workflow, one month.
| When | What happens |
|---|---|
| Day 1 | We talk. You tell us how you run — your trucks, your price levels, your labor codes, who’s allowed to create work — and which workflow to prove first. |
| Day 2–3 | We connect to your system and stand the app up against your data. You see your own customers and your own jobs, not a demo company. |
| Day 3–4 | You and a couple of your best techs run real work through it and tell us what’s wrong. We change it. |
| Rest of the month | Your crew runs real jobs on it while everyone else keeps their current app until you decide. |
An on-premise ERP we already support is connected in under a week.
- No install day. Nobody comes to your office, and nothing gets loaded onto your techs’ phones by hand.
- No contract term. Cancel at the end of any month and keep every bit of the work — it was always in your system.