Introduction
At a lot of early-stage biotech, device, or diagnostics companies, there's no regulatory affairs department — there's one person. Maybe the title is Director of Regulatory Affairs, maybe it's something broader like Head of Regulatory and Quality, but the practical reality is the same: one person is responsible for a function that at a larger company would be split across specialists in submissions, labeling, clinical regulatory strategy, and postmarket compliance. It's a specific kind of job, with its own rewards and its own real risks, and it doesn't get talked about as often as the more visible "regulatory affairs manager" or "director" roles that assume a team underneath them.
If you're considering a move into one of these roles, or you're already in one and trying to figure out whether you're doing it right, here's a grounded look at what the job actually requires.
It's worth separating this from the more common "regulatory affairs at a small company" framing, which often still assumes a lean team of two or three. A true team-of-one situation — one regulatory hire for the entire company, reporting directly to the CEO or COO — has its own specific demands that a slightly larger small-company team doesn't quite replicate, mostly because there's genuinely no one else inside the building with regulatory training to consult, delegate to, or hand off a problem to while you're out.
The Scope Is Wider Than the Title Suggests
A regulatory affairs team-of-one is rarely just doing regulatory affairs in the narrow sense. Depending on the company, the role often absorbs pieces of quality systems, clinical regulatory strategy, and sometimes even parts of compliance or legal that touch product claims and labeling. Early-stage companies generally can't justify separate regulatory and quality hires until they're closer to a pivotal trial or a commercial launch, so the one regulatory person is frequently also the de facto quality lead, writing or reviewing SOPs, managing document control, and overseeing whatever quality management system the company has in place.
This breadth is one of the most common adjustments people underestimate moving from a larger organization. At a bigger company, a regulatory affairs manager can specialize — CMC, clinical, labeling, or a therapeutic area — and lean on quality, clinical operations, and legal as separate functions with their own expertise. In a team-of-one role, there's no one else to hand the quality system questions to, and "that's not really my job" isn't a sentence that gets much use.
It's also common for the role to pick up work that technically belongs to another function entirely but that no one else at a five- or ten-person company has the regulatory literacy to handle. Reviewing marketing copy for claims that could create regulatory exposure, fielding an investor's due diligence question about the approval pathway, or sitting in on a partnership discussion to flag regulatory risk in a proposed deal structure are all things that land on a solo regulatory lead's desk simply because there's no one else positioned to catch them.
You Become the Regulatory Strategy, Not Just the Regulatory Executor
In a larger regulatory affairs department, strategy often gets set at a level above any individual contributor — a VP or a regulatory strategy committee decides the overall pathway, and specialists execute pieces of it. As the only regulatory person at a small company, you're frequently the one setting that strategy, often with direct input from the CEO or the board, and sometimes without much internal pushback or sanity-checking from a regulatory peer.
That's a real responsibility shift. It means spending time not just executing submissions but thinking through pathway choices — breakthrough designation versus standard review, 510(k) versus De Novo, whether a particular clinical design will hold up to FDA or notified body scrutiny — and being comfortable presenting that reasoning to non-regulatory executives who are making resourcing and timeline decisions based on what you tell them. If you get the strategy wrong with no one to catch it, the company feels that mistake directly, often months or years later when it's expensive to fix.
External Relationships Carry More Weight
Without an internal team to triage incoming questions or escalate issues, a team-of-one regulatory lead typically owns the relationships with consultants, outside counsel, and contract manufacturers or CROs more directly than a specialist would at a larger company. Knowing when to bring in outside regulatory consulting help — for a specific therapeutic area you don't have deep experience in, or for a jurisdiction you haven't worked in before — is a skill in itself. The honest version of this job includes recognizing the limits of what one person can reasonably know across every regulatory domain a growing company touches, and building a bench of trusted external experts rather than trying to be the expert on everything.
This also changes how much of the job is about relationship management rather than pure technical regulatory work. A team-of-one lead is often the primary point of contact for a contract manufacturer's quality team, a CRO's clinical operations lead, and outside regulatory counsel all at once, which means a meaningful share of the week can go to coordinating across these parties rather than drafting documents directly. Being organized about who owns what, and following up reliably when an external party is behind schedule, becomes a core part of the job rather than a peripheral skill.
What Makes Someone Effective in This Role
A few traits show up consistently in people who do this well:
- Breadth over narrow specialization. Deep expertise in one regulatory niche is less valuable here than solid working knowledge across submissions, labeling, quality systems basics, and clinical regulatory strategy.
- Comfort with ambiguity and incomplete information. Small companies often don't have polished internal processes yet, and part of the job is building those processes rather than just following them.
- Willingness to say no, carefully. Founders and executives at small companies sometimes push for timelines or claims that aren't regulatory supportable. Being the only regulatory voice in the room means being the one who has to push back, clearly and with reasoning, even when it's not the answer leadership wants to hear.
- Good documentation habits, by default. With no one checking your work, the discipline to document decisions and rationale — not just outcomes — has to be self-imposed. It matters later, during due diligence, an inspection, or when the company eventually does build out a team and needs to understand how past decisions were made.
The Honest Tradeoffs
This kind of role offers a level of ownership and visibility that's hard to get at a larger organization — your decisions aren't filtered through layers of review, and the impact of good regulatory strategy is directly visible in how the company progresses. It also means less structured mentorship, fewer built-in sanity checks, and real exposure if something goes wrong on your watch with no backup to catch it. It tends to suit people who've already built a solid regulatory foundation somewhere with more structure and are ready to apply it independently, more than it suits someone very early in their regulatory career who still needs close oversight to develop sound judgment.
There's also a practical career-arc question worth thinking through before taking a role like this: what happens to your position if the company grows. Sometimes the person who built the regulatory function from scratch moves naturally into a VP or head-of-regulatory role as the company scales and hires a team underneath them. Other times, a growing company brings in someone with more senior or more specialized experience to lead a larger function, and the original team-of-one hire either moves into a narrower role under that person or moves on. Neither outcome is a given, and it's worth having an honest conversation with leadership, if you can, about how they see the function evolving before you accept a role where you're the only regulatory hire.
Questions Worth Asking Before You Take the Job
A few questions tend to surface what a specific team-of-one role will actually feel like, beyond what's in the job description. How does leadership currently make regulatory-adjacent decisions, and will you have real authority to change course if you disagree with a plan already in motion? Is there budget set aside for outside regulatory consultants when a gap in your own expertise shows up, or is the expectation that you'll figure it out regardless? What's the company's funding runway, and how does that affect the realism of the regulatory timeline you'd be inheriting? And, perhaps most practically, who would you turn to internally if you needed a second opinion on a hard call — if the honest answer is no one, that's not necessarily a dealbreaker, but it's worth knowing going in rather than discovering it the first time you actually need that second opinion.
Conclusion
Being the only regulatory affairs person at a small company is a different job than a "regulatory affairs manager" title at a larger company with the same words on the business card. It asks for broader working knowledge, more independent judgment, and comfort owning strategy decisions without a built-in second opinion. For the right person at the right career stage, it's one of the fastest ways to develop real regulatory judgment — just worth going in with clear eyes about what the role actually demands day to day.