Build Success Plan

Produces a joint success plan with milestones, KPIs, stakeholders, and expansion hooks.

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

Command: build-success-plan

Inputs

  • account – customer/account name or ID.
  • horizon – time window (quarter, 2q, year).
  • include-expansion – true/false to automatically layer in upsell plays.
  • stakeholders – optional list of customer/internal execs to highlight.
  • metrics – optional KPIs to emphasize (time-to-value, adoption, ROI, NPS).

Workflow

  1. Context Intake – pull objectives, usage, sentiment, open projects, and exec notes.
  2. Milestone Drafting – translate objectives into measurable milestones with KPIs + owners.
  3. Play Attach – recommend adoption, expansion, or advocacy plays aligned to milestones.
  4. Governance Design – set review cadence, communication plan, and escalation paths.
  5. Packaging – output plan doc + QBR-ready summary.

Outputs

  • Joint success plan with objectives, milestones, KPIs, owners, timelines.
  • Governance checklist (cadence, meetings, communication).
  • Expansion opportunities mapped to milestones.

Agent/Skill Invocations

  • success-planner – facilitates design + alignment.
  • relationship-director – ensures executive engagement and narratives.
  • account-health-analyst – injects health metrics and signals.
  • success-planning-framework skill – provides templates + rubric.
  • expansion-playbook skill – surfaces upsell/cross-sell motions.

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