"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. We don't publish prices for medical work, and you should be wary of anyone who quotes a number before they understand your intended use. But "it depends" isn't useful for planning either, so here is what actually moves the budget, the tiers projects fall into, and how to plan without nasty surprises.
The tiers, at a glance
| Scope | Example | What drives the budget |
|---|---|---|
| Compliant MVP | Focused patient intake or a single-workflow tool | Compliance from day one, few integrations |
| Mid-sized product | Portal + integrations + reporting | Number and quality of integrations |
| Telemedicine platform | Video, scheduling, records, payments | Whether it holds clinical records |
| Enterprise platform | Multi-site EHR-connected system | Multi-site rollout and EHR integration |
The gap between these tiers 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 against a well-documented endpoint is the predictable case; custom bidirectional or legacy HL7 v2 connector work can easily cost twice as much or more.
- 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.
Want a real number for your project? Neurova AI scopes custom medical software with compliance costed in from the start, no surprise retrofits. Tell us what you want to build and we'll come back with a written scope, a fixed price and a date.
Frequently asked questions
How much does custom medical software cost in 2026? There is no honest single number, because a focused patient-intake tool and a multi-site platform connected to hospital records are different orders of project. The budget is set mainly by the clinical risk class (a medical device brings a quality management system, clinical evaluation and a notified body), the integrations, whether AI sits in the clinical path, and the security regime. Compliance and security requirements usually add roughly 20–50% on top of a comparable non-regulated build.
Why is medical software more expensive than a normal app? Regulated software carries overhead a normal app does not: a quality management system, risk management, IEC 62304 lifecycle documentation, clinical evaluation, security hardening, and audit-grade logging. Skipping these upfront typically costs far more to retrofit later.
How much does FHIR or EHR integration cost? It depends on the systems at the other end. A standard FHIR integration against a well-documented endpoint is the predictable case. Custom bidirectional integrations or legacy HL7 v2 connector work can easily cost twice as much or more, because mapping, testing and error handling grow with every system involved.