Pick the thing that’s eating your week. The automation I’d build for it gets drawn, then it runs, with the work moving through it, and then you can put your own numbers against it. Below that are two demos you can operate yourself. This practice is new, so there’s no logo wall. What you get instead is the working thing.
What I’d build for that
A quiet automation that reads the document and files it
The paperwork arrives, gets read, checked against what you already have, and lands where it belongs. Nobody types anything twice.
Ready
Normally: Document arrives, then Reads it, then Matches the order, then Filed.
When it isn’t sure: Document arrives, then Reads it, then Checks it's not a repeat, then Asks you.
001Document arrives
002Reads it
003Matches the order
004Checks it's not a repeat
005Filed
006Asks you
It flags every third one here so you can watch it happen. A real run of this is nearer one in 13, and the ones it flags are the ones worth your judgement anyway.
Run log00
Nothing has run yet.
The figures land when the run finishes.
A demonstration rather than a measurement: the shape of a typical week, with illustrative figures. The hours above already have the flagged ones taken back out. Yours get worked out on the call, in writing, before you commit to anything.
Work arrives, gets read, gets checked, and lands where it belongs. Nobody is at a keyboard while any of that happens.
The dashed line is the interesting one
That's the path an item takes when the automation isn't certain. Every honest system needs one, and most demos quietly leave it out.
A person is still in the picture
The point was never to remove you. It's to make sure the only things reaching you are the ones that genuinely need a decision.
It runs whether or not anyone remembers
That's the difference between a process you wrote down once and a process that actually happens every week.
Invoice inbox → ledgerRunning
01
Email arrives
From supplies@northgate.co · attachment NG-4471.pdf · 214 KB
02
Read the document
Supplier: Northgate Supplies · Total: $1,284.00 · Terms: 30 days
03
Check it against the books
Matched purchase order #8812 · amounts agree · not a duplicate
04
File the row
Written to Ledger 2026 · row 218 · flagged for Friday's payment run
Four seconds. Nobody opened the attachment, and nobody typed the total.
A scripted walkthrough with stand-in figures, not a recording of a live run.
Every step, in order
Walkthrough
Invoice inbox → spreadsheet, untouched by human hands
A PDF arrives, gets read, checked and filed. The kind of thing that takes an afternoon, on tools most businesses are already paying for.
Northgate Plumbing · customer FAQ
Do you deliver to Riverside?
Yes. Tuesdays and Fridays, and delivery is free on orders over $200.
Answers from your own material
Demo · try it
An FAQ assistant answering from a price list
A stand-in firm with a stand-in price list, so nothing here is anyone’s real pricing. Ask it something the list doesn’t cover, because admitting that is the part worth testing.
Before / after: a quoting process
Before
25min
Enquiry email → copied into a spreadsheet → priced by hand → typed into a template → sent, if someone remembers.
Around 25 minutes each, two days to send.
After
2min
Enquiry arrives → priced from your own rate card → draft quote waiting for approval → sent with one click.
Around 2 minutes each, same day.
The honest part
These are demonstrations, not case studies.
This practice is new, so the graphs above are built from what these projects actually look like rather than from a client’s live system. The shapes are real. The figures are the shape of a typical small business’s week, not a measurement of anyone’s. Yours get worked out properly on the call, in writing, before you commit to anything. If a template would do the job, I’ll tell you that instead.