A buyer-side reading list on Cisco and Adobe. The Cisco Enterprise Agreement and Smart Licensing for network, collaboration, security and SaaS. The Adobe Enterprise Term Licence Agreement, the named-user metric and the Creative Cloud, Document Cloud, Experience Cloud and Firefly add-ons. Two distinct catalogues, two distinct commercial models, one reading set for the buyer who runs both portfolios.
Cisco and Adobe operate two distinct catalogues. Cisco is the network and collaboration and security publisher whose commercial centre runs through the Enterprise Agreement and Smart Licensing. Adobe is the creative and document and experience publisher whose commercial centre runs through the Enterprise Term Licence Agreement and the named-user metric. The two are grouped editorially because the buyer-side methodology, the renewal cadence and the audit posture are structurally adjacent.
The procurement implication is that both portfolios reward the buyer who reads the catalogue suite-by-suite and the entitlement seat-by-seat. The Cisco EA tier choice and the Adobe ETLA named-user audit are the load-bearing moments in their respective renewal cycles. The Admodum Cisco practice and Adobe practice run the cycles inside one of three commercial frameworks.
This pillar groups the firm’s Cisco and Adobe commentary into ten editorial sections. The first half covers Cisco (sections ii through v); the second half covers Adobe (sections vi through ix); the closing section is the reading list.
The Cisco Enterprise Agreement is the consolidated commercial vehicle that packages Cisco subscription software across the named suites: Networking (DNA, Catalyst, SD-WAN), Collaboration (Webex, calling), Security (Umbrella, Duo, Secure Endpoint, XDR), Data Centre (Intersight, ACI) and Observability (AppDynamics, ThousandEyes). The EA delivers a multi-year subscription envelope at a stepped discount, with a true-forward (not true-up) reconciliation at each anniversary.
The buyer-side methodology sizes the EA tier per suite against the deployed estate plus a defensible growth curve. The publisher position will be to size the tier to the buyer’s aspirational rollout; the buyer position is to size to the realised utilisation and protect the headroom contractually rather than commercially.
The full methodology sits in the Cisco EA Tier Design paper. The paper sets out the suite-by-suite sizing approach, the growth-curve protection, the renewal posture and the audit interaction.
Each Cisco EA suite operates a tiered subscription. The Networking suite tiers run as Essentials, Advantage, Premier. The Collaboration suite tiers run as Webex Suite, Webex Flex, calling-only. The Security suite operates per-product tiers (Umbrella Insights, Professional, Platform; Duo MFA, Access, Beyond). The Data Centre and Observability suites operate similar tier ladders.
The buyer-side methodology selects the tier per workload and not per portfolio. A Networking suite that runs across a mixed estate (campus, branch, data centre) typically benefits from a Premier tier on the data-centre fabric and an Advantage tier on the wider campus. The Admodum methodology produces the per-workload tier recommendation that protects the buyer against the publisher’s tendency to over-tier the whole portfolio.
The tier choice is also a negotiating instrument. A buyer that elects a higher tier on one suite (where the feature use is real) gains leverage to negotiate a lower tier on another (where the feature use is shelfware). The renewal posture protocol designs the tier mix as a portfolio decision.
Cisco Smart Licensing is the publisher’s entitlement-management surface. The deployed estate registers against the Smart Account; the Smart Account reads the consumed entitlements against the contracted EA tier; the reconciliation is the publisher input to the true-forward at each anniversary.
The buyer-side question is whether the Smart Account reading matches the contractual entitlement and whether the consumption read matches the deployed reality. The two readings frequently diverge. The Smart Account may show overage that reads as a true-forward but reflects a misregistered device. The Smart Account may show under-use that reads as headroom but reflects an unregistered device that the next audit will surface.
The Admodum methodology runs the Smart Licensing reconciliation as a pre-renewal exercise. The reconciliation produces the agreed entitlement-versus-consumption picture before the publisher’s reading arrives. The output protects the buyer against publisher-driven true-forward surprises.
The Cisco EA true-forward is the contractual mechanism that converts overage at the anniversary into the new contracted tier. The mechanism reads forward (the buyer pays the new tier from the anniversary forward) rather than back (the buyer is not back-charged for the overage period). The true-forward is therefore a commercial moment, not a compliance moment.
The buyer-side renewal posture starts six months ahead of the anniversary. The Smart Licensing reconciliation produces the entitlement picture. The tier-mix protocol produces the per-suite recommendation. The growth-curve protocol produces the headroom position. The combined output enters the renewal negotiation as a buyer-side position, not as a publisher-side reading.
The full reading sits in the Cisco EA Tier Design paper and runs inside the Renewal Programme. The Cisco knowledge hub aggregates the wider Cisco reading.
The Adobe Enterprise Term Licence Agreement is the multi-year subscription contract that consolidates the buyer’s Adobe entitlements across Creative Cloud, Document Cloud, Experience Cloud and the generative-AI add-ons. The standard tenor is three years. The metric is named user; the contract records the seat count per product and the per-seat rate per year.
The buyer-side methodology sizes the ETLA seat count against the realised user count (not against the publisher’s aspirational rollout). The publisher position will be that the buyer should over-provision seats to absorb growth; the buyer position is that growth absorbs into the contractual true-up at the right rate and that over-provisioning at year-one creates shelfware that the next renewal absorbs into the baseline.
The full methodology sits in the Adobe ETLA Renewal paper. The paper sets out the named-user audit, the seat-count rationalisation, the renewal posture and the AI add-on read.
The three Adobe product families operate distinct commercial mechanics. Creative Cloud is the design and content suite, sold per named user with a per-app or All-Apps tier. Document Cloud is the PDF and signature platform, sold per named user with Acrobat Pro and Sign tiers. Experience Cloud is the marketing and analytics platform, sold per active profile and per data unit against the consumption-based metric.
The buyer-side methodology reads the three families separately. Creative Cloud sizing turns on the active-designer count, the All-Apps versus per-app mix, and the contractor and freelancer access pattern. Document Cloud sizing turns on the named-user count and the Sign transaction volume. Experience Cloud sizing turns on the data ingestion volume, the active-profile count and the named-product mix (Analytics, Target, Campaign, Real-Time CDP).
The Admodum methodology produces the per-family seat recommendation that aligns the ETLA to the realised user count. The named-user audit at renewal is the load-bearing exercise that prevents publisher-driven seat inflation.
Adobe Firefly is the generative-AI add-on family that sits across Creative Cloud, Document Cloud and Experience Cloud. Firefly pricing operates on a generative-credit metric that converts publisher-side AI compute into a per-credit consumption envelope. Adobe Express AI, Acrobat AI Assistant and Experience Cloud AI add-ons each carry their own SKU and metric.
The buyer-side methodology reads the Firefly credit envelope as a consumption commitment. The credit envelope is sized against trailing generative-AI use (not against the publisher’s aspirational adoption assumption). The IP indemnification position on Firefly outputs is contractually load-bearing and should be read in the ETLA addendum rather than assumed from publisher marketing.
The Admodum methodology negotiates the Firefly addendum explicitly. The full reading sits in the Adobe ETLA Renewal paper and in the wider AI Vendors practice for the buyer who is reading generative-AI commitments across the portfolio.
The Adobe renewal posture starts twelve months before the ETLA anniversary. The named-user audit reconciles the contracted seat count against the deployed Admin Console; the rationalisation pass removes inactive seats, contractor seats no longer in use and shadow-IT seats that the next renewal would absorb at the inflated rate.
The renewal sizing exercise runs the rationalised seat count against the contracted seat count and produces the buyer-side renewal position. The position is typically a flat or decreasing seat count (because the rationalisation removes inflation) combined with an explicit AI add-on negotiation.
The Adobe knowledge hub aggregates the wider reading. Active named-user audit responses route through the Audit Defence programme. Renewals route through the Renewal Programme.
The pillar groups Cisco and Adobe commentary into ten sections above. The spoke band below opens the forty named articles inside the cluster, twenty per publisher. The white papers below sit alongside the pillar as the methodology deliverables; the practice pages sit alongside as the engagement entry points.
A short follow-up checklist for the reader who is closing this page: visit the Cisco practice or Adobe practice for the engagement entry point; visit the Cisco knowledge hub or Adobe knowledge hub for the aggregated reading; request the two papers (Cisco EA Tier Design, Adobe ETLA Renewal); or open a private conversation with a senior Admodum advisor through /contact/.
Forty named articles inside the Cisco and Adobe cluster. Each one is a deep-read on a specific mechanic, written from the buyer’s seat.
A senior Admodum advisor will run the Cisco or Adobe methodology through with your CIO, CFO, procurement team or licensing manager on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active audits route through the Audit Defence programme.