Business Process Mapping Examples for Small Firms
A process map is a plain list of steps showing who does what, where work waits and where someone decides. Below are six worked examples from the kind of work small professional firms do every week. Copy one, change it to match how your firm really works, and you'll see where the time goes.
How to read these maps
Each map runs top to bottom. Solid boxes are ordinary steps. Teal boxes are where a person decides or reviews. Dashed boxes are repetitive steps that are good candidates for automation. Gold boxes are decision points. All six examples are hypothetical and describe no real firm.
1. Client intake (law, accounting, any service firm)
The usual problem: Enquiries arrive through a web form, email and phone, and details get retyped two or three times before anyone decides whether to take the work.
Hypothetical example: process map
- Enquiry arrives (form, email, phone)
- Details captured into one intake record
- Matter or job type suggested
- Conflict or fit check
- Take it on?No: polite decline drafted for review
- Owner or partner approves
- Engagement letter drafted from template
- Reviewed and sent
- Client file and folders created
Where AI fits: Capture, sorting and the first draft. The fit decision and the engagement terms stay with a person.
2. Invoice approval
The usual problem: Supplier invoices come in by email, someone keys them in, and approvals sit in someone's inbox.
Hypothetical example: process map
- Invoice arrives in shared inbox
- Details read and bill drafted
- Coding and job suggested
- Matches PO or contract?No: flagged with a reason for review
- Approver signs off
- Posted to the accounting system
- Payment released by a named person
Where AI fits: Reading, coding suggestions and chasing approvals. Approval and payment stay human. More on this in AI for accounting firms.
3. Proposal or fee letter
The usual problem: Each proposal starts from the last one, so old scope wording and wrong names slip through, and follow-ups depend on memory.
Hypothetical example: process map
- Scoping call or brief received
- Notes turned into a scope summary
- Owner sets scope and fee
- Proposal drafted from approved template
- Owner reviews and edits
- Sent to client
- Follow-up reminder after a set number of days
- Accepted?Yes: start intake. No: note the reason
Where AI fits: Summarising notes, drafting from templates and follow-up reminders. Scope and fee are the owner's call.
4. RFI or submittal log (architecture and construction)
The usual problem: RFIs and submittals arrive across email and project portals, and a coordinator spends hours logging, routing and chasing them.
Hypothetical example: process map
- RFI or submittal received
- Logged against the project with a number and due date
- Routed to the responsible designer or consultant
- Technical review and response
- Needs clarification?Yes: question drafted back to the contractor for review
- Response approved
- Response issued and log updated
- Overdue items flagged weekly
Where AI fits: Logging, routing, reminders and status summaries. The technical answer is always a qualified person's.
5. Month-end close
The usual problem: The close lives in one person's head and a checklist that's never quite current, and missing client documents hold everything up.
Hypothetical example: process map
- Close checklist opened
- Missing documents listed and chase emails drafted
- Chasers reviewed and sent
- Bank feeds matched; unmatched items listed
- Reviewer clears exceptions
- Variance notes drafted
- Reviewer signs off the close
- Reports sent to the owner or client
Where AI fits: Chasing, matching and first-draft notes. Clearing exceptions and sign-off stay human.
6. New hire onboarding
The usual problem: Every new starter gets a slightly different first week, depending on who's free, and accounts get set up late.
Hypothetical example: process map
- Offer accepted
- Onboarding checklist created from template
- Account and equipment requests sent
- Manager confirms access levels
- Welcome pack and first-week schedule drafted
- Manager reviews
- First day
- All accounts working?No: flagged to IT and the manager
- 30-day check-in
Where AI fits: Checklists, requests and drafts. Access levels and the check-in are a manager's job.
How to map a process yourself
- Pick one process. Choose something that happens every week and annoys people. Not the whole business.
- Set the start and end. "Invoice arrives" to "invoice paid" is clearer than "accounts."
- Walk it with the person who does it. Map what actually happens, not what the procedure manual says. Watch them do it once if you can.
- Write one step per line. Use a verb and a person: "Office manager checks the PO." Sticky notes or a numbered list are enough; you don't need software.
- Mark the waits and decisions. Where does work sit in an inbox? Where does someone say yes or no? That's usually where the time goes.
- Mark what must stay human. Judgment, client advice, approvals and payments. Everything else is a candidate for simplifying or automating.
- Fix before you automate. Remove pointless steps first. Automating a messy process just makes the mess faster.
Where AI fits in a process map
Once a process is mapped, AI is usually useful in four kinds of step: reading and extracting (invoices, forms, emails), sorting and routing, drafting from a template, and reminding or chasing. It's a poor fit for steps that need professional judgment, carry legal or financial responsibility, or happen too rarely to be worth building for.
The rule we use: AI prepares and a named person decides. For more on choosing the first loop, read what to map before you hire an AI consultant, see the industry pages for law firms and accounting firms, or read how we work as an AI automation agency for small firms.
Frequently asked questions
What is business process mapping?
Writing down, step by step, how a piece of work moves through your business: who does each step, what they check, where it waits and where decisions are made.
What is a simple example of a business process map?
Invoice approval: invoice arrives, details entered, coding checked, approver signs off, invoice posted, payment released. Even that short list shows where invoices get stuck.
What tools do I need to map a process?
None to start. A whiteboard, sticky notes or a numbered list works. Diagram software helps later, when you want to share or maintain the map.
How long does it take to map one process?
For a single, well-defined process, often a focused session or two with the person who does the work. Larger processes with many handoffs take longer.
Should I map before buying AI tools?
Yes. The map tells you which steps are worth automating and which tools you already own can do it.
Want a second pair of eyes?
Tell us about one process that eats your week and we'll map it with you, including where AI fits and where it shouldn't.