From idea to a working product, in a week or two.
Design, code, auth, payments, deploy. Same person, the whole way from a paragraph to a paying signup.
-
A real product, not a prototype
Up to ten core screens, designed and built. Auth, the core flow, payments if you need them, a simple admin, the deploy pipeline. If the idea is still fuzzy, start with the $500 idea audit first so we know what v1 should prove.
-
How the build shapes up
Days 1–3: design and the spine on staging. Days 4–7: the flows that matter. Final stretch: payments, polish, deploy. You watch it happen on a staging URL the whole way. No big reveal at the end, no surprises.
-
What gets cut, on purpose
Scope creep is what kills MVPs. I'll push back on features that don't matter for v1 and tell you the truth about what to ship later. The goal is the smallest version that still proves the idea works, not a feature list.
-
The mid-build walk and post-launch fixes
Halfway through, you can stop with a refund minus design hours done. The repo stays in your GitHub either way. After launch, one round of fixes is included. Real users find real edge cases.
Have an idea but not the v1 shape? Start with the audit.
I audit one idea, cut the fake requirements, and turn it into a v1 scope. If we build it, the full $500 rolls in as credit.
A few things people ask
What stack?
Next.js + Postgres + Stripe + Vercel by default. Swap any of it if you have a hard requirement. Auth via Clerk or Auth.js depending on the case.
Do you do mobile apps?
PWAs and React Native, yes. Native iOS/Android no. That's not what one person can ship in three weeks well.
Should I start with the audit?
If the idea is clear and scoped, no. If you need help deciding what v1 should be, what to cut, or whether it's worth building at all, audit the idea first. The $500 rolls in as credit if we build the MVP.