· 6 min read · Updated
Medtech Isn’t Healthtech: What Changes When the FDA Is in the Room
The same four operational categories apply. What sits inside them changes once there’s a regulatory pathway, a quality system, and a clearance date.
Short answer. Medtech needs the same operational foundation as healthtech, plus a layer healthtech lacks: an FDA pathway (510(k), De Novo, or PMA) that shapes engineering, go-to-market timing, and financial reporting. Operations built for a software company miss that layer, and the gap shows late, often as a stalled submission.
“Healthtech” and “medtech” get used almost interchangeably. That’s a mistake worth correcting. The operational infrastructure a digital health company needs and the operational infrastructure a device or diagnostics company needs overlap, but they aren’t the same build. If your company is medtech specifically, it’s worth understanding where the difference actually shows up.
Device founders get a lot of operational advice built for software companies, and most of it doesn’t transfer. The failure tends to surface late, and badly: a submission that stalls because the design history file got assembled after the fact, or a board meeting where the financial reporting is built around revenue for a company that isn’t cleared to sell anything yet. That isn’t a competence problem. It’s a playbook problem.
Where the overlap is real
Every early-stage healthcare company, healthtech or medtech, needs the same operational foundation: org design that doesn’t depend on the founder, a hiring and onboarding process that scales, a financial reporting cadence that survives investor diligence, and a compliance posture that doesn’t get discovered as a gap during a health system sales cycle. That part of the build is close to identical whether you’re shipping software or a Class II device.
Where does medtech diverge from healthtech?
FDA regulatory strategy isn’t optional, and it isn’t a marketing checkbox. A digital health company might navigate HIPAA and call it done. A medtech company operates inside an FDA regulatory pathway (510(k), De Novo, or PMA) that shapes engineering decisions, go-to-market timing, and even how the company structures its cap table around clinical milestones. Operational infrastructure for a medtech company has to be built with regulatory strategy as an input, not an afterthought bolted on before submission.
Quality management systems aren’t a nice-to-have. ISO 13485 and design controls show up far earlier in a medtech company’s life than equivalent quality processes do in pure software, and as of February 2026 the standard is no longer optional at all: the FDA’s new Quality Management System Regulation replaced the old Quality System Regulation and incorporates ISO 13485:2016 by reference. A team still working from a 21 CFR 820 mental model is working from a superseded one. Get this wrong and it doesn’t just create risk. It can stall or kill a submission. That changes what “Process and Cadence” means operationally: design history files, risk management documentation, and change control aren’t bureaucracy layered on top of the real work. For a device company, they are the real work.
The commercialization timeline is longer, and the operational build has to account for it. A healthtech SaaS company can often generate revenue well before achieving full regulatory clearance, iterating with pilot customers along the way. A medtech company frequently can’t sell a cleared product until clearance actually happens. That means the operational and financial infrastructure has to survive a longer runway, with investor reporting that reflects regulatory milestones, not just revenue milestones.
Supply chain and manufacturing enter the picture. Once a device moves toward production, operations now includes supplier qualification, manufacturing controls, and post-market surveillance. That is work a software company never has to touch. This is infrastructure a fractional COO coming from a pure SaaS background often hasn’t built before, and it shows.
Why this distinction matters when you’re choosing who builds your operations
A lot of fractional executive support in healthcare is built around healthtech: digital health, telehealth, remote monitoring, care management software, general “healthcare” operations that never touch FDA regulatory pathways or device quality systems. That’s a legitimate specialty, but it’s the wrong fit for a device or diagnostics company. The operational build for medtech needs someone who understands how regulatory strategy, quality systems, and the commercialization timeline constrain each other, because a decision in any one of them moves the other two. That’s a different starting point from a healthtech operational playbook applied to a device company in the hope that the overlap covers the gap.
What this looks like in practice
The four-category framework (People and Structure, Process and Cadence, Compliance and Risk, and Financial Infrastructure) still applies. What changes is what sits inside each category. Compliance and Risk for a medtech company means FDA regulatory strategy and design controls, not just HIPAA and SOC 2. Financial Infrastructure means investor reporting built around regulatory and clinical milestones, not just revenue. The framework doesn’t change. The content inside it does, and getting that content wrong is expensive.
What it looks like when it’s built right
Regulatory strategy stops being something that happens to the company and becomes an input the company plans around. The design history file is a byproduct of how the team already works, not a scramble in the weeks before submission. Investor updates are built on the milestones you actually control, so a quarter without revenue reads as progress instead of a gap you have to explain.
And when the submission goes in, nobody is reconstructing anything. It’s already there, because it got built that way the first time.
Alden Levy is the founder of Engine No. 9, a fractional COO practice for healthtech and medtech founders from Seed through Series B. He trained as a bioengineer at the University of Pennsylvania and holds an MBA from Wharton.