Case study
Six warehouses, the same number of people: a fleet tyre service that outgrew its paperwork
- The problem
- The owner ran the whole business from memory: paper worksheets in a private shorthand only he understood, warehouse stock known through a notebook in one person's pocket, and cash tallied by hand at the end of every day.
- What was built
- Bookings, warehouse and stock management, cash and invoicing, customer and vehicle records, a webshop and a mobile app, and direct connections to partner systems, with each person and partner seeing only what they should — one system covering all of it.
- What changed
- Grown from one warehouse to six, with the same number of people. The owner now works around six hours a day and recently took a fortnight away with the business running without him.
The owner was the system
A vehicle tyre service looking after company car fleets ran on twenty-five years of one owner's experience, and nothing written down anywhere else. Paper worksheets carried a private shorthand — a plus, a double minus, a question mark — that meant something precise to him and nothing to anyone else. Staff couldn't learn the process, not because it was wrong, but because it had never been written down. He was in early and late through every seasonal changeover, because the business could not run without him there.
What it cost, before anyone called it a problem
That cost was easy to miss because the business was profitable throughout. It wasn't a failing business. It was a business that couldn't grow without breaking. Stock lived in a notebook in one person's pocket. Instructions were scattered across several messaging apps, so things got lost and then people argued about whose fault it was. The till was tallied by hand every night. Tyres moved between sites on paperwork that had to be filled in twice.
What changed, and the year it took
The developer who built and still runs this system was approached directly by the client. My part was the first year: working out what the system needed to be and how the business should run around it, alongside the developer building it. He was a pen-and-paper man, and capturing more detail digitally meant more work up front for a benefit he couldn't yet see — he went ahead because he trusted the developer personally. The benefits took about a year to become visible, and about two before he considered the system indispensable. That lag is worth being honest about; it wasn't instant.
What it looks like now
Six-plus years on, the system covers bookings and worksheets; warehouse stock, storage-location optimisation and barcode labelling for tyres, moved between sites on loading sheets; cash, till and invoice management, expenses, statutory tax reporting and financial reporting with inflation adjustment; partners connected directly with automated per-partner invoicing, a webshop with order and courier tracking, and a mobile app giving private customers their own history; and an internal messaging app in place of several separate ones, with each person and each partner seeing only what they should.
Partner invoicing used to take a full day to produce by hand. It's now generated and emailed on demand. The business reports its net profit has more than quadrupled over the period.
The owner now works around six hours a day, on customer relationships and the harder cases, and recently took a two-week trip with the business running without him.
If one person holds the process in their head in your business too, the Admin Automation Audit is where I'd start, or work out what the same patterns cost first.
Recognise this in your business?
Tell me which task takes the most time, and we'll see whether it's worth fixing.
Book a free 20-minute call