When advisory isn't enough, we build. Work is cut into tasks no larger than ten hours, each against a written acceptance criterion, each through the same five gates as everything else we ship. You approve every stage on staging before the next one starts.
If a task can't be described in one sentence and capped at ten hours, it isn't scoped yet — and we say so before you sign, not in week four.
Three ways to put us on the build.
The same delivery model sits behind all three. What differs is how much you already know, and how much of it is currently on fire.
Fixed-scope sprint
You know what needs building, and you want one price, one timeline and one person accountable for it.
- Written scope
- Daily progress in plain text
- Working software, staged
2–8 weeks
Foundation install
You're starting a Next.js and Contentful build and would rather not spend five months on plumbing first.
- Live staging
- Production-ready repo
- Contentful space provisioned
- 30 days office hours
One engagement
Audit + fix sprint
You inherited a system nobody can explain, and something inside it is already going wrong.
- Architecture map
- Risk register
- Top-three fixes shipped
2 weeks
No stage starts until you've signed off the one before it.
A fixed price only means something if the scope stays visible. Work reaches a staging URL in stages, and a stage you don't approve goes back to the fleet — at our cost, not as a change order.
- 01Scopepending
Tasks cut to ten hours or less, each with a written acceptance criterion. That list is the contract.
12 tasks · 10h ceilingyour approvallocked - 02Buildpending
The fleet works the tasks in parallel from one senior engineer's spec, behind the same five gates as everything else we ship.
5 gates - 03Stagingpending
The stage lands on a URL you can click, with its acceptance criteria ticked off beside it.
staging.ceero.eu/checkout3/3 acceptance criteria - 04Your sign-offpending
You approve the stage, or you don't. Rework inside the agreed scope is our cost — and the next stage waits either way.
ApproveRequest changes
Scope changes get priced before we continue. Never after.
A boring stack, and why we don't move off it.
Not a list of everything we've ever touched. These are the four defaults we start from, and what it takes to talk us out of each one.
- Next.js App Router + React 19
- Server components make the fast path the default one instead of something a developer has to remember. It's what our starter, the Maersk work and this site all run on.
- TypeScript, strict, no escape hatches
- A fleet of agents writes a lot of code quickly. The type checker is the cheapest reviewer we have, and the only one that never gets tired.
- PostgreSQL, with validation at the boundary
- Every external input is parsed before it reaches your data, and typed all the way in. We reach for something else only when the shape genuinely isn't relational.
- Vercel + GitHub Actions
- A preview deploy per pull request is what makes staged approval work at all. The gates run here, and a red gate blocks the merge rather than filing a ticket for later.
Microservices, GraphQL and a bespoke design system are all available on request — after you've heard the argument against them. Read the argument
Bring a problem. We'll bring a fixed price.
If it can be scoped, it can be priced. If it can't be scoped yet, that's the audit — and the audit is priced too.