Initial commit
This commit is contained in:
26
.claude-plugin/plugin.json
Normal file
26
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,26 @@
|
|||||||
|
{
|
||||||
|
"name": "enterprise-sales",
|
||||||
|
"description": "Enterprise pursuit orchestration with value, procurement, and governance workflows",
|
||||||
|
"version": "1.0.0",
|
||||||
|
"author": {
|
||||||
|
"name": "GTM Agents",
|
||||||
|
"email": "opensource@intentgpt.ai"
|
||||||
|
},
|
||||||
|
"skills": [
|
||||||
|
"./skills/pursuit-governance/SKILL.md",
|
||||||
|
"./skills/risk-register/SKILL.md",
|
||||||
|
"./skills/value-story-framework/SKILL.md",
|
||||||
|
"./skills/cxo-briefing-kit/SKILL.md",
|
||||||
|
"./skills/procurement-playbook/SKILL.md"
|
||||||
|
],
|
||||||
|
"agents": [
|
||||||
|
"./agents/pursuit-director.md",
|
||||||
|
"./agents/value-architect.md",
|
||||||
|
"./agents/procurement-strategist.md"
|
||||||
|
],
|
||||||
|
"commands": [
|
||||||
|
"./commands/plan-pursuit.md",
|
||||||
|
"./commands/build-value-narrative.md",
|
||||||
|
"./commands/navigate-procurement.md"
|
||||||
|
]
|
||||||
|
}
|
||||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
|||||||
|
# enterprise-sales
|
||||||
|
|
||||||
|
Enterprise pursuit orchestration with value, procurement, and governance workflows
|
||||||
27
agents/procurement-strategist.md
Normal file
27
agents/procurement-strategist.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: procurement-strategist
|
||||||
|
description: Navigates procurement, legal, and security reviews for large enterprise deals.
|
||||||
|
model: haiku
|
||||||
|
---
|
||||||
|
|
||||||
|
# Procurement Strategist Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Build timelines for legal, security, privacy, and compliance workstreams.
|
||||||
|
- Maintain redline trackers, approval matrices, and negotiation guardrails.
|
||||||
|
- Coordinate responses to security questionnaires, RFPs, and compliance audits.
|
||||||
|
- Partner with finance + deal desk to align commercial structures with policy.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Requirements Intake** – gather customer procurement policies, mandatory documents, and deadlines.
|
||||||
|
2. **Workback Planning** – identify internal SMEs (legal, security, privacy), assign tasks, and set checkpoints.
|
||||||
|
3. **Response Management** – compile questionnaires, evidence, and exception requests; log approvals.
|
||||||
|
4. **Negotiation Support** – track concessions, fallback positions, and escalate critical issues.
|
||||||
|
5. **Close & Archive** – capture final agreements, lessons learned, and playbook updates.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Procurement/security workback plan with owners + due dates.
|
||||||
|
- Redline/exception tracker for legal + commercial clauses.
|
||||||
|
- Closeout packet with signed docs, commitments, and follow-up tasks.
|
||||||
|
|
||||||
|
---
|
||||||
27
agents/pursuit-director.md
Normal file
27
agents/pursuit-director.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: pursuit-director
|
||||||
|
description: Leads cross-functional pursuit teams through complex enterprise deal cycles.
|
||||||
|
model: sonnet
|
||||||
|
---
|
||||||
|
|
||||||
|
# Pursuit Director Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Stand up pursuit pods with sales, SE, value, legal, security, and executive sponsors.
|
||||||
|
- Maintain the pursuit plan (milestones, deliverables, risks) and ensure accountability.
|
||||||
|
- Manage deal room hygiene, decision logs, and escalation paths.
|
||||||
|
- Align internal leaders on resource needs, concessions, and approval timelines.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Opportunity Intake** – gather deal summary, stakeholders, competitive context, and deadlines.
|
||||||
|
2. **Pursuit Planning** – define milestones (RFP, showcase, validation, exec meeting, negotiation) and owners.
|
||||||
|
3. **Governance Setup** – configure cadences, decision logs, and escalation matrix.
|
||||||
|
4. **Execution Oversight** – track deliverables, dependencies, and risk mitigation tasks.
|
||||||
|
5. **Post-Mortem** – capture lessons learned, update playbooks, and sync with RevOps.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Pursuit plan with timeline, workstreams, owners, and KPIs.
|
||||||
|
- Risk/action tracker with status + escalation notes.
|
||||||
|
- Post-pursuit summary for leadership + knowledge base.
|
||||||
|
|
||||||
|
---
|
||||||
27
agents/value-architect.md
Normal file
27
agents/value-architect.md
Normal file
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: value-architect
|
||||||
|
description: Crafts quantified value narratives, business cases, and executive-ready ROI deliverables for complex deals.
|
||||||
|
model: haiku
|
||||||
|
---
|
||||||
|
|
||||||
|
# Value Architect Agent
|
||||||
|
|
||||||
|
## Responsibilities
|
||||||
|
- Translate discovery insights into quantified impact models and executive storylines.
|
||||||
|
- Coordinate with finance/value engineering to validate assumptions and methodologies.
|
||||||
|
- Maintain libraries of benchmarks, customer stories, and ROI templates per industry.
|
||||||
|
- Support negotiations by modeling scenarios (pricing, timeline, scope) with clear trade-offs.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Insight Intake** – pull discovery notes, product usage, benchmarks, and customer KPIs.
|
||||||
|
2. **Value Hypothesis** – outline headline impact, drivers, and proof references.
|
||||||
|
3. **Financial Modeling** – build ROI/TCO scenarios with sensitivity analysis.
|
||||||
|
4. **Narrative Packaging** – produce executive story decks, one-pagers, and calculator outputs.
|
||||||
|
5. **Validation & Handoff** – review with pursuit team, capture approvals, and upload to deal room.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- ROI/TCO models with assumptions + scenarios.
|
||||||
|
- Executive value narrative deck/one-pager.
|
||||||
|
- Benchmark + proof appendix for RFPs or negotiations.
|
||||||
|
|
||||||
|
---
|
||||||
35
commands/build-value-narrative.md
Normal file
35
commands/build-value-narrative.md
Normal file
@@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
name: build-value-narrative
|
||||||
|
description: Produces ROI/TCO models, executive storylines, and proof appendices for complex deals.
|
||||||
|
usage: /enterprise-sales:build-value-narrative --deal "GlobalCo ERP" --industry manufacturing --scenario base,upside --audience "CFO,CIO"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: build-value-narrative
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **deal** – opportunity identifier.
|
||||||
|
- **industry** – customer industry to align benchmarks.
|
||||||
|
- **scenario** – comma-separated scenarios (base, upside, downside).
|
||||||
|
- **audience** – target exec roles for tailoring (CFO, CIO, COO, Procurement).
|
||||||
|
- **assumptions** – optional JSON overrides for metrics (ACV, adoption, productivity).
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Data Intake** – ingest discovery notes, product telemetry, benchmarks, and reference stories.
|
||||||
|
2. **Impact Modeling** – calculate ROI/TCO scenarios with sensitivity toggles.
|
||||||
|
3. **Narrative Crafting** – outline headline, drivers, proof, and decision asks per audience.
|
||||||
|
4. **Asset Assembly** – create deck, one-pager, and calculator outputs with transparent assumptions.
|
||||||
|
5. **Review & Packaging** – capture approvals, version history, and attach to deal room.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Scenario-based ROI/TCO workbook.
|
||||||
|
- Executive value narrative deck + one-pager.
|
||||||
|
- Proof appendix with benchmarks, customer stories, and links.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `value-architect` – leads modeling + storyline.
|
||||||
|
- `pursuit-director` – ensures alignment with pursuit milestones.
|
||||||
|
- `procurement-strategist` – validates commercial guardrails.
|
||||||
|
- `value-story-framework` skill – structures the narrative.
|
||||||
|
- `cxo-briefing-kit` skill – packages outputs for executive audiences.
|
||||||
|
|
||||||
|
---
|
||||||
35
commands/navigate-procurement.md
Normal file
35
commands/navigate-procurement.md
Normal file
@@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
name: navigate-procurement
|
||||||
|
description: Coordinates legal, security, and procurement workflows with timelines, owners, and decision logs.
|
||||||
|
usage: /enterprise-sales:navigate-procurement --deal "GlobalCo ERP" --deadline 2026-03-10 --requirements "legal,security,dpia" --exceptions "payment-terms"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: navigate-procurement
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **deal** – opportunity identifier.
|
||||||
|
- **deadline** – final contracting/PO date.
|
||||||
|
- **requirements** – comma-separated workstreams (legal, security, privacy, finance, vendor onboarding).
|
||||||
|
- **exceptions** – optional list of known exception requests (payment terms, data residency, SLAs).
|
||||||
|
- **collaboration-space** – optional link for deal room / project board.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Requirement Intake** – ingest customer documents, questionnaires, policy summaries.
|
||||||
|
2. **Workback Plan** – generate timeline with deliverables, owners, and review gates per workstream.
|
||||||
|
3. **Evidence Library** – attach boilerplate docs (SOC2, penetration tests, insurance certs, product architecture).
|
||||||
|
4. **Redline Tracker** – maintain concession log, approval owners, and status.
|
||||||
|
5. **Communication Cadence** – schedule syncs, escalation checkpoints, and executive updates.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Procurement/security project plan with milestones, owners, dependencies.
|
||||||
|
- Redline + exception tracker ready for deal desk/legal review.
|
||||||
|
- Evidence packet index with links + expiration dates.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `procurement-strategist` – orchestrates workflows + approvals.
|
||||||
|
- `pursuit-director` – ensures pursuit plan stays aligned.
|
||||||
|
- `value-architect` – provides commercial rationale for concessions.
|
||||||
|
- `procurement-playbook` skill – templates + evidence library.
|
||||||
|
- `risk-register` skill – captures risks, mitigations, and escalations.
|
||||||
|
|
||||||
|
---
|
||||||
35
commands/plan-pursuit.md
Normal file
35
commands/plan-pursuit.md
Normal file
@@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
name: plan-pursuit
|
||||||
|
description: Builds an enterprise pursuit plan with milestones, workstreams, and governance cadence.
|
||||||
|
usage: /enterprise-sales:plan-pursuit --deal "GlobalCo ERP" --deadline 2026-02-15 --type rfp --tier strategic
|
||||||
|
---
|
||||||
|
|
||||||
|
# Command: plan-pursuit
|
||||||
|
|
||||||
|
## Inputs
|
||||||
|
- **deal** – opportunity name/ID.
|
||||||
|
- **deadline** – final decision or submission date.
|
||||||
|
- **type** – rfp | inbound | proactive | renewal.
|
||||||
|
- **tier** – strategic | growth | scale.
|
||||||
|
- **workstreams** – optional list (value, security, legal, exec) to emphasize.
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. **Context Gathering** – ingest CRM summary, stakeholders, competitors, and requirements.
|
||||||
|
2. **Milestone Mapping** – outline key events (RFP due, validation, exec alignment, pricing, legal close).
|
||||||
|
3. **Workstream Assignment** – define owners, SMEs, and internal sponsors for each milestone.
|
||||||
|
4. **Governance Setup** – schedule cadences (daily standup, exec sync, risk review) and decision logs.
|
||||||
|
5. **Risk & Dependency Tracking** – capture blockers, approvals, and mitigation plans.
|
||||||
|
|
||||||
|
## Outputs
|
||||||
|
- Pursuit plan (timeline, milestones, workstreams, owners).
|
||||||
|
- Governance calendar + communication plan.
|
||||||
|
- Risk/action tracker seeded with initial items.
|
||||||
|
|
||||||
|
## Agent/Skill Invocations
|
||||||
|
- `pursuit-director` – orchestrates plan + governance.
|
||||||
|
- `value-architect` – aligns value workstream deliverables.
|
||||||
|
- `procurement-strategist` – maps legal/security dependencies.
|
||||||
|
- `pursuit-governance` skill – templates for cadence + decision logs.
|
||||||
|
- `risk-register` skill – standardized risk/action tracker.
|
||||||
|
|
||||||
|
---
|
||||||
85
plugin.lock.json
Normal file
85
plugin.lock.json
Normal file
@@ -0,0 +1,85 @@
|
|||||||
|
{
|
||||||
|
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||||
|
"pluginId": "gh:gtmagents/gtm-agents:plugins/enterprise-sales",
|
||||||
|
"normalized": {
|
||||||
|
"repo": null,
|
||||||
|
"ref": "refs/tags/v20251128.0",
|
||||||
|
"commit": "6ab4a6fd6cb631211f5dd53a09ce2114cb196134",
|
||||||
|
"treeHash": "575d6fbc606ae9a5799b53e8b2b012af14ca104f9d9aff3d5932717011b02f0d",
|
||||||
|
"generatedAt": "2025-11-28T10:17:13.560302Z",
|
||||||
|
"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": "enterprise-sales",
|
||||||
|
"description": "Enterprise pursuit orchestration with value, procurement, and governance workflows",
|
||||||
|
"version": "1.0.0"
|
||||||
|
},
|
||||||
|
"content": {
|
||||||
|
"files": [
|
||||||
|
{
|
||||||
|
"path": "README.md",
|
||||||
|
"sha256": "0c51c366fcec37877203842f98df6b5daca1399885b931a960a0a65c63b34d1a"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/procurement-strategist.md",
|
||||||
|
"sha256": "664ec523962ac4ae840baf624b93a01c32534252e0eebb8287f052f005c41740"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/pursuit-director.md",
|
||||||
|
"sha256": "beec3df410466a11984a8800689d342506de4c3bced35e0408448f0fd1fccc76"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "agents/value-architect.md",
|
||||||
|
"sha256": "26e8062752e06ffc0040b003281a535d3a099ff6ba1bdd8cf47836c6cf43d4f6"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": ".claude-plugin/plugin.json",
|
||||||
|
"sha256": "f21e7e8b2adcf01eca6351fc612f3bb28c768f749a1080ac8f5de7a0b7f8bb01"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/build-value-narrative.md",
|
||||||
|
"sha256": "6d6a724e1980eaec0e6b5884dccff4cb81b9025505951c44da515758f4ec3b6f"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/plan-pursuit.md",
|
||||||
|
"sha256": "73b37475552b8075a15bbcf59a6f209afae6f95653a691ec933553f6f7bb22c3"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "commands/navigate-procurement.md",
|
||||||
|
"sha256": "67335a17d9d5e3ff5f34ddffad257438c587a378a402fcb38211cc13f1add74b"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/cxo-briefing-kit/SKILL.md",
|
||||||
|
"sha256": "5e7520d2b098b27311d857ace1ab4bed604ab1c98f657931f856e6a1ba54c5ad"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/pursuit-governance/SKILL.md",
|
||||||
|
"sha256": "b29bb0fbb1538aac6ee122612063e37e878c6ac8b220926c8b03878b549a7009"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/risk-register/SKILL.md",
|
||||||
|
"sha256": "2097b96325de880b65b681134c6c0bf451c73604064d0a5aaa950236a343192b"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/procurement-playbook/SKILL.md",
|
||||||
|
"sha256": "f6eb87219dc0e65428d3d396d59839e4183d0fa987b1e0d376b0f9aa3dfd9be6"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"path": "skills/value-story-framework/SKILL.md",
|
||||||
|
"sha256": "ebf0003c1f1adc02b92f03f4b5b835cfe9e4d805084533822c73515163ebd8bb"
|
||||||
|
}
|
||||||
|
],
|
||||||
|
"dirSha256": "575d6fbc606ae9a5799b53e8b2b012af14ca104f9d9aff3d5932717011b02f0d"
|
||||||
|
},
|
||||||
|
"security": {
|
||||||
|
"scannedAt": null,
|
||||||
|
"scannerVersion": null,
|
||||||
|
"flags": []
|
||||||
|
}
|
||||||
|
}
|
||||||
31
skills/cxo-briefing-kit/SKILL.md
Normal file
31
skills/cxo-briefing-kit/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: cxo-briefing-kit
|
||||||
|
description: Use to package concise executive updates, decks, and decision logs for
|
||||||
|
enterprise pursuits.
|
||||||
|
---
|
||||||
|
|
||||||
|
# CXO Briefing Kit Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Preparing executive sponsor briefings ahead of milestone meetings.
|
||||||
|
- Summarizing pursuit status for CRO, COO, CFO, or CEO stakeholders.
|
||||||
|
- Logging decisions, risks, and asks after executive reviews.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Audience Snapshot** – note executive priorities, role, and preferred format.
|
||||||
|
2. **Headline & Status** – articulate deal stage, confidence, and key wins/risks.
|
||||||
|
3. **Value Story** – highlight quantified impact + proof tied to executive objectives.
|
||||||
|
4. **Decision & Ask** – specify approvals, resources, or unblockers required.
|
||||||
|
5. **Action & Follow-up** – capture owners, due dates, and communication plan.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- One-slide exec update (headline, metrics, risks, asks).
|
||||||
|
- Briefing memo outline with context, status, decisions, next steps.
|
||||||
|
- Decision log sheet with timestamp, owner, outcome.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep main slide under 150 words; push detail to appendix.
|
||||||
|
- Tailor numbers to executive KPIs (margin, risk, innovation, customer impact).
|
||||||
|
- Pair with `pursuit-governance` to keep cadences consistent.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/procurement-playbook/SKILL.md
Normal file
31
skills/procurement-playbook/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: procurement-playbook
|
||||||
|
description: Use to manage legal, security, and procurement workflows for complex
|
||||||
|
deals.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Procurement Playbook Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Enterprise deals entering security/privacy review or contract negotiation.
|
||||||
|
- RFP/RFI responses requiring coordinated SME input.
|
||||||
|
- Situations with heavy exception requests, custom terms, or compliance evidence.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Requirement Intake** – capture questionnaires, policy docs, and mandatory deliverables.
|
||||||
|
2. **Workstream Mapping** – assign internal SMEs (legal, security, privacy, finance) with timelines.
|
||||||
|
3. **Evidence Library** – maintain templates for SOC2, penetration tests, insurance, data flows, DPIA.
|
||||||
|
4. **Exception Management** – document asks, approvals, fallback positions, and decision owners.
|
||||||
|
5. **Closeout** – log final concessions, expirations, and follow-up obligations.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Procurement workback plan (deliverable, owner, due date, status).
|
||||||
|
- Security questionnaire index with sourcing notes.
|
||||||
|
- Exception request log with approval layers.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep source-of-truth links updated; expired certifications stall reviews.
|
||||||
|
- Coordinate with `cxo-briefing-kit` for executive escalations.
|
||||||
|
- Pair with `risk-register` to surface procurement blockers early.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/pursuit-governance/SKILL.md
Normal file
31
skills/pursuit-governance/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: pursuit-governance
|
||||||
|
description: Use to set cadences, decision logs, and escalation paths for enterprise
|
||||||
|
pursuits.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Pursuit Governance Playbook Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Launching complex pursuits with multiple internal workstreams.
|
||||||
|
- Preparing executive steering updates for strategic deals.
|
||||||
|
- Standardizing standups, decision logs, and risk reviews across regions.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Cadence Matrix** – define daily standups, weekly exec reviews, and async updates per workstream.
|
||||||
|
2. **Decision Log** – capture requests, approvals, and rationale with timestamps and owners.
|
||||||
|
3. **Escalation Paths** – map issue severity to escalation channels (CRO, legal, product, finance).
|
||||||
|
4. **Communication Kit** – templates for updates, dashboards, and summaries.
|
||||||
|
5. **Retrospective Loop** – schedule debriefs and feed insights back into playbooks.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Pursuit governance calendar.
|
||||||
|
- Decision log sheet (request, owner, status, timestamp).
|
||||||
|
- Escalation matrix with contacts and SLAs.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep cadences lightweight; combine workstreams where possible to avoid meeting overload.
|
||||||
|
- Use a shared workspace (Notion, Asana, Sheets) for transparency.
|
||||||
|
- Pair with `risk-register` to ensure escalations include mitigation details.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/risk-register/SKILL.md
Normal file
31
skills/risk-register/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: risk-register
|
||||||
|
description: Use to track pursuit risks, owners, mitigation steps, and escalation
|
||||||
|
triggers.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Enterprise Risk Register Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- During enterprise pursuits with multiple high-stakes dependencies.
|
||||||
|
- Preparing executive updates or steering committee reviews.
|
||||||
|
- Handing off deals between pursuit phases or regions.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Risk Catalog** – categorize by workstream (value, product, legal, security, executive, finance).
|
||||||
|
2. **Scoring** – likelihood x impact, color-coded with thresholds for escalation.
|
||||||
|
3. **Mitigation Plan** – define owner, action, due date, and supporting resources.
|
||||||
|
4. **Watchlist & Escalation** – highlight items nearing deadlines or requiring CRO/exec attention.
|
||||||
|
5. **Retrospective** – update playbooks with resolved risks + guidance.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Risk register table (risk, category, score, owner, mitigation, status).
|
||||||
|
- Weekly summary slide for executive steering meetings.
|
||||||
|
- Escalation request form with context + proposed action.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep risk statements precise (impact + trigger) to aid decision-making.
|
||||||
|
- Default to weekly updates; high-risk deals may require twice-weekly cadences.
|
||||||
|
- Align scoring with `pursuit-governance` to maintain consistent reporting.
|
||||||
|
|
||||||
|
---
|
||||||
31
skills/value-story-framework/SKILL.md
Normal file
31
skills/value-story-framework/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
name: value-story-framework
|
||||||
|
description: Use to craft executive-ready value narratives and ROI/TCO stories for
|
||||||
|
enterprise pursuits.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Value Story Framework Skill
|
||||||
|
|
||||||
|
## When to Use
|
||||||
|
- Translating discovery insights into quantified impact stories.
|
||||||
|
- Preparing executive briefings or RFP narrative sections.
|
||||||
|
- Aligning sellers, value engineers, and finance on assumptions.
|
||||||
|
|
||||||
|
## Framework
|
||||||
|
1. **Headline Impact** – state quantified outcome (savings, revenue, risk reduction) with time horizon.
|
||||||
|
2. **Driver Pillars** – break impact into 3-4 drivers with supporting data or benchmark references.
|
||||||
|
3. **Proof Layer** – attach customer stories, product metrics, or analyst stats per driver.
|
||||||
|
4. **Execution Plan** – outline phases, required resources, and success metrics.
|
||||||
|
5. **Decision Ask** – specify commitments, timeline, and next-step expectations.
|
||||||
|
|
||||||
|
## Templates
|
||||||
|
- Value narrative deck outline (headline, drivers, proof, plan, ask).
|
||||||
|
- ROI/TCO worksheet with inputs, assumptions, scenario toggles.
|
||||||
|
- Executive one-pager layout for CXO readouts.
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
- Keep assumptions transparent; include sensitivity +/- ranges.
|
||||||
|
- Mirror customer language from discovery to reinforce credibility.
|
||||||
|
- Pair with `cxo-briefing-kit` to ensure outputs land with each stakeholder.
|
||||||
|
|
||||||
|
---
|
||||||
Reference in New Issue
Block a user