Guides
Mobile detailing software: the six jobs it must cover
Mobile detailing software for a van: the six jobs the tools must cover, how to define metrics that change decisions, and the records a field business needs.
What to take away
- Mobile detailing software has to work offline, on a phone, with wet hands. That constraint eliminates most of the market before any feature comparison starts.
- Six jobs matterbooking, routing, job records, quoting, invoicing and customer history. Everything else is optional.
- Define a metric by its formula and its data source before tracking it, or two people will compute it differently and both will be right.
- You hold customer addresses, access details and payment information. That makes security part of running a detailing business, not an IT topic.
- A measurement that cannot change a decision is a number, not a metric. Drop it.
The six jobs
Write the requirement before looking at any product.
Six jobs the tools must do
- Bookingcaptures vehicle and condition, produces a slot
- Routingturns bookings into a drivable order
- Job recordstage times, materials, photos, findings
- Quotingapplies size, condition and zone variables
- Invoicing and paymenttakes payment at the vehicle
- Customer and vehicle historywhat was done and when
Booking. Takes an enquiry, captures vehicle and condition, and produces a slot. Must handle a service area rather than a shop address.
Routing. Turns a day of bookings into a drivable order. This is the one most general service software does poorly, because it assumes the customer comes to you.
Job record. Stage times, materials, condition photographs, findings, and what was agreed on site. This is the input to pricing and to training, and it has to be capturable in a driveway rather than at a desk.
Quoting. Applies your size, condition and zone variables consistently, and produces a document the customer accepts in writing.
Invoicing and payment. Takes payment at the vehicle and chases what is on terms.
Customer and vehicle history. What was done, when, what was found, and when the maintenance interval is due. This is what turns one-off jobs into a route, and what makes a recurring maintenance package worth selling.
Constraints that eliminate most options
| Constraint | Why it bites in mobile work |
|---|---|
| Works offline | Coverage fails in garages, basements and rural stops, and the job record is captured there |
| Usable one-handed on a phone | The technician is wet, holding something, and standing outside |
| Handles photographs properly | The condition record is images, and it has to attach to the job |
| Service area rather than address | The whole operating model differs from a shopfront |
| Exports your own data | You will change tools, and the history is the asset |
The last row deserves attention before signing up for anything. A tool that cannot export job history, customer records and photographs is holding the most valuable thing your business has produced.
Constraints that eliminate most options
Constraint
- Works offline
- Coverage fails in garages and basements
- One-handed phone use
- Technician is wet and standing outside
- Handles photographs
- Condition record is images attached to job
- Service area not address
- Operating model differs from shopfront
- Exports your own data
- You will change tools; history is the asset
Why it bites
- Works offline
- One-handed phone use
- Handles photographs
- Service area not address
- Exports your own data
Metrics worth defining
Define each metric with a formula and a data source before you track it. The metrics worth naming here are contribution per occupied hour, overrun rate, drive time share, rework rate, booking to job ratio, and water per vehicle. Thresholds are yours to set from your own record, because no honest general threshold exists.
Metrics worth defining
Metric
- Contribution per occupied hour
- Price less direct costs divided by hours
- Drive time share
- Driving minutes divided by working minutes
- Overrun rate
- Jobs exceeding planned time divided by all jobs
- Rebooking rate
- First-time customers booking again within interval
- Rework visits
- Return visits divided by jobs
- Water per vehicle
- Gallons used divided by vehicles
- Days to collect
- Average days from invoice to payment
- Booking to job ratio
- Jobs divided by enquiries
Formula
- Contribution per occupied hour
- Ranking services honestly
- Drive time share
- Territory or route problem
- Overrun rate
- Whether time estimates are real
- Rebooking rate
- Whether you have a route
- Rework visits
- Truest quality measure
- Water per vehicle
- Route capacity and technique drift
- Days to collect
- Cash timing on commercial work
- Booking to job ratio
- Whether message matches buyer
What it is for
- Contribution per occupied hour
- Drive time share
- Overrun rate
- Rebooking rate
- Rework visits
- Water per vehicle
- Days to collect
- Booking to job ratio
That list is already longer than most operations act on. Pick four, run them for a season, add one only when it becomes routine.
Choose by the problem in front of you, not what is easiest to collect. Easy measures usually change nothing. If a measure never changed a price, a route, or a training priority, it is not earning its place. Dropping it costs nothing.
Water per vehicle belongs on a business measurement list. The EPA's WaterSense breakdown of vehicle washing shows how consumption divides across wash stages at fixed facilities that can reclaim.
A van cannot reclaim, so the tank sets the number of jobs between refills. That makes water an operating constraint with a direct effect on the day.
Defining a metric so two people compute it the same way
Four lines per metric
- Formulahow it is computed
- Data sourcewhere the numbers come from
- Ownerwho is accountable
- Decision it can changeif empty, do not track
The commonest failure is a metric with an ambiguous denominator. Jobs per day means something different if a rescheduled visit counts, and revenue per job means something different if a surcharge is recorded separately. Write the ambiguity out of it once.
Records the tools have to support
Whatever software you choose, it has to leave you holding records that satisfy the tax side and the operational side.
Records tools must support
Financial half
- Regulator
- IRS
- Requirement
- Clearly shows income and expenses
- Supporting documents
- Purchases, sales, payroll, assets
- Common failure
- Missing receipts
Operational half
- Regulator
- None
- Requirement
- Job times and materials
- Supporting documents
- Condition photographs and findings
- Common failure
- Lost job times; prices drift
For the financial half, the IRS describes a recordkeeping system as one that clearly shows income and expenses, with the documents supporting purchases, sales, payroll and assets. For the operational half there is no regulator, which is why job times and materials are the records most often lost, and why prices drift away from reality.
Security, because you hold more than you think
A detailing business holds customer names, home addresses, access details such as gate codes, vehicle information and payment data. That combination is worth something to somebody, and it lives on a phone that spends its day in a wet van.
Two agencies publish material aimed exactly at a business this size. NIST's small business cybersecurity quick start guides are short, practical and organized by topic. CISA's material for small and medium businesses covers the same ground with an emphasis on the basics that prevent most incidents.
The measures that matter most in a field operation are dull: multi-factor authentication on anything holding customer data, a screen lock on the working phone, and tested backups.
Add a rule for lost phones. For this trade, decide who may access gate codes and access notes, and remove access when someone leaves.
Choosing without being sold to
Write the requirement first, from the six jobs and the constraints above. Then trial rather than demonstrate: a real week of real bookings, captured in the driveway, by the person who will use it.
Three questions to ask any vendor, and to test rather than accept: what happens with no signal, what does an export contain, and what does it cost to leave.
Run the trial with a defined end date and a written decision rule, agreed before it starts. A trial with no end date becomes an adoption by default, and the switching cost then argues for staying with a tool nobody chose. Two weeks of ordinary work is usually enough, provided one of those weeks is a busy one.
Where the numbers connect to the rest of the business
Contribution per occupied hour and overrun rate feed the price derivation in the pricing and profit guide. Drive time share and overrun rate feed the route design in the operations and workflow guide. Rework rate feeds the sign-off ladder in the hiring and training guide.
Booking to job ratio feeds channel decisions in the marketing and growth guide. Water per vehicle feeds both the van build in the equipment and setup guide and the containment obligations mapped in the licensing and compliance guide.
Common questions
Do I need dedicated detailing software?
Not necessarily. What you need is the six jobs covered and the constraints met. Some operations do it with a scheduling tool, a payment app and a disciplined spreadsheet.
How many metrics should a small operation track?
Four, chosen because each can change a decision. More than that and none of them get acted on.
What if my software cannot export the data?
Treat that as a reason to change tools, and start keeping a parallel record of job times and customer history now rather than after the decision.
Is a paper job sheet acceptable?
Yes, provided it is entered somewhere it can be compared over time. A paper sheet that stays in the van is a record nobody reads.
