Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:30:18 +08:00
commit 6f031b5376
12 changed files with 379 additions and 0 deletions

View File

@@ -0,0 +1,31 @@
---
name: advocacy-programs
description: Use when designing and scaling reference, story, advisory, or community
programs.
---
# Customer Advocacy Programs Skill
## When to Use
- Building a new references or case study engine.
- Standing up advisory boards, councils, or community spotlights.
- Refreshing incentives, logistics, or measurement for existing advocacy motions.
## Framework
1. **Candidate Pool** identify accounts by health, persona, usage, sentiment, ARR.
2. **Value Exchange** clarify why customers would participate (access, insights, promotion, perks).
3. **Program Design** define format (case study, event, video, advisory board) with cadence and deliverables.
4. **Logistics** NDAs, approvals, briefing docs, gifting, scheduling, speaker prep.
5. **Measurement** track influence on pipeline, product feedback volume, PR reach, community growth.
## Templates
- Advocate scoring sheet + roster.
- Program brief outline (objectives, stakeholders, content needs, incentives).
- Activation checklist (outreach → prep → execution → follow-up).
## Tips
- Keep a single source of truth for advocate status to avoid overuse.
- Align incentives with procurement/compliance early (gift cards vs swag vs donations).
- Document quotes/approvals centrally so sales/PR can reuse quickly.
---

View File

@@ -0,0 +1,31 @@
---
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.
---

View File

@@ -0,0 +1,31 @@
---
name: expansion-plays
description: Use when planning adoption-to-expansion motions and cross-sell/upsell
campaigns.
---
# Expansion Playbooks Skill
## When to Use
- Identifying accounts ready for cross-sell or upsell.
- Designing lifecycle campaigns that move customers from adoption to value realization and expansion.
- Partnering with sales/CS to run QBRs, roadmap reviews, or packaging changes.
## Framework
1. **Signal Stack** product usage milestone, success plan completion, idle licenses, executive sponsor engagement.
2. **Play Types** roadmap preview, ROI workshop, packaged add-on offer, multi-product bundle, success story swap.
3. **Offer Crafting** align incentive (discount, pilot, service credits) with customer value narrative.
4. **Execution Channels** CS outreach, lifecycle nurture, webinars, executive programs.
5. **Measurement** expansion pipeline, attach rates, ARR per account, payback.
## Templates
- Expansion readiness checklist.
- QBR/EOQ review deck outline.
- Offer matrix (persona x trigger x CTA).
## Tips
- Keep CS + sales alignment tight on ownership and comp.
- Document experiments (pricing, packaging) and share learning loops with product.
- Pair with `customer-insights` to validate readiness signals before outreach.
---