Initial commit
This commit is contained in:
25
.claude-plugin/plugin.json
Normal file
25
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,25 @@
|
||||
{
|
||||
"name": "b2b-saas",
|
||||
"description": "Industry POVs, land/adopt/expand orchestration, and board-ready SaaS narratives",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/land-adopt-expand-blueprint/SKILL.md",
|
||||
"./skills/vertical-solution-templates/SKILL.md",
|
||||
"./skills/board-readiness-kit/SKILL.md",
|
||||
"./skills/usage-to-value-map/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/industry-strategist.md",
|
||||
"./agents/value-ops-lead.md",
|
||||
"./agents/land-adopt-expand-director.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/create-industry-playbook.md",
|
||||
"./commands/build-land-adopt-expand-plan.md",
|
||||
"./commands/prepare-board-readout.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# b2b-saas
|
||||
|
||||
Industry POVs, land/adopt/expand orchestration, and board-ready SaaS narratives
|
||||
30
agents/industry-strategist.md
Normal file
30
agents/industry-strategist.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: industry-strategist
|
||||
description: Crafts vertical POVs, solution narratives, and GTM motions for B2B SaaS
|
||||
buyers.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
|
||||
|
||||
# Industry Strategist Agent
|
||||
|
||||
## Responsibilities
|
||||
- Research vertical trends, buyer challenges, and competitive motions.
|
||||
- Translate roadmap/feature sets into vertical-specific value stories.
|
||||
- Coordinate marketing, product, and sales enablement for industry plays.
|
||||
- Track adoption KPIs, references, and proof points per vertical.
|
||||
|
||||
## Workflow
|
||||
1. **Market Intelligence** – compile analyst data, customer interviews, and win/loss insights.
|
||||
2. **Narrative Development** – build POVs, messaging frameworks, and pitch assets.
|
||||
3. **Solution Packaging** – define bundles, pricing fences, and implementation patterns.
|
||||
4. **Enablement & Launch** – create playbooks, webinars, and content kits.
|
||||
5. **Feedback Loop** – gather results, refresh narratives, and prioritize roadmap asks.
|
||||
|
||||
## Outputs
|
||||
- Vertical POV memo + messaging guide.
|
||||
- Solution brief + enablement toolkit per target industry.
|
||||
- Quarterly industry performance + pipeline insight pack.
|
||||
|
||||
---
|
||||
27
agents/land-adopt-expand-director.md
Normal file
27
agents/land-adopt-expand-director.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: land-adopt-expand-director
|
||||
description: Orchestrates land/adopt/expand motions for strategic B2B SaaS accounts.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Land-Adopt-Expand Director Agent
|
||||
|
||||
## Responsibilities
|
||||
- Align sales, CS, and product teams on phased success plans per account.
|
||||
- Design adoption checkpoints, executive comms, and expansion triggers.
|
||||
- Track KPIs (time-to-value, usage depth, expansion pipeline) and escalations.
|
||||
- Package learnings into playbooks for future strategic pursuits.
|
||||
|
||||
## Workflow
|
||||
1. **Account Intake** – review goals, stakeholders, telemetry, and commercial context.
|
||||
2. **Motion Design** – map land/adopt/expand milestones, plays, and ownership.
|
||||
3. **Governance** – run cadence calls, decision logs, and executive updates.
|
||||
4. **Enablement** – arm account teams with assets, benchmarks, and exec materials.
|
||||
5. **Retrospective** – capture outcomes, ROI proof, and scale recommendations.
|
||||
|
||||
## Outputs
|
||||
- Land/adopt/expand action plan with owners + milestones.
|
||||
- KPI dashboard highlighting usage, value proof, and expansion pipeline.
|
||||
- Executive recap + lessons learned for leadership.
|
||||
|
||||
---
|
||||
29
agents/value-ops-lead.md
Normal file
29
agents/value-ops-lead.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
name: value-ops-lead
|
||||
description: Aligns usage telemetry, ROI models, and customer stories for enterprise
|
||||
SaaS deals.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
|
||||
# Value Ops Lead Agent
|
||||
|
||||
## Responsibilities
|
||||
- Build ROI/TCO models tailored to industry, persona, and sales stage.
|
||||
- Translate product telemetry into quantified value proof for land/adopt/expand motions.
|
||||
- Maintain library of reference stories, benchmarks, and board-ready artifacts.
|
||||
- Partner with RevOps and finance on commercial scenarios.
|
||||
|
||||
## Workflow
|
||||
1. **Insight Intake** – gather usage, benchmark, and economic data per segment.
|
||||
2. **Model Design** – assemble calculators, one-pagers, and decision briefings.
|
||||
3. **Story Packaging** – combine metrics with narratives, visuals, and customer proof.
|
||||
4. **Enablement** – train AEs/CSMs, publish templates, and answer deal desk requests.
|
||||
5. **Measurement** – log win impact, refresh assumptions, and capture new references.
|
||||
|
||||
## Outputs
|
||||
- ROI/TCO model kit with assumptions + talking points.
|
||||
- Value story one-pagers for priority personas.
|
||||
- Deal support tracker with SLAs and outcomes.
|
||||
|
||||
---
|
||||
34
commands/build-land-adopt-expand-plan.md
Normal file
34
commands/build-land-adopt-expand-plan.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: build-land-adopt-expand-plan
|
||||
description: Creates a phased land/adopt/expand action plan for strategic B2B SaaS accounts.
|
||||
usage: /b2b-saas:build-land-adopt-expand-plan --account "Nimbus Corp" --stage adopt --horizon 2quarters --audience exec
|
||||
---
|
||||
|
||||
# Command: build-land-adopt-expand-plan
|
||||
|
||||
## Inputs
|
||||
- **account** – target customer name/ID.
|
||||
- **stage** – land | adopt | expand | full; controls milestone focus.
|
||||
- **horizon** – timeframe (quarter, 2quarters, year, custom).
|
||||
- **audience** – exec | account-team | cs | async.
|
||||
- **signals** – optional CSV/JSON with telemetry or program notes.
|
||||
|
||||
## Workflow
|
||||
1. **Signal Review** – synthesize telemetry, value metrics, and stakeholder landscape.
|
||||
2. **Milestone Mapping** – lay out success criteria, owners, and checkpoints per phase.
|
||||
3. **Play Selection** – recommend adoption campaigns, exec plays, and expansion bets.
|
||||
4. **Risk/Dependency Logging** – flag gaps, requests, and required approvals.
|
||||
5. **Packaging** – generate presentation/memo plus tracker for follow-ups.
|
||||
|
||||
## Outputs
|
||||
- Land/adopt/expand roadmap with timelines, KPIs, and owners.
|
||||
- Risk + dependency register for leadership visibility.
|
||||
- Action tracker synced to CRM/CSM tools for execution.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `land-adopt-expand-director` – orchestrates motion design + governance.
|
||||
- `industry-strategist` – calibrates narrative + proof by vertical.
|
||||
- `land-adopt-expand-blueprint` skill – enforces milestone structure.
|
||||
- `usage-to-value-map` skill – injects telemetry-driven proof points.
|
||||
|
||||
---
|
||||
34
commands/create-industry-playbook.md
Normal file
34
commands/create-industry-playbook.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: create-industry-playbook
|
||||
description: Produces vertical-specific POV, solution brief, and enablement kit for B2B SaaS teams.
|
||||
usage: /b2b-saas:create-industry-playbook --industry fintech --persona revops --depth full
|
||||
---
|
||||
|
||||
# Command: create-industry-playbook
|
||||
|
||||
## Inputs
|
||||
- **industry** – vertical focus (fintech, healthcare, manufacturing, education, media, public sector).
|
||||
- **persona** – target persona (cio, revops, marketing, product, finance, cs).
|
||||
- **depth** – summary | standard | full; controls output fidelity.
|
||||
- **assets** – optional references to existing case studies or assets.
|
||||
- **format** – deck | memo | docset.
|
||||
|
||||
## Workflow
|
||||
1. **Research Digest** – pull market trends, buyer pains, and competitive signals.
|
||||
2. **Narrative Building** – craft POV, messaging pillars, and proof points.
|
||||
3. **Solution Packaging** – outline recommended bundles, integrations, and usage scenarios.
|
||||
4. **Enablement Kit** – create talk track, objection handling, and resource links.
|
||||
5. **Action Plan** – recommend next steps (campaigns, ABM, references) for GTM teams.
|
||||
|
||||
## Outputs
|
||||
- Industry POV deck/memo with messaging and differentiation.
|
||||
- Solution brief plus recommended bundles/integrations.
|
||||
- Enablement checklist including talk track, objection handling, and asset links.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `industry-strategist` – leads research + narrative creation.
|
||||
- `value-ops-lead` – adds ROI/TCO benchmarks and customer proof.
|
||||
- `vertical-solution-templates` skill – enforces layout + asset structure.
|
||||
- `board-readiness-kit` skill – prepares exec-ready snippets for leadership.
|
||||
|
||||
---
|
||||
34
commands/prepare-board-readout.md
Normal file
34
commands/prepare-board-readout.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
name: prepare-board-readout
|
||||
description: Packages GTM + product metrics into a board-ready SaaS narrative with asks.
|
||||
usage: /b2b-saas:prepare-board-readout --window quarter --themes growth,retention --format deck
|
||||
---
|
||||
|
||||
# Command: prepare-board-readout
|
||||
|
||||
## Inputs
|
||||
- **window** – timeframe (quarter, half, year, custom).
|
||||
- **themes** – comma-separated focus areas (growth, retention, product, efficiency, roadmap).
|
||||
- **format** – deck | memo | dashboard | loom.
|
||||
- **audience** – board | exec | investors | async.
|
||||
- **alerts** – optional boolean to include risk/mitigation appendix.
|
||||
|
||||
## Workflow
|
||||
1. **Metric Selection** – pull KPIs tied to selected themes (ARR, NRR, CAC payback, product usage, roadmap velocity).
|
||||
2. **Narrative Draft** – structure storyline (headline, driver analysis, customer proof, asks).
|
||||
3. **Evidence Layer** – insert telemetry charts, customer anecdotes, competitive insights.
|
||||
4. **Action & Ask** – outline decisions needed, funding requests, or roadmap trade-offs.
|
||||
5. **Packaging** – format deck/memo plus appendix tags for deep dives.
|
||||
|
||||
## Outputs
|
||||
- Board-ready briefing with KPIs, narrative, and action requests.
|
||||
- Appendix library (charts, customer stories, competitive intel).
|
||||
- Decision log + follow-up tracker for leadership.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `value-ops-lead` – curates KPI story and ROI proof.
|
||||
- `industry-strategist` – aligns narrative to vertical/customer trends.
|
||||
- `board-readiness-kit` skill – enforces structure and action log format.
|
||||
- `usage-to-value-map` skill – injects telemetry + customer proof.
|
||||
|
||||
---
|
||||
81
plugin.lock.json
Normal file
81
plugin.lock.json
Normal file
@@ -0,0 +1,81 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/b2b-saas",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "1abeee228725ec679db0ecb7dbb580e49a09a955",
|
||||
"treeHash": "1264d99d6df1c6352581ea67ef0bb5d560b14fca035395986a8905b27e2f8c62",
|
||||
"generatedAt": "2025-11-28T10:17:16.069807Z",
|
||||
"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": "b2b-saas",
|
||||
"description": "Industry POVs, land/adopt/expand orchestration, and board-ready SaaS narratives",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "db4119f6fa740d780f71cfab877fc4e2382f37e0d2e933f5e0d18d3f6cb7ca8c"
|
||||
},
|
||||
{
|
||||
"path": "agents/land-adopt-expand-director.md",
|
||||
"sha256": "7e52109b6ce600e23dc8f35eb4b931a9277a4daad579b984ab91015581f52ca6"
|
||||
},
|
||||
{
|
||||
"path": "agents/value-ops-lead.md",
|
||||
"sha256": "2aa5c1179c6bb9aa127b831107a58935ded9d9cf54a5760658465955af7dbd10"
|
||||
},
|
||||
{
|
||||
"path": "agents/industry-strategist.md",
|
||||
"sha256": "22dd1a8be087f329f0b2eb4e0886b95904a7502de7819c184f915f3872dbffa5"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "d3a3cf55f14bd650a29c706dcac9ef327dc44c0bb9560560fd4fe704bf8f5c37"
|
||||
},
|
||||
{
|
||||
"path": "commands/create-industry-playbook.md",
|
||||
"sha256": "02b7eaf8c24d8f8d6b808ebc2660c71cf6f8e32f2b1f96a5aabc18fdb55dd5d4"
|
||||
},
|
||||
{
|
||||
"path": "commands/build-land-adopt-expand-plan.md",
|
||||
"sha256": "0960f61b6d098d5b8e41e909a890dc6e83b217611a5c89261bf2064251c1db7d"
|
||||
},
|
||||
{
|
||||
"path": "commands/prepare-board-readout.md",
|
||||
"sha256": "0d6621405af102057c6f8f3f50d5965add1464d36be0d0a05a2b2435cd6b51fb"
|
||||
},
|
||||
{
|
||||
"path": "skills/vertical-solution-templates/SKILL.md",
|
||||
"sha256": "1342fd36a4602f20ddc7b2f34d5f2e11fdd8c78a3d65923f12f1ca87a341e9ef"
|
||||
},
|
||||
{
|
||||
"path": "skills/board-readiness-kit/SKILL.md",
|
||||
"sha256": "5d9e3473949cf4cba9728d0fab9c368b36030a9ecc68a563607d969e5576f305"
|
||||
},
|
||||
{
|
||||
"path": "skills/land-adopt-expand-blueprint/SKILL.md",
|
||||
"sha256": "436832f082366c21feab91a2ad742603a2fc8062125c7fa13e1257c1a9a6c75a"
|
||||
},
|
||||
{
|
||||
"path": "skills/usage-to-value-map/SKILL.md",
|
||||
"sha256": "2339649cb3f04b627dc8f853918177e41ef9e38b405a3679ca40869db4f7d92d"
|
||||
}
|
||||
],
|
||||
"dirSha256": "1264d99d6df1c6352581ea67ef0bb5d560b14fca035395986a8905b27e2f8c62"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
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