Five stages.Total visibility.
Every engagement runs the same sequence regardless of which discipline it starts in, and regardless of its scale. A single booking agent runs the same five stages as a group-wide deployment, because a skipped stage costs most on the engagements assumed to be simple. At each boundary you know what you received, what it cost, and whether to continue.
How we work
Five stages.
No black box.
Eight to sixteen weeks from bottleneck to deployed system, with a working demo at the end of every sprint.
Every engagement moves through the same sequence regardless of which discipline it starts in. You always know which stage you are in, what comes out of it, and what it takes off the table.
- 01
Discover
1 weekA scoping call that costs nothing. We learn the business, locate the actual bottleneck, and establish the first build worth committing to.
Output — Written scope, honest recommendation
You do not build the wrong thing
- 02
Design
1–2 weeksFlows, wireframes, and system architecture — signed off before a line of production code exists.
Output — Architecture doc, interactive prototype
You see it before the build budget is committed
- 03
Build
4–10 weeksSprints with a working demo at the end of each one. You see the product every fortnight, not once at handover.
Output — Deployed staging environment
You can redirect after any demo, not only at the end
- 04
Automate
1–3 weeksWhere it earns its place, we layer in agents and pipelines so what launches is already doing work a person used to do — bookings, follow-ups, triage, the report nobody had time to write.
Output — Live integrations, monitored jobs
Automation only where it pays for itself
- 05
Support
OngoingMonitoring, iteration, vulnerability triage, and a named engineer who holds the codebase. Products that freeze on launch day were never finished.
Output — SLA, monthly iteration cadence
No handover cliff
Doing the arithmetic
Add the stages and you get seven to sixteen weeks. The eight to sixteen we quote is a Growth engagement specifically — Discover through Automate, where more than one system is in scope. A Starter compresses the same five stages into three to six weeks because there is one integration to make rather than five. Support is additive to both, not counted in either.
The exchange
Discover
You bring
An hour of your time and access to whoever actually does the work.
We deliver
A written scope, a cost range, and a recommendation on the first build worth committing to — including when that recommendation is narrower than what you asked for.
Decision point
You decide whether to continue. No cost either way.
Design
You bring
Feedback on flows within a few days of receiving them.
We deliver
System architecture, data model, and an interactive prototype of anything a user touches.
Decision point
Sign-off on the design. Changes after this point are quoted separately, and we will say so at the time.
Build
You bring
Half an hour a fortnight to look at a working demo.
We deliver
A deployed staging environment from week one and a demo at the end of every sprint.
Decision point
Acceptance against the criteria agreed in stage two, not against a vibe.
Automate
You bring
Credentials and a decision on what the system is allowed to do unsupervised.
We deliver
Integrations, scheduled jobs, monitoring, and an escalation path for when something fails at 2am.
Decision point
The system runs for two weeks under observation before anyone relies on it.
Support
You bring
Whatever cadence you want. Some clients want monthly, some want us on call.
We deliver
A named engineer who knows the codebase, an SLA, and a running list of what we would improve next.
Decision point
Cancel with 30 days notice. You keep everything.
Asked before
The seven questions everyone has
Is our project the right size for you?
Almost certainly, at either end. The agent runtime, retrieval layer, voice stack and integration infrastructure already exist and run in production — what you are paying for is the integration onto your use cases, not a platform built from scratch. That is what keeps a single defined use case commissionable rather than priced out of reach, and what keeps a multi-system rollout off a blank repository.
Can you meet enterprise security and procurement requirements?
Yes, where you have the appetite to specify them with us. SSO, role hierarchies, audit trails, data residency, penetration testing and security review are all in scope, and we would rather map them in Discover than discover them in month four. Enterprise work fails on unstated constraints far more often than on technical ceilings.
We are raising and need something to show. Can you help?
That is a routine starting point. A Starter engagement is frequently exactly this — the first working version you can put in front of a customer or an investor, deployed and real rather than clickable. It is built on the stack the full product would use, so what you pitch with is what you keep.
What if we want to stop halfway?
You can, at any stage boundary. You keep everything built to that point, including the repository and the documentation. We would rather you stopped at stage two than spent another eight weeks on something you had lost confidence in.
What if the estimate turns out to be wrong?
We tell you the week we find out, not the week before delivery. Estimates move — the thing that damages a project is finding out late, not the movement itself.
Who owns the code?
You do. Your repository, your cloud accounts, your keys. There is no proprietary layer you would need us to keep running.
Do you work with our existing team?
Usually, and we are equally used to there not being one. On roughly half our engagements we work alongside in-house engineers, building the parts they have no bandwidth for and handing over with a walkthrough. On the other half there is a founder and an ops lead, and we write the documentation for whoever they hire next.
Stage one