Example
Workflow map example: from quote request to paid invoice
This is the kind of map our assessment produces, drawn for a fictional 14-person renovation company. Every step shows who does it, where, how often, how long it takes, the evidence behind it, and whether it should be automated, assisted or kept human.
The workflow at a glance
13steps across 4 people
45 hof work a week in this workflow
5 · 5 · 3automate · assist · human
15–19 ha week that could come back
Every step, with its evidence
Open a step to see its trigger, inputs, output, the evidence it was built from, and what we would propose.
-
Log a new enquiry Automate
- Trigger
- A customer emails, fills in the website form or calls
- System
- Email, website form, phone → Leads 2026.xlsx
- Inputs
- Name, address, job description, photos if sent
- Output
- A row in the leads spreadsheet
- Frequency and time
- 25 a week × 5 min = 2.1 h/week
- Checkpoint
- Auto
- Evidence
- Email patternAbout 25 enquiry emails and form notifications a week, all landing in the office inbox
FileLeads 2026.xlsx edited most weekdays - Exceptions
- Phone enquiries are typed in by hand, often at the end of the day.
- Proposed
- Email and form enquiries go straight into the job tracker. Karen only types in phone calls.
-
Book the site visit Assist
- Trigger
- An enquiry worth a visit
- System
- Email, phone, Google Calendar
- Inputs
- Tom's calendar, the customer's availability
- Output
- A calendar event with the address and notes
- Frequency and time
- 15 a week × 10 min = 2.5 h/week
- Checkpoint
- Approve
- Evidence
- Conversation"I call everyone back the same day, but booking the visit usually takes two or three emails."
- Exceptions
- Urgent jobs such as leaks skip the queue.
- Proposed
- AI drafts the reply with Tom's open slots. Karen approves and sends it.
-
Visit the site and measure Human
- Trigger
- A booked visit
- System
- On site, phone camera
- Inputs
- Address and customer notes
- Output
- Measurements on paper, photos on Tom's phone
- Frequency and time
- 12 a week × 60 min = 12 h/week
- Checkpoint
- Human task
- Evidence
- Calendar10 to 14 site visits a week on Tom's calendar
- Exceptions
- Large jobs need a second visit.
- Proposed
- Stays human. The value is Tom's eye on site.
-
Type measurements and photos into the estimate Automate
- Trigger
- Back at the office after visits
- System
- Excel: Estimate template v7.xlsx
- Inputs
- Paper notes, phone photos
- Output
- A filled-in estimate spreadsheet
- Frequency and time
- 12 a week × 20 min = 4 h/week
- Checkpoint
- Auto
- Evidence
- Usage dataThe estimate template is opened about 12 times a week, mostly after 4 pm
Conversation"I do my estimates in the evening from my notes." - Exceptions
- Notes are sometimes incomplete and need a call to the customer.
- Proposed
- A short form on the phone during the visit fills the template, and photos file themselves to the job.
-
Request supplier prices Assist
- Trigger
- A materials list for a job
- System
- Email to three suppliers
- Inputs
- Quantities from the estimate
- Output
- Three price replies, compared by hand
- Frequency and time
- 8 a week × 25 min = 3.3 h/week
- Checkpoint
- Approve
- Evidence
- Email patternPrice requests go to the same three suppliers, usually on Tuesdays
- Exceptions
- Special-order items go to a fourth supplier.
- Proposed
- AI drafts the requests from the quantities and lines up the replies in one table. Tom approves the requests and picks the supplier.
-
Price the job Human
- Trigger
- Estimate and supplier prices in hand
- System
- Excel
- Inputs
- Quantities, supplier prices, labour rates
- Output
- A total and a margin
- Frequency and time
- 12 a week × 30 min = 6 h/week
- Checkpoint
- Human task
- Evidence
- Conversation"Margin depends on the customer, the access and how busy we are."
- Exceptions
- Repeat customers get a different rate.
- Proposed
- Stays human. The spreadsheet already does the arithmetic; the judgment is Tom's.
-
Build the quote document Automate
- Trigger
- The job is priced
- System
- Word template → PDF
- Inputs
- Priced estimate, scope wording from past quotes
- Output
- A branded PDF quote
- Frequency and time
- 12 a week × 25 min = 5 h/week
- Checkpoint
- Auto
- Evidence
- FileQuote template.docx copied about 12 times a week; scope paragraphs pasted from older quotes
- Exceptions
- Unusual scopes need new wording.
- Proposed
- The PDF is generated from the priced estimate and a library of standard scope wording. Nothing is sent from this step.
-
Review and send the quote Human
- Trigger
- A quote PDF is ready
- System
- Inputs
- Quote and estimate
- Output
- The quote sent to the customer
- Frequency and time
- 12 a week × 10 min = 2 h/week
- Checkpoint
- Approve
- Evidence
- Conversation"I look at every quote before it goes out. Most take a couple of minutes."
- Exceptions
- Maria is away one week in six; Tom sends without review.
- Proposed
- Stays human: prices always need sign-off. The review gets faster because the quote arrives complete.
-
Follow up on open quotes Assist
- Trigger
- No reply three days after sending
- System
- Email, phone
- Inputs
- The quote and the email thread
- Output
- A follow-up email or call
- Frequency and time
- 20 a week × 6 min = 2 h/week
- Checkpoint
- Approve
- Evidence
- Conversation"I mean to follow up on every quote. Honestly, about half get one."
Email patternFewer than half of sent quotes have a later message in the same thread - Exceptions
- Large jobs get a call from Maria instead.
- Proposed
- AI drafts each follow-up from the thread at day 3 and day 10. Karen approves them in one batch. Drafts stop as soon as the customer replies.
-
Turn an accepted quote into a job Automate
- Trigger
- The customer accepts
- System
- Spreadsheet, QuickBooks Online
- Inputs
- Signed quote, deposit terms
- Output
- Customer and job created in QuickBooks; row moved to the jobs sheet
- Frequency and time
- 5 a week × 15 min = 1.3 h/week
- Checkpoint
- Notify
- Evidence
- Usage dataQuickBooks Online and the leads spreadsheet are open together on these days
- Exceptions
- Some customers accept by phone.
- Proposed
- The customer, the job and a draft deposit invoice are created from the accepted quote. Karen and Maria are notified.
-
Prepare progress invoices Assist
- Trigger
- A job reaches a payment stage
- System
- QuickBooks Online
- Inputs
- Contract payment schedule, a stage update from site
- Output
- An invoice sent to the customer
- Frequency and time
- 10 a week × 15 min = 2.5 h/week
- Checkpoint
- Approve
- Evidence
- Conversation"I find out a stage is finished when someone texts me."
- Exceptions
- Change orders are billed separately.
- Proposed
- The invoice is prepared from the payment schedule when the job stage changes. Luc approves it, and Maria is notified when it goes out.
-
Chase overdue invoices Assist
- Trigger
- 7, 14 and 30 days overdue
- System
- QuickBooks Online, email
- Inputs
- Aged receivables, the invoice
- Output
- A reminder email
- Frequency and time
- 8 a week × 10 min = 1.3 h/week
- Checkpoint
- Approve
- Evidence
- FileAged receivables report exported every Friday
- Exceptions
- Disputed invoices are handled by Maria.
- Proposed
- Reminders are drafted at each stage for Luc to approve. Disputed invoices are left out automatically.
-
Record payments Automate
- Trigger
- A deposit arrives
- System
- QuickBooks Online, bank feed
- Inputs
- Bank feed, open invoices
- Output
- Invoice marked paid
- Frequency and time
- 15 a week × 4 min = 1 h/week
- Checkpoint
- Notify
- Evidence
- Usage dataBank feed matching done in one sitting on Monday mornings
- Exceptions
- Partial payments and e-transfers without a reference.
- Proposed
- Deposits are matched to invoices automatically. Anything that does not match cleanly goes to Luc.
Opportunities, ranked
Ranked by the hours each step could give back. In this example, automated steps are assumed to give back 80–90% of their time and assisted steps 40–60%, because a person still reviews the draft. A real assessment replaces these planning ranges with what the evidence shows for each step.
| # | Step | Class | Now, h/week | Back, h/week | Back, h/year |
|---|---|---|---|---|---|
| 1 | Build the quote document | Automate | 5 | 4–4.5 | 192–216 |
| 2 | Type measurements and photos into the estimate | Automate | 4 | 3.2–3.6 | 154–173 |
| 3 | Log a new enquiry | Automate | 2.1 | 1.7–1.9 | 80–90 |
| 4 | Request supplier prices | Assist | 3.3 | 1.3–2 | 64–96 |
| 5 | Book the site visit | Assist | 2.5 | 1–1.5 | 48–72 |
Hours per year use 48 working weeks.
Recommended first automation
From site visit to quote PDF (steps 4 and 7). The same information flows through both steps, so they are built together: the visit form fills the estimate, the priced estimate produces the PDF, and nothing reaches a customer until Maria approves it. Tom keeps the two steps that need him, measuring on site and setting the price.
The follow-ups (step 9) rank lower on hours, but they matter for another reason: by Karen's own account, about half of all quotes never get one.
Open questions the map does not guess
- Change orders. Tom and Maria described different ways of pricing and approving them. Flagged for Maria to decide.
- Phone enquiries. Not visible in any shared source. Karen estimates "maybe ten a week"; marked as an estimate.
- Quotes sent without review. When Maria is away, quotes go out unreviewed. Who should approve them then is unanswered.
How a map like this gets made
It starts from evidence (files, usage patterns, inbox and calendar metadata) that the business chooses to share, then short conversations to confirm and explain it. Each person checks their own steps, and the owner approves the whole map. The method is described step by step in how to find what to automate, and the service that produces it is our AI automation assessment. To run the numbers for your own team, use the ROI calculator.
Get started
Get a map of your own.
Book a free 20-minute build call. We will tell you which workflow to automate first, and send a proposal the same day.