How we work
How we map a business: follow real jobs end to end before building anything
Before we build anything, we sit with your team and follow real jobs from first contact to final invoice, workarounds included. You come away with a clear picture of how work flows and where it breaks, which is worth having even if you never build.
By Seb Lawson · 30 October 2026 · 5 min read
Before we build anything, we map how your business actually works. That means sitting with the people who do the work and following real jobs from the first enquiry to the final invoice, including the workarounds nobody ever wrote down. It’s the most important part of any project, because everything we design traces back to it. And you keep the map whether or not we build, because a clear picture of where work flows, where it stalls and where the same detail gets typed twice is worth having on its own.
We follow the work, not the org chart
The org chart tells you who reports to whom. It doesn’t tell you that every quote goes through the office manager because they’re the only one who knows the supplier discounts, or that next week’s jobs get planned in the owner’s head on the drive home.
So we pick real pieces of recent work, a handful of jobs or clients that went through the business in the last month or two, and trace each one from start to finish. Where did it begin? Who touched it next? What did they need to know, and where did they find it? Where did it wait? Where did it go wrong?
Real jobs matter because they include the awkward bits: the quote that was revised three times, the customer who paid half up front, the job that needed a permit. A process document describes how work is meant to go. Real jobs show how it actually goes.
We sit beside the people doing the work
Most of the mapping happens next to the person doing the job, watching them do it, and much less of it in a meeting room. We ask them to show us what they do, screen by screen, and to tell us where it’s annoying. It works best in person, so for clients on the island we come to you.
People are usually glad to talk about what slows them down. The office manager knows exactly which report eats Friday afternoon. The engineer knows which form gets filled in from memory in the van. Whoever does the accounts knows which invoices always come back with a query. Often nobody has asked them before, because living with it was easier.
We talk to the owner too, who tends to see the business in terms of cash and capacity. Both views matter, and the gap between them is often where the best fixes are.
Workarounds show where the tools let the team down
Every business has workarounds. They’re the informal fixes people invent when the official tools don’t quite fit: a colour code in a shared calendar, a WhatsApp group that acts as the job board, a sticky note on a monitor with the supplier account numbers.
We treat each one as evidence. A workaround marks a place where the software let the team down and someone cared enough to fix it themselves. A good system keeps whatever was clever about the workaround and removes the need for it.
The spreadsheet everyone depends on is the best record of how you work
There’s almost always one. It might be the job tracker, the price list, the client list with renewal dates, or the sheet that turns engineers’ hours into payroll. It’s been built up over years, often by one person. It has tabs nobody else understands and formulas nobody dares touch. If it broke on a Monday, the business would be struggling by Wednesday.
We treat that spreadsheet with respect, because it usually describes how the business really runs better than any software does. People built it to do the job the software couldn’t. We go through every tab, ask what each column is for, and note who updates it and when. It becomes one of the main inputs to the design.
Every retype we find is a candidate for the first fix
As we trace each job, we note every time the same information gets entered again: the customer’s name typed into the CRM, then the quote, then the job sheet, then Xero. Each retype costs a few minutes and carries a chance of a mistake. Put together, they show where joining up your tools will pay off first. There’s more on that in spreadsheets aren’t the problem, retyping is.
The map is worth having even if you never build
At the end of mapping, you have:
- A picture of how work flows through the business, from first contact to payment, drawn simply enough that anyone in the team can follow it.
- A list of the hand-offs that break, where work waits, gets lost or gets retyped, with a sense of how often each one happens.
- The workarounds and key spreadsheets written down, with who depends on each. That alone makes the business less exposed when one person is off sick or leaves.
- A recommendation on where to start, which might be a system, a small change to a tool you already own, or nothing at all for now.
A good map is useful on its own. You can use it to train a new starter, to brief your accountant, or to decide which subscription to cancel.
Nothing gets designed until the map is agreed
Our steps are map, design, build and run, and you sign off each one before the next starts. The design comes straight from the map, so every screen and every automation traces back to a real job we followed. If something in the design can’t be traced back to the map, we ask why it’s there.
This is also why mapping can’t be skipped to save money. Building has become much quicker, as we explain in why bespoke software is now within reach, but building quickly from a poor map just gets you the wrong system sooner.
Our recommendation: start with last month’s messiest job
If you want to try this yourself before talking to anyone, pick a job from last month that didn’t go smoothly. Write down every step, every person who touched it, and every place the details were typed in. You’ll learn more from that one job than from any process diagram.
If you’d like us to do it with you, book a review. In 30 minutes we’ll walk through one of your recent jobs together and show you what a full map would cover. If you’d rather start by listing your tools, build your system and bring it to the call.