What's the simplest way for a two-van firm to stop losing job details?
Get four things out of your head and into one place: the customer, the job, the photos and certificates attached to that job, and one shared calendar. That's the minimum, and for most two- and three-van firms it's also the maximum they need. The failure mode at this size isn't that people buy nothing — it's that they either carry everything mentally until it breaks, or they buy an enterprise system built for a thirty-van operation and abandon it within a quarter. Neither of those is necessary.
The real symptom isn't lost details
It's that you can't leave.
A firm where the owner holds the information is a firm where the owner has to be reachable on holiday, has to be rung about a job from four months ago, and can't hire because there's nothing for a new person to look at. The lost job details are annoying. The ceiling they put on the business is the actual cost.
You'll recognise the specific version of it: a customer rings about work you did last spring, and the only record is a text thread, an invoice in your accounts package and your memory of the day. You can usually reconstruct it. It takes eleven minutes and it happens twice a week.
Why it happens at exactly this size
One van doesn't need a system. Your head is genuinely sufficient and anything else is overhead.
Ten vans forces a system. It's obviously impossible without one, so someone builds it.
Two or three vans is the awkward middle. It's just about possible to run on memory, phone calls and texts — which means it never becomes urgent enough to fix, while getting slightly more expensive every month. Most firms stay in this band for years.
The second reason is scar tissue. A lot of small firms bought something once, found it was built for a company five times their size, spent two evenings on setup and quietly stopped opening it. That teaches "systems don't work here", which is the wrong conclusion from the right experience.
What you actually need
Four things. Not fourteen.
A customer record. Name, address, phone, and every job you've ever done for them. That's what makes the "you did work here last spring" call take thirty seconds.
A job record. What the job is, what was quoted, what's been done, what's outstanding. One entry per job, hung off the customer.
Photos and certificates attached to the job. Before and after photos, the EICR or the gas safety certificate, the serial number of the boiler. Not in a camera roll among four thousand other pictures — attached to the job, findable in two taps in three years' time when the customer sells the house.
One shared calendar. Where both vans are today, visible to both vans. Not "I'll ring him and tell him".
If you've got those four, you have a business someone else could run for a fortnight. That's the whole test.
What you don't need
Enterprise field service software. Asset registers, planned preventive maintenance schedules, dispatch optimisation and multi-level stock control are genuinely valuable to a facilities contractor with forty engineers. To a three-van firm they're setup work with no payoff, and they're the reason the last system failed.
A separate app per problem. One for quotes, one for certificates, one for scheduling, one for invoices, none of which talk to each other, is worse than a notebook. You've replaced a memory problem with an integration problem and made yourself the integration.
Anything that only works on a laptop. If it can't be updated from a van with poor signal, it will be a day out of date permanently and the team will stop trusting it.
To be fair about the market: there are perfectly good tools sized for this — ServiceM8, Tradify, Powered Now and others sit deliberately at the small end of the trade software market. If your only problem is the four things above and you're comfortable configuring and running it yourself, one of those may be all you need, and we'd rather tell you that than sell you something bigger.
How to actually make the change
Start with live work only. The jobs you're doing this month, not five years of history. Historical work can stay where it is and be looked up the slow way on the rare occasions it comes up.
Do it in a quiet fortnight. Not the week the boilers start failing.
Pick one rule and hold it. The one that works: if it changes what happens, it goes in the system. Chat stays in WhatsApp. Dates, prices and decisions don't.
Judge success on one thing. Can someone other than you answer a customer's question about a job? If yes, it worked. If no, the software isn't the problem.
If your problem is upstream of this — enquiries never becoming conversations — read whether an AI receptionist is any good for a small plumbing or electrical firm. If it's downstream, and the money isn't coming in, read how small trade firms get unpaid invoices paid.
Where OrderWolf fits
We're for the point where those four things aren't enough on their own — where you're spending money on leads, missing calls, quoting slower than the firm down the road, and want the whole chain built and run rather than configured by you at eleven at night. We rebuild the site to capture enquiries, run the AI receptionist, automate follow-up and invoicing, and hold it all in one CRM. Then we operate it.
With GEV, our Irish flagship client, the team recovered roughly 2.5 admin hours per person per day and the B2C close rate went from 45% to 70%, over a three-month deployment. Results from one installer — outcomes depend on your starting point and your market.
If you're a two-van firm whose only problem is that job details live in your head, start with the four things above. That's cheaper and it might be enough.
Common questions
Not sure whether you need a system or a stack?
We'll build you a free 90-day growth plan: an AI audit of how work reaches you, where information lives, and what's actually worth fixing first. If the answer is 'you don't need us yet', we'll tell you.
Get your free 90-day growth plan