Most business-case templates for a quality management system (QMS) assume the company has already decided it needs one. They compare vendor pricing against the cost of the system being replaced, factor in hours saved, and produce a payback period. A pre-market team running on a shared drive has nothing to put in the "current system" column, at least nothing with a price tag attached, so the template returns a number that looks like new spending with no offset.
Building the case at this stage takes a different construction. The comparison is not software against no software. It is two ways of producing the same required output, which is a documented, traceable record of how a device was designed, what risks were identified, and how the design was verified and validated. One of those ways bills monthly. The other one bills later, unpredictably, and usually in engineering hours during a quarter when the team has none to give.
1. Price the system you already have
Every pre-market company has a QMS. It's a shared drive, a file naming convention, a spreadsheet that tracks requirements, and two or three people who remember why a design decision was made in March. Nobody costs it, because it never generates an invoice.
Costing it is the first step, and the method is straightforward. Pick a two-week window and ask the team to tag hours against a short list of documentation-adjacent tasks: writing and reformatting procedures, hunting for the current version of a document, chasing signatures, rebuilding a traceability matrix after a requirement changed, and reconstructing the reasoning behind a decision nobody wrote down. Multiply by fully loaded hourly cost and then annualize.
The result tends to be uncomfortable, and it is uncomfortable in a way that matters to a founder, because the people doing this work are usually engineers. Instead of working on the device, they're spending a huge amount of time on busywork, slowing down the pace of development and dragging out timelines.
2. Put dates on the events that will force the work
A business case built on principle loses to a business case built on a calendar. Any argument that a QMS is needed "eventually" invites the reasonable response that eventually is not now.
List the events that will require documented quality records, and put a target date on each one. For most pre-market companies the list includes a 510(k) or CE marking submission, a Series A or B diligence process, a first ISO 13485 certification audit, a first supplier or customer quality agreement, and a first clinical investigation.
Next to each event, write the artifact it requires. A submission reviewer wants traceability running from user needs through design inputs, design outputs, and verification and validation activities, a requirement that now sits under ISO 13485:2016 Clause 7.3 following the FDA's Quality Management System Regulation (QMSR) transition in February 2026. Diligence teams ask for a design and development file and a risk management file built to ISO 14971. Auditors want document control plus evidence the controls were followed, not just written.
Working backward from those dates produces the part of the business case that changes the conversation. A submission targeted for the third quarter of next year means the design and development file has to be completed a quarter earlier, which means design inputs need to be under control now, not after the design settles. Stated that way, the QMS stops being a compliance purchase and becomes a schedule dependency, which is a category of risk founders already know how to evaluate.
3. Estimate the rework, because that's where the money is
Documentation captured alongside the work costs the hours the work takes. Documentation reconstructed afterward costs those same hours, plus the time spent interviewing engineers about decisions made a year ago, plus whatever verification has to be repeated because the first round cannot be evidenced.
There is a way to estimate this without guessing. Take a piece of design work the team has already completed without formal records, and have someone reconstruct it properly: the inputs, the outputs, the rationale, the trace. Time it honestly. Apply that per-unit cost to the volume of design work still ahead, and add a factor for the portions where the reasoning has already been lost to turnover or memory. Most teams that run this exercise quickly stop arguing about the software price, because the reconstruction number is larger than the annual subscription by a wide margin and it arrives all at once.
Hart Biologicals cut audit preparation time by 50% and accelerated design and development by 75% after moving off a paper-based system, largely because the reports and documentation were no longer built from scratch each time. For a fuller accounting of what the delay itself costs across a pre-market program, the real cost of waiting to build your QMS breaks the categories down in more detail.
4. Size the ask so the number survives scrutiny
The fastest way to lose this argument is to walk in asking for a system built for a commercialized manufacturer with a portfolio of cleared products and a dedicated compliance staff. A skeptical founder will price that system, correctly conclude it is oversized for a lean, pre-market team, and reject the whole premise along with it.
Scope your ask to what a pre-market team actually has to produce right now: document control, design controls with real traceability, risk management, and training records. Supplier quality depth, full corrective and preventive action (CAPA) infrastructure, and post-market surveillance can wait until there is a supply chain and a product on the market to attach them to. A right-sized QMS for pre-market teams walks through where that line sits and how it moves as a company progresses through design and development.
5. Answer the three objections before they land
Three responses come up in nearly every version of this conversation. The case is stronger when it takes all three on directly instead of waiting for them.
- Spreadsheets are free. They are not free. They are unpriced, and the cost shows up as version confusion, broken traceability when a requirement changes, and audit findings that arrive after the work is finished and expensive to fix.
- All of this can be handled closer to submission. Cleanup consistently costs more than setup, and the delay compounds, because reconstruction lands in the same quarter as the submission prep or the fundraise that made it urgent.
- Implementation will slow the team down. Weigh it against the hours already going to manual documentation work, which the exercise in the first section will have quantified by the time this comes up.
6. Bring one page, not a deck
A finished case fits on a single page:
- The annualized cost of the informal system in place today
- A dated list of the events that will demand documented records, with the artifact each one requires
- An estimate of what reconstruction costs against what capture costs
- The right-sized scope of what is actually being requested
- An implementation timeline that does not threaten the development schedule
The question in front of the room is then a clean one. The work will get done either way, so the decision is whether it gets paid for at a known rate now or at an unknown rate later, under someone else's deadline.
To put real numbers against the ask, a demo of Greenlight Guru will show what a right-sized pre-market QMS looks like in practice and what it takes to get running.
Content Toolkit for Product Development
