Healthcare innovation does not follow a single route. A promising idea may require an experiment, a software product, a structured pilot or a separate company. Choosing the wrong vehicle too early can create unnecessary cost, governance complexity and unrealistic expectations.
Start with the decision, not the format
Before asking whether to build an MVP, corporate teams should define what remains uncertain. Is there a relevant problem? Will professionals adopt the proposed workflow? Is a solution technically feasible? Can it meet procurement and data-protection requirements? Will a customer pay for it? Each question needs a different kind of evidence.
A well-designed innovation programme makes these uncertainties explicit, assigns owners and agrees what evidence will justify the next investment decision.
When an MVP is the right instrument
A minimum viable product is useful when a focused set of features can test a product assumption with intended users. The MVP should not attempt to reproduce a mature platform. Its purpose is to determine what must be learned next.
In digital health, the minimum necessary scope still depends on security, privacy, interoperability and applicable regulatory obligations. If the intended functionality creates medical-device implications, those cannot be postponed merely because the product is described as a prototype.
Our digital health validation playbook describes how to define the questions that a product experiment should answer.
When to move from MVP to a pilot
A pilot tests the solution in a specific operational environment. It is appropriate when there is enough product maturity to evaluate use under realistic conditions, together with clearly authorised access to staff, infrastructure and any necessary data.
Pilot success cannot be reduced to the number of participants. The evaluation may include adoption, task completion, implementation time, user satisfaction, operational impact and, where appropriate, clinical outcomes. Baseline measures and stop/go criteria should be agreed before launch.
Our guide to go-to-market and healthcare pilots explains why successful pilots need a commercial pathway.
When a spin-off becomes worth considering
A spin-off is an organisational decision, not a reward for finishing a pilot. It may be appropriate when a solution has a market beyond the parent organisation, requires dedicated leadership and investment, and can operate under a credible legal, commercial and governance structure.
Intellectual property, licensing, the role of the corporate partner, commercial rights, capital needs, regulatory responsibilities and team incentives should be addressed explicitly. None of these arrangements needs to follow a fixed equity formula.
A practical sequence for corporate teams
- Problem discovery: establish the affected users, current alternatives and business relevance.
- Feasibility and validation: test demand, the technical route and key constraints.
- MVP: build only what is necessary to test critical assumptions.
- Pilot: evaluate the product in an authorised real-world setting with predefined indicators.
- Scale decision: integrate, expand, license, spin off, revise or stop.
How Ventures as a Service can help
With Ventures as a Service, a corporate partner can access venture design, technology delivery and pilot-execution capabilities while retaining an appropriate role in strategic decisions. The structure of each collaboration, including any investment or equity arrangement, depends on the opportunity and the agreed contracts.
Frequently asked questions
Is a pilot always necessary before a spin-off?
No. The required validation depends on the product, market and risk profile. However, a spin-off decision should be based on sufficient evidence rather than enthusiasm alone.
Can an MVP be tested without patient data?
Often yes. Mock data, synthetic environments and workflow prototypes may answer early design questions. Any later use of real health data requires the corresponding legal basis and safeguards.
What if the pilot produces mixed results?
Review the original hypotheses. A decision to iterate, narrow the intended use or discontinue the initiative can be more responsible than pursuing scale prematurely.
Next step: explore how GooVentures works with corporate innovation teams to assess opportunities, develop products and define evidence-led venture decisions.
