Sized builds, priced after proof.
Pick the scope, not the loose parts. Every package is the same connected engine, just more modules and reach. Final pricing follows the founding diagnostic.
Sized builds, after proof.
Pick the scope, not the loose parts. Every package is the same connected engine - just more modules and reach.
Starter Build
Get inquiries owned and followed up.
- Intake & ATS/CRM update
- Required field check
- Owner assignment
- Team alert
- Basic follow-up task
Growth Build
Most popularAdd AI drafts and stale-inquiry logic.
- Everything in Starter
- AI response drafts (human-approved)
- Stale-inquiry alerts
- Richer follow-up logic
- Stronger logs
Scale Build
A multi-workflow operations system.
- Everything in Growth
- Multi-workflow across intake & follow-up
- Handoff & reporting
- Operations dashboards
- Connector layer per system
Final pricing depends on workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. Timelines begin only after Access Lock is complete.
Exactly which modules each build ships.
Every tier runs the same connected route - bigger builds switch on more stations. Nothing here is a bolt-on; the order is the dependency chain.
Fixed scope, formal handover, optional support.
Every build follows the same shape: scoped after the diagnostic, clocked from Access Lock, closed with a formal handover. No open-ended retainer disguised as a project.
Starts at Access Lock, never at contract signature. Starter lands in 10 business days; Growth in 2-3 weeks; Scale in 4-6 weeks.
The founding diagnostic produces the scope, timeline, and price range. You approve the number before the build starts - no surprise line items mid-project.
Runbook, workflow map, known limitations, and named responsibilities - reviewed together in one session. The build phase closes formally.
The workflows run in your accounts on your tools. Walk away after handover and everything keeps working - and stays yours.
The optional Managed Plan adds hour-capped support, monitoring, and change requests on a monthly basis. It is not required to keep the system running.
In-build changes go through the UAT punch list. Post-handover changes run through the Managed Plan or a scoped mini-build.
Final pricing depends on workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. Timelines begin only after Access Lock is complete.
Common questions.
Straight answers on scope, data, and how the work runs. Still unsure? A fit call sorts it fast.
Book a Workflow Fit CallAfter Access Lock is complete - once access, test data, routing rules, and owners are confirmed.
Workflow complexity, ATS/CRM access, connector availability, data quality, AI involvement, module count, and support needs. The founding diagnostic pins the number before you commit.
No. The build ends formally at Handover with a runbook and workflow map. The Managed Plan is an optional monthly, hour-capped add-on for monitoring and change requests.
Yes - that’s the point of the tiers. Starter, Growth, and Scale are the same engine at different reach, so upgrading adds modules without rebuilding what you have.
Get a build scope and price.
Book a workflow fit call. We look at how inquiries move from form and inbox to an owner and a follow-up, and where work is leaking today.
Book a Workflow Fit Call