Initial commit
This commit is contained in:
30
skills/board-readiness-kit/SKILL.md
Normal file
30
skills/board-readiness-kit/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: board-readiness-kit
|
||||
description: Narrative and artifact system for preparing SaaS board/investor updates.
|
||||
---
|
||||
|
||||
# Board Readiness Kit Skill
|
||||
|
||||
## When to Use
|
||||
- Drafting quarterly board/investor updates linked to GTM + product metrics.
|
||||
- Equipping execs with consistent KPI stories, risks, and asks.
|
||||
- Coordinating cross-functional data pulls for diligence requests.
|
||||
|
||||
## Framework
|
||||
1. **Story Spine** – headline, KPI movement, driver analysis, implication, ask.
|
||||
2. **Metric Stack** – ARR, NRR, CAC payback, pipeline coverage, product activation, roadmap velocity.
|
||||
3. **Evidence Locker** – telemetry charts, customer wins/losses, pipeline snapshots, product launch stats.
|
||||
4. **Action Register** – funding requests, hiring plans, roadmap trade-offs, go/no-go decisions.
|
||||
5. **Distribution Plan** – deck/memo templates, Q&A prep, and follow-up tracker.
|
||||
|
||||
## Templates
|
||||
- **Board Deck Outline**: See `templates/board_deck_outline.md` for slide structure.
|
||||
- **Memo template** for async updates.
|
||||
- **Decision log sheet** capturing approvals, blockers, and owners.
|
||||
|
||||
## Tips
|
||||
- Keep slide copy concise; push deep dives to appendix or data room.
|
||||
- Pre-wire risk sections with mitigation steps to build confidence.
|
||||
- Pair with `prepare-board-readout` for automation + data pulls.
|
||||
|
||||
---
|
||||
30
skills/land-adopt-expand-blueprint/SKILL.md
Normal file
30
skills/land-adopt-expand-blueprint/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: land-adopt-expand-blueprint
|
||||
description: Template for orchestrating phased motions across strategic SaaS accounts.
|
||||
---
|
||||
|
||||
# Land-Adopt-Expand Blueprint Skill
|
||||
|
||||
## When to Use
|
||||
- Designing success plans for enterprise SaaS accounts.
|
||||
- Aligning revenue, product, and CS teams on phased adoption metrics.
|
||||
- Auditing current accounts to identify expansion triggers or risks.
|
||||
|
||||
## Framework
|
||||
1. **Stakeholder Matrix** – map economic, technical, and champion roles per phase.
|
||||
2. **Milestone Ladder** – land (business case, pilot), adopt (activation, value proof), expand (multi-product, exec advocacy).
|
||||
3. **Signal Library** – telemetry + qualitative indicators that unlock stage gates.
|
||||
4. **Governance Cadence** – EBR/QBR schedule, exec sponsors, escalation paths.
|
||||
5. **Action Playbook** – recommended plays, assets, and enablement per milestone.
|
||||
|
||||
## Templates
|
||||
- Success plan table with phases, KPIs, owners, and timelines.
|
||||
- Exec summary slide for internal standups.
|
||||
- Risk/mitigation log tied to each phase.
|
||||
|
||||
## Tips
|
||||
- Tie stage gates to measurable outcomes, not just time-based milestones.
|
||||
- Share blueprint with customers to co-author success plans.
|
||||
- Pair with `build-land-adopt-expand-plan` for account-specific automation.
|
||||
|
||||
---
|
||||
31
skills/usage-to-value-map/SKILL.md
Normal file
31
skills/usage-to-value-map/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: usage-to-value-map
|
||||
description: Method for translating product telemetry into ROI narratives and expansion
|
||||
triggers.
|
||||
---
|
||||
|
||||
# Usage-to-Value Map Skill
|
||||
|
||||
## When to Use
|
||||
- Preparing exec readouts showing how product usage ties to business outcomes.
|
||||
- Prioritizing adoption plays based on feature depth, collaboration, or workflow coverage.
|
||||
- Equipping sales/CS with quantified value proof for renewal/expansion cycles.
|
||||
|
||||
## Framework
|
||||
1. **Telemetry Layer** – identify key events, feature usage, seat adoption, and integration data.
|
||||
2. **Value Drivers** – map telemetry to business KPIs (time saved, revenue uplift, compliance risk).
|
||||
3. **Benchmarking** – compare against cohort medians, champions, or best-in-class customers.
|
||||
4. **Signal→Play Mapping** – tie usage patterns to recommended plays (exec briefing, enablement, upsell).
|
||||
5. **Narrative Template** – structure story: context → usage signal → value proof → action.
|
||||
|
||||
## Templates
|
||||
- Usage-to-value canvas (signal, KPI, benchmark, recommended play).
|
||||
- Dashboard outline with spark lines + annotations for exec consumption.
|
||||
- Email/slide snippet for sharing value proof with stakeholders.
|
||||
|
||||
## Tips
|
||||
- Blend quantitative telemetry with qualitative proof (quotes, case studies) for credibility.
|
||||
- Update benchmarks quarterly to reflect product releases and customer mix.
|
||||
- Pair with `build-land-adopt-expand-plan` and `prepare-board-readout` for consistent storytelling.
|
||||
|
||||
---
|
||||
30
skills/vertical-solution-templates/SKILL.md
Normal file
30
skills/vertical-solution-templates/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: vertical-solution-templates
|
||||
description: Library of reusable solution briefs, architecture, and pricing frames per industry.
|
||||
---
|
||||
|
||||
# Vertical Solution Templates Skill
|
||||
|
||||
## When to Use
|
||||
- Localizing GTM assets for specific industries or sub-verticals.
|
||||
- Preparing ABM/field teams with ready-to-use briefs and demos.
|
||||
- Coordinating product + marketing on roadmap-aligned solution packages.
|
||||
|
||||
## Framework
|
||||
1. **Template Structure** – executive summary, pain/impact, solution architecture, proof.
|
||||
2. **Configuration Rules** – recommended modules, integrations, and data sources.
|
||||
3. **Pricing & Packaging** – typical ACV ranges, value metrics, and contract guardrails.
|
||||
4. **Evidence Kit** – case studies, references, benchmark stats, and compliance notes.
|
||||
5. **Activation Plan** – suggested campaigns, field workshops, and demo scripts.
|
||||
|
||||
## Templates
|
||||
- One-pager solution brief (PDF + slide).
|
||||
- Architecture diagram with integration callouts.
|
||||
- Pricing/ROI worksheet with editable assumptions.
|
||||
|
||||
## Tips
|
||||
- Keep templates modular so teams can mix/match by segment.
|
||||
- Refresh quarterly with new case studies and roadmap releases.
|
||||
- Pair with `create-industry-playbook` for automated population.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user