Partner Folder Structure
Purpose: Standard layout for every partner folder under
knowledge/sales/partners/. Use this when creating or reorganizing partner folders (Snowflake, Omni, Talisma, etc.) so materials are easy to find and agents can navigate consistently.
Partnerships root layout
At the partners root (knowledge/sales/partners/), shared docs are organized into:
- playbooks/ — How-to playbooks (partner, 90-day activation, rep engagement)
- tracker/ — Tracker schema, system doc, rationale, migration
- strategy/ — Ideal partner profile, positioning, evaluation framework, qualification, materials audit
- ops/ — Operational support (e.g. Slack context diagnostics)
- drafts/ — One-off drafts (e.g. intro emails) before a partner folder exists
- templates/ — Reusable templates (Control Center, outreach, briefs, etc.)
- agents/ — Agent prompts (e.g. VP of Partnerships)
Partner-specific content lives in partner folders (e.g. Snowflake/, ContextualAI/), each following the structure below.
Standard Structure (each partner folder)
Every partner folder should follow this layout:
partners/
└── [PartnerName]/ e.g. Snowflake, Omni, Talisma
├── PARTNER_CONTROL_CENTER.md ← Single source of truth; mirrors tracker + materials index
├── meetings/ ← Call notes, meeting insights, talking points
│ └── [descriptive-name].md
├── engagement/ ← Rep enablement, one-pagers, email drafts
│ ├── [asset-name].md
│ └── email-drafts/
│ └── [draft-name].md
├── ops-and-admin/ ← Program docs, registration refs, internal process
│ └── [doc-name].md
└── reference/ ← Partner-provided PDFs, external reference materials
└── [file-name].pdf
Folder Purposes
| Folder | Purpose | Examples |
|---|---|---|
| Root | Control Center only. No other loose files. | PARTNER_CONTROL_CENTER.md |
| meetings/ | Call notes, meeting recaps, talking points, strategy insights from partner conversations. | 01-steve-meeting-insights.md, connie-call-talking-points.md |
| engagement/ | Materials used to engage partner reps or AEs: one-pagers, AE-specific briefs, co-sell drafts. | ravi-gregg-engagement-materials.md |
| engagement/email-drafts/ | Email templates and drafts for partner contacts. | connie-morris-ey-opportunity.md |
| ops-and-admin/ | Programmatic or internal docs: SPN registration, partner program references, rate cards. | spn-registration-form-reference.md |
| reference/ | Partner-provided or third-party reference files (PDFs, decks). Not edited by us. | Cloud Data Warehouse for Financial Services.pdf |
Creating a New Partner Folder
- Create the partner folder:
partners/[PartnerName]/. - Create subfolders:
meetings/,engagement/,engagement/email-drafts/,ops-and-admin/,reference/. - Copy partner-control-center-template.md into the partner folder and rename to
PARTNER_CONTROL_CENTER.md. - Fill in the Control Center with tracker data and any existing materials; link to files as you add them.
- Add the partner to the Partnerships README under “Partner-Specific Documentation” with a link to their Control Center.
Reference: Snowflake (Implemented)
Snowflake is the reference implementation:
New partner folders should mirror this layout so automation and agents can assume the same paths.