How to choose an engineering partner for a medical device under MDR

Almost every medtech startup we've spoken with in the last 20 years arrives with the same question: should we hire a freelancer, build an in-house team, or work with an external engineering partner? The answer shapes the timeline, the budget and, in many cases, the regulatory viability of the project.

A medical device under MDR — whether Class I, IIa, IIb or III, including electrocardiographs, patient monitors, non-invasive imaging devices or rehabilitation equipment — is not a consumer electronics product with more paperwork. It is a regulated product under Regulation (EU) 2017/745 (MDR), with technical, clinical and quality management requirements that do not allow shortcuts.

Choosing the wrong engineering partner can extend your product's time-to-market by 12 to 24 months. Choosing right can save you that window and, more importantly, spare you a regulatory deviation that forces you to rebuild the entire technical file.

In this article we review the 5 criteria we consider non-negotiable when choosing an engineering partner for a medical device under MDR, the red flags we've seen repeated across the sector, and the specific questions you should ask at the first meeting.

Why the right partner makes the difference

Developing a medical device under MDR requires coordinating three disciplines simultaneously: electronic hardware design, embedded firmware, application software, and — in parallel — all the technical documentation required by the Regulation. Each layer has its own traps.

A common mistake in early-stage startups is to assume that the main problem is technical. In reality, the main problem is traceability and documentation. You can have the best functional prototype on the market, but if you can't demonstrate the documentary trail — requirements, specifications, verifications, validations — the Notified Body will not approve the CE mark.

An engineering partner with real experience in regulated products doesn't just deliver a prototype. They deliver a prototype plus the associated documentation, ready to be incorporated into the client's technical file. This difference, invisible at the first meeting, is what separates an 18-month development from a 36-month one.

The 5 key criteria for choosing an engineering partner

1. Current, audited ISO 13485 certification

The ISO 13485 standard defines the quality management system specific to medical devices. It is not optional: if your partner is not certified, the documentation they generate for your product does not fit what you need to present to the Notified Body.

Always ask for the current certificate, with the name of the certifying body and the validity date. Check that the scope of the certification covers the activities you need (design, development, manufacturing, or all three). A certification limited to "consulting services" does not help if you need manufacturing under ISO control.

2. Real experience with Notified Bodies

There's a huge difference between "knowing the MDR" and having gone through the full certification cycle with a Notified Body. The technical documentation that a NB approves has a level of detail and coherence that can only be learned by doing it.

Ask the partner: have they developed products that obtained CE marking under MDR? Ideally, request references for specific projects with the corresponding Notified Body number. The official list of designated Notified Bodies is available in the European Commission NANDO database.

3. Hardware + firmware + software + manufacturing capability under one roof

For a medical device under MDR, splitting the project across five suppliers — one for hardware, another for firmware, another for the app, another for mechanics, another for manufacturing — is a recipe for regulatory friction. Every handoff between suppliers is a documentary risk point.

A partner with complete technical capability lets you keep a single technical interlocutor, a single quality system and a single coherent technical file. The partner's internal coordination is their problem, not yours.

4. Technical documentation aligned with MDR from day 1

Ask the partner how they structure the technical documentation from the start of the project. If the answer is "first we make the prototype and then we document," be wary. MDR documentation cannot be reconstructed after the fact without cost overruns and without risk.

An experienced partner generates during development: user requirements, design specifications, risk analysis (ISO 14971), verifications, validations, risk management report, post-market surveillance plan. All of this forms part of the technical file required by the MDR.

If the device includes software (more than 90% do), the IEC 62304 standard adds a specific software lifecycle layer. Make sure the partner applies it and doesn't treat it as optional.

5. Verifiable track record with proprietary and client products

The most honest indicator of a partner's capability is whether they've brought their own regulated products to market — not just services for third parties. A partner with proprietary products has felt on their own skin the full cycle: design, validation, testing, Notified Body, distribution, post-market surveillance.

Ask for concrete examples. A good partner can cite products with names, class, Notified Body and marking date. If the references are vague ("we've worked in the medtech sector") without verifiable data, ask for detail or discard.

Red flags you should avoid

In these 20 years we've seen projects fail because of choosing the wrong partner. The patterns repeat:

• Price well below market. A complete MDR development (HW+FW+SW+documentation) cannot cost less than a reasonable range. If the budget is suspiciously low, it probably means MDR documentation is missing or the partner plans to learn at your expense.
• Lack of ISO 13485 certification or certification with scope limited to "consulting". Without a certified quality system, the documentation doesn't fit the technical file.
• Unrealistic timeline commitments. An MDR development from concept to serial production with CE marking typically requires 18-30 months (for Class IIa; higher classes may extend further). Promises of 6-9 months usually mean cutting corners on verification and validation.
• Zero experience with specific Notified Bodies. If the partner has never been through a NB, the first time will be paid with your product.
• Opaque subcontracting of the technical core. If the hardware is done by a third party and the firmware by a fourth, without visibility over who is who, any technical issue becomes a ping-pong of responsibilities.
• Confusion between engineering partner and legal manufacturer. The partner develops and manufactures under your specification. The legal responsibility as MDR manufacturer is yours. If the partner suggests otherwise, they haven't understood the regulatory framework.

How to evaluate in the first meeting

These are the specific questions we recommend asking in the first meeting with any candidate partner. The answers will tell you more than any commercial deck:

• How many medical products have they developed and obtained CE marking under MDR? With which Notified Body?
• Can they show me the current ISO 13485 certificate and its scope?
• Who on the team would handle the regulatory part of my project? What MDR experience do they have?
• How do they structure the technical file from project kickoff?
• What additional applicable standards do they handle (IEC 60601-1, IEC 62304, ISO 14971)?
• Do they manufacture at their own facilities or subcontract serial production?
• How do they manage obsolescence of critical electronic components?
• What happens with the intellectual property of the development? How is it contractualised?
• What is the realistic timeline from concept to first production batches?

The real cost of choosing wrong

If the partner fails on any of the 5 criteria, the cost is not just the lost budget. It's also:

• Time-to-market: rebuilding a technical file due to insufficient documentation can add 12-18 months to the project.
• Financing: medtech investors will negatively evaluate a project where the technical file is not aligned with industry standard.
• Reputation: a medical device that reaches the market with quality flaws generates regulatory consequences (post-market surveillance, action reports) and commercial ones.
• Opportunity: while your project is stalled in NB review, the competition launches to market. In medtech, the first to arrive usually consolidates the segment.

That's why the engineering partner decision deserves the same rigour as choosing the CTO or the regulatory director of your own company. It's not just another supplier. It's an extension of your technical and regulatory capability.

Frequently asked questions

Can I work with separate freelancers for hardware, firmware and software?

Technically yes, regulatorily very difficult. MDR documentation requires coherence between all product layers. Coordinating three freelancers so their outputs fit into a single technical file is a full-time job. For Class I it may make sense; for Class IIa or higher the friction usually exceeds the savings.

What's the difference between an engineering partner and a contract manufacturer?

A contract manufacturer manufactures under your already-defined specification. An engineering partner helps you define that specification, develops the product and then manufactures it. For startups without an internal technical team, an engineering partner is usually the right option.

How much does an MDR medical device development cost?

It depends on complexity and class, but a complete Class IIa development (HW+FW+SW+MDR documentation+testing+first production batches) typically sits between €200,000 and €800,000. Higher classes (IIb, III) may require more. Budgets well below usually indicate missing regulatory documentation or validations.

How long does the typical cycle take?

From concept to CE marking with serial production, the usual range for Class IIa is 18-30 months. Devices with critical software, Class IIb or III, or complex clinical requirements can reach 36-48 months. Significantly shorter timelines usually mean cutting corners on verification, validation or documentation.

Does the partner assume regulatory responsibility as MDR manufacturer?

No. The legal responsibility as MDR manufacturer corresponds to whoever places the product on the market under their name — usually you, the client. The partner is an engineering and manufacturing supplier. This separation of roles is key to the regulatory framework and must be clear in the contract.

Can I change partner mid-project?

Technically yes, practically a dead-end street. Changing partner at an advanced stage means the new team has to familiarise themselves with design, documentation and decisions already taken. It's better to invest time in choosing well at the start than to resolve it later.

← Back to home