Pricing
Priced by scope. Quoted before we start. No surprises after.
Every business hands off different work, so we don't publish a rate card. We publish how the pricing works, what drives the number, and what you'll never pay for.
- 01
Free First conversation
We learn how your team works and tell you what's worth automating. If nothing is, it ends there. No follow-up sequence.
- 02
Fixed fee Workflow Audit
We map how the work really happens and score every candidate task. You keep the roadmap whether or not you continue to a build.
- 03
Project fee Workflow Build
One workflow, connected to your tools, with a human check before anything goes out. The price is set once the audit tells us exactly what it needs to do.
- 04
Monthly Care plan
Monitoring, updates as your business changes, and the next workflow when you're ready. Or we hand it over and you run it yourself.
What moves the number
Three things, and nothing else.
Headcount doesn't matter. Revenue doesn't matter. The workflow's workload does.
How many distinct tasks
Answering inbox questions is one. Drafting quotes from a rate sheet is another. Each task is scoped and tested on its own.
How many systems it touches
Gmail alone is simple. Gmail, HubSpot and QuickBooks, with data moving between them, is more.
How messy the context is
Pricing in one clean spreadsheet is quick. Pricing in six people's heads takes longer to capture.
What you never pay for
The parts other agencies bill you for.
Common questions
Before you book.
Can I start with just the audit?
Yes, and most clients should. The audit is a standalone deliverable: a ranked roadmap of what to automate first, plus your business knowledge written down. It's yours whether you build with us, build with someone else, or build nothing. If you do build with us, the audit fee is credited toward it.
What if I already know what I want to automate?
Then the audit gets shorter and cheaper, or we fold it into the build. We'll still verify the workflow against how your team actually operates — the gap between “how we think it works” and “how it works” is where most automation projects die.
When do I start seeing the time back?
The build takes 2–4 weeks, and the workflow runs inside tools your team already uses, so there's no adoption ramp. Most teams feel the difference in the first week after handoff.
What tools do you integrate with?
Gmail, Outlook, HubSpot, Salesforce, Slack, Google Sheets, Notion, QuickBooks, Calendly, Zoom — and most anything with an API. If your stack is unusual, we'll confirm feasibility in the first conversation, before you spend a dollar.
What if it doesn't work?
Two safeguards. During the build: you approve the workflow against real examples from your business before handoff, and we keep tuning until it does what we agreed. After launch: the Care plan is optional and month-to-month. We also tell people up front when AI isn't the right answer; some workflows should stay human, and some just need a checklist.
Why no rate card?
Because the number depends on three things we can only see with you: how many tasks, how many systems, and how messy the context is. What we do publish is the structure, what moves the number, and what you never pay for. In the first conversation you get a real range for the audit, and the build price is fixed before anything is built.
Want a number? Start with sixty seconds.
Tick what eats your week and see what a first build would cover before you talk to anyone. A short note gets you the number.