Home › Services › Process audit & roadmap
// service
Find what is worth automating. In the right order.
"We should automate something" usually means three processes are eating the week and nobody has measured which. The audit replaces the guess with a list: each workflow, who touches it, how long it takes, what it would cost to automate and what it saves — ordered by payback.
What happens
- Interviews (1 day). 30–45 minutes with each person who touches the process — owner, ops, sales, support. I ask what they do on a Tuesday, not what the org chart says.
- Process map. Every recurring workflow as a diagram: trigger, steps, tools, hand-offs, where it breaks.
- Numbers. Hours per week per workflow, error cost, tool costs — and an estimate of build cost and monthly savings for each candidate.
- Roadmap. A phased plan: what to automate in week 1, month 1, quarter 1, with the dependencies between them.
- Review call. Walk-through of the plan; you keep the documents whether or not I build anything.
What you receive
- Process map (PDF + editable source).
- Automation candidates ranked by payback, each with a fixed-price quote.
- Tool recommendations with reasons — including "keep what you have" where that is the honest answer.
Who it is for
Teams of 3–30 people with recurring manual work across several tools — agencies, clinics, property managers, e-commerce, trades. If you have one obvious workflow to automate, skip the audit and describe it in the form; I will quote it directly.
Related work
All case studies →
Questions
We have people manually copying leads and data between tools every day. Where do we even start?
That is the most common automation win. I map your exact flow — form, CRM, messenger, spreadsheet — and connect it in 2–3 days. You see every step before I build. Fixed price, you own the result.
How much does this actually cost?
Fixed price, agreed before I write a single scenario — no hourly billing, no scope-creep charges. Simple integrations start around $150; multi-step workflows with AI or CRM logic run higher. You get the exact number on the discovery call.
I don't understand this tech stuff at all — will I be able to manage it after?
You don't need to be technical. I explain everything in plain language, hand over documentation with screenshots, and the platforms themselves are visual — drag-and-drop, not code. Most clients never touch the scenario after handoff.
Our case is pretty unusual — can you still help?
Tell me the details on the discovery call. If no-code tools can't cover an edge case, I say so honestly and we figure out a workaround — sometimes a small custom script, sometimes a different tool. I don't take projects I can't actually deliver.
Which tools are involved, what is done by hand today, how often. I reply within 24 hours with a fit/no-fit answer and, if it fits, a fixed quote.
See also