Mine was 14 stakeholders spanning legal, InfoSec, finance, and three BU heads at a Fortune 100 in 2023 — 212-day cycle, two MAAs in Salesforce, and a dual-SOW structure to reconcile competing procurement thresholds. Anyone topped that, and how did you keep executive sponsors engaged without triggering a re-review from security?
I kept a Fortune 50 deal on track by attaching a pre‑approved “no material change” matrix from their InfoSec to every sponsor update, mapping SOW redlines back to the initial security sign‑off so nothing triggered re‑review. Curious if, on your 212‑day “dual‑SOW” setup, your InfoSec partner would bless a one‑pager like that referencing the two MAAs as control gates.
Building on @elise_carr77, had 16 stakeholders on a about 200‑day F100 deal and the only way we avoided a re‑review was a one‑pager ‘scope freeze’ co‑signed by InfoSec and Legal; every exec update linked to the MAA in Salesforce and showed KPI/timeline only, with any data‑flow detail parked in a SecOps‑owned appendix inside the original ticket. Your dual‑SOW maps cleanly — label ‘core’ vs ‘optional’ in the freeze so procurement can move while security stays out of re‑review.