home / skills / gtmagents / gtm-agents / customer-insights
This skill helps consolidate product usage, health, and sentiment signals into actionable insights for lifecycle programs and churn prevention.
npx playbooks add skill gtmagents/gtm-agents --skill customer-insightsReview the files below or copy the command above to add this skill to your agents.
---
name: customer-insights
description: Use when consolidating product usage, health, and sentiment signals for
lifecycle programs.
---
# Customer Insights & Telemetry Skill
## When to Use
- Building segment-specific lifecycle journeys.
- Prioritizing accounts for adoption help, expansion offers, or advocacy invites.
- Diagnosing churn/retention risks and surfacing insights to CS + product.
## Framework
1. **Signals Stack** – product usage, engagement, sentiment, commercial, health composite.
2. **Data Plumbing** – define sources (warehouse, product analytics, CS tools) and refresh cadence.
3. **Normalization** – align account/user IDs, tag personas/verticals.
4. **Insight Delivery** – dashboards + alerts to lifecycle, CS, product teams.
5. **Closed Loop** – track outcomes (expansion booked, churn prevented, advocacy activated).
## Templates
- Health score schema (dimensions, weight, threshold, owner).
- Insight brief (observation, impact, recommended play, owner, due date).
- Data dictionary for lifecycle dashboards.
## Tips
- Keep manual notes from CSMs in sync with telemetry to avoid blind spots.
- Tag signals by persona/vertical for more precise plays.
- Automate distribution via Slack/email alerts tied to triggers.
---
This skill consolidates product usage, health, and sentiment signals into a single customer insights layer to power lifecycle programs. It standardizes telemetry across tools, computes health and risk scores, and delivers actionable briefs and alerts to GTM teams. The result is faster prioritization, clearer handoffs, and measurable closed-loop outcomes.
It ingests signals from product analytics, the data warehouse, CRM, and customer success tools, then normalizes account and user identifiers and tags by persona and vertical. The skill builds a signals stack (usage, engagement, sentiment, commercial, composite health), applies configurable weightings to produce health scores, and produces dashboards, alert rules, and insight briefs. Outputs are distributed to lifecycle, CS, and product teams and tracked for outcome metrics like expansion booked or churn avoided.
Which data sources should I prioritize for early value?
Start with product analytics, CRM activity, and recent support or NPS sentiment. Those deliver immediate signals for adoption and risk.
How do I choose weights for the health score?
Pick weights based on business impact and validate with historical outcomes. Iterate using A/B tests or back-testing against churn and expansion data.