Automation pricing.
Workflow scenarios, CRM setups and AI integrations, priced per unit of shipped work, with embedded engineering at $60-90/hr when you need ongoing capacity.
Priced per shipped unit.
| Offer | Price | What you get |
|---|---|---|
| Workflow scenario | from $750 each | One production automation on Make / n8n / Zapier: error handling, Slack alert on failure, daily "still works" check, documentation |
| CRM setup | $3,000-8,000 | HubSpot, GoHighLevel or Pipedrive: 3-5 right-sized pipeline stages, hand-off automation, migration, 2 team training sessions |
| AI integration | from $4,000 / use case | Discovery week first, then a production agent: lead qualification, internal Q&A, inbox triage, always with a human in the loop where stakes matter |
| Operations retainer | from $1,500/mo | Monitoring, fixes, monthly improvements and new scenarios across your stack |
| Embedded engineering | $60-90 / hr | Senior automation / CRM / AI capacity inside your team, monthly cap agreed upfront, weekly timesheet |
Every scenario is scoped in writing first, if a "simple" automation is actually three scenarios, you will know before we start, not on the invoice.
Why our automations do not rot.
Error handling by default
Every scenario ships with try/catch paths and a Slack alert on failure, silence is never success.
Daily health checks
A "still works" probe runs every day, so a quiet break is caught in hours, not weeks.
Documented and versioned
Every scenario is documented and exportable, your team can read what runs and why.
Your accounts, your keys
Everything runs in your workspaces with your API keys. Leave anytime, keep everything.
Tool-agnostic
Make for visual orchestration, n8n for self-hosting, Zapier where connectors win, native code when none fit.
Human in the loop
AI steps draft, classify and route, people approve anything customer-facing or high-stakes.
Automation in shipped systems.
Scoping automation work.
What counts as one scenario?
One trigger, one outcome, one system boundary, for example "new form lead → enriched, scored and created in the CRM with a Slack notification". If your flow branches into genuinely separate outcomes, that is scoped as separate scenarios, in writing, before we start.
Make, n8n or Zapier, and who pays for the tool?
We pick whichever your team can own after launch and we justify the choice in the scope. Tool subscriptions run on your accounts at vendor pricing, no markup.
Can we run everything ourselves afterwards?
Yes, that is the point. Documentation and a Loom walkthrough are included in every scenario; the operations retainer exists for teams that would rather we keep watch.
Get an automation quote.
Describe the manual work that drains your team. We reply with a scenario map and a fixed price per scenario.