Fixed price. Agreed upfront. No surprises.
Every build gets scoped before any money changes hands. You'll know exactly what you're getting, what it costs and how long it takes before you commit.
Pick a starting point.
These are starting shapes, not tiers. Your build gets its own scope and its own price.
Single agent
One focused agent for one leak, like missed calls or quote follow-up.
- Workflow mapping call
- One custom AI agent
- Human escalation path
- Hand-off & walkthrough
Agent + workflows
Most commonAn agent wired into your CRM, calendar and invoicing so the whole chain runs.
- Everything in single agent
- 2–3 tool integrations
- Automation workflows
- Reporting digest
Custom system
Multiple agents and pipelines across calls, leads, jobs and reviews.
- Multi-agent setup
- Custom routing logic
- Full job-to-invoice pipeline
- Optional monthly retainer
These are starting points, not fixed packages. Your final fixed price depends on scope: how many agents and workflows, which tools we connect, and how custom the logic is. You get the exact number in writing before any work starts.
There's no subscription. Running costs like phone minutes, SMS, AI usage and hosting are billed by the providers and passed through at cost, with no markup.
Three things decide the price.
What's being built. A single call agent is a different job from a pipeline that routes leads, updates your CRM and sends follow-ups.
What it connects to: your phone system, booking software, CRM and invoicing. More integrations means more wiring.
How custom the logic is. A reminder sequence is simpler than an agent that qualifies leads and routes emergencies differently at weekends.
What about after launch?
The build is a one-time price. There's no subscription.
After launch there are small running costs, like phone minutes, API usage and hosting, which depend on volume. They're passed through at cost, not marked up.
If you want someone to monitor, tune and extend the system over time, there's an optional monthly retainer. It's never the opening pitch. It only makes sense once the build is running and you've seen the value.