Process
How a feature ships here
Every change to every project goes through five steps: a written spec you approve, an agent-assisted build, a human review of every line, automated tests plus a preview URL, and a deploy with handover. AI does the typing. We do the architecture, the review and the accountability.
Five steps, no surprises.
You always know what happens next, what it costs and when it will be ready.
- Day 1
A short call
Thirty minutes to understand your business and what you need. No charge.
- Within 3 days
Written scope and price
A plain-language document: what’s included, what isn’t, the price and the date.
- Week 1
First clickable version
You see and try a working draft early, while changes are still easy.
- During the build
Progress you can see
A short update every week and a working version to try at every milestone. Never a month of silence.
- Launch
Launch and 30 days of fixes
We launch together. Anything not working as agreed is fixed at no cost.
How we use AI, exactly
We use AI coding agents on every project and would rather tell you exactly how than let you guess. Agents write most of the first draft of most code: boilerplate, migrations, tests, refactors, repetitive UI. They are fast and tireless and they do not get bored on file 40.
What they are not is accountable, and they are unreliable at knowing what should not be built — they will happily implement a bad idea beautifully. So: we write the spec, we choose the architecture, we read every line before it merges, and our name is on the result.
If you would prefer we didn’t use them, say so and we’ll quote accordingly — it will cost more and take longer, and we’ll be honest that we think you’d be paying for worse odds.
Quality gates
- Typecheck and lint
- Unit and integration tests on business logic
- Playwright end-to-end on the critical paths
- Lighthouse budget in CI
- Accessibility check (axe) in CI
- No direct pushes to main
What you see each week
A Friday written update — what shipped, what’s next, what we need from you, and any risk that appeared. A preview URL from week one. Zero status meetings unless you want them.
Tooling
Claude Code · TypeScript · Next.js · Payload · Postgres · Playwright · GitHub Actions · Sentry · Hetzner/Cloudflare