FIG. 01 — THE FLAGSHIP · STAGES 01–05
The 4-Week MVP Sprint.
Your product, live, in four weeks.
You’ve proven people want this. What you don’t have is a product — or six months to wait for one. The Sprint puts the v1 of your real system in production: validated with real buyers in Week 1, deployed to a live URL every Friday, launched on day 28. Fixed scope, fixed price, and every promise on this page written into the contract.
FIG. 02 — DEMO-WARE VS PRODUCTION
“We’ll productionize it later” — the four most expensive words you can be sold.
Most MVPs are stage props — a demo that works until a real user touches it. Ours is the v1 of the real system. Hard-coded logins, a database on someone’s laptop: that’s not an MVP, and you pay twice for it — once to build it, once to rebuild it before it can launch.
Our incentive is inverted: the price is fixed, so the only way we win is shipping the real thing fast — the same auth, infra, and code you’ll run at 10,000 users.
The MVP is v1 of the real system. — Differentiator No. 3
- AUTH
- [−]Login is a hard-coded list of test users.
- [✓]Real auth from Week 1 — sessions, password reset, roles.
- DEPLOYS
- [−]From someone’s laptop, when they remember.
- [✓]CI/CD to a live URL. CI green or no deploy.
- FAILURE
- [−]Errors vanish silently until a customer finds them.
- [✓]Tracked and alerting from the first scaffold.
- WHERE IT RUNS
- [−]“Works on my machine.”
- [✓]Works on your domain, in your cloud account.
- LAUNCH
- [−]Rebuilt from scratch before it can launch — pay twice.
- [✓]Launch is a deploy, not a rewrite. Day 28 is a Friday like the other three.
FIG. 03 — THE CALENDAR, EXACTLY
Five weeks on one ruler. Nothing hidden.
This is the actual working calendar — the same one we run internally. On Thursday of Week 1 your signed scope is sliced into three Friday deploy targets; every Monday confirms the target, every Friday proves it on the live URL. The scope contract and the calendar are the same document read two ways.
- WEEK 0Endgame
A two-hour workshop before the clock starts. Your launch-day outcome — users, jobs-to-be-done, success metrics, non-goals — becomes the Omega Statement, signed by both sides within 48 hours.
- WEEK 1▪ DEPLOYEvidence + Blueprint
Real buyers interviewed and coded, the kill/go verdict issued Thursday against published thresholds, the Build Blueprint signed Friday — and your scaffold live on production infra: repo, CI/CD, auth shell, live URL.
- WEEK 2▪ DEPLOYBuild
The core value path. Friday, 2pm: you click a link and your #1 job-to-be-done works end to end on the live URL — not a slideshow of your product. Weekend homework: try to break it.
- WEEK 3▪ DEPLOYBuild
Everything launch day needs: secondary flows, edge states, onboarding, payments if in scope, the security pass. Friday: the checklist is demoably complete and feature freeze is declared, in writing.
- WEEK 4▪ DEPLOYBuild + Launch
Hardening, dry run by a non-builder, taught handover. Friday: production go-live on your domain, wave one invited, four hours of live monitoring — and the day-one report sent the same day.
4 FRIDAYS · 4 DEPLOYS · 0 SLIDE DECKS · TOTAL CLIENT TIME: ~22 HRS ACROSS 5 WEEKS
If Week-1 evidence triggers KILL, the Sprint stops. You pay $7,500. The rest is refunded or credited.
FIG. 04 — THE FRIDAY DEPLOY RITUAL
Friday means Friday. You get a link, not a deck.
You can’t evaluate code. You don’t have to. Click the link. Break the thing. That’s the meeting — the same shape every week, and we demo only what is deployed.
The ritual, every week
- 12:00Production deploy. CI green or no deploy.
- 14:0030-minute live demo on the production URL. You click, we don’t.
- 14:30Changelog sent.
- 15:00Next Friday’s target confirmed in writing.
The deploy ledger
- FRI W1 · DEPLOYEDBlueprint signed · scaffold live: repo, CI/CD, auth shell, live URL
- FRI W2 · DEPLOYEDCore job works end to end on the live URL
- FRI W3 · DEPLOYEDLaunch-day checklist complete · feature freeze declared
- FRI W4 · LAUNCHEDProduction go-live on your domain · wave 1 invited
We demo only what is deployed. Nothing mocked, ever.
FIG. 05 — THE CHECKLIST, ITEM BY ITEM
“Production-ready” is a checklist, not an adjective.
Every item below ships inside the four weeks and lands in your accounts. None is an upsell. If another vendor quotes you an “MVP,” hand them this list and watch the price change.
- [✓]REAL AUTH
Session management, password reset, role-based access. No hard-coded users, no shared admin login.
VERIFIED BY: AUTH REVIEW IN THE WEEK-3 SECURITY PASS
- [✓]REAL INFRA
Managed cloud in your account, infrastructure as code, staging + production environments, automated backups.
VERIFIED BY: ACCESS CHECKLIST AT WEEK 0 · IaC IN YOUR REPO
- [✓]CI/CD
Every merge tested and deployed automatically. CI green or no deploy — the Friday rule is enforced by the pipeline, not by promises.
VERIFIED BY: 4 DATED FRIDAY DEPLOYS IN THE PIPELINE HISTORY
- [✓]OBSERVABILITY
Error tracking with alerting from Week 1, structured logs, uptime checks, and a dashboard wired to the 3 success metrics in your Omega Statement.
VERIFIED BY: 3 OF 3 DASHBOARD TILES LIVE · ALERT TEST FIRED IN WEEK 4
- [✓]SECURITY PASS
Secrets management, dependency audit, auth review, least-privilege access — run in Week 3, documented in the handover.
VERIFIED BY: WRITTEN SECURITY PASS IN THE HANDOVER DOCS
- [✓]HANDOVER DOCS
Architecture notes, a runbook — deploy, roll back, read dashboards — and a taught handover session.
VERIFIED BY: DRY RUN PASSED BY A NON-BUILDER, THURSDAY W4
Every item verified before launch · Gaps block go-live · All of it in your accounts
FIG. 06 — THE ARTIFACT ROW
What you’ll own. Stamped, dated, yours.
The Omega Statement and Evidence Ledger land first — then the build chapter produces these.
The shortest path, drawn
Clickable design, system architecture, and your signed scope contract — sliced into three Friday deploy targets before a line of feature code is written.
The live production system
Your domain, your repo, your cloud accounts — with four dated Friday deploys behind it. Not a prototype you’ll throw away: the v1 of the real system.
Launch day, executed
Go-live checklist executed, analytics wired to your three success metrics, onboarding live, first-user plan run — and the day-one report in your inbox.
Full code, infra, and data ownership · 2 weeks of post-launch defect fixes included
FIG. 07 — THE NUMBER AND THE TERMS
$39,500. Fixed. Here’s exactly what that buys.
50% — TO BOOK YOUR START DATE
50% — AFTER TWO FRIDAY DEPLOYS · END OF WEEK 2
- [✓]Week 0 ENDGAME workshop → your signed Omega Statement
- [✓]Week 1 EVIDENCE + BLUEPRINT: clickable design, architecture, signed scope contract
- [✓]Weeks 2–4 BUILD + LAUNCH: four Friday production deploys, go-live on your domain
- [✓]Production standards, non-negotiable: real auth, real infra, CI/CD, error monitoring, observability
- [✓]Analytics wired to your 3 success metrics; handover docs + taught handover session
- [✓]Full code, infra, and data ownership — your repo, your cloud accounts, from day one
- [✓]2 weeks of post-launch defect fixes at no charge
- [−]Ongoing feature work — that’s the Growth Package ($12,500/mo), proposed in Week 3, never sprung after launch
- [−]Native mobile apps — scoped separately; the Sprint ships responsive web
- [−]Data migrations beyond agreed seed data — migration is its own project, priced honestly
- [−]Marketing execution — the Launch Runway plans your first users; running campaigns is not our lane
If Week 1 ends without a signed Build Blueprint, you walk away and pay only the Discovery-equivalent portion: $7,500. You keep every Week-1 artifact.
If Week-1 evidence triggers KILL under the published thresholds, the Sprint stops. You pay $7,500; the remainder is refunded or credited. This rule is published — it is the strongest trust asset we own.
If we miss the agreed launch scope by the agreed date for reasons inside our control, we work free until it ships. Written into the contract, not the footer.
RAN A DISCOVERY SPRINT FIRST? THE FEE CREDITS 100%:
$39,500 − $7,500 = $32,000
Not ready to commit $39,500 to an unvalidated idea? Good instinct — that’s the instinct this studio is built on. Start with the Product Discovery Sprint — $7,500 · 1 WEEK — and let the evidence decide.
FIG. 08 — HONEST DISQUALIFIERS
Don’t book this if…
- 01You want to skip Week 1’s verdict. The kill thresholds apply even mid-sprint. If you want a build with no verdict exposure, we’re the wrong studio — deliberately.
- 02You can’t give it ~22 hours across five weeks. The calendar above needs you at the workshop, the verdict call, and four Friday demos. No founder in the room, no sprint.
- 03Sign-off needs a committee. The Omega Statement runs on a 48-hour clock and the Blueprint is signed in Week 1. If every decision routes through three stakeholders, buy the Discovery Sprint first and bring the verdict to your committee instead.
- 04Your v1 has thirty must-have features. Fixed scope means the launch-day checklist, not the wishlist. If nothing can be a non-goal, no four-week anything will be true.
- 05You need native mobile at launch. The Sprint ships responsive web. Native apps are a separate scope — we’ll say so in the Product Session, not in Week 3.
- 06You’re buying hours to direct. We sell outcomes with a published price. If you want a team of hands billing weekly, an agency will happily sell you that — and we’ve written about how that ends.
Saying no in public is the cheapest trust we buy.
FIG. 09 — ASKED BEFORE EVERY SPRINT
The questions that decide it.
Four weeks — what’s the catch?
Fixed scope. We cut to the launch-day checklist you sign in Week 0. Anything else waits for the data. That’s the trade, and it’s written down before we start.
Is it a real product or a prototype?
Real. Week 1 deploys to production infrastructure: auth, CI/CD, error tracking, live URL. There is no throwaway version — the MVP is v1 of the real system.
What if validation fails in week one?
We stop. You pay $7,500 for Week 1 at the Discovery rate; the rest is refunded or credited. The kill thresholds are published on our method page.
Who owns the code and the IP?
You do. Your repo, your cloud accounts, your data, from day one. We work in your systems, not ours — offboarding is a meeting, not a negotiation.
What tech stack do you use?
Boring, proven, documented. Managed cloud, mainstream frameworks, your accounts. No exotic dependencies you can’t hire for — the handover assumes we might never meet again.
What happens after launch?
Most clients continue on the Growth Package ($12,500/mo): one evidence-backed improvement cycle per month, same Friday deploy cadence. We propose it in Week 3 so it’s a decision, not a surprise.
FIG. Ω — THE END STATE
Four weeks from now, this is either live — or you’ll know why it shouldn’t be.
Thirty minutes. We work on your product — sketch the Omega Statement, pressure-test the idea, and tell you honestly whether it’s worth building. If we’re not the right studio, we’ll say that too.