Expansion Playbook

Use to package upsell, cross-sell, and advocacy motions tied to customer outcomes.

Published by @gtmagents·0 agent reads / 30d·0 saves·Updated June 14, 2026

Expansion Playbook Library Skill

When to Use

Preparing QBRs/EBRs where growth plays should be highlighted.
Running account reviews to recommend upsell/cross-sell motions.
Equipping AEs/CSMs with talk tracks and proof aligned to success milestones.

Framework

Trigger Mapping – link product usage, milestone completion, or executive asks to specific plays.
Value Narrative – outline business impact, ROI proof, and reference customers per play.
Commercial Guardrails – specify packaging, pricing, approvals, and compensation cues.
Enablement Kit – include decks, ROI calculators, success stories, and objection handling.
Measurement – track attach rate, win rate, and cycle time for each play.

Templates

Play card (trigger, narrative, assets, owners, KPIs).
Executive talking points for expansion proposals.
Post-play follow-up checklist with success metrics.

Tips

Keep plays prioritized (top 3 per segment) to avoid overwhelm.
Pair with account-health-framework to time plays when risk is low.
Capture learnings after each motion to refine triggers + messaging.

More on the bench

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

Qbr Builder

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

customer-success+1

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

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”