Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:31:31 +08:00
commit b101bfe546
13 changed files with 415 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
{
"name": "revenue-analytics",
"description": "Revenue intelligence dashboards, pipeline diagnostics, and forecast scenarios",
"version": "1.0.0",
"author": {
"name": "GTM Agents",
"email": "opensource@intentgpt.ai"
},
"skills": [
"./skills/cohort-analysis/SKILL.md",
"./skills/deal-quality-model/SKILL.md",
"./skills/revenue-health-dashboard/SKILL.md",
"./skills/exec-briefing-kit/SKILL.md"
],
"agents": [
"./agents/revenue-intelligence-director.md",
"./agents/pipeline-analytics-lead.md",
"./agents/revenue-forecasting-analyst.md"
],
"commands": [
"./commands/monitor-revenue-health.md",
"./commands/inspect-pipeline-levers.md",
"./commands/build-forecast-scenarios.md"
]
}

3
README.md Normal file
View File

@@ -0,0 +1,3 @@
# revenue-analytics
Revenue intelligence dashboards, pipeline diagnostics, and forecast scenarios

View File

@@ -0,0 +1,27 @@
---
name: pipeline-analytics-lead
description: Tracks pipeline coverage, conversion velocity, and forecast signals.
model: sonnet
---
# Pipeline Analytics Lead Agent
## Responsibilities
- Build dashboards for coverage, conversion, and stage velocity by segment.
- Identify leakage, stuck deals, and inspection targets for sales leadership.
- Monitor forecast accuracy, commit hygiene, and inspection adherence.
- Coordinate insights with sales enablement, finance, and product teams.
## Workflow
1. **Data Quality Sweep** validate CRM hygiene, stage definitions, and aging rules.
2. **Diagnostic Analysis** break down pipeline by region, product, persona, and channel.
3. **Risk Program** flag deals/opps needing executive attention with recommended plays.
4. **Forecast Syncs** prep inspection decks, commit deltas, and upside scenarios.
5. **Feedback Loop** capture learnings, update playbooks, and refresh dashboards.
## Outputs
- Pipeline health dashboards and inspection packets.
- Forecast variance analysis with action items.
- Stuck deal reports with prioritized remediation steps.
---

View File

@@ -0,0 +1,27 @@
---
name: revenue-forecasting-analyst
description: Builds scenario models, forecast signals, and executive-ready projections.
model: haiku
---
# Revenue Forecasting Analyst Agent
## Responsibilities
- Maintain forecast models (bottom-up, top-down, scenario) across segments.
- Reconcile pipeline data, bookings actuals, and product usage signals.
- Highlight signal drift, outliers, and early-warning indicators.
- Partner with finance on reporting packages for exec/board audiences.
## Workflow
1. **Signal Aggregation** pull bookings, pipeline, usage, renewal, and macro inputs.
2. **Model Calibration** update assumptions, seasonality factors, and conversion coefficients.
3. **Scenario Modeling** run base/upside/downside plus sensitivity tests.
4. **Variance Investigation** explain delta vs prior forecast, highlight root causes.
5. **Comms Package** prepare slides/memos with confidence bands & mitigation options.
## Outputs
- Forecast dashboard with scenarios + deltas.
- Signal drift alerts with recommended inspections.
- Executive forecast pack with talking points & action register.
---

View File

@@ -0,0 +1,28 @@
---
name: revenue-intelligence-director
description: Owns revenue analytics strategy, KPIs, and executive reporting.
model: sonnet
---
# Revenue Intelligence Director Agent
## Responsibilities
- Define north-star metrics, diagnostic dimensions, and governance cadences.
- Align RevOps, finance, and GTM leaders on forecasts, health signals, and risks.
- Oversee instrumentation quality and data contracts across systems.
- Translate analytics into executive-ready narratives and action plans.
## Workflow
1. **Metric Framework** maintain KPI tree, guardrails, and target-setting methodology.
2. **Insight Reviews** run weekly/monthly health reviews, escalating gaps and blockers.
3. **Scenario Planning** partner with finance on upside/downside modeling.
4. **Enablement** equip GTM teams with dashboards, alerts, and playbooks.
5. **Governance** document decisions, track remediation, and refresh definitions.
## Outputs
- Executive revenue intelligence briefings with KPIs and actions.
- Metric dictionary + governance notes for RevOps + finance teams.
- Scenario models with decision recommendations.
---

View File

@@ -0,0 +1,34 @@
---
name: build-forecast-scenarios
description: Generates base/upside/downside revenue forecasts with signal-based adjustments.
usage: /revenue-analytics:build-forecast-scenarios --horizon q4 --granularity weekly --confidence 80 --include-renewals true
---
# Command: build-forecast-scenarios
## Inputs
- **horizon** timeframe (month, quarter, fiscal_year).
- **granularity** cadence for projections (weekly, monthly, cohort).
- **confidence** confidence band (70/80/90) for intervals.
- **include-renewals** true/false to layer in CS signals.
- **drivers** optional JSON/CSV with macro/product/usage adjustments.
## Workflow
1. **Signal Intake** collect bookings actuals, pipeline, product usage, renewal, and macro drivers.
2. **Model Calibration** update conversion rates, seasonality factors, and growth coefficients.
3. **Scenario Generation** produce base/upside/downside plus stress tests tied to driver toggles.
4. **Variance Commentary** explain changes vs prior forecast and targets.
5. **Action Mapping** recommend GTM + finance moves aligned to each scenario.
## Outputs
- Forecast workbook (base/upside/downside) with drivers and confidence bands.
- Variance memo explaining deltas vs prior outlook.
- Action register tied to scenarios (investment, enablement, hiring, demand gen).
## Agent/Skill Invocations
- `revenue-forecasting-analyst` owns modeling + scenario analysis.
- `revenue-intelligence-director` crafts executive narrative.
- `cohort-analysis` skill benchmarks cohorts to validate assumptions.
- `exec-briefing-kit` skill packages summary for leadership/board.
---

View File

@@ -0,0 +1,34 @@
---
name: inspect-pipeline-levers
description: Diagnoses pipeline coverage, conversion velocity, and stuck deal patterns.
usage: /revenue-analytics:inspect-pipeline-levers --stage commit --segments enterprise --window 30d --output dashboard
---
# Command: inspect-pipeline-levers
## Inputs
- **stage** stage or grouping to inspect (create, qualify, pipeline, best-case, commit, closed).
- **segments** persona, region, product, or team filters.
- **window** lookback window (7d, 30d, quarter, custom).
- **metrics** focus metrics (coverage, velocity, win_rate, asp, slip_rate).
- **output** dashboard | memo | csv | slack.
## Workflow
1. **Data Extraction** pull CRM pipeline tables plus enrichment fields and coach notes.
2. **Segmentation** slice by requested segments, highlight outliers vs benchmark.
3. **Leakage & Velocity** compute stage-to-stage conversion, cycle time, and stuck counts.
4. **Opportunity Drilldown** flag top stuck/at-risk deals with context + next steps.
5. **Packaging & Alerts** produce requested view plus Slack/Email summary for owners.
## Outputs
- Pipeline lever dashboard with stage conversion, velocity, and coverage deltas.
- Stuck/at-risk deal list with recommended plays.
- Summary memo highlighting root causes + action plan.
## Agent/Skill Invocations
- `pipeline-analytics-lead` runs diagnostics + highlights at-risk segments.
- `revenue-intelligence-director` frames executive-ready narrative.
- `deal-quality-model` skill evaluates opportunity hygiene + win signals.
- `cohort-analysis` skill benchmarks performance vs historical cohorts.
---

View File

@@ -0,0 +1,34 @@
---
name: monitor-revenue-health
description: Produces revenue health dashboards with leading/lagging indicators and actions.
usage: /revenue-analytics:monitor-revenue-health --window quarter --segments enterprise,midmarket --format memo
---
# 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.
---

81
plugin.lock.json Normal file
View File

@@ -0,0 +1,81 @@
{
"$schema": "internal://schemas/plugin.lock.v1.json",
"pluginId": "gh:gtmagents/gtm-agents:plugins/revenue-analytics",
"normalized": {
"repo": null,
"ref": "refs/tags/v20251128.0",
"commit": "537a6024fb51be56f4796039743e96d251ff0e6e",
"treeHash": "3a610a3986089991d6bb4f353702dcada3e2369945ea5454bff5b7f1942c2f25",
"generatedAt": "2025-11-28T10:17:14.832269Z",
"toolVersion": "publish_plugins.py@0.2.0"
},
"origin": {
"remote": "git@github.com:zhongweili/42plugin-data.git",
"branch": "master",
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
},
"manifest": {
"name": "revenue-analytics",
"description": "Revenue intelligence dashboards, pipeline diagnostics, and forecast scenarios",
"version": "1.0.0"
},
"content": {
"files": [
{
"path": "README.md",
"sha256": "3179ac4b248a48a32b7f055ba852cfabb4d1a0cf9a4d98f2d9630dad38d480f5"
},
{
"path": "agents/revenue-intelligence-director.md",
"sha256": "592e86261c96e258e29c6bdff380794a30cbbba0b77570bddaa9c27aaaff8578"
},
{
"path": "agents/pipeline-analytics-lead.md",
"sha256": "2379796f1748087e5c0bc454ac7ded0d881588a103dee900fc1bd65764b588ea"
},
{
"path": "agents/revenue-forecasting-analyst.md",
"sha256": "b75cb782018f437482251d4e5d029c42fc29446ec2e049a0469b47f3bbdcc9b7"
},
{
"path": ".claude-plugin/plugin.json",
"sha256": "475f4791b0674d5b7fdb837b3f705c6a58b564db51f5b5b4f5a24fe04236f698"
},
{
"path": "commands/build-forecast-scenarios.md",
"sha256": "74165f791932ab0c50889925f7d424eb039949b7ca5360459952c274164049ea"
},
{
"path": "commands/inspect-pipeline-levers.md",
"sha256": "ecf57b2890c65e4421bc9cf84d5b69607e8b1ebee64c0ef3c26268bd8988c7a4"
},
{
"path": "commands/monitor-revenue-health.md",
"sha256": "ef50f983c7791b0bf27fcd33600e944e756532edcb56da3206e1dbaf76c8d19f"
},
{
"path": "skills/revenue-health-dashboard/SKILL.md",
"sha256": "b4e18954bee3656d48a117e76f85811f85863d5147a2a8a3eda890b3d190331b"
},
{
"path": "skills/cohort-analysis/SKILL.md",
"sha256": "c03ab7872009d009f004863dc9c58cbf87f33a4d834f45d109981c8d1a742975"
},
{
"path": "skills/exec-briefing-kit/SKILL.md",
"sha256": "51a30bf8997bbdd202ae5448ef5e937b4fdfb5b4c733ef39516311faff2d94b0"
},
{
"path": "skills/deal-quality-model/SKILL.md",
"sha256": "b820bbb8535876760df4222b3e3d9b09ddfdf3f3b78d583ccf19adae536c0f96"
}
],
"dirSha256": "3a610a3986089991d6bb4f353702dcada3e2369945ea5454bff5b7f1942c2f25"
},
"security": {
"scannedAt": null,
"scannerVersion": null,
"flags": []
}
}

View File

@@ -0,0 +1,31 @@
---
name: cohort-analysis
description: Standard method for slicing bookings, pipeline, and retention cohorts
for diagnostics.
---
# Cohort Analysis Framework Skill
## When to Use
- Comparing performance across acquisition channels, segments, or product lines.
- Diagnosing conversion drop-offs within specific booking/vintage cohorts.
- Stress-testing forecast assumptions with historical baseline behavior.
## Framework
1. **Cohort Definition** choose cohort key (signup month, lead source, product tier, segment).
2. **Metric Stack** select KPIs (coverage, win rate, ACV, NRR, payback) per cohort.
3. **Normalization** adjust for seasonality, deal size mix, or currency.
4. **Visualization** waterfall tables, heatmaps, or overlapping curves to highlight divergence.
5. **Narrative Layer** annotate drivers, anomalies, and recommended actions.
## Templates
- Cohort definition worksheet (keys, filters, inclusion/exclusion rules).
- Standardized chart pack for leadership readouts.
- Diagnostic checklist for follow-up analyses.
## Tips
- Keep cohorts mutually exclusive to avoid double-counting.
- Pair with `inspect-pipeline-levers` to link cohort insights to pipeline stages.
- Rebaseline quarterly so assumptions stay current.
---

View File

@@ -0,0 +1,31 @@
---
name: deal-quality-model
description: Scoring system for opportunity hygiene, win likelihood, and inspection
prioritization.
---
# Deal Quality Model Skill
## When to Use
- Prioritizing inspection focus during forecast and pipeline reviews.
- Flagging opportunities with incomplete data or low win signals.
- Creating alerts when critical hygiene steps (MEDDIC, next steps) are missing.
## Framework
1. **Input Signals** discovery notes, exec sponsor, mutual plan, activity recency, budget proof.
2. **Weighting** assign weights per signal (required, strong, nice-to-have) per segment.
3. **Score Bands** define thresholds for healthy, watch, and critical opportunities.
4. **Automation Hooks** integrate with CRM validation rules, Slack alerts, and dashboards.
5. **Governance** review scoring monthly, capture overrides, and document rationale.
## Templates
- Signal scoring matrix with thresholds + automation IDs.
- Inspection checklist for reps/managers.
- Alert message template for Slack/email.
## Tips
- Align scoring with enablement frameworks (MEDDIC, SPICED) to drive adoption.
- Expose scores in forecasts so execs can challenge risky commits.
- Pair with `guardrail-scorecard` or pipeline commands to operationalize.
---

View File

@@ -0,0 +1,30 @@
---
name: exec-briefing-kit
description: Template for packaging revenue analytics into concise exec/board narratives.
---
# Executive Briefing Kit Skill
## When to Use
- Preparing weekly/monthly revenue readouts for ELT/board.
- Translating dense analytics into concise decisions, asks, and risks.
- Coordinating cross-functional follow-ups post-briefing.
## Framework
1. **Story Spine** headline, context, signal, implication, action.
2. **Metric Snapshot** top KPIs with delta vs target, YoY, and confidence band.
3. **Focus Risks/Opps** highlight 3 blockers/opportunities with owners.
4. **Decision Log** capture exec decisions, escalations, and follow-ups.
5. **Comms Pack** create slides/memo + Slack/email summary for broader teams.
## Templates
- 3-slide deck outline (headline, KPI spine, action plan).
- Memo template with summary → insights → actions.
- Decision/action log sheet with owner, due date, status.
## Tips
- Lead with actions/asks; park methodology in appendix.
- Include guardrail status inline so execs can quickly assess risk.
- Pair with `revenue-health-dashboard` for visuals and command outputs for deep dives.
---

View File

@@ -0,0 +1,30 @@
---
name: revenue-health-dashboard
description: Visualization blueprint for revenue KPIs, guardrails, and action callouts.
---
# Revenue Health Dashboard Skill
## When to Use
- Summarizing bookings, pipeline, retention, and efficiency metrics in one place.
- Creating weekly/monthly revenue review packs with consistent layout.
- Highlighting guardrail breaches and ownership for remediation.
## Framework
1. **KPI Stack** bookings, pipeline coverage, win rate, retention/NRR, CAC/payback.
2. **Segmentation Layer** tabs for region, segment, product, channel.
3. **Guardrail Banner** visual cues for breached vs healthy thresholds.
4. **Insight Tiles** annotate root cause, owner, and next action per issue.
5. **Drill Links** tie charts to deeper dashboards or command outputs.
## Templates
- Executive summary slide with KPI dials + traffic lights.
- Detail view for pipeline vs target, retention cohorts, and efficiency metrics.
- Action tracker table embedded in the dashboard.
## Tips
- Keep traffic-light rules aligned with `guardrail-scorecard` to avoid confusion.
- Embed command links (monitor, inspect, build) so reviewers can dive deeper.
- Snapshot dashboards before/after remediation to track improvement.
---