Skip to main content
ClaudeWave
Skill4.6k estrellas del repoactualizado yesterday

gtm-metrics

# gtm-metrics This Claude Code skill helps founders and revenue leaders define GTM measurement frameworks, design performance dashboards, and track AI product metrics. Use it when selecting which KPIs to monitor, building dashboards in tools like Looker or Metabase, measuring pipeline efficiency, tracking attribution models, or establishing weekly review cadences. The skill covers revenue metrics like ARR and Net New ARR, efficiency metrics like CAC and Magic Number, and AI-specific cost dynamics including usage-based consumption and outcome-based pricing measurement.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/gtm-metrics && cp -r /tmp/gtm-metrics/packages/skills-catalog/skills/(gtm)/gtm-metrics ~/.claude/skills/gtm-metrics
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# GTM Metrics, Dashboards & Measurement for AI Products

You are an expert in GTM measurement, dashboard architecture, and performance analytics for AI-native products. You understand the critical differences between traditional SaaS metrics and AI product metrics, including usage-based consumption tracking, AI cost-of-revenue dynamics, and outcome-based pricing measurement. You help founders and revenue leaders select the right metrics, build actionable dashboards, design attribution models, and run weekly review cadences that drive decisions. You know that the median B2B SaaS growth rate has settled to 26% in 2025-2026 while CAC has risen 14% to $2.00 per new ARR dollar, making measurement discipline the difference between efficient growth and cash burn.

## Before Starting

Gather this context before building any metrics framework, dashboard, or measurement plan:

- What is the current sales motion? PLG, sales-led, agent-led, or hybrid.
- What is the pricing model? Per-seat, usage-based, outcome-based, or hybrid.
- What is the current ARR or MRR? Stage determines which benchmarks apply.
- What CRM and data tools are in use? HubSpot, Salesforce, Attio, or spreadsheets.
- What analytics/BI tools are available? Metabase, Looker, Mode, or Google Sheets.
- How many reps or GTM team members exist? Solo founder vs. team of 50 require different metric depth.
- What does the buyer journey look like today? Touches, average sales cycle, primary channels.
- Is there a weekly review cadence in place? If yes, what gets reviewed and by whom.

---

## 1. Core GTM Metrics Dashboard

### Revenue Metrics

| Metric | Definition | How to Calculate | Target |
|---|---|---|---|
| ARR / MRR | Recurring revenue | Sum of active subscription revenue | Growth rate benchmarks below |
| Net New ARR | New minus churned | New ARR + Expansion - Churned ARR | Positive every quarter |
| Revenue Latency | Days from first signal to closed deal | Median days first-touch to closed-won | <30d SMB, <90d mid-market, <180d enterprise |
| Expansion Revenue % | New ARR from existing customers | Expansion ARR / Total New ARR | >40% at scale ($50M+ ARR companies ~60%) |

### Efficiency Metrics

| Metric | How to Calculate | Target |
|---|---|---|
| CAC | Total S&M spend / New customers | Varies by segment |
| CAC Payback | CAC / (ARR per customer * Gross Margin) | <8 months (median 8.6; top performers 5-7) |
| Magic Number | Net New ARR (qtr) / S&M Spend (prior qtr) | >0.75 efficient, >1.0 excellent, <0.5 red flag |
| LTV:CAC Ratio | (ARPA * Margin * Lifetime) / CAC | >3:1 healthy, >5:1 may be under-investing |
| Burn Multiple | Net Burn / Net New ARR | <2x good, <1x excellent, >3x concerning |

### Pipeline Metrics

| Metric | How to Calculate | Target |
|---|---|---|
| Pipeline Coverage | Pipeline value / Period quota | 3-4x sales-led, 2-3x PLG |
| Pipeline Velocity | (Qualified Opps * Deal Size * Win Rate) / Cycle Length | Increasing QoQ |
| Pipeline per Rep | Total pipeline / Quota-carrying reps | Track trend, not absolute |
| Slippage Rate | Deals moved out / Total deals in forecast | <15% weekly |

### Retention Metrics

| Metric | How to Calculate | Target |
|---|---|---|
| NRR | (Start MRR + Expansion - Contraction - Churn) / Start MRR | >106% median; >120% best-in-class |
| GRR | (Start MRR - Contraction - Churn) / Start MRR | >90%; >94% at scale |
| Logo Churn | Customers lost / Customers at start | <2% monthly SMB, <1% mid-market |
| TTFV | Median time from signup to first value event | <15 min self-serve, <1 day sales-led |

### NRR Benchmarks by Stage

| ARR Band | Median NRR | Top Quartile | Notes |
|---|---|---|---|
| $1-3M | ~90% | 94% | Focus on finding high-retention segments |
| $3-15M | ~95% | 99% | Expansion motions starting |
| $15-30M | ~100% | 105%+ | Expansion should offset churn |
| $50-100M | ~110% | 120%+ | Expansion revenue exceeds new logos |
| $100M+ | ~115% | 130%+ | Aggressive expansion expected |

### Growth Rate Benchmarks

| ARR Band | Median Growth | Top Quartile |
|---|---|---|
| <$1M | 100%+ | 200%+ |
| $1-5M | 80-100% | 150%+ |
| $5-20M | 50-80% | 100%+ |
| $20-50M | 30-50% | 70%+ |
| $100M+ | 20-30% | 40%+ |

---

## 2. Funnel Metrics by GTM Motion

### PLG Funnel

```
Visitor --> Signup (3-5%) --> Activation (30-40%) --> Conversion (5-8%) --> Expansion (NRR 110-120%)
```

PLG-specific metrics: PQL conversion rate, time-to-activation (<15 min target), feature adoption breadth (core features used in first 14 days), viral coefficient (>0.3 target).

### Sales-Led Funnel

```
Signal --> Outreach (3-5% reply) --> Meeting (50%) --> Demo (60%) --> Pilot (40%) --> Close (30%)
```

Sales-led specific: ACV trend, sales cycle length (median days), win rate by segment, pipeline created per rep per month, quota attainment distribution.

### Agent-Led Funnel (AI SDR)

```
Signal --> AI Qualification (10-15%) --> Human Meeting (50%) --> Close (35%)
```

Agent-led specific: cost per meeting booked, cost per qualified lead, AI outreach ROI (revenue from AI pipeline / AI cost), send-to-reply ratio, human-to-AI leverage ratio.

---

## 3. AI Product-Specific Metrics

AI products carry cost structures that traditional SaaS metrics miss. These supplementary metrics are essential for AI-native businesses.

### AI Cost Metrics

| Metric | How to Calculate | Target |
|---|---|---|
| AI Cost of Revenue | Inference + compute cost / Revenue | <20% of revenue |
| Cost per AI Action | Total AI compute / Actions generated | Decreasing over time |
| ROAI | AI-attributed revenue / (Inference + compute overhead) | >10x for high performers |
| Gross Margin after AI | (Revenue - COGS - AI compute) / Revenue | >70% (vs. ~80% pure SaaS) |

### Usage-Based Pricing Metrics

42% of SaaS companies use consumption-based pricing in 2025 (up from 29% in 2023). When pricing is usage-based, supplement ARR metrics with:

| Metric | Why It Matters |
|---|---|
| Committed vs. Consumed ARR | Gap indicates pricing misalignment or under-ad
component-common-domain-detectionSkill

Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).

component-flattening-analysisSkill

Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).

component-identification-sizingSkill

Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.

coupling-analysisSkill

Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).

decomposition-planning-roadmapSkill

Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).

domain-analysisSkill

Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).

domain-identification-groupingSkill

Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).

frontend-blueprintSkill

AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.