HealthTech MVP development
A first version pilot customers can use, built so it survives their security review.
Healthcare changes what a minimum viable product means
A healthcare product touching appointments, notes or intake forms is a regulated system from day one. The expensive decisions are invisible: identity, consent, where data sits, how integration gets added. Most failures are a demo that could not survive the first security review.
What we do for founders
| Stage | What happens | What you get |
|---|---|---|
| Discovery | Understanding the clinical or operational process, the users, the buyer and the constraints | An agreed scope for a first version, and a list of what is deliberately being left out |
| Product definition | Turning that into screens, flows and a data model | Wireframes or a clickable prototype you can show to users and investors |
| Technical planning | Architecture, security model, hosting, integration approach, AI feasibility | A technical plan and a build estimate |
| Build | Design, development and testing in short cycles | Working software you can see throughout, not a status report |
| Pilot readiness | Security review preparation, documentation, monitoring, support arrangements | A product that survives a customer’s due diligence |
| Scale | The work that volume, new customers and new integrations require | Continued development with the same team |
On timelines. We do not publish a fixed number of weeks for an MVP, because it would be a marketing number rather than a commitment. You will get a timeline after technical planning, and we would rather lose a deal than agree to one we cannot meet.
What a first version looks like
Decisions worth getting right early
| Decision | Why it matters later |
|---|---|
| Where data is hosted | Changing region after launch means migration, new agreements and potentially a re-review by every customer |
| How identity and permissions work | Retrofitting role-based access into a product built for one user type is close to a rewrite |
| How consent is captured and withdrawn | Buyers ask, and an answer added afterwards rarely satisfies an information governance review |
| Whether the data model anticipates integration | A model designed around your screens becomes expensive when FHIR mapping arrives |
| Audit logging | Cheap to add at the start, intrusive to add across an existing codebase |
| Whether AI is needed at all | Many early products are better served by rules and good design, with AI added once there is data |
How we engage with early-stage companies
Discovery and technical plan
For founders who need a credible plan and estimate before raising or committing budget.
MVP build
A defined first version to an agreed scope, built for a named pilot customer.
Ongoing product team
Continuous development where priorities change month to month.
Embedded engineers
Individuals joining your team where you have an internal lead but need specific expertise.
Handover support
Building the first version and then transferring it to a team you hire. If that is your plan, we build towards it rather than around it.
Security review support
Preparing for the questionnaire your first enterprise customer will send, ideally before they send it.
Working with founders
Frequently asked questions
Yes, if only to establish what is realistic. A short discovery engagement is inexpensive and frequently changes what a founder decides to build first. If the budget will not cover a viable first version, we would rather tell you that than deliver something that cannot be used.
Yes. Building the product to satisfy that kind of review is straightforward if it is known about early, and painful if it arrives afterwards. Send it to us during planning if you have it.
Yes. Code, infrastructure, documentation and design assets transfer to you, and are handed over in a state another team could pick up.
That is a normal outcome and we plan for it. Documentation, sensible structure and a proper handover are part of the work rather than a favour at the end.
Tell us what you are building
Bring the idea, the first customer you have in mind and any constraints you already know about. The first conversation is with an engineer.