Key points
- If your team catches even one split buy a month on a capability worth, for example, roughly 200,000 dollars in annual spend, the combined-volume discount you recover pays for the effort many times over across a year.
Why the split happens and why it survives review
The split starts with language. Two teams almost never describe the same need the same way. One writes automation platform, the other writes workflow orchestration, and the intake queue treats them as unrelated because the words do not match. We wrote a whole piece on that failure, the same capability, described two ways, bought twice, and the volume-split problem is its close cousin. Even when the words do match, the timelines rarely do, so the two requests land in different weeks of the pipeline and get assigned to whoever is free.
It survives review because procurement measures each deal against its own baseline. A buyer closing the forty-seat request looks at forty-seat comparables, lands a discount that looks fine for forty seats, and books a win. The ninety-seat buyer does the same. Both deals pass their own gate. There is no gate that asks whether these two should have been one. The organisation never sees the counterfactual, because the counterfactual is a deal that was never quoted.
It also survives because consolidation is work. Combining two intakes means reconciling two timelines, two budget owners, and two internal sponsors who each want their delivery date protected. It is easier to let each run. The cost of that ease is invisible until someone quantifies the discount the combined volume would have commanded, which is exactly the number nobody has time to build by hand.
app.isvcosell.com/spend
The estate view surfaces two intakes for the same capability side by side before either closes.
THE SAME JOB, TWICE
TODAY, BY HAND
Read both intake tickets and notice the descriptions might point at the same capability
Pull historical purchase records to confirm the two teams are not already covered elsewhere
Email both budget owners to compare seat counts, timelines, and delivery constraints
Draft a combined volume position and estimate what discount it should earn
Roughly 10 hours, spread across two weeks and blocked on two people replying to email
WITH ISVCOSELL
Open the estate view where ISVCOSELL has already flagged the two overlapping requests
Ask ISVCOSELL to combine the seat counts and confirm no existing contract covers the need
Read the benchmarked discount for the combined volume against closed comparable deals
Export the consolidated position as a single negotiation brief
About 25 minutes of your attention
What changes: 10 hours of email archaeology and manual math becomes about 25 minutes of review. If your team catches even one split buy a month on a capability worth, for example, roughly 200,000 dollars in annual spend, the combined-volume discount you recover pays for the effort many times over across a year.
PART TWO
What the combined number is actually worth
Discount curves reward volume in steps, not smoothly. A vendor that gives eight percent off forty seats may give fifteen percent off one hundred and thirty, because the larger commitment crosses a threshold in their own pricing model. When you buy the two halves separately, you sit below that threshold twice and pay the higher rate on both. The gap is not hypothetical. Benchmarking against closed deals at the combined volume shows you exactly where the step is.
This is where benchmarking against comparable closed deals earns its keep. Instead of arguing the combined buy deserves a better rate on principle, you show the vendor where similar organisations landed at similar volume. The conversation stops being about your budget and starts being about the market. That is a position the vendor cannot easily wave away, and it is one you can only build when the two intakes are treated as one.
"You negotiated from forty seats and from ninety seats when the leverage you held was one hundred and thirty."
PART THREE
The platform motion that removes the split
The detection happens before either deal closes. Spend visibility gives ISVCOSELL the estate, and ISVCOSELL reads incoming requests against it. When two intakes point at the same capability, even under different names and different volumes, ISVCOSELL flags the overlap and proposes the combined figure. One of the six specialist agents handles that cross-request matching so it is not left to a human noticing a pattern in a busy queue.
Once the combined volume exists as a single number, benchmarking prices it. The library holds benchmarks across 1,483 vendors, calibrated to documented market evidence, and the relevant comparables narrow to the deals that actually resemble yours. You get the discount the combined commitment should command, expressed as a percentile against real outcomes rather than a guess. That figure travels straight into the negotiation as evidence.
app.isvcosell.com/benchmark/workflow-automation
Percentile bars price the combined volume against comparable closed deals, not against each half.
If you want to interrogate the number rather than accept it, you can. Ask ISVCOSELL directly, as covered in what is covered and what a good discount looks like, and she answers with cited figures you can hand to the vendor. The point is that the combined position is built once, defended with evidence, and negotiated as a single commitment instead of two undersized ones.
1 One number replaces two. The combined seat count sits in front of the vendor as a single commitment, so you negotiate from the volume you actually hold.
2 The overlap surfaces early. ISVCOSELL flags the two requests while both are still open, before either closes at its own smaller-volume rate.
3 The discount is quantified, not asserted. Benchmarking against closed comparables shows the rate the combined volume should command as a percentile, not an opinion.
4 Timelines reconcile once, not never. Combining the intakes forces one conversation about delivery dates instead of two deals that quietly ignore each other.
5 The counterfactual becomes visible. You can see what the single buy would have cost versus the two separate ones, which is the number that never existed before.
PART FOUR
What this does not solve
Consolidation is not always the right answer, and the platform will not make that judgement for you. Sometimes two teams genuinely need different tools that only look similar in an intake ticket, and forcing them onto one contract creates a fit problem worse than the discount is worth. ISVCOSELL flags the overlap. Deciding whether the combined buy actually serves both teams is a human call.
Timelines can also be a hard constraint. If one team needs the capability this quarter and the other cannot commit budget until next year, combining them may mean the urgent team waits or the patient team pays before it is ready. The platform shows you the trade. It does not remove the trade. Some splits are the correct outcome once you can see the full picture, and that is fine. The failure this post names is not splitting on purpose. It is splitting by accident, and never knowing the combined number existed.
Finally, the discount curve belongs to the vendor. Benchmarking tells you where the market landed and where the volume threshold sits, but the vendor still has to agree to price the combined commitment on that curve. What the platform gives you is the evidence to insist. When the leverage is a shared decision, as it often is with cloud commitments in FinOps meets procurement, the same discipline applies. See the whole need as one number, price it against the market, and negotiate from there.
About the author
Fredrik Filipsson, Cofounder, ISVCOSELL
Fredrik has spent more than twenty years in enterprise software, with time at Oracle, IBM, SAP, and Salesforce before moving to the buy side. He structured and priced the kind of large agreements most buyers only see once or twice in a career, which taught him where the leverage sits and how far a vendor will actually move. He started ISVCOSELL to hand that knowledge to every sourcing team.
More posts by Fredrik 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
See both requests as one number before you sign either
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