Sponsors (Life Science startups)
Almost every early-stage life science company I meet has been told they need to build everything. Usually by someone whose experience is at a scale you're nowhere near, using templates from a company with departments you don't have.
What you actually need depends on where you are. At R&D that's discipline around documentation. Approaching clinical it's oversight of what you've outsourced. It's a different answer at each stage and it's almost never "all of it".
I help early-stage life science companies build quality systems sized for where they are, that can grow rather than be replaced.
28 years in life sciences across three continents
Training facilitator on quality management for early-stage drug development
What I hear from sponsors
No idea how much quality system is actually enough
Every advisor says build everything
A milestone is coming and quality isn't ready
Real regulatory obligations, no QA function
Everything outsourced, and nobody really overseeing it
A partner or investor has started asking questions
Why this happens
Life science startups in the early stages of development often struggle to implement a quality system that suits where they are. They either have nothing, or they have one designed for a large manufacturing organisation.
The challenge is finding the balance. The system has to enable flexibility, effective collaboration, efficient technology transfer and decent knowledge management, all at once, with a small team.
It's rarely a judgement problem. It's usually inherited advice:
Templates sized for large manufacturers.
They're what's available, and they come with an implied organisation behind them.
Advice from people who worked at scale.
Excellent experience, wrong context. What was right at a thousand people is wrong at twelve.
Quality treated as a later problem.
Until suddenly it's an immediate one, usually because of a milestone or a partner.
Nobody internally to ask.
The founder is a scientist, not a quality professional, and there's no one to sanity-check the advice.
What you actually need, by stage
R&D.
Documentation discipline and traceability. You're generating data that will need to stand up later. You don't need a quality management system yet.
Preclinical.
The processes that will have to hold up when someone reviews them. Still lighter than most people expect.
Clinical.
Oversight of what you've outsourced, and the processes the trial actually depends on. This is where most companies discover the gap, usually including technology transfer.
Commercial.
A full system, built on what came before rather than started again. If the earlier stages were done properly, this is an extension rather than a rebuild.
What tends to help
Design and implementation of tailored quality systems
When it's time to build, sized for where you are.
Audit support
for contractor and supplier audits, when everything is outsourced and you have no internal resource to oversee it.
Customised training
When a small team has to get this right without a QA department behind them.
You'll notice that's four services rather than six. The other two are for organisations further along, and recommending them to you would be exactly the overbuilding this page is arguing against.
How I work
01 / 03
Understand the operation before designing anything.
02 / 03
Build only what's needed for where you are.
03 / 03
Implement, then verify against the requirements that actually apply.
Proof
A quality system built for Phase 1 — biotech CDMO
Moving out of R&D into Phase 1 clinical manufacturing, with no internal QA, a scientific team unfamiliar with regulatory and quality process, and a limited budget. I mapped the business processes, ran a gap analysis, and designed a QMS sized for where they were and able to scale. Then an implementation roadmap, and mentoring for the QA person they eventually hired.
Investigating an unexpected result — biotech sponsor
A small biotech had hit a data reproducibility problem. The scientific team was struggling to investigate it, plan the next experiments, and do both in a way that would stand up to regulatory expectations. The project was slipping and investor confidence with it.
I ran a tailored training and brainstorming session on handling unexpected events during drug development: what regulators look for, and which quality tools apply. The session used their actual problem as the worked example, and they came away with a draft investigation and remediation plan they could act on.
CLIENT PERSPECTIVE
"As a project manager for an early-stage company, this session provided practical insights that have significantly impacted my approach to project quality. Rather than a rigid standard, quality is about meeting the specific needs of our customers and stakeholders."
Cecile Francis, Director of Strategic Projects, UniQuest
CLIENT PERSPECTIVE
"I had the pleasure of collaborating with UQM Consulting during a critical phase of our move to GMP-like operations at Southern RNA. The Quality Assurance services provided exceeded our expectations in every aspect. Antiksha demonstrated an unparalleled level of expertise and commitment to ensuring the highest standards in our processes, business and current quality framework."
Garry Heaney, CEO, Southern RNA
Questions early-stage companies ask
How much quality system do we actually need right now?
Less than you've been told, almost certainly. It depends on your stage and what you've outsourced, and it's a thirty-minute conversation rather than a proposal.
When should we bring in QA?
Usually before you think, and in a smaller form than you think. Expertise earlier, headcount later.
Can we start small and grow it?
Yes, and you should. A system built to grow is cheaper than one built to impress and then rebuilt.
Do we need to hire a QA manager?
Not necessarily yet. There's a stage where quality and compliance expertise suited to your development stage is worth more than a full-time hire you can't quite justify. QA Support →
How do we oversee a contract manufacturer?
Deliberately, and in writing. This is where small companies are most exposed, because the risk sits in someone else's building. Auditing them properly is usually the first step. Audit support →
Our team has no quality system background. Can you work with them?
Yes, and it's some of the most useful work I do. The trick is using a problem you're actually facing as the example rather than a generic one.
What will an investor or partner expect to see?
Evidence that quality is governed rather than improvised. That's a much lower bar than a full quality system, and it's a reasonable thing to prepare for.
