MVP Development for Startups

An MVP is not a cheap version of your product. It is the smallest version that can tell you whether the product should exist. I help founders cut the idea down to the features that test the riskiest assumption, then build it properly, so what you launch can grow into the real product instead of being thrown away. I was CTO at Bitbrand and built Deliveristo’s app from prototype to first store release, so I know what the first months of a startup ask of the tech.

What’s included

What you get

  • Feature prioritisation The smallest scope that tests your riskiest assumption.
  • Mobile or web app Native, React Native or web, whichever reaches your users fastest.
  • Backend & auth Accounts, data and APIs on a managed backend like Supabase or Firebase.
  • Payments Subscriptions or in-app purchases when revenue is part of the test.
  • Analytics from day one The events you need to judge whether the MVP worked.
  • Launch & iteration Store release, feedback loop and the next version planned together.

Process

How it works

  1. 01

    Assumptions

    We name what must be true for the business to work.

  2. 02

    Cut scope

    Only the features that test those assumptions make the list.

  3. 03

    Build fast, build right

    Short cycles on a codebase meant to survive success.

  4. 04

    Measure

    Launch, read the data, and decide what to build next.

Proof

Related work

FAQ

Common questions

Something else? Ask me directly .

How long does it take to build an MVP?

Most mobile or web MVPs take a few weeks to a few months, depending on scope. The biggest lever on time is how ruthlessly we cut features, which is why scoping comes first.

Mobile app or web app for my MVP?

Go where your users already are and where the core feature works best. If it depends on the phone (location, camera, notifications, the Watch) go mobile; if people will use it at a desk, a web app is faster and cheaper to validate.

Will the MVP have to be rewritten later?

It should not. I keep the scope small, not the quality, so the codebase can grow into the full product.

Can you work with a non-technical founder?

Yes. I explain trade-offs in plain language, help you make the technical decisions, and hand over a documented project you fully own.

Do you sign an NDA?

Yes, happily, before we discuss the details of your idea.

Other services

Need something else?

All services

Have a project in mind?

Tell me what you’re building.