Sunset the program family
Reduces perceived cost during the cloud transition but triggers contractual refund exposure.
Engagement narrative — Microsoft · 2011–2015
A program family that had outgrown its governance — multibillion-dollar contract exposure, nine-figure voucher liability — consolidated into one globally governed, partner-delivered platform.
The operating problem
Microsoft's Software Assurance planning-service programs began as separate product pilots, each with its own portal, partner registry, voucher rules, deliverables, and reimbursement flow. By the time volume scaled, the platform carried roughly $18.5B in enterprise contract exposure and $700M–$1B in outstanding voucher liability — obligations customers were contractually entitled to redeem. The fragmented platforms functioned; the governance did not.
Options on the table
Reduces perceived cost during the cloud transition but triggers contractual refund exposure.
Preserves autonomy but sustains fragmentation, inconsistent standards, and weak financial controls.
One global portal and partner registry, standardized deliverables, enforced financial controls, liability managed as one operating structure.
What I put in place
What changed
Annual planning engagements scaled from ~6,000 to ~37,500 across eight offers, twenty products, and forty engagement types, serving 70,000+ customers at peak with 89% sustained customer satisfaction. Finance-validated analysis showed an 8% renewal improvement across $1.8B in influenced Software Assurance renewal revenue, and the platform shifted from loosely governed pilots to a controlled, scalable liability-management system.
Why it mattered
During Microsoft's hybrid-to-cloud transition, Software Assurance represented major contractual and commercial exposure. Unifying the platform avoided refund risk, governed liability at global scale, and measurably strengthened renewal performance — the governance and protection of a global renewal platform under strategic transition, not another partner-program expansion.