Cisco EA Renewal, Part 2: Negotiation Prep, Three Calls Into July

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

Call one: the framing call 0:00

Part one gave the talking points. Now the three calls. I am Claire, Tom is with me, and this is part two of the VendorBenchmark Cisco EA renewal prep. Call one, six to nine months out, forces the renewal basis onto activated counts.

Open with it: we run this renewal as a formal sourcing event, alongside an activation audit across every suite in the agreement; all commercial communication routes through me, including anything through the partner; and today I need a quote basis of activated counts rather than entitlements, the True Forward definitions and anniversary dates in writing, and your timeline from quote to signature.

Five questions 0:43

Five questions, in order. Will the renewal be quoted per suite at our activated counts, confirmed in writing before anything else. Send me the True Forward definitions: what is measured, when, and how the anniversary resets work. Which suites, including Splunk, does Cisco intend to add or restructure, priced line by line.

What is the deviation and approval structure on an account our size, and who owns it beyond the partner. And when does your fiscal quarter close relative to our renewal date. The basis question is the deal: Cisco's default math starts from entitlements, which renews every suite you never deployed.

Deflections, and call two opens 1:27

Deflect these word for word. They point to the cross portfolio discount: commitment does not oblige us to renew shelfware; requote on activation and we discuss structure. They ask about budget: we build the budget after we see your quote on the activated basis. They route pressure through the partner: the partner transacts, commercials run here.

Then call two, after the quote arrives on the entitled basis, suites blended, Splunk woven in. Acknowledge, do not react. Open with the baseline: our agreement costs X per year, our activation audit supports Y, your quote is Z; walk me through every suite, one at a time.

The six moves of call two 2:07

The six moves of call two. Unbundle the suites: each on its own line, and the undeployed ones come out. Renew what activated: the next quote carries our deployed and used counts, and the difference is a lower invoice, not value shifted into new suites. Work the flanks: named vendors, real numbers; close the gaps or the segments close.

Give Splunk its own table, on an optimized ingest baseline, benchmarked against its own market. Fix the True Forward paper: definitions, anniversaries, a growth band, no retroactivity. And summon the desk: whoever owns deviation authority; I do not run final rounds through the channel.

Call three: the close 2:53

Call three, timed to a quarter end, ideally July. Open with: we sign inside your quarter if the remaining items land; here is the complete list; nothing gets added after today. Per suite pricing at activated counts, undeployed suites removed and taken as a lower invoice. Uplift capped at zero to three percent.

True Forward fixed in the schedules: definitions, anniversaries, a growth band, no retroactivity. Value shift rights between suites. Splunk on its own line, rate locked. Collaboration repriced against the market or removed.

Third party support on the mature estate, penalty free. Everything co terminated, with a short extension pre agreed as fallback.

Customize the script 3:36

Customize it. Heavy Splunk estate: optimize before you renew, ingest hygiene and the right pricing model, then benchmark against its own market and keep it a separate line. Collaboration in the agreement: the easiest money on the table; let the alternative be logged and accept collaboration near free or not at all. Hardware refresh approaching: peak leverage arrives with the refresh, and attach subscriptions and support terms are negotiated at purchase.

And when it stalls: the activation reduction executes either way; the question is whether the rest lands in your July or in next year's number. More briefings at redresscompliance dot com slash research videos.