SERVICE

MVP development

Our MVP development service turns a founder's idea into a working first version you can test with real users. It is for founders with an idea or an early-stage product. The first version goes live in 6–8 weeks.

MVP stands for minimum viable product: just enough product to test one key assumption. First we pin down what you want to learn, then we build only the part that tests it. The code and accounts are set up in your name. The product is yours.

The way we work is simple. The person you talk to is the person who writes the code. There is no sales team or project manager in between. We make decisions with you and write down the reasoning. We don't suggest features you don't need.

Who is MVP development for?

For founders who want to build an app but aren't sure what belongs in the first version, or who should build it. The idea doesn't need to be polished. You just need to know what you want to test, and we can work that out together on the first call.

Non-technical founders

You know your industry, not software. We make technical decisions with you and explain the reasoning.

Teams before fundraising

You'd rather show investors a working product and early user data than a slide deck.

New products in established companies

You want to test a new product alongside your main business without tying up your core team.

Technical founders

You can write the code but don't have the time, or you need a second pair of hands to ship the first version fast.

What problem does MVP development solve?

When you build software for a startup, the risk is rarely the code. It is the scope. A badly chosen scope wastes even well-written code. So the four problems below are all about scope, decisions and ownership. None of them is about which technology to use.

Everything wants in

The longer the feature list, the higher the time and cost, and the later you learn anything. We cut the scope down to the first user and one core flow.

Nobody to make tech calls

Which infrastructure, which ready-made services, what to leave for later? We make these decisions together and write them down.

A tight budget

Money spent on the wrong feature doesn't come back. Scope sets the cost of an MVP, and the assumption you want to test sets the scope.

Fear of lock-in

The code sits in your repository and the accounts are in your name. We hand over in a way that another team can pick up the work.

What does MVP development include?

The MVP Sprint package includes the following. We confirm the exact scope with you on the call, based on your idea.

  • Scoping: the assumption to test, the first user and the core flow
  • Interface design: screens that work on mobile and desktop
  • A working product: sign-up and login, the core flow, a basic admin screen
  • Ready-made services for standard parts such as accounts and payments
  • Launch: domain, hosting and basic monitoring
  • Basic analytics so you can see how it is used
  • Code in your repository and accounts in your name
  • A written technical note on next steps

What the first version leaves out is clear too: a separate native app in the app stores, a multi-language interface and detailed admin reports are discussed separately. If the assumption you want to test depends on one of these, we build the scope around it.

How it works

Example scenario: Picture a founder with an idea for an app that helps managers of small apartment buildings track service charges. Their list is long: charges, shared costs, announcements, repair requests, voting, online payment, accounting reports. They realise building all of it would take months.

In the scoping session, one assumption is chosen: will building managers pay to move service charge tracking into an app? The first version includes only the flat list, the amount each flat owes, payment records and a reminder sent to residents. Voting and accounting reports wait.

There is no online payment in the first version. The manager marks payments as received by hand. This is a deliberate choice, not a gap: first see whether managers use the product, then invest in payments.

The founder tries the first version with a handful of building managers and sees from real use which features people actually want. The next investment decision rests on what they observed, not on a guess. This scenario is fictional and does not describe a real startup.

PROCESS

Three steps. No surprises.

  1. We listen.

    We learn how your business runs and where time gets lost. A free 20-minute call.

  2. We get specific.

    We put scope, timeline and price in writing. We won't suggest features you don't need.

  3. We build.

    You see progress every week. We stay on hand after delivery, too.

Price and timeline

What does an MVP cost? MVP development is done through our MVP Sprint package. Scope sets the cost of an MVP. We quote in writing after a free 20-minute call where we talk through the scope.

What raises the price

  • Several user roles and approval steps
  • Integration with payments, maps or other services
  • Wanting both a web app and a separate mobile app
  • AI-powered features and the testing they need

What lowers the price

  • One type of user and one core flow
  • Using ready-made services for accounts and payments
  • Starting with a web app first
  • One person who can make decisions quickly

We take half the fee at the start and half on delivery. For larger scopes we agree a three-stage payment plan. After launch, the running costs are hosting and any ready-made services you connect. The accounts are in your name, so you see those bills directly. If you want to keep developing after the first version, we discuss that separately, on a monthly basis.

Frequently asked questions

What goes into an MVP?

Anything that affects the assumption you want to test goes in. Everything else waits. Security and data integrity are never cut. We write the list together during scoping.

Is there a monthly fee?

You don't pay us a mandatory monthly fee. Hosting and any ready-made services have their own usage costs. At an early stage these are usually low, and we list them in the quote. If you like, you can add monthly development support after delivery.

Who owns the code and data?

You do. We open the code repository, hosting and service accounts in your name. You can hand the product to your own team or another team whenever you want.

How long does it take?

The MVP Sprint takes 6–8 weeks. We work in weekly steps, so you see and try working parts before launch.

Is it safe to share our idea?

What you tell us on the call stays with us. If you prefer, we sign a non-disclosure agreement before going into detail.

What happens after the MVP?

Based on what users tell you, there are three paths: grow the product, change direction or stop. If you carry on, we keep building on the same code. You don't need to throw the first version away and start again.

Tell us about your business.

On a free call we listen to what you need. Then we give you scope, timeline and price in writing.

Book a call