What shapes an MVP in the United Kingdom
A first version is mostly a product question. In the UK it is also a legal question, and the answers are cheaper before the build than after it.
| Topic | What it means for your MVP | Decide early |
|---|---|---|
| Who owns the work | Under UK copyright law, the first owner of commissioned software is the person or firm that wrote it. Ownership moves to your company only by a written assignment that the author signs. Investors look for it | The ownership and licensing terms your agreement should state, with your solicitor |
| Data protection | UK GDPR applies from the first user. You need a lawful basis, a privacy notice and security in proportion to the risk, and most organisations that process personal data pay a fee to the regulator | What you collect at sign-up, and who is responsible for it |
| Users interacting with each other | If people can post content or message one another, the Online Safety Act is likely to apply, with illegal content risk assessments and reporting tools required whatever the company's size. Services likely to be used by children have further duties | Whether user-to-user features can wait until after the first test |
| Regulated activity | Handling payments, lending, investments or insurance can require authorisation from the financial regulator, or a partnership with a firm that has it | Whether the idea touches regulated activity, before any build |
| Emails to a waitlist | Marketing email to individuals needs their consent, so a waitlist form should ask for it in plain words and keep a record | The wording of the sign-up form |
Four first versions, and what each one tests
Pick the version that answers your riskiest question at the lowest cost.
Investor demo
For raising a first round on something people can click.
- Story and core journey agreed
- Key screens designed
- Interactive demo assembled
- Tested with target users
- Refined for the pitch
Private beta
For learning from a small group before opening the doors.
- Sign-up page with clear consent
- Applicants screened
- Access granted in small groups
- Usage and feedback reviewed weekly
- Go or no-go decision recorded
First revenue
For proving that someone will pay.
- Offer published with a price
- Customer signs up
- Pays by card or Direct Debit
- Uses the core feature
- Renews or tells you why not
Community product with safeguards
For ideas that depend on users talking to each other.
- Profiles created
- Posts and messages enabled
- Report button on every item
- Reports reviewed by a person
- Risk assessment kept up to date
What we build
Discovery
A structured start that tests the idea against real users and trims the scope to one outcome. See product discovery workshops.
Prototype
A realistic, clickable version for interviews and investor meetings, made without writing production code.
Working MVP
A web or mobile product with sign-up, the core feature and payment, written to be extended and not thrown away.
Privacy groundwork
Minimal data collection, a privacy notice that matches the product and the records a small company needs under UK GDPR.
Moderation basics
Reporting, blocking and review tools for products where users interact, sized for a first release.
Handover pack
Repository access, documentation and a record of what was built, organised for an investor's due diligence.
What we need from you
- A plain statement of the problem and who has it
- Your adviser's view on any regulated activity
- Access to prospective users for interviews
- Your budget range and the date that matters
- A founder available for decisions each week
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for a UK MVP
Before development starts
0 of 7 checkedWhat to do next
Send us the problem, the people who have it and what you have learned from them so far. We will propose the smallest build that could settle your riskiest assumption, and be clear about what it would not include. Start a conversation or book a 30-minute call.
Deciding how polished a first version must be? Read our comparison of a prototype and a production-ready MVP.
Common questions
Does a fintech MVP need authorisation from the regulator?
It may. Taking deposits, holding client money, offering credit, arranging investments or selling insurance are regulated activities, and carrying them on without authorisation is an offence. Many startups begin by partnering with an authorised firm, or by designing the first version so that a licensed payment provider handles the regulated part. Take advice before you build, because the answer can change the product's whole shape.
Who owns the intellectual property in an MVP built by a contractor?
Whoever the agreement says. UK copyright law makes the author the first owner of commissioned work, and an assignment has to be in writing and signed, so paying the invoice does not transfer ownership by itself. Raise the point before work begins and take legal advice on the wording. Ownership and licensing terms are defined in the project agreement.
Does the Online Safety Act apply to a small startup?
It can. The Act covers services that let users share content or interact with each other and that have links to the UK, with no exemption for small companies. Duties include assessing the risk of illegal content and giving users a way to report it. Many MVPs sidestep this by leaving user-to-user features out of the first version. Where they are essential, we build the required tools in.
What data protection steps does an MVP need before launch?
Decide what personal data the product needs and collect nothing else. Write a privacy notice that says what you do with it. Identify your lawful basis, keep the data secure and know how you would handle a request or a breach. Check whether you must pay the regulator's data protection fee. An impact assessment is needed if the processing is high risk.
Where to go from here
Related serviceStartup MVP DevelopmentA first version real customers can use