Key points
- It probably said something like 250 seats, or 2TB of storage, or 5 million API calls a month.
Why the snapshot wins in the room
Intake rewards specificity. When a requester writes 250 seats, that number is checkable, defensible, and easy to approve. When someone says the team might grow to 400 by year two, that is a projection, and projections invite argument. So the projection gets dropped in favour of the fact, and the fact becomes the commitment. The organisation optimises for a spec that is easy to sign, not a spec that survives contact with its own growth.
There is a second reason the snapshot persists. The person who files the intake ticket is rarely the person who owns the renewal. The requesting team knows this year's headcount plan. They do not carry the memory of what happened the last three times a contract was sized to launch-day usage. That institutional knowledge lives in procurement, and procurement usually sees the request after the number is already written down. We wrote about a related version of this in the one line request that hides a multi year commitment.
app.isvcosell.com/benchmarks
The benchmark library, sorted by how comparable buyers structured commitments for growth.
THE SAME JOB, TWICE
TODAY, BY HAND
Pull the intake ticket and confirm the current usage figure the requester supplied
Chase the requesting team by email for a headcount or usage forecast, then wait days for a hedged answer
Search old contracts and invoices to find what growth looked like on the last comparable deal
Draft a sizing assumption and a growth clause from scratch, unsure whether the tiers you propose match the market
Roughly 10 hours, spread across two weeks of back and forth
WITH ISVCOSELL
Open the intake record where ISVCOSELL has already prompted the requester for a trajectory, not just a snapshot
Read the benchmark cohort of comparable closed deals showing how peers tiered for growth
Let ISVCOSELL translate the captured trajectory into a sizing range and suggested step-up terms
Review the draft commitment structure and adjust before it reaches the vendor
About 35 minutes of your attention
What changes: 10 hours of email archaeology and guesswork becomes about 35 minutes of review. Across a portfolio filing, say, 40 sizing decisions a year, that is roughly 380 hours returned, and more to the point it is 40 contracts sized to the curve instead of the snapshot, where a single mis-sized deal can cost more in year-two overage than the whole exercise saved.
PART TWO
The gap always favours the seller
Consider what happens after the undersized spec is signed. Usage grows past the committed tier. Now you have exactly two moves, and the vendor priced both. Option one is overage, where you pay the list rate for everything above your commit, and list is the number you negotiated away from at signing. Option two is early renegotiation, where you reopen the contract mid-term because you need more capacity, which hands the vendor a live deadline and a buyer who cannot walk away.
"A spec frozen at today's scale is not a neutral number. It is a future negotiation you have already agreed to lose."
This is the same dynamic we describe in sizing AI commits from your usage, not the vendor's growth story. The vendor's growth story is optimistic on purpose, and the buyer's snapshot is conservative by accident, and the space between them is where margin lives. The fix is not to guess higher. The fix is to capture the real trajectory at intake and to size the commitment against evidence of how comparable buyers actually structured their deals.
PART THREE
What the platform does about it
Two things happen. First, ISVCOSELL changes the intake conversation. Instead of accepting the snapshot and moving on, the intake prompt asks for the trajectory the eventual commitment has to accommodate. Where is headcount going. What does the data volume look like at term end. Is usage seasonal or steadily climbing. These are questions the requesting team can answer, but only when someone asks them at the right moment, before the number hardens into a spec.
Second, the benchmark library shows you how comparable buyers handled the same problem. You are not inventing a growth clause in a vacuum. You are looking at the structure of comparable deals, drawn from documented market evidence, filtered down to the cohort that matches your vendor, your size, and your usage shape. With the peer cohort on the table, the pattern of how peers tiered their commitments, negotiated step-up pricing, and capped overage is not opinion. It is evidence you can put in front of a vendor.
app.isvcosell.com/benchmarks/detail
A single benchmark showing how peers structured tiers and step-up pricing against usage growth.
The two motions reinforce each other. The trajectory ISVCOSELL captures at intake tells you which cohort of benchmarks is relevant, and the benchmarks tell you what a defensible structure for that trajectory looks like. This is the difference between researched pricing evidence and survey averages, a distinction we draw out in survey benchmarks flatter everyone.
1 Intake asks for the curve. ISVCOSELL prompts the requester for the growth trajectory, not just today's usage, so the number that reaches procurement already carries its own future.
2 The cohort narrows to your shape. The captured trajectory selects the comparable closed deals that actually match your usage pattern, not a generic average.
3 The structure comes from evidence. You see how peers tiered commitments, negotiated step-up rates, and capped overage, then you propose the same structure from a position of proof.
4 The commitment absorbs growth on your terms. When usage climbs, it climbs into pre-negotiated tiers, not into list-rate overage or a mid-term renegotiation you did not choose.
PART FOUR
What this does not solve
Be honest about the limits. The platform cannot tell you what your headcount will actually be in two years. If the requesting team's forecast is wrong, the sizing built on it will be wrong too, and no benchmark corrects for a growth number that was fiction from the start. What the platform does is make the assumption explicit, sourced, and reviewable, so that when reality diverges you know exactly which input to revisit rather than discovering the gap on an overage invoice.
It also cannot force a vendor to offer step-up pricing they do not sell. Some vendors structure their catalogue precisely to make growth expensive. The benchmarks will show you that, and they will show you which comparable buyers refused those terms and what they got instead, but the negotiation is still yours to run. The platform arms the buyer. It does not replace the buyer. When the structure genuinely does not exist in any single vendor's offering, that is a different problem, the one we cover in the spec that adds up but nobody sells.
And it does not retroactively fix a contract already signed to a snapshot. If you are living with an undersized commit today, benchmarking will tell you how far off market your position is and what a fair correction looks like, but the leverage you have mid-term is the leverage the original spec left you. The value compounds when you use it at intake, before the number hardens, which is the whole point of asking for the trajectory in the first place.
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
Size the commitment to the trajectory, not the snapshot
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