Choosing the wrong engineering firm for a consumer gadget costs you a schedule slip. Choosing the wrong firm for a medical device can cost you the submission. FDA does not evaluate your product in isolation; it evaluates the evidence trail that produced it, and that trail is generated, or quietly not generated, by whoever does the engineering. A device that works beautifully on the bench with no design history behind it is not a submission package. It is an expensive prototype.
The criteria that matter here are mostly invisible in a portfolio. Renderings look identical whether or not anyone maintained a design input traceability matrix. Here is how to see past the portfolio and judge what a development partner will actually hand you at the end.
The Quality System Has to Exist Before Your Project Does
The first filter is ISO 13485 certification, and the useful question is not "are you certified" but "certified for what scope." Every certificate carries a scope statement, and a firm certified for design and development of electromechanical medical devices is a different animal from one certified only for contract machining. Ask for the certificate itself, read the scope line, check the registrar and the expiration date, and ask when the last surveillance audit happened and how many nonconformities came out of it.
Some firms will tell you they work "in accordance with" or "in the spirit of" the standard without holding a certificate. That is not automatically disqualifying for early feasibility work, but it means their procedures have never been examined by an outside auditor. When an FDA investigator asks who controlled the design and under what procedures, an uncertified consultancy leaves the entire burden of proof on you.
Design Controls Are a Verb, Not a Deliverable
US device work runs under 21 CFR 820.30 design controls, and the tell is whether the firm talks about them as ongoing practice or as paperwork assembled at the end of the project. Ask what their design input document looks like, how they process a change request that arrives after design freeze, who is required to sign a design review, and how many formal design reviews a program of your size normally gets.
Then ask to see a redacted design history file from a device that reached clearance. A serious firm has one and will walk you through it under NDA with the client identifiers removed. What you are looking for is specific: numbered design inputs written as testable requirements, a traceability matrix linking every input to a verification test and every test to a result, an ISO 14971 risk file that was revised as the design changed rather than composed in a weekend at the end, and design review minutes with named attendees and closed action items.
Verification Capability, Not Verification Promises
Ask directly which tests they run in house and which they subcontract. Nobody has everything. Environmental chambers, drop and vibration rigs, force and cycle testers, and basic EMC pre-compliance are reasonable to expect on site or a short drive away. Full IEC 60601 electrical safety and EMC testing goes to an accredited third-party lab, and the firm's real value is designing so the unit passes the first time instead of the third. Ask what fraction of their designs clear formal 60601 testing without a design change; a firm that has never tracked that number has never felt the pain of a failure.
The distinction between verification and validation should come out of them unprompted. If the person selling you the project uses the words interchangeably, the engineers probably do too, and the protocols will show it.
Regulatory Experience in Your Class and Your Pathway
"We have medical experience" spans everything from a Class I exempt bandage to a Class III implant. Push for specifics. How many 510(k) submissions have you supported, under which product codes, and how many drew an Additional Information request? What was the request about? A firm that admits to two AI letters and explains what it learned is more credible than one claiming a perfect record.
Sterile, patient-contact, software-driven, and battery-powered devices each add a discipline. If your device includes any of them, ask who on staff owns that discipline and whether that person is billable to your project or a name on the capabilities slide. The gap between the pitch team and the delivery team is the single most common complaint in this business.
The Handoff Nobody Scopes Properly
Development ends at design transfer, and that is where most projects lose months. Ask what the transfer package contains: released drawings with tolerances, an approved bill of materials with qualified suppliers, process validation protocols, inspection plans, and the device master record. Ask whether they have transferred to a contract manufacturer before and whether they will support the first production build. "We hand over CAD files" is not design transfer.
Questions to Ask Before You Sign
- Who specifically will work on this, what percentage of their time, and can I meet them before the contract?
- What is your change control process when I change my mind in month five, and what does a change cost?
- What happens to the project if my funding gaps for three months?
- Which of the regulatory deliverables are in scope and which are excluded?
- Who owns the IP, including background technology you bring to my design?
- Can I speak to two clients whose devices reached market and one whose project was canceled?
- What is your estimate range, and what would push it to the high end?
- If we fail verification, who pays for the redesign?
The canceled-project reference is the most informative call you will make. Ask that client how the firm behaved when things went badly. Broader guidance on reference calls is in our piece on checking references on an engineering firm.
Reading the Quote
Medical programs are quoted in phases for a reason: nobody can price verification before design inputs are locked. Be suspicious of a single fixed number covering concept through clearance, and equally suspicious of a quote far below the others, which usually means regulatory documentation was silently left out. Our breakdown of medical device development cost shows where the money normally goes.
Talk to Us About Your Device
Projects House develops medical devices for US clients through a global engineering and manufacturing network, working inside design controls from the first requirement rather than reconstructing them later. Send your device concept, intended use, and target classification through our contact form and we will tell you honestly what the pathway looks like.