Don’t start with the 510(k): a founder’s guide to medical device regulatory strategy.

i. The default 510(k) trap

Most first-time medical device founders learn the regulatory landscape in roughly this sequence:

1. They build a product.
2. Someone — an advisor, an investor, a consultant, a friend with industry experience — tells them it’s a Class II device.
3. They search "Class II FDA pathway" and discover the 510(k) submission process.
4. They build a roadmap around 18–26 months of work and $150–350K of regulatory, clinical, and quality spending.
5. They go raise capital to fund that roadmap.

Each step makes sense individually. The problem is the sequence itself: it locks in an assumption that may not be true — that the only path to market is the regulatory pathway the founder first encountered.

In practice, most products have multiple viable regulatory paths. The cheapest and fastest path is often available if the product’s intended use and claims are scoped strategically. The trap isn’t the 510(k) itself; it’s never asking whether a 510(k) was necessary in the first place.

This matters because the cost of getting it wrong compounds. A founder who commits to a 510(k) before doing the regulatory analysis ends up:

• Raising more capital than necessary, diluting equity sooner
• Spending 12–18 months on a QMS, testing, and submission preparation that could have been a 2–3 month exercise
• Delaying real customer feedback and revenue by 12–24 months
• Reducing optionality — once you’ve told FDA "this is a Class II device," walking it back is hard
• Increasing investor risk, which shows up in valuation

The financial impact for an early-stage company is rarely just the $200K of regulatory spend. The opportunity cost — lost market timing, deferred learning, additional runway burn — is usually larger.

ii. Regulatory strategy is downstream of business strategy

The smarter mental model: your FDA regulatory pathway is a function of three business inputs, not a starting point.

1. What your business needs to accomplish in the next 6–12 months. Proof of concept? Recurring revenue? A clinical study to support a future submission? An acquisition conversation?
2. How much capital is available — or could realistically be raised — to spend on regulatory, quality, and clinical work.
3. What claims you actually need to make to generate that revenue or evidence.

Once those three things are clear, the regulatory pathway becomes a derived answer rather than a starting assumption.

Here’s the principle in plain language: every claim you make about your product has a regulatory cost. Bigger claims, bigger costs. The right question for a founder isn’t "what does FDA require for the full product vision?" It’s "what’s the smallest claim that gets us to the next business milestone?"

Regulatory strategy isn’t about minimizing what you tell FDA. It’s about matching the regulatory burden you take on to the business value you can extract from each phase.

iii. The regulatory ladder: three phases

Here’s how the principle plays out in practice. Stage your regulatory burden in three phases, where each phase’s burden is justified by the business milestones the previous phase achieved.

Phase 1: Launch as a non-device

In many cases, a product can launch today — with no FDA regulation at all — if its claims are scoped narrowly enough. Several major exclusions and exemptions exist:

• General wellness exclusion. Products that promote general wellness (fitness, stress management, sleep, mindfulness, weight management for general health) without claims about specific diseases or conditions. FDA’s guidance "General Wellness: Policy for Low Risk Devices" lays out the criteria.
• Clinical Decision Support (CDS) exclusion. Software functions that support healthcare professionals’ decision-making, where the professional can independently review the recommendation and the software discloses its reasoning. Codified at Section 520(o)(1)(E) of the Federal Food, Drug, and Cosmetic Act.
• Low-risk software exclusions. A range of software functions explicitly carved out under Section 520(o) of the FD&C Act — including hospital administrative software, electronic health records, and certain wellness and lifestyle applications.
• Mobile medical applications. FDA’s mobile medical applications guidance outlines which mobile apps are regulated as devices and which fall outside FDA’s scope.

The goal of Phase 1 isn’t to avoid being a medical device forever. It’s to launch something — generate revenue, prove demand, get user data, build distribution — while your claims are still flexible.

This phase typically costs $5,000–$25,000 in regulatory analysis and claim review, with a timeline of 2–6 months including product launch preparation. For software products, this often means scoping the initial release to fit one of the exclusions and then designing the product architecture to accommodate expanded functionality later without major rework.

Phase 2: Expand to Class I

With revenue and proof of demand from Phase 1 in hand, you can justify the next step: expanded claims that put your product in Class I — the lowest-risk regulated category.

Most Class I devices are 510(k)-exempt, which means they require:

• FDA establishment registration (annual fee approximately $9,280 for FY2026)
• Device listing
• Compliance with general controls: labeling, basic manufacturing requirements, complaint handling, medical device reporting
• A QMS scoped to Class I requirements — lighter than a full ISO 13485 implementation but with the core elements in place

This lets you make some therapeutic, diagnostic, or treatment-related claims while staying out of the 510(k) submission process entirely. For many digital health products, monitoring devices, and adjunct accessories, Class I is the right destination — not a stepping stone.

Phase 2 typically costs $25,000–$75,000 for QMS setup, registration, listing, and initial compliance, with a 3–6 month timeline.

Phase 3: Graduate to Class II

By the time you reach Phase 3, you’ve validated demand, generated revenue, and ideally raised the funding that justifies the cost of a full 510(k) premarket submission. Now the regulatory burden is justified by the business case rather than being assumed as a starting cost.

This is where the original "default" pathway becomes appropriate — but you’ve arrived at it on your own terms, having already proven the market, captured users, and built the company that can absorb the cost.

For Class II / 510(k):

• Full ISO 13485:2016 / 21 CFR Part 820-aligned QMS (now harmonized under FDA QMSR as of February 2026)
• Predicate device identification and substantial equivalence argument
• Performance testing, often including clinical data depending on device type
• 510(k) submission preparation, typically 6–9 months
• FDA review and response cycle, typically 3–6 months from submission
• Post-clearance compliance: post-market surveillance, MDR reporting, ongoing QMS maintenance

Total cost: typically $150,000–$350,000 over 12–26 months, plus ongoing operating costs of $50K–$150K per year.

iv. Case study: how this saved one client $190,000

An anonymized example from our practice illustrates the principle concretely.

Before the analysis

The client came to us convinced their software product was a Class II medical device requiring a 510(k) submission. Their plan was to spend 18–26 months and $200,000 on the regulatory and quality work needed to clear the device, then commercialize.

They had raised seed funding partially against this plan, with their Series A pitch built around FDA clearance as the key milestone.

The analysis

We conducted a structured regulatory analysis:

1. Mapped the intended use and claims against FDA’s device definition in Section 201(h) of the FD&C Act.
2. Identified the Clinical Decision Support exclusion under Section 520(o)(1)(E) and the related FDA guidance "Clinical Decision Support Software." The product fell under one of the four CDS carve-outs introduced by the 21st Century Cures Act.
3. Drafted and submitted a 513(g) request — a formal mechanism for asking FDA to confirm regulatory status in writing.

The outcome

FDA responded in writing confirming that the product was not a medical device under Section 201(h), citing the CDS guidance. The client was free to launch with no QMS, no FDA registration, no 510(k) submission, and no ongoing compliance burden.

Net result: approximately $190,000 in regulatory cost avoided and ~15 months of runway preserved. More importantly, the client could launch and start generating revenue immediately, putting them in a stronger position for their Series A conversation than the original plan would have.

v. The mechanics: 513(g), claims, and exclusions

What is a 513(g) request?

A 513(g) is a formal mechanism, named for Section 513(g) of the Federal Food, Drug, and Cosmetic Act, that lets a sponsor ask FDA in writing whether their product is a medical device — and if so, what classification it falls under. The response is binding, written, and citable.

For FY2026, the standard 513(g) FDA user fee is approximately $5,961, with a small business discount available that reduces it to approximately $2,981 for qualifying companies. Preparation typically costs another $5,000–$15,000 in regulatory work depending on complexity. FDA’s target response time is 60 days from acceptance.

When to use a 513(g):

• Your product is genuinely ambiguous — it could be a wellness product, it could be a device, and the answer materially affects your plans
• You want regulatory certainty before raising capital, going to market, or entering acquisition conversations
• You need a defensible written answer to give investors, partners, customers, or your board
• Your competitive landscape includes both regulated and unregulated products doing similar things, and you want clarity on where you sit

When not to use one:

• Your product is clearly a regulated device with established predicates — the answer is already known and FDA will simply confirm it
• The cost and timeline of a 513(g) aren’t justified by the business question being answered
• You’re asking for permission to do something FDA has already addressed in published guidance

How claims drive classification

Two products with identical hardware and software can have wildly different regulatory classifications based purely on the claims their makers attach to them. A heart rate sensor sold as "tracks your wellness" is a consumer product. The exact same sensor sold as "detects atrial fibrillation" is a Class II medical device. A sleep tracker marketed for "better sleep habits" is unregulated; the same tracker marketed for "diagnosing sleep apnea" requires a 510(k).

This isn’t a loophole or a workaround — it’s how FDA’s risk-based regulatory system is designed to work. The regulation scales with the claim because the claim drives the risk profile. A misdiagnosis of atrial fibrillation has clinical consequences; an inaccurate wellness score doesn’t.

The implication for founders: writing your intended use statement is one of the highest-leverage regulatory decisions you’ll make. Get it wrong by being too expansive, and you’ve signed up for a 510(k) you didn’t need. Get it right by scoping precisely to what your business actually requires today, and you can launch with the lightest possible regulatory burden — while preserving the option to expand later.

Some practical tactics:

• Separate the marketing claim from the regulatory claim. Your website can talk about benefits and outcomes; your intended use statement should be narrow and clinical. They don’t need to be identical.
• Avoid disease-specific language in Phase 1 unless you need it for revenue.
• Avoid "diagnosis," "treatment," "prevention," and "cure" when "track," "monitor," "support," or "general wellness" will do.
• Test the language by asking: "If FDA read this in isolation, would they conclude we’re making a medical device claim?"

Exclusions worth knowing

The four most commonly applicable carve-outs for early-stage health and digital health products:

1. General Wellness. FDA guidance "General Wellness: Policy for Low Risk Devices" defines what qualifies as a general wellness product and outlines the conditions under which FDA will not enforce regulatory requirements.
2. Clinical Decision Support (CDS). Section 520(o)(1)(E) of the FD&C Act and FDA’s "Clinical Decision Support Software" guidance describe the four criteria a software function must meet to fall outside FDA device regulation. The four criteria are restrictive but workable for many use cases.
3. Mobile Medical Applications. FDA’s mobile medical applications guidance lays out which mobile apps are regulated as medical devices and which fall outside FDA’s scope.
4. Low-risk hospital administrative software. Sections 520(o)(1)(A)–(D) of the FD&C Act exclude software for hospital administrative functions, certain electronic health records functions, and general health and wellness from device regulation.

A thorough regulatory analysis evaluates whether your product can credibly fit into one of these carve-outs given the claims you intend to make. Often the answer is "yes, if you adjust the claims this way."

vi. When the ladder doesn’t apply

Honesty matters here: some products genuinely cannot be staged this way.

If you’re building an implantable cardiac defibrillator, an insulin pump, a surgical robot, or any device whose intended use is intrinsically high-risk and unambiguously medical, you don’t have a "non-device" version. The product’s function is clinical at its core, and the regulatory pathway is not optional.

For those products, the strategic question shifts from "which pathway?" to "which predicate device gives us the cleanest 510(k) story?" or "do we need a De Novo classification or a PMA?" The principle of aligning regulatory burden with business stage still applies, but the floor is higher and the optionality is narrower.

The ladder strategy is most useful for:

• Software-driven products — digital health, wellness apps, remote monitoring, decision support
• Products with reasonable consumer or general-health applications — where the same technology could serve a wellness market and a clinical market with different claims
• Products whose differentiated claims are clinical but whose core function isn’t — for example, a wearable that records data passively but is marketed for specific conditions
• Products in adjacencies to regulated spaces — digital therapeutics, telehealth platforms, AI-assisted clinical workflows, remote patient monitoring

If you’re not sure whether your product fits, a 60-minute regulatory conversation can usually answer it. You don’t need a full analysis to know whether the staged approach is on the table.

vii. What founders should actually do

If you’re a medical device founder reading this and recognizing parts of your own situation, here’s the practical sequence:

1. Conduct a regulatory analysis before allocating any regulatory budget. Cost: $5K–$15K. Outcome: a written assessment of every viable pathway for your product and the claims associated with each. This is the highest-leverage $10K you can spend in the company’s first year.
2. Decide what milestone matters most in the next 12 months. Revenue? Clinical evidence? Investor confidence? Acquirer interest? Match the regulatory pathway to that milestone, not to the full product vision. The full vision’s regulatory cost is tomorrow’s problem.
3. Write your intended use statement with discipline. Every word adds or removes regulatory burden. Treat it like contractual language. Have it reviewed by someone who’s read FDA’s actual decisions and not just the public-facing guidance.
4. Build in optionality. Design your product architecture so that expanding claims later doesn’t require re-engineering the software, the QMS, or the data infrastructure. The expensive part isn’t the first launch — it’s having to redo foundational work when you graduate to the next phase.
5. Re-evaluate annually. The regulatory landscape evolves. The CDS exclusion didn’t exist in its current form before 2016. The General Wellness guidance was updated significantly in 2019. The FDA QMSR took effect in February 2026. New carve-outs, new pathways, and new FDA programs appear regularly; your strategy should be checked against them at least once a year.
6. Tell investors the staged strategy. Sophisticated medical device investors understand and respect this approach — it shows capital discipline and strategic thinking. Unsophisticated investors may need education, but the ones who get it will fund you faster and at better terms than the ones who don’t.

viii. Common questions

How much does a 510(k) actually cost?

For a medical device startup, the total cost of a 510(k) submission — including QMS implementation, testing, predicate research, submission preparation, FDA user fees, and a year of post-clearance compliance — typically runs $150,000 to $350,000. The FDA standard user fee alone is approximately $24,335 for FY2026, with a small business discount bringing it to approximately $6,084 for qualifying companies.

What’s the difference between a 513(g) and a Pre-Submission (Q-Sub)?

A 513(g) asks FDA whether your product is a device and what its classification is. A Pre-Submission (Q-Sub) is a meeting request for feedback on a planned submission — typically used when you already know you’re going to submit and want FDA’s input on your approach. They serve different purposes; a 513(g) is for clarifying status, a Q-Sub is for refining a known plan.

Can I market my product as “FDA registered” if I’m Class I?

You can state factually that your company is FDA registered and your device is listed with FDA, but you cannot imply this is an FDA endorsement, clearance, or approval. FDA has issued warning letters to companies that conflate registration with clearance. Be precise with the language and review marketing copy with regulatory eyes.

Does the FDA QMSR change anything for early-stage companies?

The QMSR took effect February 2, 2026, aligning U.S. 21 CFR Part 820 with ISO 13485:2016. For startups, the practical effect is that a single ISO 13485-aligned QMS now satisfies both U.S. and most international requirements, simplifying global expansion. If you were planning to build a Part 820 QMS, you should now build to ISO 13485:2016 with the FDA-specific layered requirements identified separately.

What if my advisor or investor insists we file a 510(k)?

This happens. Two approaches: first, do the regulatory analysis anyway — the cost is small and the written analysis gives you a basis for an informed conversation rather than a debate of opinions. Second, if the analysis shows the 510(k) is unnecessary, present it as preserving optionality rather than avoiding the work. You can always file later; you can’t easily get back the runway you spent on premature submission.

How does ISO 13485 fit into this?

ISO 13485:2016 is the international quality management system standard for medical devices, now harmonized with FDA’s QMSR. In the ladder framework: Phase 1 typically requires no QMS at all. Phase 2 requires a Class I-scoped QMS (lighter than full ISO 13485). Phase 3 requires a full ISO 13485-aligned QMS. If you’re planning to graduate eventually, designing your initial QMS to ISO 13485’s structure — even before you fully implement it — makes scaling much easier.

What about international markets — EU, UK, Canada, others?

The ladder strategy is U.S.-focused, but the underlying principle (match regulatory burden to business stage) applies internationally. Each market has its own equivalents to the exclusions discussed here. The EU MDR has Class I self-certification with similar logic to FDA’s Class I exemptions, though with different specifics. A regulatory strategy that’s serious about international markets needs to map each phase against each target geography. That’s a deeper exercise than this article covers.

Closing

The 510(k) isn’t the enemy. Building a roadmap around it before you’ve done the analysis is.

Most expensive regulatory mistakes don’t come from doing the wrong work. They come from doing the right work for the wrong question. "How do we get our product cleared?" is a useful question, but it’s the second question. The first question is: "What does our business actually need to accomplish in the next 12 months, and what’s the smallest regulatory burden that gets us there?"

Get the first question right, and the second question gets dramatically cheaper.