Every stage ends with something you can check
Not a status update. A document, a working page, or a system your team is already using. If a stage cannot end that way, it is scoped wrong and we re-cut it before starting.
§ 01 / 06The sequence
Four stages, in this order
- 01
Build plan · 30 minutes, free
Your analytics open on the call. We map where enquiries come from and where they stall, then name the first fix. You leave with the order of work in writing.
- 02
Discovery · 3 working days, $2,400
We open the real data, read the existing code or accounts, and write down what the system has to do. The document is yours whether or not we build it.
- 03
Build · 4 to 8 weeks, staged
Releases every two weeks, each usable on its own. You judge each one in use rather than in a demo.
- 04
Handover · 1 week
Your team publishes a page while we watch. The runbook is written for someone who has never met us.
- 1Build planA written order of work
- 2DiscoveryFindings, architecture, and a dated schedule
- 3BuildA working system, released in pieces
- 4HandoverRunbook, admin guide, and your accounts
§ 02 / 06Working together
How the week runs
- One call a week
- Thirty minutes, same day and time
Cancelled when there is nothing to decide. We do not hold meetings to report.
- Written updates
- Every Friday, whether or not there is good news
- One channel
- A shared channel with your team and ours
Not a ticketing system you have to log into.
- Named people
- You know who is doing the work, by name
Not a shared queue and not an account manager relaying messages.
- Response time
- We reply within one business hour
§ 03 / 06When it goes wrong
What happens when we are wrong
Estimates miss. Discovery finds things nobody knew about. The question is not whether that happens but what a vendor does when it does.
- Estimate misses
- We absorb the first 15%
Beyond that we stop and re-plan with you before spending more.
- Scope grows
- It becomes a separate, separately priced piece
It never quietly extends the current one.
- We are the wrong fit
- We say so and name who is better
Usually in the first call, occasionally during discovery.
- You want to stop
- Thirty days notice, no exit fee
Repository, accounts, and documents are already yours.
§ 04 / 06What we build on
The stack, and why
A technical buyer will want this. We choose tools that another team can pick up, not ones that make us hard to replace.
- Web
- TypeScript, React, Next.js
The largest hiring pool of any modern web stack.
- Data
- PostgreSQL with a typed schema
Portable between hosts. No proprietary database.
- Hosting
- Vercel or your own infrastructure
We will deploy to yours if you prefer, and say what it costs.
- Mobile
- React Native, one codebase for both stores
- AI
- Hosted models with grounded retrieval and escalation
No model trained on your data without a written agreement.
If your team already runs something different and it works, we build on that rather than on our preference.
§ 05 / 06Commitments
Held to these on every project
§ 01 / 01Questions
About how we work
Who actually does the work?
A named engineer and, where marketing is involved, a named marketer. You meet them before the contract, not after. We do not subcontract without telling you.
What time zone do you work in?
US Central business hours for calls and replies. Development work happens across a wider window, which is why a Friday update exists rather than a daily standup you would have to attend.
Can we start with something small?
We prefer it. Discovery at $2,400 is the smallest honest starting point, and a good number of clients stop there for a few months before building.
Do you sign NDAs?
Yes, before discovery. We will read it rather than sign blind, and we will flag anything unusual rather than agree and hope.
Client cases with real numbers will appear on this site as clients clear them for publication. Until then we would rather show the process than invent results.
Start with the plan
Thirty minutes. You leave with the order of work either way.
Free, 30 minutes, no slide deck.