Cisco Advisory
Including Cisco Meraki in the Enterprise Agreement: What it Really Costs
What inclusion means, where the cost hides, and how to negotiate the Meraki line as its own deal inside the EA.
What inclusion means, where the cost hides, and how to negotiate the Meraki line as its own deal inside the EA.
Folding Meraki into the Cisco Enterprise Agreement simplifies the calendar, and a single blended number can quietly carry a weak Meraki rate.
It means Meraki dashboard licenses move from standalone renewals into the Cisco Enterprise Agreement as one of its suites, with a single co terminated end date and a growth allowance baked in.
Meraki licenses are still consumed per device through the Meraki licensing model, but the EA wraps them in true forward growth terms and a shared discount.
The hidden cost sits in device headroom, co termination write offs, and a blended discount that masks the Meraki line.
Meraki in the EA: where the cost hides
| Cost driver | How it appears | Buyer counter |
|---|---|---|
| Device headroom | Growth allowance above live count | Set allowance to a real 12 month plan |
| Co termination | Meraki dates pulled forward | Credit unused paid Meraki term |
| Blended discount | One number across suites | Break out the Meraki line discount |
| True forward | Annual growth billing | Cap unit price for the full term |
| Support tier | Bundled at premium | Match tier to actual need |
Tie headroom to a written deployment plan. We see 15 to 30 percent padding presented as standard when 5 to 10 percent matches real rollout.
If Meraki was renewed recently, co termination can write off 6 to 12 months you already paid. Ask for that term to be credited.
A single blended discount lets a strong networking rate carry a weak Meraki rate. Force the Meraki line to stand on its own number.
It makes sense when device growth is real and predictable, and when you can hold the Smart Licensing unit price flat for the term. It rarely makes sense purely to simplify a renewal calendar. Compare the included suites against the Cisco EA buying guidance.
Treat Meraki as a separate negotiation that happens to share a contract. Its own count, its own discount, its own price hold.
The common advice is that bundling Meraki into the EA always saves money through volume and simplicity. We disagree. In a clear majority of the estates we reviewed, the blended discount let Cisco carry a weak Meraki rate on the back of a strong networking rate, while the growth allowance billed for devices that were never deployed. The buyer side move is to demand the Meraki line discount as its own number, set the growth allowance to a written plan rather than a percentage, and cap the per device price for the full term. Simplicity is worth something, but not 10 to 20 discount points.
Lock the per device unit price for the entire term. Without that, annual true forward billing applies list creep to every new device you add.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A Meraki line inside an Enterprise Agreement is still a Meraki negotiation. The contract shares a signature, not a discount.
It moves Meraki dashboard licenses into the Enterprise Agreement as a suite with one co terminated end date and a forward growth allowance. Licenses are still consumed per device.
Sometimes, but not automatically. The saving depends on real device growth and on holding the unit price flat. A blended discount can mask a weak Meraki rate.
Per device, the same as standalone, but wrapped in true forward growth terms. You deploy under an allowance and the EA bills growth annually.
Co termination aligns Meraki to the EA end date. If Meraki was renewed recently, it can write off 6 to 12 months you already paid unless you negotiate a credit.
Tie it to a written 12 month deployment plan, usually 5 to 10 percent. Padding of 15 to 30 percent is common and rarely justified.
A single blended number lets a strong networking rate carry a weak Meraki rate. A separate Meraki discount number exposes the real deal.
Keep it standalone when the estate is flat, when growth is unpredictable, or when the EA discount on Meraki will not match the networking line.
Cap the per device unit price for the entire EA term. Without a cap, each added device is billed at a drifting list price.
The guide gives you the device reconciliation method, the growth allowance test, and the clauses that hold per device pricing flat.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
