Scope
Defined before we start
The teardown already says what should be built, in what order, and roughly what it costs. The proposal is that document with a price against it.
Why this exists
A role opens. Someone writes a job description listing what the person will do all day.
Half of it is judgment. Half of it is moving information between systems on a schedule.
Nobody separates the two before hiring for both.
A job description is a workflow nobody wrote down.
It's the most honest document a company produces about its own operations — written by the person who actually feels the gap, listing the work in the order it happens. It just gets used for recruiting instead of for operations.
A teardown reads it the other way round.
The deliverable
Six sections. Written, not a call.
You get a document you can forward to whoever signs off — not a slide deck and not a recording of someone talking at you.
01
How the workflow runs today
Every step from trigger to completion. Who touches it, which tools, where it waits, where it gets handed off. Most companies have never seen this written down.
02
What it currently costs
Steps multiplied by frequency and minutes, against a loaded hourly rate. The problem stops being a feeling and becomes a number.
03
The automation map
Every step marked automate, augment, or keep human — each with the reason. The "keep human" calls are the ones that make the rest trustworthy.
04
What the automated version looks like
Triggers, decision logic, integration points, what happens when it fails, and what escalates to a person.
05
Build estimate
Scope, timeline and cost range — including an honest view on whether you should build it in-house instead.
06
Recommendation and sequencing
What to do first, what to leave alone, and what to revisit in six months.
Process
Three touchpoints, five days.
Day 1Intake call
Thirty minutes. You walk through the role and how the work actually happens — not how the process document says it does.
Days 2–5The teardown
We map it, cost it, and separate the mechanical from the human. Occasional follow-up questions by email.
Day 5Walkthrough
Thirty minutes on the findings. The document is yours either way, with no obligation attached to it.
If the teardown concludes nothing meaningful should be automated, you pay nothing.
Sometimes the honest answer is that a role needs a person. When that's the case, you get the document, the reasoning and the cost analysis — and no invoice.
We would rather tell you to make the hire than sell you a system you don't need. It is the only position that makes the rest of the analysis worth reading.
After the teardown
If you want it built, we build it.
The teardown is deliberately independent — it has to be, or the analysis isn't worth reading. But most people who commission one want the first flow built once they've seen what it's worth.
We do that too, and the scope comes straight out of the document you've already read. No second discovery phase, no re-explaining your business, no surprise about what's in and what's out.
Fee
Teardown comes off the build
The $750 is credited in full. You never pay twice for the same analysis.
Honesty clause
Sometimes it isn't us
If the right builder is your own team, or a specialist vendor, the teardown says so plainly — before you've spent anything with us.
Scope
What this is, and what it isn't.
What it is
- Analysis of one role or one workflow
- A written document you can forward
- An honest cost of the manual version
- A clear line between machine work and human work
- A build estimate you can take to anyone
What it isn't
- A sales call with a document attached
- Software, or a licence to anything
- A commitment to build with us — that stays your choice
- A recommendation to automate by default
- A vendor comparison or procurement exercise
Questions
Straight answers.
Who is this for?
Companies about to hire for a role that is substantially repeatable — operations, coordination, intake, CRM administration, lead follow-up, order or application processing, support triage. It works the same whether you are a software company, a property manager, a professional services firm or an e-commerce brand. The pattern matters more than the industry.
Do we have to stop the hire?
No, and often you shouldn't. Plenty of teardowns conclude that the role is worth filling and that a system should handle the parts that were quietly stealing the person's week. Knowing which parts those are before you write the job description is the point.
What do you need from us?
The job description, thirty minutes of someone's time who knows how the work really happens, and a rough sense of volumes. Nothing confidential is required, and we will not ask for system access.
Why $750?
Because it should be cheap relative to the decision it informs. A mis-scoped hire costs a year of salary. A teardown costs less than a week of one.
What if we want the build afterwards?
Then the teardown fee comes off it. But that is a separate decision made after you have read the analysis, not a condition of it. If the right builder is your own team or another vendor, the document says so.
Is this AI?
The analysis is done by a person. What it recommends may or may not involve AI — that depends entirely on the workflow, and a good number of the answers are ordinary automation, better process design, or nothing at all.
Send us the job description.
Or describe the workflow in a paragraph. We will tell you within a day whether a teardown is worth doing — and if it isn't, we will say that instead.
Calendar not loading? Open booking in a new tab.