The Four Week Build.
Brief on Monday. Live four Fridays later. Fixed fee. Code owned by you.
Discovery & Architecture .
A ninety-minute discovery call with no slides and no discovery deck. The brief is written in your words, signed off, and the data model is drafted on paper before the contract is final. A fixed-fee proposal lands inside forty-eight hours.
- — Signed brief
- — Data model on paper
- — Fixed fee agreed
Design .
Real screens, not wireframes. Brand, identity, and the editorial register land in week two, alongside the schema, authentication, and the risky integrations. A live staging URL goes up on day three so you watch the build as it happens.
- — Real screens
- — Walking skeleton
- — Staging URL live
Build .
The operator UI gets its keyboard shortcuts, bulk actions, and the screens the vendor refused to give you. Error paths, edge cases, and the boring ones are handled, not skipped. The AEO layer goes in: schema graph, llms.txt, direct-answer markup.
- — Operator UI complete
- — AEO layer wired
- — Feature-complete build
Launch & Handover .
Production cutover with you on the call. The source repo transfers to your organisation if it isn’t already there. A runbook lands in your inbox alongside a Loom walkthrough, and the ninety-day post-launch guarantee starts the moment the site is live.
- — Production cutover
- — Source transferred
- — 90-day guarantee active
What's included.
- Written brief
- Data model on paper
- Architecture & schema
- Fixed-fee proposal
- Brand identity
- Editorial design
- Full-stack development
- Operator UI
- AEO content layer
- Schema.org markup
- llms.txt directive
- Production deployment
- Source repo transfer
- Runbook documentation
- Loom walkthrough
- 90-day post-launch guarantee
Costs are scoped in week one and agreed before week two begins.
Every engagement is fixed-fee. No retainers, no monthly invoices, no scope-creep clauses to renegotiate at week three.
Why it works.
Four weeks is the constraint that makes the rest of it possible. It rules out the long discovery phase that produces nothing. It rules out the multi-stage replatform that ships eighteen months late. It rules out the agency dance — three account managers, two project managers, four developers nobody talked to.
What's left is the build. Operator on operator. One person doing the work, one person ringing them on Tuesday morning. Decisions made in the call, not in a status report.
The constraint is also a forcing function. When the cycle is four weeks, scope is set in week one and respected throughout. When the cycle is open-ended, scope drifts and the project is what pays for it.
Common questions.
What happens in the first week?
Discovery and architecture. A ninety-minute call with no slides, the brief written in your words and signed off, the data model drafted on paper, and a fixed-fee proposal within forty-eight hours.
When do I see something real?
By day three of week two a live staging URL goes up, and you watch the build as it happens. Real screens, not wireframes.
What do I get at handover?
Production cutover with you on the call, the source repository transferred to your organisation, a runbook, a Loom walkthrough, and a ninety-day post-launch guarantee that starts the moment you are live.
How is it priced?
Every engagement is a fixed fee, scoped in week one and agreed before week two begins. No retainers, no monthly invoices, no scope-creep clauses.
Why four weeks?
The constraint is the point. It rules out the discovery phase that produces nothing and the replatform that ships eighteen months late, and it forces scope to be set in week one and respected throughout.
Who actually does the work?
One person, operator to operator. Decisions are made on the call, not in a status report, with no account managers or hand-offs in between.
Start a build.
A 90-minute conversation. No slides, no discovery deck. A written proposal within 48 hours.
Start a conversation