MVP Development for Startups

Most startup ideas begin as a long list of features. We start by asking who the first users are, what job they want done, and how they cope without you today. From that we agree on a single hypothesis to test and the smallest set of functions needed to test it. Everything else goes into a backlog that you can revisit once the first release has produced evidence. If a spreadsheet, a form or a manual process can test the idea faster, we will say so.

1. Scoping. A short workshop and a written scope with what is in, what is out and how we will judge success.
2. Prototype. Where useful, a clickable design that you can show to potential users before any code is written.
3. Iterations. Short cycles that each end with a working demo you can click through.
4. Release. A first version for a small group of real users.
5. Learning. We review usage and feedback with you and decide what to change, add or drop.

We prefer mainstream, well-documented tools that many developers know, because the people working on a startup's code often change. The aim is code that is clean enough to extend but not over-engineered for users you do not have yet. We agree early where you will own the code, the accounts and the data, so you are not tied to us. If your MVP needs a website, a web application or a mobile app, we recommend the cheapest format that can still answer your question.

As soon as your product handles personal data, data protection law applies. The Information Commissioner's Office says you must determine and document your lawful basis before you start using personal information, and should not swap to a different basis later without good reason, so it is cheaper to decide during scoping than after launch. UK GDPR, and the EU GDPR if your users are in the EU, requires you to tell people certain things when you collect their data, including your purposes and lawful basis (Article 13), and, where a service provider processes data for you, to have a contract with it in writing (Article 28). We build the technical side and flag the questions you should take to a lawyer.

The result of an MVP is a decision: continue, change direction or stop. If you continue, we can keep working with you or hand over cleanly to your own team. Costs depend entirely on scope, platform and the number of iterations, so we give a figure on request after the scoping workshop rather than a catalogue price. Our entry price for simple websites, from 300 € excl. VAT, is on the pricing page. To talk about your idea, contact us or request a quote, and see our wider services.

What is an MVP?

The smallest version of a product that lets you test one core hypothesis with real users.

What decides how long our MVP takes?

It depends on scope, which is why we agree it in a scoping workshop first. We work in short iterations with demos.

Will I own the code?

We agree early that you own the code, accounts and data, so you can change team.

Do you also advise against building?

Yes. If a manual process or existing tool can test your idea faster, we will say so.

What does it cost?

It depends on scope, platform and iterations, so a figure is given on request after scoping.