"How much will it cost?" is the first question every founder and practice manager asks — and the honest answer is "it depends," because a patient-intake tool and a Class IIb diagnostic platform live in different universes. But "it depends" isn't useful for planning. So here are real 2026 ranges, the factors that move them, and how to budget without nasty surprises. Figures are indicative and expressed in euros for European buyers.
The ranges, at a glance
| Scope | Typical range | Example |
|---|---|---|
| Compliant MVP | €45k–€90k | Focused patient intake or a single-workflow tool |
| Mid-sized product | €120k–€400k | Portal + integrations + reporting |
| Telemedicine platform | €60k–€1M+ | Video, scheduling, records, payments |
| Enterprise platform | €1M+ | Multi-site EHR-connected system |
The spread is wide because medical software cost scales with clinical risk, integrations, and compliance — not screen count.
The compliance premium is real — and non-negotiable
Building regulated healthcare software carries overhead a normal app does not: a quality management system, risk management, IEC 62304 lifecycle documentation, security hardening, and audit-grade logging. Expect compliance and security to add roughly 20–50% on top of a comparable non-regulated build.
The budget-wrecker: a quote that excludes compliance infrastructure isn't cheaper — it's a deferred expense. Retrofitting HIPAA/GDPR-grade security and documentation mid-project routinely costs 30–50% of the original build budget once discovered. Security architecture belongs on day one, not after the demo.
What actually drives the number
- Clinical risk class. A Class IIa/IIb SaMD needs a notified body, clinical evaluation, and a full QMS — a step-change in cost over a non-device tool.
- Integrations. A standard FHIR integration typically runs €20k–€40k; custom bidirectional or legacy HL7 v2 connector work can exceed €80k.
- AI features. Model development, validation, and EU AI Act obligations add data-governance and monitoring cost.
- Security & compliance regime. NEN 7510 and GDPR in the Netherlands, plus EU hosting and access logging.
- Interoperability scope. EHDS readiness and standardized APIs.
- Run costs. Hosting, monitoring, support, and post-market surveillance — budget 15–25% of build cost per year.
Build vs. buy vs. custom
Not everything should be custom. For commoditised needs — an AI scribe, generic scheduling — off-the-shelf is often faster and cheaper. Custom earns its keep when your workflow is your differentiator, when integrations are deep, or when no vendor fits your clinical model. A good partner will tell you honestly where to buy and where to build.
How to budget sensibly
- Start with intended use and risk class — it sets the compliance floor.
- Scope an MVP that is compliant from day one, not a prototype you'll rebuild.
- Price integrations separately — they're often underestimated.
- Reserve 15–25% for run and post-market costs.
- Insist compliance is in the quote — if it isn't, the number is fiction.
Frequently asked questions
How much does custom medical software cost in 2026? Roughly €45k for a compliant MVP up to €3M+ for enterprise platforms, with mid-sized products commonly €120k–€400k. Compliance typically adds 20–50%.
Why is it more expensive than a normal app? Regulated software needs a QMS, risk management, lifecycle documentation, clinical evaluation, and hardened security — costly to retrofit if skipped.
How much does FHIR/EHR integration cost? A standard FHIR integration is commonly €20k–€40k; custom or legacy HL7 v2 work can exceed €80k.
Want a real number for your project? Neurova AI scopes custom medical software with compliance costed in from the start — no surprise retrofits. Book a call and we'll give you an honest range.