A working product in production
Not a Figma file, not a clickable prototype. Real code, real deploys, real users hitting it on day one.
M
Service / MVP Development
From spec to paying customer in six weeks.
We take a one-page idea to a live product, then hand you the keys. No theatre, no boilerplate.
What you get
By the end, you'll have…
A first paying customer — or an honest reason there isn't one
We help you get the thing in front of buyers in week five. If the market says no, you'll know why before you raise.
All the code in your repo, no lock-in
You own the GitHub org, the Firebase project, the domain, the keys. Walk away with a vendor or without — either works.
A short post-launch retainer
Day 31 isn't the day everything breaks. We stay on for fixes, small features, and the inevitable "can we add…" while you find a permanent team.
A scope you can defend to investors
We write down what's in and what's out, in plain English. Useful when the next round of "could we also…" hits.
A path to version two
We leave behind a short doc on what to build next based on what real users actually did — not what the deck said they would.
How it works
Six weeks, four beats.
Scope
One working session to lock the one-page spec, the success metric, and the launch date. Estimate is fixed-fee from here.
Core build
Auth, data model, the one workflow that matters. You see a deployed environment by end of week one and weekly builds after.
Real users
Five to ten beta users in the product, real feedback loops, the rough edges sanded. The thing starts feeling like a thing.
Launch + handover
Production cutover, custom domain, monitoring, and a written handover. You leave the project owning everything.
Typical stack
Tools that fit the problem.
We pick from a short list we know cold, so day one is building — not learning.
- Angular
- NestJS
- Firebase
- Tailwind
- Ionic
- Vercel
- Stripe
- SendGrid
- Gemini
- Postmark
Questions
Stuff founders actually ask.
What if my idea isn't ready?
Then week zero is where we go. Most "not ready" really means "I haven't written it down yet." A 30-minute call usually gets it to one page.
What happens after the six weeks?
You own the code and we're on a short retainer (usually 10–20 hours a month for the first 60 days) for fixes and small features. Most clients then either bring it in-house or extend us.
Can we extend if we need more?
Yes — into a custom engagement, a longer retainer, or month-by-month. We won't pad the original six weeks to keep ourselves billing.
Do you take equity?
Rarely, and only on projects we'd build anyway. The default is cash. It keeps the relationship simple and the incentives honest.
What does it actually cost?
A six-week MVP usually lands between $25k and $55k depending on integrations, auth complexity, and whether mobile is in scope. We quote fixed-fee after the week-zero scope.
Got a spec? Or just an idea?
A 30-minute call is enough to scope it, price it, and tell you if six weeks is realistic.