1 / 7
Coupa · Sr. Lead, P&T Operations · 90-Day Plan
Turning the CuCP Framework
into Adopted Reality
A 90-day plan to implement and scale the Customer Collaboration Program — from paper framework to predictable launch engine.
The Challenge — and the Reframe
Change management starts with understanding the resistance, then flipping the narrative.
The Problem: Fragmented Execution
- Ad-hoc EAP/LA engagement, no standard process
- "Definition drift" — scope shifts before GA
- No exit criteria → risky launch decisions
- PMs see CuCP as admin overhead slowing velocity
Strategy: Earn Adoption, Don't Mandate It
- Lead with PM pain — not programme goals
- Find proto-champions already doing good EAP work
- Make first experience frictionless — I absorb the admin
- Their story converts sceptics, mine doesn't
The message that lands: "CuCP is your evidence kit — not a compliance checklist."
Structured EAP data protects PMs at GA. It answers "how do we know this is ready?" with customer signal, not gut feel.
Capability Classifications: Standard vs. AI
Pre-GA validation strategies are structured to match the risk profile of each release path.
Standard Capabilities
- Definition: Deterministic logic and workflows (no AI involved). E.g., sourcing dashboards, routing rules.
- Focus: Validate operational readiness, scalability, support enablement.
- Gating: Closed Beta (EAP) and Limited Availability (LA) require a $0 Order Form.
- Exit: LA phase gates readiness with commercial alignment before General Availability.
AI Capabilities (AI-Assisted & Agentic)
- Definition: Powered by ML/LLMs. Probabilistic models. E.g., Copilots, Agent Studio workflows.
- Focus: Model tuning, trust/safety guardrails, telemetry integration.
- Billing: EAP & Open Beta are free of charge via customer AI Credits.
- Gating: Open Beta is enabled via UI toggle (no $0 Order Forms; utilizes Fair Use Caps).
The Principle of Proportional Governance: The level of release gating must align to feature risk and complexity. Pre-GA phases are optional and variable based on PM assessment.
90-Day Rollout: Pilot → Learn → Scale
No big-bang mandate. Build trust through service, then scale on proven evidence.
Phase 1
Days 1–30
Listen & Align
- 1:1 listening sessions (8–10 PMs)
- Shadow 2 live EAP/LA cycles
- Map informal processes in use
- Identify proto-champions
- Select pilot: 1 Standard + 1 AI
⟶ Friction map + pilot cohort confirmed
Phase 2
Days 31–60
Pilot & Refine
- Run 2–3 live CuCP pilots
- I act as embedded CuCP Concierge
- Weekly retros — cut admin overhead
- Capture before/after evidence
- Activate PM champions
⟶ Playbook v1.0 + champion stories
Phase 3
Days 61–90
Scale & Institutionalise
- All-hands enablement (champions present)
- Self-serve KB + templates live
- #cucp-support + office hours
- Admin tasks automated
- Leadership dashboard live
⟶ All PMs enabled · tracking live
Enablement & Support Model
Four pillars that make CuCP stupidly easy to run — before it becomes expected.
🎯
CuCP Concierge (Days 1–60)
I act as the operational support for pilot PMs. They learn the process; I handle templates, customer invites, and exit criteria tracking. PM overhead: near zero.
High-touch during pilot
📋
Playbook + Cheat Sheets
Two 1-page cheat sheets: Standard capability path and AI capability path. Separate because their pre-GA goals, cohort sizes, and exit criteria differ meaningfully.
Self-serve from Day 60
💬
#cucp-support + Office Hours
Live Slack channel for real-time questions. Weekly 30-min open office hours for the first 90 days. PMs get answers in minutes, not days — reduces perceived friction.
Async + sync support
🏆
Champion-Led Rollout
Pilot PMs present at the all-hands enablement session — not me. Peer stories are far more credible than top-down messaging for converting sceptics.
Peer credibility > authority
Measuring Initial Success
Six metrics prove the rollout is working. One leading indicator matters most in the first 90 days.
| KPI | Baseline | Day 90 Target | How Measured | Type |
|---|
| ⭐ PM Satisfaction Score — "Is CuCP helping?" |
— | ≥ 4.0 / 5.0 | Post-pilot survey |
Leading |
| % eligible releases using CuCP |
0% (ad-hoc) | ≥ 50% | Release tracker |
Lagging |
| EAP → GA cycle time |
Measure Days 1–30 | No regression; –10% | Release logs |
Lagging |
| Definition drift incidents |
Unmeasured | Tracked; 0 in pilots | EAP/LA retros |
Leading |
| Customer participation rate |
— | ≥ 70% invited customers engage | CuCP tracker |
Lagging |
| PM admin time per release cycle |
— | < 2 hours | PM self-report |
Leading |
⭐ If PMs feel CuCP helps — scaling is pull, not push. Fix the playbook before mandating.
What Day 90 Looks Like
Three outcomes that prove the CuCP rollout succeeded — and what I need from leadership to get there.
Evidence of Success
- ≥ 50% eligible releases running CuCP
- PM satisfaction ≥ 4.0 / 5.0
- 2–3 champion PMs advocating internally
- Self-serve KB live — zero dependency on me
- Leadership dashboard showing programme health
Proportional Governance Principle
- Days 1–30: Observe only, no mandate
- Days 31–60: Voluntary pilot, earn trust
- Days 61–90: Clear expectation for eligible releases
- Day 90+: Data-backed mandate — only after PM satisfaction confirmed
My Ask of P&T Leadership
🛡️ Air cover during pilot — no forced mandate
🎙️ Exec sponsor for all-hands session
🔗 Access to 2–3 willing pilot PMs in Week 1
📊 Release log access for baseline measurement
📊 Download PPTX (Light Theme)