The core flow, end to end
Sign up, do the thing, pay for it. About eight screens on a clean system UI, working on a phone and a laptop.
01 · 2–4 weeks
MVP Sprint
The smallest thing that is a real product: a web app that signs users up, does the one thing your idea is about, takes payment and runs on your own accounts. $5K fixed.
Price
$5K
Included
Web app · auth · one core flow
Included
Stripe payments
Included
Deployed on your accounts
It runsD5
Fixed$5K
Pay on deploy50/50
Your repo</>
How it works
Scope is agreed on a 30-minute call and written down: who the user is, the one flow they complete, what they pay for and roughly which screens that takes. That document is the contract, with a price and a launch date on it.
Day 5 is a deployed URL with the core flow working end to end. Then a demo every three to four days until launch. The stack is deliberately mainstream: Next.js, Node or Python, PostgreSQL, Vercel, Supabase or AWS, Stripe. Nothing you would have to rewrite to grow, and nothing a future hire can't read on day one.
50% to start, 50% on deployment. If the date agreed at scoping is missed, the second half is waived. App Store and Google Play review time does not count against the date. The date moves only if the scope changes in writing.
What you get
Four things land on your side.
Auth, Stripe and one integration
Accounts, sessions and password reset. Subscriptions or one-off payments through Stripe. One more third-party API if the flow needs it.
Deployed on your accounts
Production on your Vercel or AWS, your database, your Stripe, your domain, with monitoring and error alerts switched on.
Source, docs, 30 days of support
The repository is yours from the first commit. A short runbook, and a month of fixes after launch.
How it runs
MVP Sprint, week by week.
Scope
Day 0: a 30-minute call, then a one-page scope with a fixed price and a launch date. You sign it, 50% is invoiced.
Skeleton
Day 5: repo, deploy pipeline and the core flow running end to end on a real URL.
Build
Weeks 1–3: a live demo every 3–4 days, daily written progress in Slack, your feedback in the next build.
Launch
The agreed date: production deploy, monitoring, runbook. The second 50% is invoiced on deployment, or waived.
Questions
What people ask before they book.
- Is $5K really enough?
- For one product that does one thing well, yes. It covers auth, one core flow, Stripe, a clean system UI and deployment. It does not cover native mobile apps, custom brand design, a second payment provider or more than one extra integration, and it assumes about eight screens.
- What exactly is not included?
- Native iOS and Android apps, custom brand design or a designer's Figma, a second payment provider, more than one extra integration, and more than about eight screens. Each of those is the Product Build, or quoted as an add-on before it is built.
- What if I need a mobile app later?
- The web app is built with Next.js and the backend is shared, so iOS and Android can be added from the same codebase with Expo as a Product Build. Nothing gets thrown away.
- What do I need to prepare?
- Two sentences about who uses it and what it does, and accounts on GitHub, Vercel or AWS, Supabase or Neon, Stripe and your domain registrar. Codeks deploys into them. If you don't have them yet, creating them takes an hour and is walked through on the call.
Start here