One of the most pivotal choices a founder makes is building the team. Getting your company off the ground requires a group that can cover every essential role, and in MedTech—with its dense layers of regulation and red tape—there’s no way around eventually bringing regulatory expertise into the fold.

But when is the right time to do that? And just as importantly: what kind of person should you be looking for?

I’ve seen many young ventures wrestle with these questions. I’ve also seen how the wrong answers can slow companies down, drain resources, and lead to expensive rework. A big part of the problem is that many first-time founders don’t fully grasp how broad and varied the quality/regulatory space really is. What looks like a single role from the outside is, in reality, a bundle of very different responsibilities.

Here’s what that bundle usually includes.

Driving Regulatory Strategy

Early on, nothing matters more than defining your product—its intended use and purpose. That definition shapes its regulatory classification and, with it, the level of regulatory burden your company will face.

A strong regulatory person can work side by side with management to weigh the trade-offs that come with different paths. What’s the leanest product you could get cleared? Is it smarter to aim for initial clearance in the US or the EU? These are strategic calls that can ripple through your entire timeline and business model.

Shaping Clinical Strategy

In most cases, you’ll need clinical data to support your eventual submission. Often, these studies are drafted by clinical experts like the doctor-inventor, who are naturally focused on creating work that will make for compelling academic papers.

That’s where things can go sideways. If no one is thinking about regulatory requirements during study design, you risk ending up with impressive data that regulators can’t use. Having someone at the table with a regulatory perspective helps ensure that the right endpoints—including safety endpoints—are baked in from the start.

Just as crucial, this person can make sure the study fully adheres to Good Clinical Practice standards, avoiding painful (and expensive) gaps that can come back to haunt you at submission time.

Supporting the Development Team

Medical devices must comply with a maze of standards. Development teams often expect the quality/regulatory person to identify which standards apply, interpret their dense language, and help prioritize which verification activities to tackle first.

Risk management is another critical area. Inexperienced teams, left to their own devices, often either list hundreds of extreme “death risk” scenarios or overlook serious risks entirely. Both extremes can create major obstacles later in development—or even derail a submission.

And then there’s documentation. Requirements, design outputs, verification plans: all of it has to be properly written, linked, and signed off. A good quality person can coach the team through this work and flag the vague wording or open ends that could trigger regulatory pushback.

Managing Suppliers

If you’re outsourcing part of development or production, supplier management becomes a regulatory issue as well as a business one. This means setting up written Quality Agreements, running supplier audits, and agreeing early on which documents the supplier will need to provide for your future technical file.

Miss this step, and it can create massive delays down the road. For example, a biocompatibility assessment requires a complete list of every material used in production—including things as mundane as cooling or cutting fluids. If you only discover that gap at the end, it’s too late.

Building a fit for purpose QMS

Before you can bring a device to market, you’ll need a fully functioning Quality Management System (QMS). A good QMS is tailored to how your company actually works—which processes are in-house, which are outsourced—and ideally integrates with tools your team is already using.

It’s a deceptively tricky task. Many quality/regulatory professionals have strong opinions here, and implementing a full QMS too early can slow your momentum to a crawl and sap morale. Leave it too late, though, and you risk failing audits and stalling your launch. The timing matters as much as the design.

Preparing Submission Files

When development is complete and the product has been fully verified and validated, all the evidence has to be pulled together into a submission file.

This is where storytelling matters. A strong regulatory person can structure the file so it guides reviewers clearly through your product’s risk profile, helping them understand and trust your documentation. Detailed checklists that link every requirement to supporting evidence make reviews faster, smoother, and far less costly.

Maintaining Compliance After Launch

Once the product is on the market, the nature of the work shifts again. Customer complaints must be assessed to see if they’re reportable. Regular internal and external audits need to be prepared and carried out. Any proposed design changes must be reviewed to see if they require new submissions.

And as your company grows and evolves, your QMS has to evolve with it—new roles, new processes, and new responsibilities will all need to be reflected.

So Many Roles — Hard to Find in One Person

When you lay it all out, it’s clear why this is such a tough hire. These tasks demand radically different mindsets. Strategic decisions require big-picture thinking and broad judgment. Standards checklists demand obsessive attention to detail.

In larger companies, these tasks are split across entire departments. Regulatory Affairs handles strategy, submissions, and communication with authorities. Norm Compliance works closely with technical teams to interpret standards and oversee testing. Quality Managers review documents to make sure templates are followed and signatures are complete. Process Owners slowly update and expand the QMS over time.

Trying to combine all of that in one person is a tall order.

When—and Who—to Hire

In a startup, none of these jobs are full-time at the beginning. You might not need a dedicated hire at all in the early stages.

If you do decide to hire, experience becomes the next big question. Someone from a large company will likely have worked in just one slice of the field—Regulatory Affairs or Quality, not both—and probably won’t have experience building a lean QMS from scratch. They’re used to mature teams and established processes, and often their job has been to compile records rather than create them.

What about someone from a startup? The issue here is depth versus breadth. If they’ve only worked on a single product in a single environment, they may have limited perspective—and depending on when they joined and left, they may not have seen the long-term consequences of their decisions.

Consultants can be a great resource, especially early on. They’ve seen many different companies, products, and challenges. But their scope is often narrow—focused on setting up QMSs or polishing specific documents—and they usually don’t have deep insight into the dynamics of your business.

Highly experienced people also expect to be paid accordingly, and as noted, the role won’t be full-time at first. Hire someone too senior too early, and they’ll likely fill their time doing what they’re most comfortable with (often writing procedures) rather than what the company truly needs in those early days: building technical documentation, managing risks, and working with the clinical team.

Over the years, I’ve seen many setups: fractional QA/RA experts on the payroll, reliance on external consultants, and hybrids where a young, inexperienced person works closely with an experienced consultant for guidance and strategic oversight.

A Balanced Approach That Works

The most effective setup I’ve seen is to start with an in-depth regulatory, clinical, and development assessment to map out realistic milestones, timelines, and funding needs.

Then, when development is picking up speed, bring on your first internal quality/regulatory person. This can be someone with a technical or slightly clinical background who’s curious about regulatory work. Early on, they might also take on other responsibilities—such as organizing your first clinical or usability study.

With hands-on external support, they can build experience gradually. At first, their focus will be on assembling technical documentation. Over time, they can begin tailoring SOPs and building a complete QMS. The advantage is that they grow to understand both your business and your product while developing regulatory expertise. Meanwhile, your consultant can stay lightly involved, ready to help with strategy or surge capacity when submission time comes.

I’d love to hear how other founders approached this decision. What worked for you? What would you do differently next time?

And if you’re a founder facing this question now, feel free to reach out—I’m always happy to have an informal conversation.

To comment and share your thoughts join the conversation at LinkedIn!

Related posts:

Public Gatekeepers, Private Returns

The commercial incentives shaping EU medical device conformity assessment Key Messages The EU’s decentralized conformity assessment model relies on independent, mostly commercial notified bodies to

Read More »

Don’t hesitate to ask us your questions.

Drop an e-mail or contact us via LinkedIn

This website uses cookies to ensure you get the best experience on our website. If you want to get more information about this, please view our privacy policy page.