Home / Insights

What does it cost to develop a medical wearable? The cost drivers, phase by phase

Every team asks how much a medical wearable will cost before they ask anything else. The honest answer depends on a handful of decisions, and most of them can be made early.

There is no price list for a medical device, because two devices that look alike can carry very different risks and requirements. What we can do is show where the money and time go, so you can estimate your own project and ask suppliers the right questions.

The five phases and what drives each

PhaseTypical lengthWhat drives the cost
Feasibility2–4 weeksHow many sensors must be proven, and whether data from real people is needed before deciding.
Prototype2–4 monthsCustom board or development board, number of board revisions, enclosure complexity, and whether one or two apps are needed.
Verification and pilot2–6 monthsBench testing against reference equipment, number of pilot units, and the size of the study.
Certification6–18 monthsDevice risk class, target markets, clinical evidence needed, and test lab work for safety, EMC, biocompatibility and radio.
Manufacturing transfer2–6 monthsVolumes, test fixtures, supplier qualification and a quality system that a certified manufacturer accepts.

The lengths are typical planning ranges for a small wearable with one to three sensors, not quotes. Certification is usually the longest and least predictable phase, and the one most often missing from early budgets.

Six decisions that move the cost most

  1. What the device claims. A wellness device that shows heart rate is a different product, legally, from one that detects arrhythmia. The intended use sets the risk class, which sets the testing and evidence.
  2. How many sensors. Each sensor adds hardware, firmware, algorithms, tests and its own failure modes. ECG plus SpO₂ plus motion is three projects that must work together.
  3. Wear time. A device worn for one hour and one worn for ten days need different batteries, adhesives and power budgets.
  4. Where the signal is processed. On the device, on the phone or in the cloud. Each choice moves effort between firmware, app and backend.
  5. Markets. India, Europe and the US each have their own approvals for the device and its radio. Each additional market adds work.
  6. Starting point. A blank page, a development board, or a working prototype.

Where a working prototype saves money

The early phases are where most wearables lose months: getting a clean signal from the skin, through the firmware and over Bluetooth, to an app that shows it correctly. Starting from a prototype that already does this, such as our Hridya ECG and SpO₂ patch, shortens feasibility and the first prototype round. It does not remove certification, but it means the budget goes into your product instead of re-solving known problems.

Rule of thumb: fix the intended use and the target markets before you ask for a quote. They change the estimate more than any technical choice.

How to get a useful estimate

  • Write one paragraph on who wears the device, for how long, and what decision it supports.
  • List the signals you need and the ones that would be nice to have.
  • Name your first market and your expected pilot size.
  • Ask for a fixed price for the first phase only. A good partner can price feasibility exactly and the later phases as ranges that narrow as you go.

That is how we work: a fixed-price first step, then each later phase quoted when the previous one ends. See how we work and the standards map for what certification involves.

Timelines are typical planning ranges, not quotes. Every project is estimated in writing after a first conversation.

Want an ECG and SpO₂ patch under your own brand?

Our prototype, Hridya, already records ECG, SpO₂ and motion and streams them to its own app. Develop it with us into your product, or let the same team build your own device.

Start a conversation Develop Hridya