MVP development

MVP development: from idea to paying users

An MVP isn't a cheap version of your product. It's the smallest version that proves people want it. We help you cut the scope to the one thing you need to prove, build it properly and launch it with payments and analytics in place, so your next decision rests on real data instead of opinions.

  • Scope cut to the riskiest assumption you need to test
  • Payments, accounts and analytics from the first release
  • Built on a foundation that grows, so nothing gets thrown away

From idea to evidence

  1. Idea

    Who has the problem, and what would they pay to have it solved?

  2. Riskiest assumption

    The one thing that must be true for the product to work.

  3. Smallest sellable version

    Only the features needed to test that assumption with real users.

  4. Launch with tracking

    Payments, analytics and conversion events live from day one.

  5. Learn and decide

    Double down, adjust or stop, based on what users actually do.

How we scope an MVP.
What we can build

What you get

Everything a first version needs to be used, paid for and measured, and nothing it doesn't.

A scope you can defend

Your idea turned into a short list of must-haves, a list for later and a clear definition of what success looks like.

Designs of the key flows

Clickable designs of the screens that matter, so you can show them to users and investors before we build.

A production-grade first version

Real accounts, real data and real security, on a codebase that can grow. Not a prototype you'll have to throw away.

Payments from day one

Subscriptions, one-off payments or usage-based billing with Stripe. A sign-up is a signal; a payment is proof.

Analytics and feedback

Product analytics and conversion tracking from the first user, so you know what people do, not just what they say.

Ready to show investors

A live product, clean demo data and clear metrics, on code you can show in a technical due diligence.

Proof, not promises

We've taken our own products from idea to launch

Twelve Lumens and Salestreak both went from first commit to a live product in 2026, with billing, accounts, five languages and analytics in place. Postcrest started the same way in 2023 and has grown through more than 1,700 commits since.

That's the approach we bring to your MVP: launch the smallest thing that can earn money, measure it, then build what the data asks for.

  • Stripe billing, trials and discounts in place
  • Product analytics and server-side conversion tracking built in
  • Marketing pages in five languages, ready for search engines
  • Paid acquisition tested in small, capped experiments before scaling up
  • One codebase from the first version onwards: Postcrest has grown on it since 2023
Twelve Lumens app: a property with rooms sorted automatically and photos staged in the Modern style
Twelve Lumens went from first commit to a live product with billing and five languages in 2026.
products we took from idea to launch
3
launches in 2026
2
commits on our longest-running product
1,700+
languages in our newest products
5
Who it's for

Who we build MVPs for

First-time founders

You know the problem and the market, but not how to get software built. We guide you from scope to launch in plain language.

Companies testing a new product

Validate a new digital product or service without pulling your existing team off their work.

Founders preparing to raise

A live product with real users and clear metrics makes a much stronger case than a slide deck.

Teams outgrowing a no-code prototype

Your no-code or spreadsheet prototype proved the idea. Now it has to scale. We rebuild it properly and move your users over.

How it works

How we build your MVP

Fast doesn't mean sloppy. It means deciding early what not to build.

  1. 1

    Scope

    Working sessions to agree on the problem, the users, the must-haves and what success looks like.

  2. 2

    Design

    Clickable designs of the key flows, so everyone agrees on what we're building.

  3. 3

    Build

    Short increments on a test environment you can use early on, with room to adjust as you learn.

  4. 4

    Launch

    Live with payments, analytics and error tracking switched on from the first user.

  5. 5

    Measure

    Look at what users actually do: where they drop off, what they pay for and what they ignore.

  6. 6

    Iterate or scale

    Build the next most valuable thing, or harden the product for growth.

A stack that's quick to start and safe to grow

Ruby on Rails with Hotwire lets a small team ship a complete product quickly, and the same codebase carries you well past launch.

  • Ruby on Rails
  • Hotwire
  • PostgreSQL
  • Tailwind CSS
  • Stripe
  • PostHog
  • Sentry
  • Kamal
  • Cloudflare
Cost & timeline

What does an MVP cost?

Less than a full product, more than a prototype. The estimate depends mainly on these five things:

Scope
The number of must-have features. Every feature you move to 'later' shortens the road to launch.
Type of product
A marketplace with two sides needs more than a tool for one type of user.
Payments and pricing
One subscription is simple. Usage-based pricing or payouts to others take more work.
Integrations and AI
External APIs and AI features add value, and they also add work and running costs.
Design ambition
A clean, standard look gets you to market faster than a fully custom design.
FAQ

Questions about MVP development

How much does it cost to build an MVP?

It depends mainly on the number of must-have features, the type of product and how you'll charge for it. After a free intro call you get a written scope and estimate, often with suggestions to cut the scope and launch sooner.

How long does it take to build an MVP?

That depends on the scope, which is why we spend real effort cutting it. We plan in phases with a clear first release, and the estimate after the intro call includes a timeline per phase.

What should an MVP include?

Only what's needed to test your riskiest assumption: usually one core workflow, accounts and a way to pay. Everything else can wait until users ask for it.

What's the difference between an MVP and a prototype?

A prototype shows how something could work. An MVP is a real product that real users can use and pay for. We build MVPs on a production-grade foundation, so you don't have to start over.

Can you rebuild our no-code MVP?

Yes. We rebuild what's proven, improve what isn't and move your users and data over, so the switch is barely noticeable for customers.

Do I need a technical co-founder to build an MVP?

Not to get started. We act as your technical partner through scope, build and launch, and can hand everything over to your own team later, with documentation.

Have an idea worth testing?

Tell us the problem, who has it and how you'd charge for it. You'll get an honest view on scope and the fastest route to real users.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to