Sales (knowledge/sales/)
Internal revenue / GTM operations tree: partner relationships, commercial assets, research, agents, and lead workspaces. There is no separate knowledge/gtm/ tree — GTM vault content lives here.
GTM sales corpus (not client delivery)
Index: SALES-GTM-CORPUS.md — where GTM / sales content lives in vault/gtm/sales/** (hundreds of markdown files in the monorepo) and how it differs from vault/clients/**/transcripts (mostly delivery, not sales). Reusable negotiation language: README.md · BACKFILL-LOG.md.
Onboarding Fast Path
If you are new and want to run workflows immediately:
- Read
.cursor/skills/GTM_SALES_PARTNERSHIPS_QUICKSTART.md - Use
.cursor/skills/GTM_PARTNER_AUTOMATION_CATALOG.mdto choose the right skill layer - Treat
knowledge/sales/partners/as canonical partner documentation
Where to put new work
| Kind | Path | Notes |
|---|---|---|
| Lead / prospect (pipeline) | knowledge/sales/leads/{slug}/ | Prefer one spine doc {slug}-lead.md; optional transcripts/, proposals/ under that folder. |
| SOW framework & pricing | knowledge/sales/sow-framework/, knowledge/sales/pricing/ | Includes renewal path taxonomy: FDTaaS vs Data Foundations Sprint. |
| Partners | knowledge/sales/partners/ | Program framework (playbooks/, tracker/, templates/, …) and per-vendor folders (Control Centers, meetings/, engagement/, transcripts/, etc.). |
| Active client deliverables | knowledge/clients/{client}/ | Do not create knowledge/sales/clients/ — see vault guide. |
| GTM agents / playbooks | knowledge/sales/agents/ | Registry, feedback sessions, prompts. |
| Quarterly sales-engineering / GTM ops plans | knowledge/sales/plans/ | e.g. Q2 2026 Sales Engineering roadmap (cross-functional hub: ../plans/platform/q2-2026-legal-finance-sales-engineering-roadmap.md). |
Key subfolders
leads/— Prospect workspaces (SOWs, proposals, case-study refs). See README.md for SOW workflow context.leads/_templates/— Spine + play templates and starter bundle. See README.md:lead-spine-template.md,lead-play-template.md,starter/(copy intoleads/<slug>/).sow-framework/— How we structure and price SOWs, including the two renewal paths:- Fractional Data Team-as-a-Service (e.g. CTA annual/retainer style)
- Data Foundations Sprint (e.g. LMNT sprint/milestone style)
partners/— Single partner hub: qualification/tracker/templates/playbooks and vendor folders (Snowflake, Omni, GSV, …). See README.md.agents/— Sales-facing agent assets.services/— Service-line offers, SOPs, demos (catalog lives here).research/,campaign-launch/,marketing-assets/,content/(includescontent/cc-content-system/personal KBs),enablement/, etc. Lead workspaces such as plan-medicare and breezy live underleads/.
Related
- Vault routing: KNOWLEDGE_AND_STANDARDS_GUIDE.md
- Cleanup history: knowledge-platform-delivery-cleanup-opportunities.md