Success Planning Framework

Use to structure collaborative success plans with milestones, KPIs, and governance.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Success Planning Framework Skill

When to Use

  • Kicking off strategic accounts, renewals, or large expansions.
  • Preparing QBR/EBR sessions that require clear impact narratives.
  • Aligning internal and customer stakeholders on joint execution plans.

Framework

  1. Objective Definition – document customer outcomes, KPIs, and time horizons.
  2. Milestone Architecture – break objectives into measurable milestones with owners.
  3. Governance Layer – set review cadence, communication channels, and escalation triggers.
  4. Proof & Assets – link data, case studies, product roadmap elements required per milestone.
  5. Measurement & Feedback – capture progress, blockers, and new opportunities each cycle.

Templates

  • Success Plan Canvas: See assets/success_plan_canvas.md for objectives and milestones.
  • Success plan table (objective, milestone, KPI, owner, due date).
  • Governance charter outline (cadence, audience, agenda, inputs).
  • Risk/action log with status + accountability.

Tips

  • Keep milestones customer-value focused before internal metrics.
  • Co-create live with stakeholders to drive commitment.
  • Pair with account-health-framework outputs to keep signals current.

Bundled with this artifact

1 file

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0