Who it's for
Small and mid-sized businesses that want a full written plan before committing to a build. It fits when more than one workflow is eating the team's week, the tools don't agree with each other, or a vendor holds accounts or data your brand should own, and you want it all on paper, priced, before you spend on fixing it.
If you already know the one workflow you want fixed, you probably don't need this. Start with the free Automation Audit instead, and go straight to a written scope for a Workflow Quick Win.
What's included
- Your workflows, tools, and data mapped end to end
- Vendor and data-ownership risks identified
- A prioritized roadmap with a fixed quote for each build
- Written plan in about 2 weeks, with read-only access
- Fee credited toward your first build if it starts within 30 days
What you get: the written plan
The diagnostic produces one document. Two samples show exactly how it is laid out: one for a fictional service company and one for a fictional online store:
- Summary. What we found, what it costs you, and what we recommend doing first.
- Stack and workflow map. The tools you run, how data moves between them, and where people re-type it by hand.
- Where time and money leak. Each manual workflow with its hours and yearly cost, worked out with the same formula as the ops cost calculator.
- Vendor and data risks. Accounts, data, and access that sit with a vendor instead of your company, and the action to fix each one.
- Prioritized roadmap. The fixes worth building, in order, each with a fixed quote and an estimated payback.
- What we don't recommend yet. The leaks with a cheaper answer than a build, so you don't pay for one you don't need.
- Next steps. How the fee is credited, and the choice to build, build with someone else, or stop there.
Want a rough number before you ask? The ops cost calculator uses the same formula as section 3, free and with no email.
Timeline and access
About 2 weeks from the kickoff call to the written plan: a 60-minute kickoff, then a 45-minute walkthrough of the finished plan.
Read-only access you grant and can revoke: a view-only staff or collaborator account, or a read-only API token. Never your passwords. We list every access we were given at the end so you can remove it. How we handle access and data is on the security page.
Price
From $2,500. Typical range $2,500–$4,000.
The fee is credited toward your first build if it starts within 30 days. Third-party software and usage charges for any build stay separate and are disclosed before you approve its scope. Every other price is on the pricing page.
How it differs from the free audit
| Free Automation Audit | Systems Diagnostic | |
|---|---|---|
| Price | Free | From $2,500 (typical range $2,500–$4,000), credited toward your first build if it starts within 30 days |
| Format | A 30-minute call, then an async look at a few real examples you send | A written document you keep |
| Time | A 30-minute call | About 2 weeks from the kickoff call to the written plan: a 60-minute kickoff, then a 45-minute walkthrough of the finished plan. |
| Access | None. Screenshots or exports you choose to send | Read-only access you grant and can revoke: a view-only staff or collaborator account, or a read-only API token. Never your passwords. We list every access we were given at the end so you can remove it. |
| Scope | One workflow or area of the business | Your workflows, tools, and data, mapped end to end |
| You leave with | Your top fixes ranked by effort and impact, and a practical next step | Vendor and data-ownership risks identified, and a prioritized roadmap with a fixed quote for each build |
| Best for | Finding out what to fix first, at no cost | Companies that want a full written plan before committing to a build |
Both lead to the same place: a written scope and fixed quote, and no build starts until you approve it. See what happens after you book.
What we need from you
- A few real examples of the work, sent when it's easy. Screenshots are fine.
- Read-only access to the tools in scope, granted by you. Never your passwords.
- About an hour and three quarters of calls: the kickoff and the walkthrough.
- Your own counts, exports, and time estimates for the workflows in question. The plan says which numbers came from where.