Medical Device Consultancy: A Guide for Product Teams and Startups
Choosing a medical device consultancy is not just a search for a team that can make a concept look polished. The right partner should help your product team resolve the physical product questions that affect usability, technical feasibility, prototyping, and a path toward manufacturing. The first step is to define what you need the consultancy to own, what expertise must remain with your team or regulatory specialists, and what evidence you need before moving forward.
Talk with Jackson Hedden about your product development needs
What should a medical device consultancy help your team decide?
A medical device consultancy should help clarify the product decisions that are difficult to make with an internal team alone. Depending on the project, that may mean shaping the physical product, integrating mechanical and electrical requirements, building prototypes to learn from, or preparing design information for manufacturing. Define the decisions and deliverables first; do not assume every consultancy offers the same scope.
The term medical device consultancy can describe many different kinds of support. One firm may focus on regulatory strategy, another on industrial design, and another on technical development or manufacturing. Some combine several disciplines. A credible selection process starts by separating those needs instead of treating the label as a complete description of what the firm does.
For a product company or startup, useful support often concerns the product itself: how it will be held, worn, cleaned, assembled, charged, serviced, or used alongside other equipment. The answers may affect enclosure geometry, material choices, component layout, interfaces, prototype plans, and production methods. These decisions are related, so it helps when the people working on the form understand the technical and manufacturing constraints too.
That does not mean a design consultancy automatically supplies clinical, quality-system, testing, or regulatory expertise. Those are distinct responsibilities. Before work begins, identify who is qualified and contracted to make each decision, and who owns the records or approvals associated with it. Keep product design and regulatory work coordinated, but do not assume one substitutes for the other.
A useful starting brief names the productâs intended users and environment, the problem it is meant to address, what is already known, and what remains uncertain. It should also state the immediate decision the project needs to make. For example, is the team deciding whether a physical form is viable, how a device can accommodate a set of components, or what must be learned from the next prototype?
Start with the projectâs unresolved questions
Write down the uncertainties that could change the product direction. Avoid vague statements such as âwe need a better design.â Describe the question in a way a project team can investigate. Examples include:
Can the product fit the known components while remaining comfortable to hold or wear?
Can intended users understand the physical controls and status cues in the use environment?
Which enclosure, assembly, or service-access decisions should be tested before design freeze?
What prototype is needed to evaluate the form, fit, interaction, or manufacturing process?
What information must be clarified with a regulatory or quality specialist before design work proceeds?
These questions help a consultancy propose work that has a clear purpose. They also make it easier to compare proposals. If one proposal focuses on appearance concepts and another includes component layout, prototype builds, and a manufacturing review, the difference is meaningful only when the team knows what decision each activity is expected to support.
Which capabilities matter for a medical device project?
Capability fit depends on your device, development stage, and internal resources. A consultancy may need industrial design, mechanical and electrical design, prototype planning, design-for-manufacturing input, or coordination with your specialists. Ask for examples of how those disciplines work together on physical products, and confirm which people and outputs are actually included in your proposed scope.
Do not select a partner by counting service labels. Ask how the team turns user and technical needs into design inputs, weighs competing constraints, tests risky assumptions, and documents design decisions. For a physical product, an attractive concept that cannot accommodate components or be assembled as intended is not a complete answer. Likewise, a technically plausible object can still be confusing or uncomfortable to use.
Industrial design and human interaction
Industrial design shapes the productâs physical form and its relationship with people. Depending on the product, that can include proportions, grip, reach, orientation, controls, visual hierarchy, and the way a device fits into a use environment. Ask how the consultancy plans to explore these factors, what it will test with models or prototypes, and how it will address feedback without losing sight of technical constraints.
Discuss the difference between an appearance model and a prototype intended to answer a use or fit question. A visual model can help people react to size and form. A functional prototype may be needed to assess a control, mechanism, component arrangement, or physical sequence. Neither is automatically evidence of clinical performance or regulatory compliance. Be specific about the question each build can and cannot answer.
Mechanical and electrical integration
When a device includes electronics, sensors, power, or moving parts, the physical and electrical decisions interact. Component envelopes, connectors, heat, access, fastening, wiring, and enclosure layout may affect one another. Ask who will coordinate mechanical and electrical work, how component assumptions will be tracked, and when the team will review fit and integration using real components or representative models.
Early coordination can reveal conflicts while there is still room to change the architecture. For instance, the location of a charging connection can affect enclosure geometry and how a person handles the device. A display or indicator can influence orientation and visibility. The point is not to presume a particular technical answer, but to ensure that these interdependent choices are considered together rather than handed between disconnected teams.
For projects that need dedicated electrical input, review the scope of Jackson Heddenâs electrical design services and ask whether the proposed activities match your device requirements. The project brief should make clear what circuitry, components, interfaces, or integration tasks are included, as well as what remains the responsibility of your internal or specialist team.
Prototyping and manufacturing awareness
Prototypes are most useful when they are built to answer a defined question. A rough model may test size or reach. A more refined prototype may help assess assembly sequence, component fit, or an interaction. Before agreeing to a build, ask what the model represents, what materials or processes it uses, what it cannot demonstrate, and how results will inform the next design decision.
Manufacturing input matters before the final handoff. A design should be discussed in relation to materials, part geometry, assembly, tolerances, finishing, supplier capabilities, and production volume assumptions as those become known. The consultancy should explain the level of manufacturing detail its scope provides. A concept review, a production-feasibility discussion, and detailed manufacturing documentation are different deliverables.
Explore the relevant prototyping services and manufacturing support in context of your stage. Ask whether the partner will help select prototype approaches, review production constraints, or prepare a handoff. A broad capability statement is less useful than an agreed list of tasks, decision gates, and tangible outputs.
How do you compare consultancy options without comparing names alone?
Compare each option against the work your project needs, not against firm size or a long list of capabilities. Ask what the team will do, who will do it, what you will receive, what assumptions the proposal makes, and how decisions will be reviewed. A side-by-side scope comparison exposes gaps that a polished presentation or general promise can leave hidden.
The National Institutes of Healthâs guidance on selecting a regulatory consultant notes that organizations may consider different-size firms or independent consultants depending on budget and the services needed. That is a useful reminder to match the type of provider to the actual scope. It is not an endorsement of a specific consultancy or a substitute for checking the relevant expertise and responsibilities for your project. Read the NIH guidance on selecting a regulatory consultant.
Use a consistent set of questions in initial conversations. Ask the prospective partner to distinguish what it has done from what it proposes to do for your product. Request an example of a relevant process or deliverable, while respecting any confidentiality obligations. Then compare how each firm handles the following areas:
Scope clarity: Are phases, activities, deliverables, assumptions, and exclusions written down?
Relevant disciplines: Does the proposed team cover the specific design, mechanical, electrical, prototype, or manufacturing questions you identified?
Decision process: How are concepts reviewed, risks surfaced, and changes approved?
Prototype intent: Is each build linked to a question and a planned review?
Coordination: How will the consultancy work with your clinical, quality, regulatory, or manufacturing specialists?
Handoff: What files, drawings, specifications, records, or other outputs will your team receive, and in what format?
Ownership: Who owns design files, prototypes, decisions, and follow-up actions?
Scope and stage: Which questions will this phase resolve, and what is outside scope? Useful evidence: Named activities, assumptions, milestones, and exclusions
Team capabilities: Who covers industrial design, mechanical or electrical integration, and manufacturing input? Useful evidence: Named roles, responsibility boundaries, and collaboration approach
Prototype plan: What will each prototype test, and what will it not establish? Useful evidence: Build purpose, fidelity, review method, and next decision
Deliverables and handoff: What files and documentation will transfer to our team? Useful evidence: Output list, formats, ownership, and handoff point
Specialist coordination: How will our regulatory, quality, clinical, and manufacturing advisers be involved? Useful evidence: Defined interfaces and responsibilities, without implying unscoped expertise
Do not interpret a low-level estimate as a direct measure of value unless the scopes match. One firm may be quoting a discovery phase; another may include multiple prototype iterations and preparation for a manufacturing discussion. Compare similar outputs, identify unresolved assumptions, and ask what would trigger a change in scope. If the proposal does not explain how the team will make decisions, request that detail before signing.
Turn a broad request into a scoped first phase
If you are not ready to define a full development program, ask each candidate to scope a contained first phase. A useful phase does not need to settle every technical question. It should reduce uncertainty enough to make a better next decision. For example, the team might map user and product needs, review the known component envelope, sketch several physical directions, build a simple mockup, or assess an assembly concern. Choose activities that answer your actual question, not a standard package that happens to be available.
Set a beginning and an end to the phase. At the beginning, agree on the materials the consultancy will review and the assumptions it may rely on. During the work, identify planned check-ins where the team can react before too much effort accumulates around one direction. At the end, specify the outputs and the decision meeting: perhaps a preferred concept with reasons, an annotated list of unresolved risks, a prototype recommendation, or a proposal for the next stage. The exact outputs should reflect the project rather than a generic template.
Ask what client participation the work requires. A phase can stall if the consultancy needs component data, access to subject-matter experts, or timely feedback that no one has agreed to provide. Name an internal decision-maker, identify reviewers, and set a realistic process for resolving conflicting comments. If feedback arrives from several stakeholders, decide who consolidates it and who has authority to approve a change in direction.
Separate fixed assumptions from questions that could alter the scope. If the design depends on dimensions that have not been confirmed, for example, the proposal should say so and describe what happens if those dimensions change. The same applies to component availability, material preferences, manufacturing processes, and intended use. Explicit assumptions make it easier to understand what a phase can deliver and when a new decision or additional work may be needed.
Finally, agree how changes will be handled. Ask how the team will document a new requirement, assess its effect on schedule or outputs, and obtain approval before proceeding. This is not about preventing useful iteration. Iteration is part of development. It is about ensuring that the project team knows when a new request changes the question being answered, so it can choose whether to adjust the plan deliberately.
Notice warning signs in a proposal
A proposal deserves clarification when it promises a finished or compliant device without explaining what work supports that claim, treats a visual concept as proof of technical readiness, or leaves the design handoff undefined. Be cautious when a firm cannot distinguish its own responsibilities from those of your regulatory, quality, clinical, or manufacturing partners. Broad assurances are not a substitute for named activities and accountable roles.
Other gaps may be less dramatic but still important. A proposal may omit who supplies components, who approves design changes, whether prototype fabrication is included, or what happens to files after the engagement. It may use terms such as âvalidation,â âproduction-ready,â or âregulatory supportâ without defining them. Ask the firm to state what those terms mean in the specific scope and what evidence or specialist review would be required before making such a conclusion.
Questions are not necessarily evidence that a firm is unsuitable. Clear, candid answers help you judge whether expectations align. A partner should be able to describe limits, dependencies, and unknowns as well as capabilities. If a key uncertainty cannot be resolved in an introductory conversation, make it an explicit item for discovery rather than assuming it will disappear after kickoff.
Look for specific proof, not broad assurances
A case study is most useful when it shows the nature of the problem, the project teamâs role, the development activities, and the kind of outcome that can responsibly be shared. Ask which aspects are comparable to your project. A deviceâs form factor, environment, technical complexity, or production context may differ even when the category sounds similar.
For a relevant example of work, review Jackson Heddenâs RelieVRx case study. Use any case study as a starting point for questions about scope and collaboration, not as proof that a new product will have the same results or follow the same path. Confirm what the consultancy actually contributed and what other project partners handled.
Also ask about the working rhythm. Who is your day-to-day contact? How often are concepts or prototypes reviewed? What information does the team need from you to avoid stalled decisions? How are open issues recorded? A manageable collaboration process is especially important when founders, product leaders, clinicians, technical specialists, and external advisers all have input.
What should you prepare before engaging a consultancy?
You do not need a finished specification to start a useful conversation. You do need a candid picture of the product, the people involved, the constraints already known, and the choices that remain open. Share enough context to let a potential partner identify relevant work and scope the next step without presenting assumptions as settled facts.
Gather the materials that show the current state of the project. These might include sketches, CAD, a component list, mockups, user research, known size constraints, previous prototype observations, or supplier feedback. Label what is confirmed, what is provisional, and what is still a hypothesis. This simple distinction can prevent a team from designing around an outdated assumption.
A practical project brief
A focused brief can include:
Product purpose: Describe the problem and the intended use at a high level. Avoid claiming clinical benefits that have not been established.
Users and setting: Identify who will interact with the product, where it may be used, and relevant handling or environmental conditions that are known.
Current stage: Explain what has been decided, what has been prototyped, and what remains under investigation.
Known requirements: Share dimensions, component envelopes, power or connectivity assumptions, interfaces, materials, or other constraints that are genuinely established.
Open questions: Rank the product risks and decisions you want the next phase to address.
Project participants: Identify internal owners and external specialists who need to review or approve relevant work.
Target handoff: State what your team needs at the end of the proposed phase to decide what comes next.
If some information is confidential, discuss appropriate protections before sharing it. If a requirement depends on regulatory interpretation, clinical judgment, or a quality-system process, identify the responsible specialist rather than asking the design partner to infer it from incomplete information.
Agree on what the next phase will prove
Before authorizing a large body of work, agree on the next decision gate. That might be selecting a form direction, confirming that key components can fit, evaluating a physical interaction, or deciding whether a prototype merits further development. The gate should have an owner, evidence to review, and clear criteria for moving forward or revising the plan.
Make the criteria practical. âThe prototype feels rightâ is difficult to assess consistently. âThe intended user can locate and operate the control in the agreed use scenarioâ is more concrete, although the exact test method and any required validation must be determined by the appropriate project specialists. For manufacturing, a gate might instead review whether assembly access, part breakdown, or a production assumption needs more investigation.
Document decisions as they are made. Record the alternatives considered, the reason a direction was selected, open risks, and who owns follow-up. This does not replace required design controls or quality records. It gives the cross-functional team a shared account of what it has agreed and what remains unresolved.
How should design, regulatory, and manufacturing work connect?
Product development is more effective when design decisions are informed by regulatory, quality, clinical, and manufacturing input at the right moments. That does not require every consultancy to provide every specialty. It requires clear responsibility boundaries, timely communication, and a shared understanding of which decisions each discipline can make or advise on.
Set up a responsibility map early. Name the person or organization responsible for product design decisions, regulatory strategy, quality-system activities, clinical input, testing, supplier selection, and manufacturing approval where relevant. The exact roles depend on the product and organization. The important point is to avoid an unspoken assumption that a design contractor owns work that its proposal does not include.
Bring the right specialist into a review before a decision becomes difficult to change. For example, seek appropriate regulatory and quality input when intended use or product claims are being framed. Ask manufacturing partners to review production assumptions when material, geometry, assembly, or process choices need that input. The consultancy can coordinate product design work and translate constraints into design questions, while each specialist retains responsibility for their own domain.
For manufacturing preparation, clarify whether the engagement includes concept-level feasibility, supplier communication, detailed drawings, bills of materials, assembly instructions, or production support. These are not interchangeable. Jackson Hedden describes integrated product development capabilities spanning industrial design, mechanical and electrical design, prototyping, and manufacturing support. Review the product design services and ask which specific elements fit the project in front of you.
Keep the design handoff in view from the start. Confirm which native files and exports will be supplied, how revisions are managed, what documentation accompanies the files, and whether a receiving manufacturer or internal team can use them. A handoff should not be left until the end to discover that a critical format, decision record, or manufacturing detail was never included in scope.
Review your medical device project with Jackson Hedden
Frequently Asked Questions
These answers offer a starting point for evaluating fit. The right scope depends on the device, the development stage, and the expertise already available within your organization.
What is a medical device consultancy?
It is a consulting or development firm that provides some form of support for medical-device work. Services vary and can include regulatory advice, product design, technical development, prototyping, or manufacturing support. Confirm the actual disciplines, deliverables, and responsibilities in the proposed scope rather than relying on the label.
Does every medical device consultancy provide regulatory consulting?
No. Some focus on product design or technical development, while other firms provide regulatory or quality expertise. Ask directly which services are included and who is qualified and responsible for regulatory decisions. Coordinate design work with your regulatory and quality specialists; do not assume product design support replaces them.
When should a startup bring in a consultancy?
Consider outside support when a specific product decision requires capabilities or capacity your team does not have, such as developing a physical form, coordinating mechanical and electrical constraints, planning a prototype, or preparing for manufacturing discussions. The engagement can be scoped around the next decision rather than an undefined request to âdevelop the whole device.â
What should a first project phase include?
It should include a defined problem, agreed activities, named outputs, a review point, and clarity about what the phase will not establish. Depending on the need, it could focus on requirements clarification, concept exploration, prototype learning, or a feasibility question. Tie the work to a decision the team must make and specify who will review it.
How can I compare consultancy proposals?
Compare proposals with the same checklist: scope, team roles, relevant experience, assumptions, prototype purpose, deliverables, decision process, specialist coordination, and handoff. Ask firms to clarify differences before comparing estimates. If one proposal covers substantially different activities, it is not an apples-to-apples comparison.
What should I ask about prototypes?
Ask what question each prototype is meant to answer, how closely it represents the intended product, what materials or components it uses, and what conclusions it cannot support. Also clarify who reviews the build, how findings are captured, and how the results affect the next design iteration.
A strong consultancy relationship begins with an honest scope: the product questions to resolve, the expertise required, and the evidence needed to choose the next step. Use that clarity to select a partner whose capabilities fit the work and whose responsibilities are explicit.
