The beachhead market strategy for a MedTech startup is a deliberate narrowing of the first intended purpose under MDR Article 2(12) so that a single, winnable segment carries the company through its first CE mark. You pick one indication, one user group, one clinical setting, one geography. You write the intended purpose to match that exact scope. You classify under Article 51, build the clinical evaluation under Article 61, and place the device on the market under Article 5. All sized to that narrow purpose. Expansion comes later, as a planned change to the intended purpose, with new conformity assessment scope for the new claims. Narrow first. Expand on purpose. Anything else is an opportunity trap dressed up as ambition.

By Felix Lenhard and Tibor Zechmeister. Last updated 10 April 2026.

TL;DR

  • A beachhead in MedTech is the narrowest defensible intended purpose that still carries a real business. One indication, one user group, one clinical setting, one geography.
  • The intended purpose under Regulation (EU) 2017/745, Article 2(12), is the fulcrum. It is built from the label, the instructions for use, the promotional and sales materials, and the clinical evaluation. Read together as a single picture.
  • A narrow intended purpose narrows the whole regulatory file. Classification under Article 51 is cleaner. Clinical evaluation under Article 61 is smaller. Placing on the market under Article 5 is faster.
  • One indication is not a small ambition. It is the only ambition that fits a startup budget.
  • Opportunity keeps you poor. Every "we could also do X" conversation stretches the intended purpose, which stretches the file, which stretches the timeline, which stretches the runway.
  • Expansion is a change to the intended purpose. Under the MDR, it requires reassessing classification, extending the clinical evaluation, and. Where the claim change is significant. A new or extended conformity assessment by the notified body.
  • A Graz case from Tibor's practice shows how narrowing the first intended purpose moved a company from stalled to shipping without changing the product itself.
  • The beachhead is not wellness-first. The two strategies are cousins. One narrows segment, the other narrows the very category. And they can be combined.

A Graz company that stopped trying to win every room

A small team in Graz came to Tibor stuck. The product was real. The technology worked. The team had a list of ten clinical applications the device might support, and their draft intended purpose was written to cover as many of them as possible. They thought this made the device more valuable. They were wrong in a specific, expensive way.

The wide intended purpose pushed the classification higher. It pulled more GSPRs into scope. It forced a clinical evaluation that would have needed to cover every claimed use, including the ones the team had not yet properly investigated. The notified body scope would have ballooned. The timeline stretched past their runway. The product had not moved one centimetre, and the regulation had already quoted them a quote they could not pay.

The fix was a subtraction on the label, not on the product. Tibor worked through the claims with the founders and narrowed the intended purpose to a single indication, a single user group, and a single clinical setting. The one the team actually had the strongest evidence for. The product did not change. The software did not change. The hardware did not change. The words on the label, in the draft instructions for use, in the sales deck, and in the clinical evaluation plan changed together and coherently.

The classification landed cleaner. The clinical evaluation plan shrank to a scope they could actually finance. The notified body conversation became tractable. They got moving. The nine other applications stayed on a roadmap document. Explicitly labelled as future indications to be added through formal changes to the intended purpose when the evidence and the budget existed. That is a beachhead. Not a small ambition. A sequenced ambition.

What a beachhead actually is in MedTech

In the broader business literature, a beachhead is the first foothold. You pick one narrow segment, win it completely, and use that base to advance into adjacent segments. In MedTech the mechanics are the same, but the leverage point is different. In SaaS you narrow by segment, pricing, and marketing. In MedTech you narrow by intended purpose under Article 2(12), and the regulation amplifies every word of the narrowing into the structure of your entire technical file.

A MedTech beachhead has four dimensions, and the discipline is to narrow on all four at once.

  • One indication. The specific clinical problem the device addresses at launch. Not "respiratory conditions" but, for example, a specific monitoring task in a specific condition. The MDR clinical evaluation under Article 61 is built against the indication. Every indication you add multiplies the clinical evidence burden.
  • One user group. The specific professional or patient population that interacts with the device. Trained clinicians in a hospital setting is a different user group from patients self-administering at home. Usability engineering, labelling, and training materials all key off this.
  • One clinical setting. Hospital, clinic, home, ambulance, operating room. The environment of use changes the risk profile, the electromagnetic compatibility requirements, the infection control expectations, and a dozen other things the technical file has to reflect.
  • One geography. The member state or small cluster of member states where the product goes first. The CE mark is EU-wide in principle, but sales, reimbursement, distribution, PRRC, authorised representative for non-EU manufacturers, and local vigilance expectations all live on top of that.

A narrow beachhead is the combination of the narrowest defensible answer on each of these four dimensions that still gives you a real business. Not the smallest answer. The smallest answer that wins.

How a narrow intended purpose narrows your regulatory burden

The MDR is written in a way that makes intended purpose the lever for almost everything else. Article 2(12) defines intended purpose as the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use, in promotional or sales materials or statements, and as specified by the manufacturer in the clinical evaluation. Four sources, read together, build one picture.

Every downstream obligation reads that picture.

Classification under Article 51 and Annex VIII reads the intended purpose to work out which classification rule applies and at what class. A narrower purpose often lands at a cleaner, lower classification because the rules key off characteristics. Duration of contact, invasiveness, active function, intended condition being treated. That the manufacturer defines through the purpose statement. A wider purpose can pull the device into a higher class because it now covers a use the higher class rules were written for.

Clinical evaluation under Article 61 and Annex XIV reads the intended purpose to define the scope of the evaluation. Every claim inside the purpose statement needs clinical data behind it. A narrow purpose allows a focused evaluation that can often lean on literature, equivalence where defensible, and a targeted clinical investigation. A wide purpose forces clinical data for every claimed indication, every claimed population, every claimed setting. The cost scales with the scope, not with the product.

Placing on the market under Article 5 reads the intended purpose to confirm that the device actually meets the GSPRs for the claimed use. Article 5 is the door into the EU market; the intended purpose is the shape of what you are carrying through that door.

Narrow the purpose, and every one of these doors narrows with it. That is not a trick. It is the regulation behaving exactly as written.

One indication vs. multiple indications

The temptation to claim multiple indications at launch is the single most expensive instinct we see in first-time MedTech founders. The logic feels sound. More indications equals a larger addressable market. A larger addressable market equals a better investor story. A better investor story equals a bigger round. Bigger round equals more runway. Everyone wins.

The regulation reads it differently. Each additional indication adds a clinical sub-evaluation, a set of claims in the IFU, a risk analysis layer, a usability consideration, and a slice of post-market surveillance obligation. Each one is individually small. The cumulative weight is what breaks the project.

Tibor has seen the same pattern more than once. A startup writes an intended purpose covering three indications because the founders believe the product can handle all three. The clinical evaluation needs data for all three. Two of the three have strong published literature. The third does not, and a new clinical investigation would be required. The cost and timeline for that one investigation alone dwarfs the rest of the project.

The honest move in that situation is to drop the third indication from the first intended purpose. Not delete it from the company's future. Drop it from the first purpose. Ship the device for the two indications where the evidence exists. Build revenue. Collect post-market data. Use that foundation to fund the investigation that brings the third indication in later, through a planned change. The device becomes profitable while the original three-indication plan would still have been in clinical investigation.

One indication is not a failure of ambition. It is the ambition the runway can actually pay for.

The "opportunity keeps you poor" discipline

Felix has a line he repeats to founders who cannot let go of the wider market at launch. Opportunity keeps you poor. Every meeting that begins with "we could also do X" is not a meeting about growth. It is a meeting about scope creep wearing a growth costume.

Every time the intended purpose widens by a sentence, the file widens by a chapter. Every chapter costs time. Every unit of time costs runway. Every unit of runway was supposed to be the fuel for shipping, not the fuel for scope discussions. By the time the company has widened the purpose three times. Because one more indication here, one more user group there, one more setting because a pilot hospital asked for it. The project is twice as expensive and twice as slow, the clinical evaluation is a swamp, and the founders are confused about why the regulation keeps getting heavier when the product has not changed.

Scope discipline in MedTech is not a preference. It is the difference between a startup that ships and a startup that runs out of money in its second clinical evaluation. The discipline looks like this.

  • Every proposed addition to the intended purpose gets written down as a separate line item with a separate cost estimate.
  • The default answer to any new claim during the first CE path is not yes. It is "not in this intended purpose." If it survives the roadmap conversation, it becomes a planned future change, not a live edit to the current file.
  • Every "we could also do X" is explicitly translated into the additional clinical evaluation work, classification risk, and notified body scope it would create. Founders stop asking for scope changes once they see them priced.
  • The roadmap for future indications is a real document. It is not a slide. It says which indications the company will add, in what order, with what evidence, and in which planned change to the intended purpose.

The discipline is not austerity. It is sequencing. You are not giving up the bigger market. You are refusing to let the bigger market kill the first market.

How expansion actually works under the MDR

The beachhead strategy only works if expansion is real. Narrowing the first intended purpose is only a good decision if the path from the first purpose to the second is understood and actionable. Otherwise you are not running a beachhead. You are running a permanent retreat.

Under the MDR, expansion is a deliberate change to the intended purpose, with downstream consequences that have to be worked through.

  • The new intended purpose is drafted. Article 2(12) applies to the new version the same way it applied to the old one. The label, the IFU, the promotional materials, and the clinical evaluation all need to tell the new story together.
  • The classification under Article 51 is reassessed. A new indication, a new user group, or a new setting can push the classification into a different class or trigger a different classification rule under Annex VIII. The classification determines everything that follows.
  • The clinical evaluation under Article 61 and Annex XIV is extended. New claims need new clinical data. Literature, equivalence where defensible, or a new clinical investigation. Whichever the evidence actually supports.
  • The technical documentation is updated. The risk file, the GSPR checklist, the usability engineering file, the labelling, the IFU, and the post-market plan all change to match the new purpose.
  • The notified body is engaged for the change. Whether this is a straightforward change notification or a substantial change requiring a new or extended conformity assessment depends on the nature and significance of the modification. The notified body is the referee; the manufacturer is the one who has to make the case in writing.
  • Post-market surveillance data from the first phase is used. The beachhead phase generates real-world data that can feed directly into the expanded clinical evaluation. That is a structural advantage of the beachhead approach over a day-one wide purpose.

Expansion is work. It is less work than trying to cover everything on the first CE path, and it is funded by the revenue from the first phase. That is the whole economic logic of a beachhead.

Common beachhead mistakes

Three failure modes show up repeatedly.

Too narrow. The intended purpose is narrowed to the point that the remaining market cannot support a business. A hundred patients a year across three hospitals is not a beachhead. It is a hobby with a CE mark. The discipline is to narrow to the smallest segment that still wins, not to the smallest segment that fits on a slide.

Too broad. The founders call the strategy a beachhead in the pitch deck but write an intended purpose that still covers three indications, two user groups, and two settings. The label of "beachhead" has been applied to a project that has not actually been narrowed. The regulation does not read labels on pitch decks. It reads the intended purpose in the technical file. If the file is wide, the beachhead is fictional.

Changing too soon. The company finishes the first CE path, ships the device, gets two months of market traction, and immediately starts filing changes to add indications. The post-market data is not mature enough to feed the clinical evaluation extension, the quality system has not stabilised on the first purpose, and the notified body is being asked to process a change to a file that has barely had time to dry. The planned roadmap exists for a reason. The first indication needs to run long enough to earn the second.

All three mistakes come from the same root cause: treating the beachhead as a rhetorical position rather than a set of decisions encoded in the technical file.

The Subtract to Ship angle

The beachhead is a subtraction. You are not adding scope. You are removing every indication, user group, setting, and geography from the first intended purpose that does not earn its place in the first CE path. The remaining intended purpose is the one that traces cleanly through Article 51 classification, Article 61 clinical evaluation, and Article 5 placing on the market. With a file a startup can actually finance and a notified body scope a startup can actually negotiate.

The subtraction is hard because every cut feels like giving up market. It is not. Every cut is compressing the time to the first CE mark, which is compressing the time to the first revenue, which is compressing the time the company stays alive. The widest intended purpose is the one that looks like ambition and behaves like failure. The narrowest defensible purpose is the one that looks like restraint and behaves like shipping. Read the Subtract to Ship framework for MDR for the full methodology that sits behind this move.

Reality Check. Where do you stand?

  1. Can you state your first intended purpose in one paragraph that names one indication, one user group, one clinical setting, and one geography?
  2. Does your current draft intended purpose stretch to cover claims you cannot back with real clinical evidence today?
  3. Have you priced the clinical evaluation under Article 61 against the current intended purpose, or against a narrower purpose you have not yet written down?
  4. Would narrowing the intended purpose change your classification under Article 51 in a way that makes the conformity assessment lighter?
  5. Do you have a written roadmap of future indications, each tied to a planned change to the intended purpose, with the evidence and budget required for the change?
  6. When a stakeholder. Investor, pilot hospital, advisor. Asks you to widen the purpose, do you have a standard answer that protects the beachhead?
  7. Are the four Article 2(12) sources. Label, IFU, promotional materials, clinical evaluation. Currently telling the same narrow story, or is one of them already wider than the others?
  8. Could your post-market surveillance plan actually feed the expansion you are planning, or is it a minimal plan that will leave you without evidence when the time comes to change the purpose?
  9. If you had to ship in twelve months instead of twenty-four, which parts of the current intended purpose would you cut first. And why are they still in?

If more than two of these are weak, the beachhead is not yet sharp enough to survive the first CE path.

Frequently Asked Questions

What is the beachhead market strategy for a MedTech startup? It is the deliberate narrowing of the first intended purpose under MDR Article 2(12) to one indication, one user group, one clinical setting, and one geography. The narrow purpose drives a narrower classification under Article 51, a smaller clinical evaluation under Article 61, and a faster path to placing on the market under Article 5. Expansion is handled later as a planned change to the intended purpose.

How is the beachhead strategy different from wellness-first? The beachhead strategy narrows the segment inside the medical device category. Wellness-first narrows out of the medical device category entirely, by writing an intended purpose that does not meet the Article 2(1) definition. The two can be combined. A wellness-first launch can itself be a beachhead inside the wellness space. But they answer different questions. See wellness first, medical device later.

Can I still expand to the wider market after a beachhead launch? Yes, through a planned change to the intended purpose. The expansion triggers reassessment of classification under Article 51, extension of the clinical evaluation under Article 61, updates to the technical documentation, and engagement with the notified body for the change. Post-market data from the beachhead phase feeds the expanded clinical evaluation directly.

What is the risk of writing the intended purpose too narrowly? The first market may be too small to support a business. The discipline is to narrow to the smallest segment that still wins, not to the smallest segment that fits the evidence. If the narrowed segment cannot generate enough revenue to fund the planned expansion, the sequencing collapses.

How does the intended purpose affect classification under Article 51? Classification rules in Annex VIII apply based on characteristics of the device as described in the intended purpose. Duration of contact, invasiveness, active function, the condition being treated, and so on. A wider intended purpose can pull the device into a rule that yields a higher class than a narrower purpose would.

Does the beachhead approach work for software as a medical device? Yes, and often especially well. Software claims scale almost frictionlessly in marketing but scale painfully in clinical evaluation. A narrow intended purpose on software-as-a-medical-device lets the clinical evaluation focus on the single clinical question the software is answering, rather than every possible use.

What happens if I accidentally drift wider during the first CE path? Every surface where the device is described. Label, IFU, website, investor deck, sales script. Counts under Article 2(12). Drift on any surface pulls the whole intended purpose wider, which pulls the regulatory file wider, which eats the advantage of the beachhead. Audit the four surfaces regularly during the first CE path.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, consolidated text. Articles cited: Article 2(12) definition of intended purpose; Article 5 placing on the market and putting into service; Article 51 classification; Article 61 clinical evaluation; Annex VIII classification rules; Annex XIV clinical evaluation and post-market clinical follow-up. Official Journal L 117, 5.5.2017.
  2. Regulation (EU) 2023/607 of the European Parliament and of the Council of 15 March 2023 amending Regulations (EU) 2017/745 and (EU) 2017/746 as regards the transitional provisions for certain medical devices and in vitro diagnostic medical devices. Official Journal L 80, 20.3.2023.

This post is part of the MedTech Startup Strategy & PMF series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. Narrow first, expand on purpose, and let the intended purpose under Article 2(12) do the work the marketing deck cannot.