Between 20 and 35 percent of committed Cisco suite value was never deployed, because the scope accepted at signing was the scope Cisco proposed
An enterprise agreement is sold as simplification, and simplification is what makes the unused half invisible. The scope you accept at signature decides whether the next three years save money or bank overspend.
Prepared by Redress Compliance · August 17, 2026 · Cisco advisory. 20 to 30 Cisco Enterprise Agreement negotiations advised, 2024 to 2025.
Executive summary
Between 20 and 35 percent of committed suite value was never deployed. Across the agreement term, on estates that had accepted the suite scope Cisco proposed rather than the scope their own deployment plan supported.
True forward is a reconciliation, not a free growth allowance. Estates that grew freely met a 15 to 25 percent true up at anniversary they had not budgeted for, because the allowance defers the charge rather than removing it.
Bundling collaboration and security into one agreement removes the right to drop either. Suite lock in is the quiet cost of the bundle, and it is decided by how the agreement is structured rather than by what it prices.
The renewal is where scope resets, so the deployment review has to come first. A quote received before you know your own deployment position is a quote you cannot argue with.
How does a Cisco enterprise agreement actually work?
A Cisco Enterprise Agreement is a multi year, suite based contract bundling software across networking, security, and collaboration into one commitment.
Its selling point is true forward: you deploy first and reconcile at anniversary, rather than buying ahead of need. The growth allowance lets you expand without an immediate charge.
That mechanism is genuinely useful, and it is also where the misunderstanding lives. The allowance defers the charge. It does not remove it, and the renewal trues up to actual consumption.
| Mechanism | What it promises | What it does | Where the cost lands |
|---|---|---|---|
| Suite bundling | Simplification across networking, security, collaboration | Prices coverage rather than fit | 20 to 35 percent committed and never deployed |
| True forward | Grow now, reconcile later | Defers the charge, never removes it | 15 to 25 percent true up at anniversary |
| Growth allowance | Deploy without immediate charge | Reads as headroom, behaves as credit | Renewal trues up to actual consumption |
| Single agreement | One contract, one renewal | Removes the right to drop one suite | Suite lock in, invisible as a line item |
The agreement prices the scope you accept, not the scope you deploy, and nothing in the structure ever reconciles downward. True forward moves in one direction. That is why over scoping at signature is the single largest overspend driver in the Cisco estate, and why it cannot be corrected until the term ends.
Where does the unused 20 to 35 percent come from?
From accepting a suite because it is offered as one, rather than because every user needs every part of it. The proposal is built around coverage, and coverage is easier to sell than fit.
- Score each suite against the users who would actually use it, rather than against the headcount that could theoretically be licensed for it.
- Separate the deployment plan from the wish list, because a suite that arrives eighteen months into a three year term is paying for eighteen months of nothing.
- Price the a la carte alternative for every suite you are unsure about, so the bundle has to beat a real number rather than an assumption.
- Refuse to bundle collaboration and security into one commitment unless the paper preserves the right to drop one without repricing the other.
The Cisco ELA guide
Suite scope, true forward rights, the growth allowance, and the buyer side moves across the Cisco enterprise agreement.
Get the brief →What the Cisco agreements showed, 2024 to 2025
Across roughly 20 to 30 Cisco Enterprise Agreement negotiations Fredrik Filipsson advised on between 2024 and 2025, the recurring finding was that buyers accepted the scope Cisco proposed rather than the scope they could deploy.
Scope inflation ran at 20 to 35 percent of committed suite value never deployed across the term. That is not a rounding error inside a bundle, it is a fifth to a third of the software line paying for nothing.
The second pattern was the true forward surprise. Estates that grew freely under the allowance met a 15 to 25 percent true up at anniversary that had not been budgeted, because the allowance had been read as headroom rather than as deferral.
The third was suite lock in. Bundling collaboration and security into a single agreement removed the leverage to drop either one at renewal, which is a structural cost that never shows up as a line item.
All three are decided at signature. None of them can be fixed inside the term, which is what makes the scoping conversation the whole negotiation. The renewal position sits at the ELA renewal playbook, and the reconciliation detail at the true up guide.
- Your quote benchmarked against 500,000+ real closed deals, adjusted for size, region, and industry
- True up modeled against the growth allowance so the anniversary charge is not a surprise
- Reduction rights and suite separability language flagged with the exact quote and page
Which terms decide what happens at anniversary?
Three, and all three are negotiable at signature in a way they are not afterward.
The growth allowance and what follows it
Establish exactly what the allowance covers, what it defers, and what the reconciliation looks like. An allowance you cannot model is a bill you cannot budget.
The right to reduce
Cisco paper does not grant a reduction right by default. If the estate can shrink, or a business unit can be divested, that right is worth more than a discount point.
Suite separability
Confirm in writing that dropping one suite at renewal does not reprice the survivors. Without it, the bundle that looked like a saving becomes the reason you cannot leave any part of it.
What to settle before signature
- The reconciliation method, written plainly enough that finance can model the anniversary charge from it.
- A reduction right, which Cisco paper does not grant by default and which matters most if a divestiture is on the roadmap.
- Separability between suites, so collaboration and security can move independently at renewal.
- A scope baseline you produced, built from deployment data rather than from the proposal.
What the engagements measured
Across roughly 20 to 30 Cisco Enterprise Agreement negotiations:
Suite value paid for across the term on estates that accepted the proposed scope rather than the deployable one.
Met by estates that grew freely under the allowance and had read it as headroom rather than as a deferred charge.
Bundling collaboration and security into one agreement removed the leverage to drop either at renewal, which is the cost that never appears as a line.
The renewal is the only point where scope resets, so a deployment review that arrives after the quote has already lost the argument.
Watch the briefing · 4:55Cisco Negotiations in 2026How to prepare, and the tactics you will face across the agreement conversation.
Your first five moves
- Pull deployment data by suite before the quote arrives, since a scope conversation without your own numbers is a scope conversation you lose.
- Score every suite against users who would actually use it, not against the headcount that could be licensed for it.
- Model the true up before you rely on the growth allowance, because 15 to 25 percent at anniversary is the unbudgeted norm.
- Get suite separability in writing, so dropping collaboration or security at renewal does not reprice what remains.
- Negotiate a reduction right at signature. The negotiation practice runs the deployment review and scopes the agreement with you.
Frequently asked questions
What is a Cisco Enterprise Agreement?
A multi year, suite based contract that bundles software across networking, security, and collaboration into a single commitment, with true forward rights that let you deploy first and reconcile at anniversary.
How much of a typical ELA goes unused?
Between 20 and 35 percent of committed suite value was never deployed across the term, on the agreements reviewed in 2024 and 2025. The cause is scope accepted at signing rather than scope planned.
Does true forward mean growth is free?
No. It defers the charge rather than removing it. Estates that grew freely under the allowance met a 15 to 25 percent true up at anniversary that they had not budgeted for.
Why is over scoping so expensive?
Because nothing in the structure reconciles downward. True forward moves in one direction only, so a suite committed at signature is paid for across the whole term whether or not it is deployed.
What is suite lock in?
Bundling collaboration and security into one agreement removes the leverage to drop either at renewal. It is a structural cost decided by how the agreement is built, and it never appears as a line item.
When can scope actually be reset?
At renewal, and only there. That is why the deployment review has to precede the quote, because a scope argument made without your own consumption data is one you cannot win.
Is a reduction right standard?
No. Cisco paper does not grant one by default. If the estate could shrink or a business unit could be divested, that right is worth more to you than an extra discount point.
Should collaboration and security sit in one agreement?
Only if the paper preserves the right to drop one without repricing the other. Confirm suite separability in writing, otherwise the bundle becomes the reason you cannot leave any part of it.
What is the biggest single lever?
Scope, settled at signature. It outweighs the headline discount, because a discount applies to a commitment you may not need while scope decides how large that commitment is.
How early should the review start?
Before the quote. Deployment data by suite, a scored fit for each one, and a modeled true up are what turn the scoping conversation from a vendor proposal into a buyer position.
