The Short Answer
How should an established company build an MVP?
As a small, time-boxed project with one named decision-maker, a budget approved only for the MVP stage, a written hypothesis and success metric, and security and legal review agreed in advance. Keep the team and scope small, test with a subset of real customers, and decide at the end whether to scale, change or stop.
Why Small Projects Win Inside Big Companies
The evidence for keeping new product work small is strong. The Standish Group's CHAOS Manifesto 2013 found that 76% of projects under $1 million in labour succeeded in 2012, against 10% of projects over $10 million, using a strict definition of on time, on budget and with the required features. A McKinsey and University of Oxford study of more than 5,400 IT projects found large projects ran 45% over budget and 7% over time on average, while delivering 56% less value than predicted.
New products inside established companies tend to grow into large projects, because every department has a requirement to add. An MVP is a deliberate way to stay in the small-project category until the idea has earned a bigger one.
What Is Different From a Startup MVP
| Startup | Established company | |
|---|---|---|
| Biggest risk | Running out of money | Running out of patience, or scope growing |
| Customers | Has to find them | Has them, and must protect the relationship |
| Brand | Nothing to lose | A failed experiment is visible |
| Decisions | Founder decides | Several stakeholders, often sequential |
| Data and security | Light, at first | Existing policies apply from day one |
| Success | Survival | A business case for further investment |
The advantages are real: access to customers for testing, a sales channel, and budget. The job is to use them without importing the process that makes large projects slow.
Governance That Does Not Stall the Build
- Approve the stage, not the product. Fund the MVP with a fixed budget and a decision point. Asking for approval of the full product up front invites full-product scope.
- One accountable owner. A person who can make product calls within a day. Committees add weeks.
- Agree review windows in advance. Security, legal and brand review with turnaround times agreed before the build starts.
- Start the document with the customer. Amazon's working backwards process, described by its CTO in 2006, starts with a press release and FAQ for the finished product, then works back to the minimum needed. It is a useful way to get stakeholders to agree what the MVP is for before anyone argues about features.
- Use test data first. A sandbox or synthetic data avoids the longest security reviews in the early weeks.
The UK government, one of the largest organisations in the country, works this way on new services: a time-boxed discovery, prototypes in alpha, and a private beta with a limited group before opening to everyone.
In-House, Separate Brand or Spin-Out
| Structure | Best when | Watch out for |
|---|---|---|
| In-house, existing brand | The product extends what customers already buy | Existing processes and brand rules applying in full |
| Separate brand or domain | You want to test without risking the main brand | Customers may still connect it to you |
| Spin-out or new entity | The product may serve a different market or raise its own funding | Legal set-up time; IP must be assigned clearly |
Whichever structure you choose, the code and IP must belong to the right legal entity from the start. If an outside partner builds it, an assignment of copyright is only effective in writing and signed, under the Copyright, Designs and Patents Act 1988, s90(3). See software development contracts.
Readiness Check
Interactive checklist
Is your organisation ready to run an MVP?
Tick what is already agreed. Anything unticked is likely to slow the MVP down more than the build itself.
0 of 10 in place
Not yet. Agree the decisions and governance items first; starting the build without them usually means weeks of waiting mid-project.
A Practical Sequence
- 1
Write the press release and FAQ
One page describing the finished product from the customer’s side. Use it to agree the hypothesis with sponsors.
- 2
Fund the MVP stage only
A fixed budget, a named owner, and a decision date.
- 3
Clear governance before the build
Security, legal and brand review windows agreed; test data in place.
- 4
Build small and fast
A focused team or a fixed-price external partner, with weekly demos to the owner. See the MVP development process.
- 5
Test with a subset of customers
Invite a defined group, with consent, and measure the success metric.
- 6
Decide and hand over
Scale, change or stop. If it continues, agree who runs it and how the code passes to that team.
For the stages in more detail, see the MVP development process and how to scope an MVP. Loomstrat Studio works with established companies spinning out a new SaaS product that needs a production first release, on a fixed price with full handover; see MVP development or SaaS platform development.
Frequently Asked Questions
Can large companies build MVPs?
Yes, and the evidence favours it. The Standish Group found 76% of projects under $1 million in labour succeeded in 2012, against 10% over $10 million. An MVP keeps a new product in the small-project category until it has earned more investment.
How is an enterprise MVP different from a startup MVP?
The enterprise has customers, brand and budget to protect, more stakeholders, and security and data policies that apply from day one. The main risk is scope growing and decisions slowing, rather than running out of money.
Who should own an MVP inside a large company?
One named person with authority to make product decisions quickly and a budget approved for the MVP stage. Decisions by committee are the most common cause of delay.
Should a corporate MVP use the main brand?
Use the main brand when the product extends what customers already buy. Use a separate brand or domain when you want to test without risking the main brand, or a spin-out when the product may serve a different market.
What is the working backwards method?
Amazon’s product definition process, described by its CTO Werner Vogels in 2006: write the press release first, then an FAQ, then the customer experience and user manual, and work back to the minimum technology needed.
Should an established company use an external partner to build an MVP?
Often, when the internal team is committed to existing products or the MVP needs to move faster than internal processes allow. Agree a fixed scope and price, weekly demos and a written IP assignment to the right legal entity.
The advantage of an established company is not speed, but it does not need to be. It needs a small enough project, a clear owner and the discipline to stop if the answer is no.