Monitor Retention

Builds retention dashboards, signal briefs, and recommended save plays per cohort.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·

Command: monitor-retention

Inputs

  • window – analysis window (month, quarter, rolling-90d).
  • grouping – comma-separated dimensions (plan, persona, region, product, acquisition-channel).
  • include-expansion – true/false to show upsell impact alongside churn.
  • signals – optional list of metrics to emphasize (usage, support, sentiment, billing).
  • format – dashboard | deck | brief.

Workflow

  1. Data Refresh – query billing, product telemetry, support, survey, and pipeline sources.
  2. Cohort Calculations – compute retention, churn, expansion, and health indexes per grouping.
  3. Signal Detection – surface top risk/improvement cohorts with quantified impact.
  4. Play Recommendations – map cohorts to lifecycle or CS save plays with owners.
  5. Packaging – produce dashboards/decks plus action trackers for leadership reviews.

Outputs

  • Retention dashboard with drillable cohorts.
  • Signal brief highlighting risks/opportunities + recommended plays.
  • Action tracker with owners, due dates, and success metrics.

Agent/Skill Invocations

  • retention-analyst – leads analytics + insights.
  • segmentation-architect – ensures segment definitions align.
  • customer-insights-partner – adds qualitative proof.
  • retention-dashboard skill – provides visualization templates.
  • save-play-library skill – links insights to remediation programs.

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