Renewal quotes anchored to the highest telemetry reading rather than steady state usage in 50 to 60 percent of cases, so the estate's worst week became the number the next term was priced from
Smart Software Manager is sold as a convenience and read as commercial intelligence. The seller has usually looked at your consumption data before you have.
Prepared by Redress Compliance · August 18, 2026 · Cisco advisory. 30 to 40 renewals advised, 2024 to 2025.
Executive summary
Renewal quotes anchored to the peak telemetry reading in 50 to 60 percent of cases. Not the steady state, not the average. The highest number the estate ever reported became the baseline for the next term.
Telemetry flagged feature usage above entitlement that buyers had not tracked, adding 10 to 20 percent to the ask before any negotiation about rate had begun.
Few buyers had reviewed what CSSM reports before the seller did. That is the whole asymmetry: the data is yours, it describes your estate, and the vendor reads it first.
Feature flags report what is enabled, not what is licensed. A feature switched on during a trial or a troubleshooting session reports the same as one bought deliberately.
What does Smart Software Manager actually report?
More than licence counts. Devices register, request entitlement and report consumption on a cadence, and the signal set is broader than the phrase licence tracking suggests. Cisco documents the model in its Smart Licensing Using Policy material.
| Signal | What it contains | Why the renewal team cares |
|---|---|---|
| Account hierarchy | Smart and Virtual Account structure | Ties every device to a billing entity |
| Device inventory | Serial, product family, model, software version | Shows the estate's true shape and age |
| Entitlement counts | Purchased and reserved units per licence tag | The number you paid for |
| Consumption counts | Active units in use per tag | The number they will quote from |
| Feature flags | Which features are enabled | Enabled is not the same as licensed |
Enabled is not the same as licensed
A feature switched on during a trial, a proof of concept or a troubleshooting session reports identically to one deliberately purchased. The telemetry does not record intent, and the renewal conversation does not ask.
Why does the peak reading become the price?
Because it is the highest defensible number in the dataset, and nobody on the buyer side has produced a competing one. A quote anchored to peak consumption is not a misreading. It is a selection.
Across the renewals advised, that selection was made in 50 to 60 percent of cases. The estate's busiest week, its migration overlap, its temporary dual running, all get read as the steady state the next term should cover.
Peak consumption is real data used to answer the wrong question. The right question is what the estate runs on an ordinary week, and only the buyer can answer that, because only the buyer knows which spikes were events.
The Cisco Smart Licensing control playbook
What CSSM reports, how the account hierarchy shapes the view, the telemetry hygiene review, and the offline options for regulated estates.
Get the brief →What 30 to 40 Cisco renewals showed
Across roughly 30 to 40 Cisco renewals Fredrik Filipsson advised between 2024 and 2025, Smart Software Manager telemetry was used to reset the baseline upward more often than buyers expected.
Peak counting led. Renewal quotes anchored to the highest telemetry reading rather than steady state usage in 50 to 60 percent of cases, which sets a baseline the estate does not actually need.
Hidden overage followed. Telemetry flagged feature usage above entitlement that buyers had not tracked, adding 10 to 20 percent to the ask. In most cases this was not deliberate over deployment, it was features left enabled.
Underneath both sat a data control gap. Few buyers had reviewed what CSSM reports before the seller did, so the first time the numbers were discussed was in a meeting the vendor had prepared for and the buyer had not.
Clean data is an asset in that conversation rather than a liability, which our brief on Cisco Smart Licensing argues in full. This page is about the other half: what the same data does when the seller reads it first.
- Every risky clause flagged with the verbatim quote and the page anchor
- Entitlements and consumption checked against the contract, tag by tag
- Paste ready replacement language and an evidence trail for the response
What controls does a buyer actually have?
Four, and all of them are organizational rather than technical. Cisco sets out the account model on its Smart Accounts pages, and the ownership question is the first one to settle.
- Account governance. Own the Smart Account rather than letting a partner hold it, because whoever owns it sees the estate first.
- Role separation. Limit who can enable features, since an enabled flag becomes an entitlement question later.
- Review cadence. Read the same reports the renewal team reads, on a schedule, not at renewal.
- Lead time. Run a telemetry hygiene review at least ninety days before any renewal or true forward.
Where the estate sits inside an enterprise agreement, the same telemetry feeds the true up. Our Cisco ELA guide and the true up guide work that mechanism.
Peak sizing is not unique to CSSM
The same pattern shows up wherever a count is taken at the busiest moment. Our brief on contact centre licensing works the annual peak against the busy hour, which is the same argument in a different meter.
When is an offline or air gapped model justified?
When the regulatory profile genuinely requires it, not as a way to hide consumption. On premises and offline Smart License Manager options exist and are documented alongside the wider Cisco software licensing model.
They carry an operational cost. Reservation and manual reconciliation replace the automatic flow, and somebody has to own that process for the whole term.
The commercial effect is a side benefit, not the reason
Choosing an offline model to control a data flow you have not otherwise governed is solving a governance problem with an architecture change. Fix the governance first and the architecture question usually answers itself.
What the renewals measured, 2024 to 2025
Two cuts of the engagement file frame the exposure.
Rather than to steady state usage, across the Cisco renewals advised in 2024 and 2025.
Where telemetry flagged consumption above entitlement that the buyer had not been monitoring.
Both numbers describe the same asymmetry. The data is accurate, it belongs to the buyer, and it is read by the seller first.
Watch the briefing · 5:33Cisco 2026 TacticsThe moves Cisco runs into a renewal, and which of them depend on data you could have read first.
Your first five moves
- Pull the same CSSM reports the renewal team reads, at least ninety days before the renewal, so the first look is not theirs.
- Establish steady state consumption against peak, because 50 to 60 percent of quotes anchored to the peak reading.
- Audit enabled feature flags against entitlement, which added 10 to 20 percent to the ask where nobody had tracked it.
- Own the Smart Account rather than leaving it with a partner, and separate the roles that can enable features.
- Bring your own baseline to the meeting. The Cisco practice reconciles the telemetry before the quote is built, which is the only point at which the anchor is still movable.
Frequently asked questions
What does CSSM report to Cisco?
Account hierarchy, device inventory with serial and software version, entitlement counts, consumption counts and enabled feature flags. It is broader than the phrase licence tracking suggests.
How is telemetry used against a buyer at renewal?
By anchoring the quote to the highest consumption reading rather than steady state usage, which happened in 50 to 60 percent of the renewals advised.
What is hidden overage?
Feature usage above entitlement that the buyer has not been tracking. Telemetry surfaces it at renewal, where it added 10 to 20 percent to the ask.
Does an enabled feature mean we are using it?
No, and that is the problem. A feature switched on during a trial or a troubleshooting session reports the same as one deliberately purchased, because telemetry does not record intent.
When should a telemetry review happen?
At least ninety days before any renewal or true forward. Later than that and the quote is already built on the vendor's reading of the data.
Who should own the Smart Account?
The customer, not the partner. Whoever owns the account sees the estate first, and that ordering is the whole commercial asymmetry.
Can telemetry be turned off?
Offline and on premises Smart License Manager options exist for regulated environments, at the cost of manual reservation and reconciliation that somebody has to own for the full term.
Is using an offline model a negotiation tactic?
It should not be. Choosing an architecture to control a data flow you have not governed is solving a governance problem the expensive way. Fix the governance first.
What counts as steady state usage?
What the estate runs in an ordinary week, excluding migration overlap, dual running and temporary events. Only the buyer can distinguish those, which is why only the buyer can produce the number.
What is the single most useful preparation?
Reading the reports the renewal team reads before they do. Few buyers had, and that gap explains more of the outcome than any argument about rate.
