Monitor Revenue Health

Produces revenue health dashboards with leading/lagging indicators and actions.

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

Command: monitor-revenue-health

Inputs

  • window – time horizon (month | quarter | rolling_90 | custom).
  • segments – comma-separated list (enterprise, midmarket, smb, channel, region).
  • metrics – optional override for KPI set (bookings, pipeline, churn, NRR, CAC).
  • format – dashboard | memo | briefing | csv.
  • alerts – true/false to include guardrail breach notifications.

Workflow

  1. Data Sync – aggregate bookings, pipeline, retention, and leading indicator tables.
  2. Diagnostics – run anomaly detection vs targets, YoY, and guardrail thresholds.
  3. Insight Layer – annotate root causes, impacted teams, and decision urgency.
  4. Action Builder – recommend plays (enablement, marketing, CS) tied to gaps.
  5. Packaging – assemble dashboard/memo plus follow-up checklist + owners.

Outputs

  • Revenue health dashboard with KPIs, variance explanations, and drill links.
  • Alert summary with guardrail status and breach details.
  • Action register with owners, due dates, and playbook links.

Agent/Skill Invocations

  • revenue-intelligence-director – frames KPIs and narrates insights.
  • pipeline-analytics-lead – supplies pipeline diagnostics.
  • revenue-health-dashboard skill – standardizes visual layout + scorecards.
  • exec-briefing-kit skill – formats leadership-ready summaries.

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