// BROWNFIELD BUILD — 7 days on YOUR repo · 5 Brownfield slots a week, next Monday start
Stuck → Deployed
by Sunday.
One week. Your repo, your keyboard. Day 1 we lock one major feature or one major fix — in your own words — as the scope. Then we ship it together in 15–30 minutes a day with 10-min unstick calls the moment you hit a wall until you paste a real URL into your group chat by Day 7.
// WHO THIS IS FOR
You started it.
Something got between you and shipped.
which one sounds like your last three weekends?Half-built → Merged
The repo exists. Last commit was 18 days ago. This week we open it back up, kill the one bug that killed the momentum, and merge your next feature by Friday.
"it broke 3 weeks ago and I haven't opened it since"Cursor solo → Shipping partner
You can code. You ship with AI. You just can't do another weekend staring at the same file alone — one focused session a day with someone building alongside you, and it moves again.
"I don't need a class, I need someone shipping with me"Local only → Live URL
It runs on localhost. Nobody else has ever seen it. By Day 7 it's deployed, a custom domain is pointed at it, and the link works when you send it to a stranger.
"one more week of this and I'm shelving it"// HOW THE SPRINT RUNS
Seven days.
Every one has a job.
DAY 1 — SCOPING · 45 MIN
We lock the scope. In your own words. On paper.
We open your repo together. You name the wall — the one major feature or one major fix you're stuck on — and we lock it as the target, in your own words, plus the Version Map to a live URL by Sunday. In extreme cases where I see a nearer blocker or closer target, I'll say so on the call. No mid-sprint renegotiation. If Day 1 doesn't leave you with a map you can act on, the sprint is refunded before Day 2 starts.
DAY 2–6 — DAILY BUILD SESSIONS · 15–30 MIN EACH
One push every day. You never lose a day again.
Screen share, your codebase, hands on your keyboard — one focused session every single day, sized so it fits between a job and a life. Momentum never gets a day off. And the second you hit a wall between sessions: 10-minute unstick calls, up to 5 across the week, plus an async line that answers inside 24 hours.
DAY 7 — SHIP REVIEW · 30 MIN
You paste the URL into a group chat while I watch.
We demo the deployed app on the real URL. You keep the recording of every session and a written next-3-steps doc so you know what to open on Monday — the muscle memory of shipping, not just the win.
// CLAIM YOUR SLOT
Cheaper than a week of a freelancer. Nothing gets added to it inside the sprint.
one flat price. no retainer, no scope-creep meetings, no "let's hop on a quick call."Your price: $399 — Five Brownfield slots a week because I deliver every sprint personally — and I only take what I can actually ship.
Reply in ~5 min · Accepted builders get a payment link (Cash App Pay or card) + Day 1 booking · First accepted, first locked · Sprint starts Monday
// THE GUARANTEE
Deployed by Day 7. Or your money back.
If your next version isn't live on a real URL by the Day 7 ship review — deployed, working, visitable — I refund the full $399. Not part of it. All of it. No form, no back-and-forth, no fine print. One reply and it's done. I only ship what I can ship, which is why applications get reviewed before payment.
the only guarantee worth writing is the one you'd honor without being asked.// QUESTIONS
Before you apply.
Why apply — why can't I just pay?
Two reasons, both real. One: five Brownfield slots a week, because I deliver every sprint personally and can't fake capacity. Two: I only take projects I can actually ship in seven days, so I read the form before I take the money. The form is short. Accepted applicants get a payment link within ~5 minutes and the slot locks when you pay.
My app is still just an idea — is this the right sprint?
No — the Greenfield Build is the right one first. One week to conceive the imaginative solution, plus a PRD and a working AI-native demo of your idea you can point at. $199. After that, the Brownfield Build takes the demo to a deployed app on a real URL. See the Greenfield Build →
Are you writing the code, or am I?
You are — on your keyboard, on your repo, with me on screen share writing alongside you using the same AI-native workflow I ship with every day. You leave the week with the shipped version and the operating environment we built together (prompts, docs, tools, skills) so you keep shipping after Day 7. A freelancer takes the codebase and the learning; this doesn't.
What if my definition of "shipped" is bigger than one week?
That's what Day 1 is for. In 45 minutes we lock one major feature or one major fix as the target and write the Version Map — the exact next version we can honestly deploy by Day 7 given your codebase. Anything past that lands in the next-version roadmap doc. If the map we agree on Day 1 isn't live by Day 7, the full $399 comes back. If the project genuinely needs 2–4 weeks of runway, we scope that in the Day 1 call.
What happens after Day 7?
You keep everything — recordings, Version Map, next-version roadmap, the operating environment we built together, and the live URL. On the Day 7 call I'll offer the Skool community ($69/mo or $500/yr with a 7-day free trial) — weekly Labs, searchable library organized by problem, direct line to me between sessions. Repeat sprints are always open when the next real wall shows up. See Ship Club →
open it Monday. deploy it Sunday.