The important choice is not whether your regulatory lead is on payroll. It is whether they know your device, join decisions early and carry the work through. Here is how to make that model work for your next milestone and the routine work between milestones.
Choose execution, not another layer of advice
An embedded regulatory lead should turn a question into a decision, a record and a next action. Advice alone leaves you to translate the answer, find someone to write the documentation and reconcile the result with engineering.
Envoy is Dovetail's embedded regulatory service. Your senior expert writes technical documentation and submissions, runs gap analyses, manages regulator correspondence and implements and manages the quality management system within the agreed device scope. They join the meetings where regulatory decisions affect the product, then carry those decisions into the evidence.
Embedded describes how the expert works with you, not their employment status. Daily access, continuity and execution belong in the engagement design. You do not have to create an internal regulatory position to get them.
| Model | Who carries the work | What to check |
|---|---|---|
| Advisory consultant | Your team implements the advice unless delivery is included | Who writes, resolves questions and keeps the records current? |
| Dedicated in-house hire | One employee carries the responsibilities you assign | Which device and market experience do they bring, and what specialist support and cover will they need? |
| Envoy embedded expert | A named senior lead executes the agreed QA/RA work alongside your team, with broader expertise behind them | Which product, recurring activities, decisions and deliverables are covered, and how will inputs and approvals flow? |
Some consultants also execute. Compare the actual agreement, not the label. For an early-stage company, our recommended starting point is embedded delivery rather than building a department or buying advice that leaves the execution with you.
Why experience and fewer handoffs make the difference
Speed comes from resolving the right question before it becomes expensive rework. When a regulatory lead joins a design discussion, they can challenge an evidence assumption before you commit to a testing plan, then carry the agreed rationale into the documentation. You avoid a separate briefing, a late review and another round of explanations.
Accumulated experience matters most at the edges. A rule may be public, but recognising where a device description, evidence plan or response to a reviewer needs closer scrutiny takes practice. An expert who can draw on broader device and market experience has more than one previous project to compare with yours, and can bring in the right perspective when a question crosses disciplines.
Dovetail co-founder Spencer Todd brings experience at the US FDA and hands-on work bringing medical devices to market. Co-founder Severin Högl has built and certified a patient-monitoring app. That combination of regulatory and product experience informs why we built Envoy around a lead who does the work alongside you.
The mechanism is practical, not a promise of a fixed approval date. Keep the lead close to the product, resolve questions early and preserve the reasoning so the next document or decision does not start from scratch.
Daily QA/RA work belongs in the embedded model
Recurring work is a reason to embed your expert more closely, not an automatic reason to hire. Quality and regulatory affairs, or QA/RA, includes the routines that keep your plan current as the product changes, not just the submission at the end.
Within the agreed scope, Envoy can manage the QMS, maintain regulatory documentation, handle FDA or notified-body correspondence and support post-certification work. Bring a design change or a documentation question to the same lead who knows the strategy, rather than assembling a fresh briefing for each task. The retainer covers questions about the scoped product, not just a fixed list of documents.
Your engineers still supply design files and testing data, explain product decisions and review the technical facts. Your authorised decision-makers provide the judgments and approvals the work requires. That participation is not a requirement to hire a separate regulatory coordinator. Assign an existing founder, engineering lead or product owner to connect the expert with the right people and protect time for their inputs.
Plan the work around your next milestone
Start with the work you need done, then agree how Envoy will carry it. “Get us through the submission” can hide pathway questions, evidence gaps, documentation, test-plan reviews and responses to regulators.
| Your current work | What to agree with your embedded lead |
|---|---|
| Early feasibility and market selection | Challenge pathway assumptions before committing development and testing spend |
| Active development and evidence generation | Join design decisions, maintain records and flag evidence gaps as the device changes |
| Submission or conformity-assessment preparation | Own agreed documentation, package review and regulator correspondence, with clear input deadlines |
| Marketed devices and product changes | Define recurring QMS, change-review and post-certification activities for the markets you supply |
Give each output a deadline, an effort estimate and a dependency. Separate work the expert can execute from information only your team can provide. A regulatory lead can organise an evidence review but cannot manufacture missing test data or decide what your device actually does.
Required device testing is outside the Envoy engagement. Internal and supplier audits use a separately priced partner arrangement, and notified-body fees are paid separately. Put any additional product or specialist work into the scope discussion rather than assuming a retainer covers unrelated work.
Use a workload example to allocate execution
This invented four-week example shows how to plan the work, not how many hours Envoy promises or what a submission should cost. Validate competence and sequencing separately from the hours.
Suppose you need an evidence-gap review before agreeing a testing plan. Instead of reserving all record preparation for an internal regulatory hire, agree which preparation and coordination tasks the embedded lead can carry using your existing records.
| Work item | Product-team input hours | Embedded expert hours | Proposed output owner |
|---|---|---|---|
| Assemble current design and evidence records | 8 | 16 | Embedded lead, with engineering supplying source records |
| Review pathway assumptions and evidence gaps | 4 | 24 | Embedded regulatory lead |
| Review the proposed testing plan | 12 | 12 | Engineering lead, with embedded expert review |
| Record decisions and resolve open questions | 8 | 12 | Embedded lead records decisions, authorised product owner approves |
| Total over four weeks | 32 | 64 | Each output keeps its named owner |
The plan allocates eight product-team input hours and 16 embedded expert hours per week on average. These are fictional allocations, not measured savings from outsourcing. They illustrate a delivery design in which the expert carries preparation, analysis and follow-through while your existing team supplies product knowledge and approvals.
If your team has eight hours available each week, the average fits, but the sequence still matters. Check peak weeks and when source records will arrive before agreeing a completion date. If an input is missing, resolve that dependency or revise the plan. Buying expert time cannot replace evidence that does not exist.
For your own plan, add these fields to every row.
| Planning field | What to write down |
|---|---|
| Milestone and acceptance criteria | The output and how you will decide it is ready |
| Required experience | The device, market or method experience the work needs |
| Delivery, review and decision authority | Named people and their distinct responsibilities |
| Evidence location | Where approved records and decision history will live |
| Available capacity and cover | Committed time, peak weeks and absence arrangements |
| Handover condition | What must transfer if the engagement or role changes |
Compare the function you get, not salary against fees
One salary does not necessarily buy the range of expertise your device needs. Compare the same scope over the same period, including the work someone must still do around the lead.
For a hire, include compensation, employer costs, recruitment, onboarding, management time, tools and remaining specialist support. For Envoy, include the agreed fees, your team's product input and approval time, scope changes and any separately priced work. Keep testing, regulator fees and other third-party costs visible in both budgets.
Ask who will execute recurring work, how cover works and where decisions and evidence will live. A proposal that leaves those answers blank is not equivalent to an embedded regulatory function. Nor should you assume an employee can cover every device, market and specialist question alone.
Use your own budget inputs rather than universal salary thresholds or invented delay savings. Our recommendation rests on access to senior execution and broader experience without building that function one hire at a time.
Keep ownership and continuity visible
Name the Envoy delivery lead, your authorised internal decision owner, review responsibilities, escalation route and cover arrangements before the work starts. Distinguish drafting, review and approval so shared involvement does not leave you reconciling two versions of the same output.
Keep approved evidence and decision records accessible to your company. Agree access to editable source files, correspondence, open questions, assumptions and decision rationale, along with confidentiality, notice terms and handover support. Continuity should live in the records and the delivery arrangement, not only in one person's memory.
A useful test is to ask another suitably qualified person to explain the current plan from those records. They should be able to tell what has been decided, what remains uncertain and who owns the next action.
External execution does not remove the manufacturer's applicable compliance obligations. Under EU MDR Article 10(9), the manufacturer's QMS includes management responsibility and selection and control of suppliers and subcontractors. US manufacturers subject to Part 820 must meet its applicable QMS requirements. Keep the required company decisions and oversight explicit while the embedded expert carries the agreed work.
Scale the scope as the work grows
A new market, more frequent design changes or post-certification work should trigger a scope and capacity review with your embedded lead. Daily volume alone is not a reason to replace embedded delivery with a hire. Agree the recurring activities, required expertise, cover and product-team input before the workload outgrows the plan.
If you already have a regulatory employee, Envoy can work alongside them with clear responsibilities. You do not need to remove a capable person to use embedded expertise, and you do not need to recruit one as a prerequisite. Build around the work and preserve one clear route from question to decision to evidence.
Related decisions
Compare Envoy with a regulatory consultant to examine execution and scope. Use the EU or FDA first guide for market sequencing, and the medical-device supplier qualification guide to plan how you assess outside providers.
Why we built Dovetail to work differently
We built Envoy because you should be able to get senior regulatory leadership and daily execution without recruiting a department. A lead who understands your device, writes the documentation and stays with the decisions can shorten the path between a question and useful work.
Bring your next milestone, recurring QA/RA tasks and current evidence to a discovery call. We will map what Envoy can carry, what your team needs to supply and where the dependencies sit, so you can move forward with a named lead and a clear plan.
Further reading
- EU MDR Article 10(9) sets out the manufacturer's QMS duties, including supplier and subcontractor control.
- 21 CFR 820.1 describes US applicability, and 21 CFR 820.10 sets out the manufacturer's applicable QMS requirements.
The workload fields, example hours and handover checks are practical planning recommendations, not statutory staffing requirements.
