Creating a Defensible Medical Device Competitive Comparison

A procurement analyst asks you to fill in a competitive comparison table before the technical committee meets, and the fast answer feels like the right one. Rank your system higher on every row, describe the other device in the worst light you can get away with, and hand back a document that reads like a sales pitch. That approach can cost you the deal later, because a table full of claims you cannot back up tells a technical buyer more about your tactics than about the equipment. As a capital sales representative, you get judged on the paper trail you leave behind, not only on the conversation in the room.

Why This Conversation Goes Wrong

The trap is speed. Procurement wants the table fast, so you fill in gaps from memory, from an old sell sheet, or from something a colleague said about the competitor two years ago. None of that survives contact with a technical committee that actually owns the equipment specs. Someone on that committee has used the competitor device, or knows someone who has, and one wrong row undoes trust in every other row.

There is a second trap underneath the first one. The procurement analyst is not the decision maker. They are collecting input for engineers, clinicians, and service leads who will pick apart every claim before a purchase order gets signed. A comparison table with unsupported adjectives does not help that group. It gives them one more thing to argue about, and it puts your name on the argument.

What A Defensible Comparison Actually Contains

A comparison table exists to make the committee's decision easier to check, not easier to reach. That means every row needs three things, a criterion the committee actually cares about, a source for the claim, and a person who can verify it if challenged. Marketing language does not meet that bar. A spec sheet citation does.

This is the same discipline that shows up across capital equipment evaluations generally. If you have handled a device cybersecurity review, you already know how a technical group treats unverified input, they set it aside and ask again. The approach described in Sequencing a Capital Device Cybersecurity Review works for the same reason a good comparison table works, the committee gets a document they can trace back to a source instead of a document they have to trust on faith.

How To Prepare Before You Answer

Do not open a blank table and start typing. Ask the procurement analyst which specifications, workflow requirements, service considerations, and site constraints the committee will actually use to judge the equipment. A generic comparison built around specs nobody asked for wastes your time and theirs.

Get the exact competitor model number. "The other system" could mean three different products from the same company, each with different specs. Ask for the source the committee expects you to cite, and ask whether their procurement process has rules about how vendors may characterize a competitor, because some health systems restrict this explicitly.

Then build your side first. Pull approved specifications for your own product and label the source of each one, a data sheet, a regulatory filing, a clinical study your company published. If a row the committee wants filled cannot be supported by a source you are allowed to use, say so directly instead of guessing.

What To Say When The Analyst Pushes For A Verdict

Picture the analyst asking, "Where does the other system fall short compared to yours." A vague or defensive answer here reads as evasive, and a confident answer without sources reads as unreliable. Neither helps you.

You can say, "I can build a comparison against the criteria your committee is actually using. Can you send me the exact model number they are evaluating and their list of evaluation questions. I will bring approved specifications and sources for our system for each one."

The analyst might press further, "Just tell me the two or three things where you clearly win." You can answer, "I want to give your committee something they can rely on rather than my opinion. Once I have their criteria, I will show you every row where our documentation clearly supports an advantage, and I will flag any row where the honest answer is that both systems need direct evaluation."

If the analyst asks you to guess at a competitor spec you cannot source, say plainly that you will not put an unverified number in front of a technical committee, and offer to tell them exactly what documentation would settle the question.

Mistakes That Undermine Your Credibility

Guessing at competitor specifications from memory is the most common mistake, and it is the one that does the most damage, because a wrong number gets discovered eventually and taints everything else you submitted. Pulling numbers from your own marketing collateral instead of engineering documentation is nearly as bad, since a technical reviewer treats the two very differently even if the numbers happen to match.

Staying silent on a row you cannot fill is another failure. Silence reads as an admission that your product loses on that criterion, even when the real issue is that no permitted source exists yet. Say what you do not know and what would resolve it.

Promising to "get back with the real numbers" and then not following through in writing is worse than never promising at all. The same discipline applies to other capital equipment conversations, including the one described in Surfacing Equipment Decommissioning Dependencies Earlywhere naming what you do not yet know, early and in writing, is what keeps a deal moving instead of stalling it.

How To Practice And Score This Conversation

A manager can run this drill with almost no setup. Take a real comparison table from a past deal and read every row out loud. Mark each claim as sourced, unsourced, or an adjective doing the work a source should be doing. Unsourced claims and bare adjectives get rewritten as either a cited specification or an open question the committee can validate themselves.

Then run the live exchange. Have a peer play the procurement analyst and push for a fast verdict, the way a real analyst under a deadline will. Score the rep on three things, whether they asked for the committee's actual criteria before answering, whether every claim they made included a source, and whether they named gaps directly instead of talking around them.

DealSpeak is built for this kind of rehearsal, since a rep can run the same exchange against an AI counterpart playing the procurement analyst and see exactly where the answers drifted into unsupported territory. The Medical Devices practice conversations library has other scenarios built around the same habit, separating what you can prove from what you are tempted to claim.

A comparison table is not a sales tool, it is evidence the committee will reuse long after your call ends. Build every row so it survives someone else checking it, and you protect both the deal and your name on the document.