Why the baseline goes missing
A requester writes intake to get to yes, not to expose the trade off. Stating the cost of the current workaround is work, and worse, it invites the question the requester would rather avoid: is the pain actually expensive enough to fund. So the field stays blank. The business case becomes a description of the new tool's features rather than a comparison against the present state. This is the same failure pattern as a ticket that names the vendor instead of the need, and it produces the same result: procurement inherits a conclusion and is asked to source it.
The reason this persists is structural, not personal. Nobody owns the counterfactual. The requester owns the request, finance owns the budget, but the cost of the status quo belongs to no one, so no one measures it. In a world without a baseline, every request clears the same low bar. A tool that saves ten hours a year and a tool that saves ten hours a week look identical on paper, because neither is asked to prove the size of the problem it removes.
PART TWO
What a missing baseline actually costs you
Three failures follow from the blank field. First, you cannot prioritise. If no request states the value of the current situation, you cannot rank one against another, so requests get funded in the order they arrive or in the order of who shouts loudest. Second, you cannot detect duplication. A request for a new tool rarely mentions that a broader platform already in the estate covers the same function, which is exactly how rights the business already owns get requested again. Third, you lose the negotiation. Without a documented cost of the workaround, you have no walk away position, because you have never established that walking away is survivable.
"If doing nothing has no price, then everything is worth funding and nothing can be ranked."
The compounding effect is a spend base full of tools that were never tested against the alternative of not buying them. Some of those tools overlap. Some replace a workaround that cost less than the license. You only find out at renewal, when the usage report is thin and nobody remembers why the purchase cleared.
PART THREE
The platform motion: show the estate, then demand the counterfactual
The fix has two halves, and both live before approval rather than after. The first half is visibility. Before you can judge a new request, you need to see what the business already owns and pays for, because a large share of new requests are quietly covered by an existing entitlement. The spend and estate view gives you that map, so a request for a point tool can be checked against the platform license already sitting in the portfolio.
app.isvcosell.com/spend
The spend and estate view shows what is already owned before a new line is approved.
THE SAME JOB, TWICE
TODAY, BY HAND
Read the request and notice it states no cost for the current workaround
Pull an export of active licenses and open two or three admin consoles to see if anything already covers the function
Email the requesting team and the tool owners asking what the manual process costs today in hours
Draft a business case comparison from the fragments that come back, if they come back at all
Roughly 9 hours, spread across two weeks of chasing
WITH ISVCOSELL
Open the request and let ISVCOSELL match it against the spend and estate view for overlapping entitlements
ISVCOSELL flags the covering license or confirms none exists
ISVCOSELL holds intake until the requester states the cost of the current workaround
Review the completed comparison, status quo cost beside proposed cost, in one screen
About 25 minutes of your attention
What changes: 9 hours of email archaeology becomes about 25 minutes of review. Across, for example, roughly a dozen requests a month, that is close to a hundred hours a month returned to the desk, and every request now arrives with the one number that lets you rank it.
The second half is intake discipline. ISVCOSELL, the analyst agent, pushes the request back until it states the cost of the current workaround before any new spend is approved. This is not a form field that people skip. It is a gate. The requester has to name what doing nothing costs, in hours or dollars, and ISVCOSELL cites the estate data that either supports a purchase or shows the function is already licensed. The same discipline catches shadow IT and duplicate tools at the request, because the overlap check runs before approval, not at the next audit.
app.isvcosell.com/ISVCOSELL
ISVCOSELL holds intake until the cost of the current workaround is stated, with estate figures cited.
PART FOUR
What a good request looks like once the gate holds
1 The status quo has a price. The request states what the current workaround costs, in hours per week or dollars per year, so the purchase can be tested against not buying it.
2 The estate is checked first. Spend visibility confirms whether an existing license already covers the function before a new line is considered.
3 Requests become rankable. With a stated baseline on every request, you can sort by value removed and fund the ones that clear a real bar, not the ones that arrive first.
4 Duplication surfaces at intake. Overlapping tools are caught before approval, when a decline costs nothing, rather than at renewal when the contract is live.
5 You keep a walk away position. A documented cost of the workaround tells you how much leverage you hold, which is the difference between negotiating and accepting the first quote.
None of this requires the requester to become an analyst. It requires the request to carry one number it was hiding, and the platform to check that number against what you already own. Once both halves run before approval, the pile of requests stops looking uniform and starts sorting itself. The connection to answering the CFO's overpaying question in one page is direct: you cannot answer whether you overpay until you know what each purchase was measured against.
PART FIVE
Honest limits
The platform can force the baseline to be stated and can check the estate for overlap, but it cannot verify that the stated cost of the workaround is honest. If a requester claims the manual process eats forty hours a week when it eats four, the arithmetic will still favour the purchase. ISVCOSELL cites what the estate data can prove, and it can challenge a number that looks inconsistent with usage, but it cannot audit a team's own time logs it never sees.
Visibility also depends on the estate being loaded. A license bought on a personal card and never brought into the system will not appear in the overlap check, which is the same blind spot that lets duplicate tools survive. And the gate raises the friction of asking, which is the point, but a determined requester with executive air cover can still route around procurement entirely. The platform makes the disciplined path the default and the well documented one. It does not remove the human judgement about whether a stated number is true, and it does not replace the conversation you still owe the business when a request is declined.
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
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
Make every request price the status quo before it prices the vendor
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.
Watch it in action
ISVCOSELL: the three minute demo What discount should we expect? One question, every agreement
Browse the full demo library →
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