Systems · Fixed scope · Real proof
Four systems.
Understand the fit before
you book a call.
Each one has a fixed scope, a stated timeline and a delivery model. Where public proof is available, inspect it before you talk. Pick by the problem you have, not by the label.
Each system is scoped and quoted for your business on a discovery call, because the same system costs a different amount in a two-person firm and a fifty-person one. I take a maximum of two build clients at a time.
| AI Intake | Voice Reception | Document Engine | Governed Outbound | |
|---|---|---|---|---|
| Fixes | Enquiries sitting unanswered | Calls missed or mishandled | Documents rebuilt by hand | Outbound that is generic or ungoverned |
| You give it | Your intake channels | Your call flow and rules | Your templates and fields | Your target accounts and voice |
| It gives you | Qualified, routed enquiries | Answered calls, written up | Finished document sets | Drafted outreach awaiting approval |
| Human stays in | Escalation rules | Handover to a person | Template ownership | Approval before send |
| Typical timeline | 2 to 4 weeks | 2 to 3 weeks | 4 to 8 weeks | 3 to 6 weeks |
| Try it | Intake demo | No public demo | Document case study | Signal Hooks |
| Read the build | Demo scenario | No public proof | Legal case study | Signal Hooks case study |
| Full detail | Workflow automation | AI voice agents | Document automation | AI sales agents |
The intake link is an illustrative demonstration for a fictional firm. The document and outbound rows point to a client case study and a studio-owned product. Voice reception: Public demo currently unavailable.
Which one do I need?
- Enquiries arriving faster than anyone can answer them? Workflow automation
- Calls going to voicemail during the working day? AI voice agents
- The same document rebuilt from an old copy every time? Document automation
- Outbound that either does not go out, or should not have? AI sales agents
How an engagement runs.
Step one
Discovery call
Half an hour on the process that is costing you most. You leave knowing whether a system is worth building, what it would do, and what it would take. If the honest answer is that you do not need one, I will say so.
Step two
Scope and build
Scope, price, and timeline agreed in writing before any code is written. You see working pieces during the build, not a reveal at the end.
Step three
Run it, or own it
Take the system in-house with documentation and handover, or keep me on Integration Cover: a monthly block of 10, 20 or 40 engineering hours for changes, new integrations, and monitoring. Three-month minimum, with month one for onboarding and documentation, and any hours beyond the block agreed in advance at the tier rate.
Build engagements are fixed price, agreed in writing before the work starts. What that price is depends on your document set, your call volume, and the tools already in place, which is what the discovery call is for. Ongoing Integration Cover works differently: it is a monthly block of hours on a three-month minimum, with overflow agreed in advance at the tier rate. Complex or regulated work is scoped properly rather than guessed at.
Not sure which one, or whether you need one at all?
The systems audit maps how the work moves now and tells you what is worth automating. It is a standalone piece of work. You do not have to build anything with us afterwards.