Strivenn Thinking
Pull up a seat at our
digital campfire
where story, strategy,
and AI spark
new possibilities
for sharper brands
and smarter teams.
Sales Said You Lost on Price. Your Roadmap Believed Them.
By Jasmine Gruia-Gray
"Lost on price" is the most expensive two words in your CRM.
Roman priests believed Rome held a secret true name known only to the gods. If an enemy ever discovered it and spoke it aloud during a siege, the divine protection of the city would transfer to them. The name was so dangerous it was never written down, never recorded, never spoken. Its keeper was Angerona: a minor goddess always depicted the same way, one finger pressed to sealed and bandaged lips.
Angerona also presided over the winter solstice. Her festival, the Angeronalia, fell on December 21. The darkest night of the year, the moment before the light begins its return. She was the goddess of the thing that cannot yet be said. Not deception. Not ignorance. Sealed intelligence, fully present, waiting for the right conditions to surface.
Roman priests understood something worth holding onto: the most critical information about your market position is often already in the room. It is sealed. The question is whether you have built the process to open it.
Your customers already know why you lost their business. The principal investigator (PI) who stopped answering your Regional Sales Manager’s (RSM’s) emails knows. The lab manager who ran the head-to-head evaluation knows. The procurement lead who approved the vendor shortlist knows. All three have a finger pressed to sealed lips. Your current win/loss process is not the ritual that unseals them.
That is a Product Manager (PM) problem. It is also the PM opportunity hiding in plain sight.
The Intelligence Gap in Your CRM
Most RUO PMs inherit a win/loss process built by Sales, for Sales, and optimized for Sales reports. A loss code enters the CRM. A summary surfaces in the quarterly business review (QBR) deck. “Lost on price.” “Competitor had better sensitivity.” Something gets added to the backlog.
Here is what that cycle costs you specifically: every “lost on price” entry is a misfiled diagnosis. Labs running validated ELISA workflows on your antibodies don’t switch suppliers because a competitor charges 12% less. Revalidation alone erases that margin in staff hours within the first month. When a customer switches despite that friction, something structural failed first. The one conversation your RSM had with the procurement contact six weeks after the decision is not where you find it.
The PM who builds a direct intelligence system gets two things back: a roadmap grounded in what actually drives purchase decisions, and a commercial partnership that makes you harder to leave out of the conversations that shape strategy.
Three Assumptions That Are Filling Your Backlog with the Wrong Priorities
Assumption 1: “Win/loss is Sales’ job. I get the executive summary.”
Your RSM ran the post-loss debrief with one person: the contact who managed the vendor relationship. Not the PI who raised the original need. Not the lab manager who evaluated the options. Not the procurement lead who approved the vendor list.
In commercial strategy, the full group of people who influence or decide a purchase of an RUO life sciences product, the Decision Making Unit (DMU), typically involves the PI who identifies the scientific need, the lab manager or senior scientist who evaluates technical options, and procurement who controls the vendor contract. Each person holds a different piece of the decision. Each has different priorities and a different explanation for why you lost. Your RSM spoke to one of them, after the decision was over, when that contact had the most reason to be diplomatic.
The Association for Key Account Management’s (AKAM) key account competency framework (akam.org/kam-competencies) is built on mapping who holds budget responsibility, who participates in decisions, and who the principal influencers are. That depth of understanding is the gap most win/loss processes leave unfilled.
What a PM gets with more than win/loss summaries: a Product Requirements Document (PRD) grounded in what actually lost the deal, not what was easiest to report. Build a 30-day exit interview protocol that reaches at least two DMU contacts per evaluated loss. Six questions maximum. One of them should be: “What would have needed to be true for us to win?” That answer belongs in your roadmap.
Assumption 2: “We’re losing on product gaps. The answer is in the backlog.”
Your competitor’s qPCR master mix didn’t win on a 5% efficiency advantage. It won because their field application scientist (FAS) visited the lab three times during evaluation, their validated method note matched the customer’s exact thermocycler configuration, and their distributor rep had been building that relationship for 18 months.
That “sensitivity improvement” sitting in the backlog? There’s a good chance it isn’t the reason you lost. Without a structured post-loss conversation across the full DMU, the product gap is simply the easiest explanation to log.
Force every evaluated loss into four buckets before it touches the backlog: (1) technical performance gap, (2) commercial infrastructure gap (FAS coverage, distributor support quality, response time), (3) relationship or trust gap, (4) timing or budget mismatch. Track which buckets accumulate.
Post-Launch Intelligence Framework
The 4-Bucket Loss Taxonomy
Classify every evaluated loss before it touches your backlog
► Within 30 days of an evaluated loss, assign a primary bucket based on your DMU interviews, then cross-reference with the action below before opening a backlog item.
Technical or Performance Gap
The product did not meet a scientific or technical requirement that was decisive in the evaluation.
RUO Example
Antibody cross-reactivity failed multiplex western blot validation. Sequencer run quality fell below the customer's QC threshold.
Confirm with 2 DMU contacts before adding to PRD. Technical gaps are frequently the convenient explanation, not the actual one.
Commercial Infrastructure Gap
Product specs were competitive but the commercial experience around them was not.
RUO Example
FAS unavailable during the evaluation period. No validated method note for the customer's thermocycler model.
Bring the pattern to your VP of Sales for territory-level review. This is not a product roadmap item. Do not let it become one.
Relationship or Trust
Gap
A competing supplier had deeper or longer-established relationships with key DMU members.
RUO Example
Competitor FAS had been visiting the lab quarterly for 3 years. PI previously published using the competitor's reagents.
Map your DMU coverage in similar at-risk accounts now. Identify which contacts lack a direct relationship with your team.
Timing or Budget Mismatch
The customer was not in an active buying cycle or had budget already committed elsewhere.
Fiscal year budget frozen at time of evaluation. Account locked into a 3-year enterprise reagent contract.
Add to 12-month watch list. Re-engage 60 days before the next budget cycle. Do not treat this as a product or commercial failure.
Volume-adjusted thresholds
20+ evaluated deals/quarter
Any bucket exceeds 40% over 6 months
Structural intervention needed. One bucket dominating at this volume is not variance - it is a pattern.
8-19 evaluated deals/quarter
3 consecutive losses in the same bucket
Act on the streak. Don't wait for the 6-month window. Randomness rarely produces three identical failures in a row.
Fewer than 8 deals/quarter
2 proxy signals pointing at the same gap
Track quote-to-close by territory, time to initial technical response, and 90-day reorder rate. When two converge, that is your signal.
DMU = Decision Making Unit: the PI who named the need, the lab manager who evaluated the options, and procurement who approved the vendor. Classify losses based on primary bucket only. For AKAM's framework on understanding the full DMU, see akam.org/kam-competencies.
If one bucket represents more than 40% of losses in a rolling six-month window, your next investment should address that root cause, not the next item added to the backlog. Running fewer than 20 evaluated deals per quarter? Watch for three consecutive losses sharing the same primary bucket instead. That streak is your pattern. Randomness rarely produces three identical failures in a row.
What you get when you fix this: protection from the most expensive mistake in post-launch product management, which is funding development cycles to solve the wrong problem. When Buckets 2 or 3 are dominating, bring the pattern to your VP of Sales. Territory-level commercial gaps showing up across three or more losses are data they can act on. This is not a product problem, and you now have the evidence to say so.
Assumption 3: “We only need to debrief strategic accounts. They give us the real picture.”
Your largest pharma accounts have procurement teams trained to manage supplier relationships. Trained to give feedback that preserves future negotiating leverage, not feedback that exposes actual decision drivers. The 30 academic labs that ghosted your RSM’s follow-up emails are telling you the truth with their silence. You built a debrief process that captures the polished version of reality from the accounts with the most reason to polish it.
Run a tiered cadence instead. Strategic accounts: PM-led DMU interviews within 30 days of decision. Mid-market accounts: a three-question digital pulse at day 14 post-decision (why did you evaluate alternatives, what tipped the decision, what would bring you back). Synthesize both tiers quarterly.
What you get when you fix this: your most honest product signal. The mid-market data is unmanaged and unfiltered. It shows you the structural patterns before they become the competitive losses that land in the QBR deck.
Aligning with Your VP of Sales or CCO
This program earns commercial buy-in the moment you position it correctly. Don’t walk into your VP of Sales or CCO’s office and say you are taking ownership of win/loss analysis. Say: “I want to build an exit interview protocol that gives your team competitive territory intelligence and gives product management cleaner roadmap priorities. Here is the draft. Can we run the first five together?”
The four-bucket output serves both sides directly. Buckets two and three map commercial infrastructure gaps by territory and by product line. That is material a VP of Sales can use in the next territory review and present to the CCO as evidence of where commercial investment is being lost. You are building a shared system that did not exist before, with a quarterly output going to Sales, Marketing, and PMs simultaneously.
The PM who is a consistent source of commercial intelligence is harder to leave out of the conversations that determine what gets built next.
Your One Behavior Change
Angerona did not unseal her own lips. The Angeronalia did. That December ritual, the protocol, the calendar: these were the mechanisms through which sealed intelligence became accessible. Roman priests didn’t wait for it to surface on its own. They built the conditions.
Your customers have already told you what you needed to know. Not to your RSM. Not in the managed post-decision conversation. In the silence, in the unfiltered mid-market data, in the three DMU members who were in the room when the decision was made and whom nobody asked directly.
This week, block 30 minutes with your VP of Sales or CCO. Don’t bring findings. Bring a proposal: a six-question exit interview protocol, joint ownership, within 30 days of every evaluated loss, with a quarterly synthesis shared across Sales, Marketing, and PMs. Make it theirs as much as yours. That is the shift: from receiving a summary to owning the system that creates one.
Q: How do I get Sales to participate without this feeling like a performance review of their team? ▼
Lead with what Sales gets from the output, not what you are trying to find. Buckets two and three, commercial infrastructure gaps and relationship gaps, give a sales leader territory-level data on where commercial investment is being lost. That is material they can act on and bring to the next territory review. That framing shifts a politically sensitive request into a shared intelligence project. Start with the output they can use.
Q: We just launched. We have almost no loss data yet. Is it too early to set this up? ▼
It is exactly the right time. Set your baselines now: quote-to-close rate by territory, time to first technical response, and 90-day reorder rate at launch. Build the exit interview protocol and get alignment with your VP of Sales before you need it. The worst outcome is not having too little data. It is having data you cannot interpret because you forgot to set the baseline before the losses started.
Q: The DMU looks very different in an academic lab versus a large pharma account. Does the approach change? ▼
Yes, deliberately. In an academic lab, the PI often holds most of the decision authority and is the most accessible contact after the decision is made. One rigorous conversation usually surfaces what you need. In a pharma account, the PI, the lab manager, and procurement may each have been given a different version of why the decision went the way it did. You need at least two of the three to get a signal you can trust. Scale the depth of the interview to the complexity of the DMU, not the size of the account.