Key points
- For example, on a 900,000 dollar three year subscription, keeping a second credible bidder alive to the final round is commonly worth somewhere in the region of 5 to 10 percent of net unit price, so roughly 45,000 to 90,000 dollars on that one deal.
- The problem was that you had already told them, in writing, three months earlier, that only their product could satisfy lines 41, 96 and 173. The discount they eventually offer will be large as a percentage of list, which is exactly the trap described in discount off list is a trap.
A requirements list is a consensus artifact, not a specification
The reason nothing gets ranked is not laziness. It is that ranking is the only genuinely political act in the whole sourcing process, and the person holding the pen usually has the least authority in the room. Marking a line as a want rather than a need means telling a named colleague that their concern is tradeable. If the project later goes badly, that annotation is the first thing anyone will find. Marking everything as required costs nothing today and distributes the blame perfectly evenly. So the rational individual choice, repeated across eight stakeholders, produces an irrational collective document.
The second reason is that most requirement templates have no vocabulary for degree. A line either appears or it does not. There is no field for how much you would pay to have it, no field for whether a workaround exists, no field for whether three of the five bidders already offer it as standard so it costs nothing to demand. A requirement that every vendor in the category satisfies is not a requirement at all in any useful sense. It is a description of the market. Yet it sits in your scoresheet with the same weight as the one genuinely differentiating capability that only one bidder has, and that one bidder knows it.
The third reason is inheritance. Roughly half the lines in a typical enterprise requirements document are copied forward from the last cycle, and a good number of those were originally written by reading the incumbent vendor's own feature page. That is how a specification quietly becomes a portrait of one product. When you then run a competitive process against a portrait, the original sitter wins. This is a specific and measurable form of the problem we described in vendor lock-in: measuring switching costs before the vendor prices them for you, except here the lock-in is self inflicted and written down in your own document.
app.isvcosell.com/benchmarks
The benchmark library, filtered to the capability lines that carry a measurable price premium in closed deals.
THE SAME JOB, TWICE
TODAY, BY HAND
Read the 214 line requirements document end to end and try to guess which lines came from a real constraint and which came from a template
Build a weighting spreadsheet, send it to eight stakeholders, and receive five replies, three of which weight their own section highest
Search the shared drive and two years of email for the last time anyone priced a similar capability, to find out whether requirement 87 is expensive or free
Draft a scoring model you privately do not believe in, then watch four of six bidders fail it and write the sole source justification
Roughly 30 hours of analyst time, spread across three weeks, and a shortlist of one at the end of it
WITH ISVCOSELL
Upload the requirements document into intake and let ISVCOSELL cluster the 214 lines into capability groups, duplicates, and inherited text
Answer the triage prompts that separate genuine must-haves from wants, workarounds, and lines every bidder already meets as standard
Read the price impact view that maps each surviving requirement against closed benchmark transactions in the same category
Export the ranked requirement set with the walk away lines marked, ready for the scoresheet and the negotiation brief
About 45 minutes of your attention
What changes: roughly 30 hours of triage becomes about 45 minutes, which is around 29 hours returned to the procurement lead in a single cycle. The larger arithmetic is the shortlist. For example, on a 900,000 dollar three year subscription, keeping a second credible bidder alive to the final round is commonly worth somewhere in the region of 5 to 10 percent of net unit price, so roughly 45,000 to 90,000 dollars on that one deal. Run four sourcing events a year and the ranking discipline is worth more than the analyst time by an order of magnitude.
PART TWO
Mandatory everything is the same as leverage nothing
Negotiating power in software sourcing is almost entirely a function of what you can credibly decline. Not what you can threaten, not what you can benchmark, what you can decline. Every requirement you mark as mandatory is a thing you have publicly promised you will not walk away from. Two hundred and fourteen mandatory lines is two hundred and fourteen promises not to walk. The vendor's deal desk reads that document with more care than your own stakeholders did, and it reads it as a map of where you have no exit.
This is why the pricing conversation feels strange in these processes. You go in with a benchmark, you present a credible number, and the response is polite and immovable. The number was fine. The problem was that you had already told them, in writing, three months earlier, that only their product could satisfy lines 41, 96 and 173. The discount they eventually offer will be large as a percentage of list, which is exactly the trap described in discount off list is a trap. A sixty percent discount on a list price the vendor sets unilaterally is not a concession, it is a presentation choice.
"Every line you mark mandatory is a written promise that you will not walk away from it, and the deal desk reads that document more carefully than your own stakeholders did"
There is a second cost that shows up later. When everything is mandatory during selection, nothing is contractually protected after signature, because the team is exhausted by the time it reaches the paper. The lines that mattered most were never separated out, so they never became commitments, service levels or price protections. You end up with a contract that satisfies a scoresheet and protects nothing, which is the gap we map in the must have coverage grid.
PART THREE
The weekly licensing brief
Want to be updated when major licensing and pricing changes land? One analyst brief a week: the price rises, metric changes and audit campaigns that move software costs. Work email only.
Get the brief
Ranking at intake, before the market ever sees the list
The platform motion here starts earlier than most people expect. Not at the RFP, at intake. When a requirements document enters ISVCOSELL, ISVCOSELL reads it as a set of claims rather than a list of lines. She clusters near duplicates, flags text that has been inherited from previous cycles, and identifies lines that describe the same underlying capability in three different stakeholders' vocabularies. On a typical 200 line document that consolidation alone tends to remove a meaningful share of the volume before any judgement is required, because a large part of what looks like scope is repetition.
Then comes the triage. ISVCOSELL asks the question the template never had a field for: if this line were not met, what specifically happens. There are only a few honest answers. The deal is legally impossible. A workaround exists but costs operational effort. A workaround exists and costs nothing. Someone will be annoyed. Those four answers produce a rank, and crucially they produce it as a recorded response from a named function rather than as an analyst's private opinion. That changes the politics. The security lead is not being overruled, they are being asked to describe a consequence, which is a question they are qualified and willing to answer.
app.isvcosell.com/ISVCOSELL/requirements-triage
ISVCOSELL separating must-haves from wants and citing the closed deals behind each price impact estimate.
PART FOUR
Which requirements actually move price
Ranking by internal consequence is half the job. The other half is external. A requirement can be genuinely important to you and still be free, because every serious bidder in the category ships it as standard. Another can look minor and carry a large premium, because only two vendors support it and both price it as an upgrade tier. You cannot tell these apart by reading the requirement. You can only tell by looking at what comparable organisations actually paid.
That is where the benchmark library does the work. ISVCOSELL maps each surviving requirement against closed transactions in the same category and size band, drawn from modelled deal cohorts and organised into the benchmarks for 1,483 vendors. The output is not a score, it is a price impact estimate per requirement with the comparable deals behind it. Some lines come back with no measurable effect on net unit price. Those are the lines you should demand loudly and free. Others come back with a clear premium attached, and those are the lines that need a real internal decision rather than a checkbox.
1 The document shrinks before it goes out. Duplicate and inherited lines are consolidated at intake, so bidders respond to a specification rather than to a transcript of eight stakeholder meetings.
2 Every line carries a consequence, not a label. Instead of Required and Nice to have, each requirement records what specifically happens if it is not met, attributed to the function that said it.
3 Free demands are separated from paid ones. Requirements with no measurable price effect in closed benchmarks are marked as such, so you can insist on all of them without spending any negotiating capital.
4 Walk away lines are named in advance. You go into the final round knowing which three or four requirements you would genuinely lose the deal over, and which forty you would trade. So does your own team, in writing, before anyone is under pressure.
5 The shortlist stays at two or more. Because compliance is scored against ranked requirements rather than flat ones, credible bidders stop failing on lines that never mattered, and the price you are quoted is a competitive price rather than a sole source price.
6 The ranking survives into the contract. The lines you ranked highest become the candidates for service levels, commitments and price protection, rather than disappearing into an appendix nobody reads after signature.
PART FIVE
What this does not solve
Be clear about the limits. ISVCOSELL cannot rank your requirements for you in the sense that matters. She can identify duplicates, surface inherited text, ask the consequence question consistently and show you the market price of each line. She cannot decide that your compliance function is being overcautious about data residency, and she should not. That judgement belongs to people with accountability, and any tool that pretends otherwise is selling you a way to lose an argument you have not had yet.
The benchmarks also have honest boundaries. Price impact estimates are strongest in categories with deep comparable coverage and thinner where a requirement is genuinely rare. When only a handful of comparable deals include a given capability, the platform shows you the count rather than smoothing it into a confident number, and you should treat a thin sample as a direction rather than a target. Newly released capabilities in fast moving categories will always have less history behind them than mature ones.
And ranking cannot manufacture a second bidder where the market has only one. In some categories there is genuinely a single viable supplier for a specific regulated workload. What ranking does in that case is different but still valuable. It tells you honestly that you are in a sole source position before you spend eleven weeks discovering it, which means you can negotiate as a sole source buyer, on term length, price protection and exit rights, rather than pretending to run a competition the vendor already knows you have lost.
The failure mode this removes is narrow and common. It is the process where a shortlist of six became a shortlist of one for reasons that had nothing to do with capability, and everything to do with a spreadsheet column that said Required 214 times. That column costs real money every year, quietly, and nobody ever writes it down as a line item.
About the author
Morten Andersen, Cofounder, ISVCOSELL
Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built ISVCOSELL to make that pattern recognition repeatable.
More posts by Morten Connect on LinkedIn →
See it in the product
How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →
FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED
Find out which of your requirements the market actually charges for
The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.
Start your free trial → Or decode a contract free, no account
Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.
V ISVCOSELL
A ISVCOSELL product · © 2026
PLATFORM Benchmarking Negotiations Contract management AI workflows Document search Renewal calendar
PRODUCT Use cases Features Security Pricing Deployment options About
RESOURCES Getting started ROI calculator Agent protocol FAQ Blog Request access
Watch it in action
ISVCOSELL: the three minute demo What discount should we expect? One question, every agreement