MVP, end to end
From a Figma file to something your users can log into
The whole product, built by the person who will still be there when it needs changing. Frontend, backend, the integrations a real product needs, deployed to infrastructure you own - and code documented well enough to hand to a team later without an archaeology phase.
from $5,500From 3 weeks
What you get
- Frontend, backend, and integrations (auth, payments, queues as needed)
- Deployed to production - Cloudflare or Docker, domains, environments
- Clean, documented code that's easy to hand off to a team
Who it's for
- Founders with a validated idea, a design, and no engineering team yet
- Teams that need a second product built while the first one keeps their engineers busy
- Anyone who has been quoted six figures by an agency for something that does not need six figures
Who it isn't for
- Ideas that still need discovery - an MVP built on an unanswered question is an expensive way to ask it
- Products whose core is a native mobile app
- Work with no decision-maker available week to week
How it runs
Scope, week zero
The brief becomes a written list of flows with a line through everything that is version two. This is where the budget is actually decided, and it is fixed before any code is written.
Spine first
Auth, data model, deployment and CI on day one, not at the end. The unglamorous half is what makes the second month cheap, and it is the half that gets skipped when a build is priced by the screen.
Weekly, on a real URL
Every week ends with something deployed you can click. No demo builds, no screenshots standing in for progress.
Handover
Repository, infrastructure and domains in your accounts from the start, never mine. A README that gets a new developer running locally, and the decisions written down where they will be found.
Questions
What does 'from $5,500' actually buy?
A single-purpose product: authentication, one core workflow done properly, an admin view, and production deployment. Payments, queues, multi-tenancy and integrations each move the number, which is why scope is fixed in week zero rather than argued about in week six.
Do you do the design too?
I build from your Figma. If there is no design, the honest options are a deliberately plain interface built on a component library, or bringing a designer in - I will tell you which one your product needs.
What happens after launch?
Either nothing, and you own everything, or the retainer, which is the same person continuing at a predictable weekly rate. There is no lock-in in the build that would make the first option painful.
Fixed price or hourly?
Fixed for the scope agreed in week zero. Changes to that scope get their own number before they start, not a surprise on the invoice.
Proof
Everything above is checkable. References from the people I shipped with, the engagements behind them, the public repositories, and the full stack.
Other ways to work together
Tell me what you are building
The design, or the brief, or three sentences. I will come back with what it would take and what I would cut, which is usually the more useful half.