Cisco ELA 2026: how the Enterprise License Agreement is priced. And how to negotiate the baseline before it sets your costs.

A Cisco ELA is priced off the quantity you commit, and every True Forward raises that quantity for good. Commit to what you can prove you run, and fix growth and renewal terms before you sign.

What does a Cisco ELA actually buy in 2026?

A Cisco ELA buys a fixed price on a defined slice of the Cisco portfolio for three or five years, plus the right to deploy inside that slice without a purchase order each time. Cisco sells it as a way to stop counting licenses, and counting Cisco licenses is miserable work.

What you sign is a multi year price floor, set by the quantity you commit. Floors are far easier to raise than to lower, which is why the committed baseline matters more than the discount printed on the quote.

ELA or EA: which name is on your contract?

Cisco now sells this model through its standard Enterprise Agreement program, currently EA 3.0. ELA is the older term for Cisco's individually negotiated enterprise deals, and many buyers and contracts still use it. The mechanics below follow the EA program, so read an older ELA against its own terms.

The current program guide sets a minimum of $100,000 total contract value in Full Commit Suites, over a 3 or 5 year term.

• One end date. Later orders co terminate with the initial order by default.
• Five portfolios. Networking Infrastructure, Applications Infrastructure, Collaboration, Security and Services.
• Full or partial commit. Full Commit Suites carry price protection for the term. Partial Commit Suites lock a fixed discount.
• Smart Account first. Licenses are provisioned through EA Workspace, which needs a Cisco Smart Account.

How the committed baseline sets the price

You declare how much of an architecture you intend to run, Cisco prices that quantity, and everything downstream keys off it. Your discount tier, your growth allowance and the renewal quote three years later are all calculated from it, yet few people in the room will remember agreeing the figure.

A 30 percent discount on a commitment 40 percent larger than your deployment is a well marketed increase, as the example further down shows. For the wider practice, see the Cisco services practice, the Cisco negotiation services and the Cisco ELA negotiation playbook.

Three term shapes

• Three years. Closer to a real planning horizon, so the baseline has less time to drift.
• Five years. A deeper discount, at the cost of your ability to walk.
• Custom term. Seen at the top of the market, and usually where the more interesting concessions live.

Commit to what Smart Licensing can evidence today and leave the architecture roadmap out of the baseline. Roadmaps slip, and baselines do not. The Cisco ELA true forward guide and the Cisco Smart Licensing guide cover the underlying mechanics.

Which Cisco ELA suites overshoot on scope?

Networking and security overshoot most often in the agreements we rebuild, and each of the four common suites has its own typical pattern. Cisco organizes an ELA by architecture, and each architecture carries a tiered suite. Because you buy a tier and not a single product, over scoping is easy to do and expensive to undo.

Cisco prices the tier that covers your most demanding site, then applies it to every site. You get one price and one entitlement, and you fund advanced features for buildings that will never switch them on.

How the EA 3.0 portfolios map to these suites

Cisco's current portfolio pages cut the catalog slightly differently. Catalyst, Meraki and data center networking sit in Networking Infrastructure, while Intersight sits in Applications Infrastructure with ThousandEyes, AppDynamics and Nutanix. The scope question does not change: which tier, on how many units, at which sites.

Ask for deployment evidence suite by suite before accepting a tier. If Cisco cannot show the telemetry, the tier is a guess, and a five year premium on a guess is a poor trade. See the Cisco Meraki licensing guide and Cisco DNA license rightsizing for the networking tiers.

How does Cisco True Forward work, and what does it cost over the term?

True Forward raises your entitlement to actual usage at each annual milestone and bills the increase forward to the end of the term. There is no back charge. It is the fairest true up mechanism any major vendor offers, and it can still push your run rate up sharply over a term, because the new baseline never comes back down.

What the program documents say

• Annual milestones. Dates are set at the initial order, and Full Commit Suites true forward once a year.
• Forward billing. Excess usage and its support are charged from the milestone date to term end.
• Invoice timing. Cisco invoices your partner of record 60 days after the milestone.
• Early triggers. Usage above 105 percent of initial entitlement in the first six months can bring the event forward, and above 115 percent later can prompt an off cycle invoice.
• Price protection. On Full Commit Suites, the True Forward price cannot exceed your original order price.

Why one busy year becomes a permanent cost

The new baseline stays for the rest of the term. Growth counted at the second milestone of a five year agreement is billed for three years, and it becomes the starting point for the renewal quote. Each later milestone adds to that floor, and nothing in the standard terms takes it back out.

The growth allowance is smaller than most buyers assume

Older Cisco EA and ELA terms offered a 20 percent growth allowance. The EA 3.0 program guide sets a one time 15 percent allowance, on the Security and Collaboration portfolios only. Networking has none, so every networking unit above baseline goes to True Forward.

Either figure is measured against your commitment. Committing 20 percent above real deployment to use the allowance means buying the same capacity twice. Usage inside the allowance also counts as current usage at renewal, where it gets priced.

A worked example of True Forward compounding

Say you commit 5,000 units on a networking suite for five years at a net $80 per unit per year, or $400,000 a year. At the second milestone you run 5,600 units. At the third you run 5,850.

The run rate ends 17 percent above what you signed. If 400 of the added units served a project that closed in year four, you paid for them to term end, and they stay in the renewal count unless the devices are released in CSSM before Cisco takes the figure.

Treat each milestone as a negotiation. You hold information Cisco wants, namely next year's deployment plan, and a milestone is a reasonable moment to trade it. Our comparison of true up and True Forward sets the two billing models side by side.

How do you measure your own Cisco consumption before renewal?

Reconcile entitlement against live deployment for each suite, then sort the result into four buckets. Whoever brings the consumption data sets the terms of the conversation. On most renewals we join, that party is Cisco, and the customer spends the cycle reacting to the other side's picture.

• Under consumed. Paid for, not deployed. Your strongest scope reduction argument, and the number Cisco will least want itemized.
• At consumption. Running roughly where you committed. Leave it alone and spend your negotiating capital elsewhere.
• Over consumed. Already above baseline and heading for a True Forward. Price it now, before the milestone prices it for you.
• Untracked. Deployed outside Smart Licensing visibility. Finding it during a renewal is expensive, and finding it during an audit is worse.

Where the numbers live

Smart Licensing and Cisco Smart Software Manager hold most of what you need. Check them against the operational consoles:

1. Cisco Smart Software Manager. Entitlement and reported usage by virtual account, the figures Cisco reads at the milestone.
2. EA Workspace. Suites, entitled quantities and consumption against them.
3. Catalyst Center and the Meraki dashboard. Device inventory and license tier per device.
4. Webex Control Hub. Assigned versus active users for Meetings, Calling and Contact Center.
5. Duo Admin Panel. Enrolled and active users, which often sit below total headcount.

Run this six months before you need it, because a position assembled under renewal pressure concedes. The Smart Licensing guide has the reporting detail, and our note on CSSM telemetry explains what Cisco sees before you do.

What happens to the baseline at Cisco ELA renewal?

At renewal Cisco resets the baseline to your current usage and quotes from there. That one sentence explains most of the unpleasant surprises in Cisco renewals, and few buyers hear it plainly in year one.

Three years of unmanaged growth become the opening position for the next three, and every True Forward absorbed without argument is now permanent. The discount percentage may even improve while the invoice grows.

Four terms worth more than the headline rate

• Scope. Which suites and tiers stay in.
• Quantity. The baseline itself.
• Term. What you pay for flexibility.
• Growth mechanics. How the next term's True Forward behaves.

Bring a credible alternative, meaning an actual costed architecture, even a partial one. Cisco prices competitive risk far more generously than loyalty, and an experienced account team can tell a threat from a spreadsheet. See Cisco negotiation services for how we run the cycle.

Why we advise against committing high to reach a better discount tier

The usual advice is to commit to the roadmap, because a larger commitment qualifies for a deeper discount band. We disagree, because roadmaps slip and the scope gap we measure at renewal shows the extra units often sit idle for the term. Say list is $100 per unit per year and you run 5,000 units.

The deeper discount costs $90,000 a year, or $450,000 over five years, for 2,000 units you may never switch on. Commit to the evidence and write the growth discount into the contract, so the roadmap buys at the better rate when it arrives.

A renewal where the discount improves and the invoice grows is easy to approve and hard to explain a year later.

Where does the money leak in a Cisco ELA?

Four leaks account for most of the overspend we find, and all four are visible in the contract before anyone signs it.

• Suite escalation. A tier bought for the demanding minority and applied to the compliant majority.
• True Forward compounding. Milestone increases absorbed as routine, each one permanently raising the floor.
• Consumption drift. Deployment diverging from entitlement, discovered by Cisco rather than by you.
• Renewal reset. The combined effect of the other three, arriving as a single number three years later.

None of this requires bad faith. It is what happens when one party tracks the numbers continuously and the other looks every three years. The Cisco ELA negotiation playbook 2026 covers each leak in detail.

Common mistakes and what they cost

• Letting the partner size the quote. Every unit of shelfware in a partner built baseline is billed for the full term.
• Counting users from HR headcount. Security and Collaboration are sized on users, and contractors who never log in, shared accounts and leavers all inflate the number.
• Missing the milestone. Once the invoice lands, the new quantity is already in the system and hard to dispute.
• Leaving retired kit registered. A license still assigned to a device you removed from service keeps counting as usage in CSSM until you release it, so clean up before each milestone.

What will the Cisco account team say, and how should you answer?

Expect the same handful of lines on most renewals, and have the reply ready.

• "The EA saves you money against buying à la carte." Ask your partner for a transactional quote on the same products and quantities, and compare the two line by line.
• "Premier is standard for customers your size." Ask which Premier features are active, and at which sites.
• "You have headroom in the growth allowance." Ask which percentage applies to which portfolio on your paper, and how that usage is treated at renewal.
• "This pricing expires at quarter end." That tells you whose deadline it is. Reply that you will sign when the open terms are closed, and have your approvals lined up so you can move fast once they are.

Which contract terms should you ask for in a Cisco ELA?

Ask for terms that limit how far the baseline can move, during the term and at renewal. They are worth more than a few extra points of discount.

• A cap on the renewal reset. Limit how far renewal quantity or price can rise over the final year run rate.
• Growth pricing fixed now. Future deployment then buys at today's unit price.
• A growth allowance where the program has none. The allowance is a contract term like any other.
• A swap right at milestones. Move value between suites or tiers when deployment changes, instead of paying for both.
• Usage data before each milestone. Any dispute then happens before the invoice is raised.

What have we seen in recent Cisco ELA renewals?

Across the Cisco renewals we ran in 2024 and 2025, the median discount from Cisco's opening position landed at 24 percent. The median gap between contracted software scope and live deployment landed at 26 percent. Those two numbers belong on the same page, and they rarely are.

The gap is widest where Cisco sells breadth. On most Cisco agreements we rebuild, networking and security are under deployed by 18 to 34 percent, and that breadth is what raises the renewal floor.

How the approach changes with the size of the agreement

A buyer near the $100,000 minimum usually runs one suite, and the main question is whether an EA beats buying the same products on their own. A large buyer across several portfolios has more to trade. Price each suite separately and use the portfolio you are least committed to as the competitive test.

In what order should you negotiate a Cisco ELA?

Evidence first, commercial terms second, and the close last, timed to Cisco's calendar. These are the 11 steps we run on a live Cisco ELA, and the early ones do most of the work.

1. Build the deployment picture first, suite by suite, before any commercial conversation opens.
2. Set the baseline from evidence of what you can prove you run.
3. Price each suite separately, with Cisco's standalone number for every architecture in the bundle.
4. Test the bundle against the parts. If the bundle does not beat the sum, take the parts.
5. Right size the tier: Premier where assurance is used, Essentials where it is not.
6. Model True Forward across the full term, covering every remaining year of compounding.
7. Negotiate the growth allowance separately, as its own contract term.
8. Fix the renewal mechanics in the original contract. Cap the reset before you need it capped.
9. Cost a credible alternative. Partial is fine, as long as it is real.
10. Time the close to Cisco's quarter. The last two weeks are worth several points, and Cisco's fiscal year ends in late July.
11. Keep the file open after signature, tracking consumption monthly so the next renewal starts from your numbers.

Start later than this and the timeline collapses. A renewal negotiated inside 90 days leaves room only to accept the price, with extra meetings along the way.

What to do next

If your Cisco renewal falls inside the next eighteen months, work through these in order.

1. Pull the entitlement report. Reconcile Smart Licensing entitlement against live deployment for every suite in the agreement.
2. Sort the result. Put a number against under consumed, at consumption, over consumed and untracked.
3. Model True Forward to term end, including its effect on the renewal baseline.
4. Test the bundle with standalone pricing for each suite.
5. Cost one alternative architecture, even partially, so the competitive position is real.
6. Open the commercial conversation on the timeline above and align the close to Cisco's quarter end.
7. Bring in help where it pays. Our six week Cisco ELA scoping engagement reconciles entitlement, sizes True Forward exposure and sets the negotiation plan, and our Cisco practice also runs renewals and audit defense. Vendor Shield covers all your vendors, and the software spend assessment sizes your Cisco position in under five minutes.

Frequently asked questions