Beyond checkbox compliance: Turning quality from a cost into an investment

“If you want to extend your runway, the way to do that is not to have a deficiency because of quality that costs you six months of delays, or nine months of delays, or even three months of delays,” Paul Grand, founder and CEO of MedTech Innovator, told the accelerator’s 2026 cohort at a workshop Infera co-hosted with Sequenex this summer. “The best way to extend your runway is to eliminate those things.”

Much of what companies spend on quality, in staff hours, consultant fees, and software, goes toward producing the record: the procedures, risk files, test reports, and sign-offs that show a regulator what you built and how. Without the record, no device gets to market. It’s how a regulator confirms a device is safe and effective, and how a team proves its process holds up. But when quality is treated as compliance alone, some of that spending produces documents that satisfy an auditor without making the product any better. On paper, everything checks out. In practice, procedures adopted from a template can describe a process nobody follows, and a test suite can report 95 percent coverage while the riskiest requirements go untested.

When the same budget goes into quality work that shapes the product, testing starts with the riskiest requirements, so the failures that matter most surface while engineers can still fix them. Usability work happens early enough to change the design, before anything is locked into tooling. The record that comes out of that work is just as complete, and the product is better for it.

That difference determines what quality costs. Quality spend is a cost when it only fills out the record. It’s an investment when it makes the product better. And investing in quality doesn’t mean adding more process. Overbuilding is one of the most common ways quality turns into pure cost.

Passing an audit is the minimum, but most quality systems are built to stop there

Companies at every stage end up with quality systems built to pass audits and little else, and for understandable reasons. Teams new to regulated development reach for templates, borrowed processes, and definitions conservative enough that no auditor could fault them. Established companies carry quality systems built for an earlier version of the business, systems that are hard to change mid-stream. Quality professionals are trained to think conservatively at every stage. Over time, those choices add up to checkbox compliance, where quality work exists mainly to complete the record.

The teams we spoke with compared notes on where their quality budgets went. What they described backs up something the FDA made explicit more than a decade ago: compliance is the floor, and quality is the strategy. Quality is the work that makes a product better than the minimum a regulator requires, and it’s where the return on quality spending comes from.

Checkbox compliance always costs more than you budgeted for

The true cost of checkbox compliance never comes in the form of consultant invoices or eQMS licensing fees alone. It shows up in engineering hours. When quality work happens separately from how the product gets built, it eventually stops the build. Engineers pause to produce documents, answer questions they’ve already answered in their own work, and revisit decisions the record never captured. We’ve watched it happen on teams we’ve worked with, led, and advised. Innovation freezes, and smart engineers start to feel that this isn’t what they signed up for.

It also shows up as rework. Team after team in the workshop described having to step back to move forward, redoing early quality work because the first version didn’t hold up at the next milestone. That means paying for the work twice: once for the first version, and again to redo it. The second round usually costs more, because the product has moved on and the evidence has to be reconstructed.

Right-size your QMS, because every procedure is a promise you’ll pay to keep

ISO 13485, the international standard for medical device quality management systems, is at its core a promise to have a process. It prescribes some things, but mostly it holds you to what you say you’ll do. Every procedure you write down is a commitment an auditor will expect you to keep.

That’s what makes overbuilding so expensive. A quality system sized for a larger company, a later stage, or a riskier product commits your team to work the product doesn’t need. Templates and outside processes arrive with their own language and their own assumptions. Reporting definitions written to catch everything do exactly that, and corrective actions and complaints pile up faster than anyone can learn from them. Once a procedure is in place, retiring it means explaining to an auditor why it no longer applies, so excess process tends to persist.

Right-sizing starts with the procedures you already have. Check whether your team follows them. Where it doesn’t, rewrite them to match how the team works, then add what makes the record defensible:

• A named approver
• A frozen version at approval
• Links to the requirement and the risk
• Evidence the review happened

Define exactly what needs to be reported, so your team isn’t logging everything under the sun out of worry that an auditor might disagree. It helps to make your decisions risk-based, so you’re afforded flexibility rather than rigidity in how you comply with your processes. That helps alleviate the burden on your team, and it gives you a clear justification when an auditor asks why everything isn’t done the same way every time. Then keep pruning as the product changes, so the quality system grows with the product rather than ahead of it.

The cheapest time to fix a risk, product design, or integration gap is early in development

Checkbox compliance also shows up in timing. When quality work is aimed only at the submission, the analysis that shapes the design gets pushed to the end. Risk, usability, and integration findings then arrive when they can no longer change much about the product.

For hardware and software alike, that means risk, failure modes, and usability analysis. Skip them early, and the problems surface once you’re deep in manufacturing or development, when fixing them means going back to the beginning and paying for new molds or reworking an architecture that’s already built.

Usability gaps can also surface at the FDA. Nikki once worked with a client who received a lengthy deficiency letter about human factors testing. The root cause was that they had never planned usability engineering around FDA expectations while they built the product. They had to withdraw the submission and build a full usability process, which took months and hundreds of thousands of dollars in rework and consulting. A submission can be complete by a company’s own standards without being high quality, and the difference shows up in how long it takes to get to market.

For connected devices, the gap is often integration. The device, the app, and the cloud can each work on their own while the full system has never been tested together the way it will be used.

In each case, the team could fairly say the product worked. But software that works and software that’s ready are two different things. Working is an engineering statement. Ready is a clinical, regulatory, and commercial one. Before each milestone, map what that milestone will ask to see, and fund the work that could still change the design.

Expertise is worth paying for when it fits the stage you’re in

Quality and regulatory work ebbs and flows in intensity. There are stretches where it feels like all you do, and months where it runs steadily in the background. That makes it hard to know when to hire, when to bring in a consultant, and when to do the work yourself. Staff or buy for the busiest stretch, and you overspend the rest of the year. Bring in too little experience, and the work may need to be redone.

Expertise is worth the money when it fits what your stage needs. There are multiple ways to reach the same compliance endpoint. The people worth paying for can find the one that fits where you are today, without defaulting to a one-size-fits-all approach.

The challenge is that you often have to choose a consultant or a quality hire before anyone on your team has the expertise to tell whether their work is any good. Founders and quality leaders at the workshop said the signals they relied on were references from people they trust, experience with products like theirs, and partners who listen before they prescribe. Several had learned the hard way that the lowest bid rarely turns out to be the cheapest.

Quality pays for itself when it finds the gaps you can still fix

Quality spend becomes an investment when it does what quality professionals are trained to do: find gaps, see where risk is concentrated, and spot where test coverage is thin relative to the risk profile. That work changes what you build. It also comes back around as a faster path to market, because fewer deficiencies mean fewer delays to launch and commercialization.

More experienced teams in the workshop shared what they'd found had been worth paying for: good people, a quality foundation early enough to grow from, and whatever it takes to fix your biggest weakness. None of those are about producing more documents. Each one helps a team do the work right the first time, early enough that it carries forward instead of being rebuilt later.