Business process mapping: how to map a process in an afternoon (and spot what to automate)

Business process mapping means drawing out, step by step, how a piece of work moves through your business - who does what, in what order, and where it sits waiting. For a 10 to 100-person firm, an honest map of one process (enquiry to paid invoice, say) usually shows the retyping, the waiting and the one person everything queues behind within an afternoon. Once you can see those you can sort them out, and quite often automate them.

A business process is any job your firm does over and over with a clear start and end - turning an enquiry into a quote, getting a new starter set up, closing the month. Mapping it means drawing that job out as a sequence of steps, so the decisions and hand-offs are visible.

What you end up with is a process map: boxes for steps, diamonds for decisions, arrows for the order. A good one fits on a page and shows what kicks the work off, what happens in what order, who does each step and where it ends.

A flowchart is the drawing style, and a workflow chart usually means the same thing as a process map. What matters is mapping the process as it really runs on a normal Tuesday, rather than how it was meant to run.

In a growing firm most processes were never designed. They grew one workaround at a time, and nobody can see the whole thing any more. You'll probably recognise the result:

• Double-handling. The same job touched twice because two people each assume the other hasn't done it.
• Re-keying. Customer and job details typed into a spreadsheet, then a pricing workbook, then Xero.
• Waiting. Work sitting in an inbox for days because the next step relies on someone noticing it.
• The bottleneck person. The owner, or one estimator, who has to approve, price or check everything, so the whole process runs at their pace.

In a 2026 survey of 1,000 UK SME owners by American Express and Small Business Saturday UK, owners estimated they spend an average of 11 hours a week on admin and finance tasks, and only about half that on sales and business development (Startups Magazine, July 2026). A map won't save that time on its own. It shows exactly where the time goes, which is the step before fixing anything.

You don't need software or a consultant to start - just an afternoon, a whiteboard and the people who actually do the work.

1. Pick one process and name its start and end. "Enquiry received" to "invoice paid" is a good size. "Operations" is far too big.
2. Get the people who do it in the room. The owner's version and the office's version are rarely the same thing.
3. Walk one real, recent job through it. Real examples bring out the workarounds general descriptions skip.
4. Write each step as verb plus object. "Retype job into Xero" rather than "Accounts". Note who does it and which system or file it happens in.
5. Add the decisions and loops. Approvals, rework, "no reply", "overdue". The loops are usually where the time goes.
6. Mark the pain. Flag every step where information gets retyped, where work waits for a person, and where only one person can do it.
7. Check it with someone who wasn't there. If they can follow it, it's clear enough to improve.

Map today's process first, warts and all, rather than the ideal version. The gap between the two is the whole point.

For a small business, two formats cover pretty much everything:

• A basic flowchart. Steps and decisions in order, top to bottom. Start here - it's quick and anyone can read it.
• A swimlane map. The same flowchart split into lanes, one per person or team. Every arrow that crosses a lane is a hand-off, and hand-offs are where work waits and details get retyped.

You might also come across SIPOC (a one-page summary of suppliers, inputs, process, outputs and customers, handy for agreeing scope) and value stream maps (a lean manufacturing tool that times each step and the waits in between). You don't need either for a first map.

Here's a typical enquiry-to-payment process in a small contractor or service firm, written in Mermaid, a plain-text way of describing a flowchart (more on why below). Even as text it reads line by line - each arrow leads to the next step, and the curly brackets are decisions.

flowchart TD
    A[Enquiry arrives by email or phone] --> B[Office logs it in a spreadsheet]
    B --> C[Estimator retypes the details into the pricing workbook]
    C --> D{Owner checks the price}
    D -- Changes --> C
    D -- Approved --> E[Quote typed up in Word and emailed]
    E --> F{Customer accepts?}
    F -- No reply --> G[Someone remembers to chase the quote]
    G --> F
    F -- Accepted --> H[Job details retyped onto a job sheet]
    H --> I[Job done and signed off on site]
    I --> J[Office retypes the job and price into a Xero invoice]
    J --> K{Paid on time?}
    K -- Overdue --> L[Owner chases payment by phone]
    L --> K
    K -- Paid --> M[Job closed]
    classDef retype fill:#fde2d0,stroke:#F66B0E
    classDef wait fill:#fff3c4,stroke:#c99a00
    class C,H,J retype
    class D,G,L wait

View this map as a flowchart in MermaidView, a free online Mermaid editor that runs in your browser with no sign-up. You can edit the text there and watch the diagram change.

Read the map and the problems are hard to miss:

• The same details are typed three times - into the pricing workbook, onto the job sheet and into the Xero invoice. Every retype costs time and invites mistakes.
• Three loops wait on a person - the owner's price check, chasing a quote that's gone quiet and chasing an overdue invoice. Nothing prompts the chasing. It happens when someone remembers.
• The owner sits in two of those loops. When they're on site or on holiday, quoting and getting paid both slow down.

A whiteboard is fine for the workshop. The trouble comes afterwards - the photo goes into a folder, the Visio file needs Visio, and six months on nobody's updated either. Mermaid gets round that by making the map text that renders as a diagram, so the same map is both readable text and a flowchart.

• No special software. It's just text, so it can live in a document, an email, a wiki page or a ticket. Anyone can change a step by editing a line.
• It renders in tools you may already use. Paste it into MermaidView to see the flowchart and export it as an image. GitHub, Notion (in a code block set to Mermaid) and Obsidian also draw Mermaid diagrams straight from the text.
• AI assistants can work with it. ChatGPT, Claude and Microsoft Copilot all read and write Mermaid. Describe your process in plain words and ask for a Mermaid flowchart, and you'll get a first draft to correct. Or paste your map in and ask where the retyping and waiting are. Treat the answer as a second opinion rather than a verdict (the assistant only knows what the map tells it).

To go further, our free guide covers connecting ChatGPT, Claude or Copilot to your business systems, including which plan you need and what happens to your data (enter your name and work email to open it).

This is where a map earns its keep. Every step falls into one of three groups: judgement, moving information from one place to another, or waiting for someone to remember. Software can usually take the last two. A clear map is effectively the spec for automating the process, because it already says what goes in, what comes out and what happens in between.

Applied to the example above:

• The enquiry goes into a quoting tool once, so nobody retypes it.
• Pricing rules move out of one person's workbook, so anyone on the team can produce a quote and the owner only checks the exceptions.
• When a quote goes quiet, a reminder gets drafted for someone to approve and send.
• An accepted quote becomes the job sheet and, once the job's signed off, the Xero invoice, without anyone typing it again.
• Overdue invoices trigger a polite chaser in your own words, with a person approving it before it goes out.

That's the work we do at Streamlined Analytics. We take your map (or your description of how a job runs), find the steps worth automating, and build software that connects them so the process runs itself, with your team approving anything that goes to a customer. Have a look at what we automate for the jobs that come up most.

That's a UK specialist supplier whose quoting we moved out of one estimator's workbook. It's one client's result rather than a promise, and yours will depend on your process.

Our builds are fixed price, from £3,000 plus VAT, agreed before we start and quoted in stages. Optional care plans start at £250 a month, and you own what we build. The details are on our pricing page. If your process is quoting, you can try the sample quoting tool first - no call, no sign-up.

When automation isn't the answer: if a step genuinely needs judgement every time, or a process only runs a few times a year, mapping it and tidying it up by hand is often enough. We'll say so.

Pick the process that touches money (usually quoting or invoicing) and map it this week using the steps above. Then, if it's of interest, book a free 30-minute review. Send us your process map, or just describe how the job runs, and we'll show you what could be automated and roughly what it would cost, even if the answer is "leave it as it is".

If your bottleneck is reporting, see how to automate your monthly Excel reports. If you're weighing up outside help, have a read of what an AI automation agency should cost.