Partner Enablement
Help channel, co-sell, and technology partners sell your product effectively. Partners are an extension of your sales team — but they have less context, less training, and less urgency. The materials need to be simpler, more self-serve, and more opinionated than internal enablement.
Partner Types
- Channel Partners / Resellers: Sell your product as part of their portfolio
- Co-sell Partners: Sell alongside you into shared accounts
- Technology Partners: Integrate with your product and bring joint solutions to market
- Referral Partners: Send leads your way for a commission
- Services Partners: Implement your product for customers
Each type needs different enablement — a reseller needs a full playbook; a referral partner needs a one-pager.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PARTNER ENABLEMENT │
├─────────────────────────────────────────────────────────────────┤
│ DELIVERABLES │
│ 1. Partner Playbook — Complete selling guide for partners │
│ 2. Co-Sell Guide — How to run joint opportunities │
│ 3. Joint Value Prop — Combined messaging for the partnership │
│ 4. Partner Onboarding Kit — Everything a new partner needs │
│ 5. Deal Registration Guide — How to register and track deals │
│ 6. Partner Battle Card — Competitive positioning for partners │
├─────────────────────────────────────────────────────────────────┤
│ KEY PRINCIPLE │
│ Partner materials must be simpler than internal materials. │
│ Partners have less time, less context, and more products to │
│ sell. Make it dead simple to understand, position, and sell. │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Partner-sourced deal data and win rates │
│ + ~~CRM: Partner deal pipeline and conversion metrics │
│ + ~~CRM: Customer profiles for partner success stories │
│ + ~~data enrichment (ZoomInfo): Partner company research │
│ + ~~data enrichment (ZoomInfo): Partner customer tech stacks │
│ + ~~data enrichment (Clay): Partner company enrichment │
│ + ~~data enrichment (LinkedIn): Partner contact profiles │
│ + ~~data enrichment (LinkedIn): Partner company updates │
│ + ~~conversation intelligence (Gong): Partner call patterns │
│ + ~~conversation intelligence (Gong): Joint call recordings │
│ + ~~chat: Partner feedback and deal discussions │
└─────────────────────────────────────────────────────────────────┘
Execution Flow
Step 0: Automatic Data Pull (Before Asking the User Anything)
CRITICAL: Before asking for partner context, pull data from connected tools. Partner materials are strongest when grounded in real deal data from the partner channel.
CRM Data Pull
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
- Pull partner-sourced deals. Search
deals for deals associated with the partner (by partner name, source, or deal type).
- Properties:
dealname, amount, dealstage, closedate, createdate, pipeline, hubspot_owner_id, dealtype, description, closed_won_reason, closed_lost_reason
- Compute: partner channel win rate, avg deal size, avg cycle length
- Identify partner ICP from won deals. Pull companies associated with partner-sourced won deals.
- Properties:
name, industry, numberofemployees, annualrevenue
- Pattern: Which company profiles win through the partner channel? → Feeds "Who To Sell This To"
- Pull buying committee from partner wins. Get contacts from partner-sourced won deals.
- Properties:
firstname, lastname, jobtitle, email
- Pattern: Which titles appear in partner-closed deals? → Feeds "Best-Fit Personas"
- Analyze partner losses. Pull closed-lost deals from partner channel.
- Common loss reasons → Feeds "Common Objections" and training focus areas
- Check partner pipeline. Pull open deals from partner channel.
- Stage distribution → Shows where partners get stuck (enablement gap)
Sales Intelligence Data Pull
ZoomInfo (if available):
- Research the partner company. Use
zoominfo_search_company with the partner's company name.
- Company size, focus areas, customer base → Tailor materials to partner's context
- Get partner customer tech stacks. Use
zoominfo_get_tech_stack on partner's existing customer base.
- Common tech stacks → Integration positioning for the partner playbook
Clay (if available):
- Enrich the partner company. Use
clay_enrich_company with the partner domain.
- Growth signals, recent changes, market positioning → Partner context
LinkedIn (if available):
- Get partner contact profiles. Use
linkedin_get_profile for partner sales leadership.
- Background, priorities, communication style → Tailor materials to partner audience
- Search partner company updates. Use
linkedin_search_companies for partner company.
- Recent initiatives, focus areas, market positioning → Align materials to partner strategy
Gong Data Pull
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
- Find partner co-sell calls. Use
gong_search_calls with the partner company name.
- How do partner reps currently position your product?
- Analyze joint call patterns. Use
gong_get_call_stats on partner-involved calls.
- Talk-to-listen ratios, topics covered → Where do partners struggle?
- Extract positioning gaps. Use
gong_get_transcript on partner-led calls.
- Where do partners misspeak about features or value props? → Training focus
Chat Data Pull
If chat tools are available (slack_search_public, slack_search_public_and_private):
- Search for the partner name in partner/channel channels
- Surface partner feedback, deal questions, and enablement requests
- Look for common questions partners ask — these reveal enablement gaps
Present What You Found
"I pulled data for the [Partner] channel: [N] partner-sourced deals in the last [period] — [X]% win rate with $[X] avg deal size. Per CRM, partners win most with [company profile] companies, and common loss reasons include [reasons]. [If Gong:] Found [N] joint calls — partners tend to [positioning pattern]. [If ZoomInfo:] Partner focuses on [market/industry] with [N] customers. Building partner materials now..."
Step 1: Gather Remaining Context
After the auto-pull, ask ONLY for what the tools couldn't provide:
- Partner type — Channel, co-sell, technology, referral, or services?
- Deliverable — Playbook, co-sell guide, joint value prop, onboarding kit, or battle card?
- Partner-specific context — Margin structure, deal registration process, support SLA
- Relationship nuance — What the partner cares about, their competitive landscape
Step 2: Generate Partner Materials
Build using ALL evidence. Use partner-channel deal data as primary evidence. Cite sources: "Per CRM (partner deals):", "Per Gong (joint calls):", "Per ZoomInfo:", "Per Slack:". Keep materials simpler than internal equivalents — partners have less time and context.
Step 3: Store Insights
- Update
memory/deal-patterns.md with partner channel patterns discovered
- Update
memory/content-registry.md with new partner enablement assets
- Log in
memory/changelog.md
Getting Started
- "Build a partner playbook for our channel resellers"
- "Create a co-sell guide for our partnership with [Partner]"
- "Help me build a joint value proposition with [Technology Partner]"
- "Create an onboarding kit for new partners"
- "Build a partner-facing battle card for our competitive landscape"
Output: Partner Playbook
# Partner Sales Playbook: [Your Product]
**For:** [Partner Type] Partners
**Version:** [X.0]
**Last Updated:** [Date]
---
## Your 60-Second Pitch
[The simplest possible explanation of what the product does, who it's for, and why they should care. If a partner can't explain this in a meeting without preparation, the pitch is too complex.]
---
## Who To Sell This To
### Ideal Customer
| Attribute | Detail |
|-----------|--------|
| Company size | [Range] |
| Industry | [Top 3] |
| Trigger event | [What makes them ready to buy now] |
### Best-Fit Personas
**Primary:** [Title] — [What they care about in one sentence]
**Secondary:** [Title] — [What they care about]
### Qualifying Questions
Ask these three questions. If the prospect answers "yes" to two or more, they're a fit:
1. "[Simple qualifying question]"
2. "[Question]"
3. "[Question]"
---
## How to Position
### Lead with this:
> "[One sentence value proposition that works in any conversation]"
### Avoid saying:
- [Common mistake partners make when positioning]
- [Technical detail that confuses prospects at this stage]
### Customer Proof Point
"[Customer X] deployed [your product] and saw [specific result] in [timeframe]."
---
## Pricing & Deal Structure
| Tier/SKU | Price | Partner Margin | Notes |
|----------|-------|---------------|-------|
| [Tier] | $[X] | [X]% | [When to recommend] |
---
## Common Objections (Top 3)
### "[Objection 1]"
> "[Simple response — one paragraph max]"
### "[Objection 2]"
> "[Response]"
### "[Objection 3]"
> "[Response]"
---
## Deal Registration & Support
**How to register:** [Simple steps]
**Support contact:** [Who to reach out to]
**Demo support:** [How to get a demo for their prospect]
**SLA:** [Response time for partner requests]
---
## Resources
| Resource | What It Is | Link |
|----------|-----------|------|
| Demo video | [Description] | [Link] |
| One-pager | [Description] | [Link] |
| Case study | [Description] | [Link] |
Design Principles for Partner Content
- Shorter is better. Partners won't read 20 pages. Keep it under 5.
- Decision-ready, not information-rich. "Sell this to companies with 50-500 employees" not "our product scales from SMB to enterprise."
- Scripted, not conceptual. Give them exact words to say, not messaging frameworks.
- Self-serve. Partners won't attend your training. Make materials that work without explanation.
- Focus on WIIFM. What's in it for the partner? Lead with their margin, their customer value, their competitive advantage.
Related Skills
- battle-cards → Simplified competitive cards for partner use
- playbook-builder → Full playbooks adapted for partner context
- buyer-persona → Simplified personas for partner qualification
- campaign-to-field → Joint marketing campaigns translated for partner field teams
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: partner-enablement-23description: Create enablement materials for channel partners, co-sell partners, and technology partners — partner playbooks, co-sell guides, joint value propositions, and partner onboarding kits. Use this skill when building partner sales materials, co-selling strategies, channel partner programs, joint go-to-market motions, or when someone says "enable our partners", "partner playbook", "co-sell guide", "channel partner kit", or "help partners sell our product". Also trigger when someone mentions partner ecosystem, alliance management, channel strategy, or co-marketing. Use when this capability is needed.4---56# Partner Enablement78Help channel, co-sell, and technology partners sell your product effectively. Partners are an extension of your sales team — but they have less context, less training, and less urgency. The materials need to be simpler, more self-serve, and more opinionated than internal enablement.910## Partner Types1112- **Channel Partners / Resellers:** Sell your product as part of their portfolio13- **Co-sell Partners:** Sell alongside you into shared accounts14- **Technology Partners:** Integrate with your product and bring joint solutions to market15- **Referral Partners:** Send leads your way for a commission16- **Services Partners:** Implement your product for customers1718Each type needs different enablement — a reseller needs a full playbook; a referral partner needs a one-pager.1920---2122## How It Works2324```25┌─────────────────────────────────────────────────────────────────┐26│ PARTNER ENABLEMENT │27├─────────────────────────────────────────────────────────────────┤28│ DELIVERABLES │29│ 1. Partner Playbook — Complete selling guide for partners │30│ 2. Co-Sell Guide — How to run joint opportunities │31│ 3. Joint Value Prop — Combined messaging for the partnership │32│ 4. Partner Onboarding Kit — Everything a new partner needs │33│ 5. Deal Registration Guide — How to register and track deals │34│ 6. Partner Battle Card — Competitive positioning for partners │35├─────────────────────────────────────────────────────────────────┤36│ KEY PRINCIPLE │37│ Partner materials must be simpler than internal materials. │38│ Partners have less time, less context, and more products to │39│ sell. Make it dead simple to understand, position, and sell. │40├─────────────────────────────────────────────────────────────────┤41│ SUPERCHARGED (when you connect your tools) │42│ + ~~CRM: Partner-sourced deal data and win rates │43│ + ~~CRM: Partner deal pipeline and conversion metrics │44│ + ~~CRM: Customer profiles for partner success stories │45│ + ~~data enrichment (ZoomInfo): Partner company research │46│ + ~~data enrichment (ZoomInfo): Partner customer tech stacks │47│ + ~~data enrichment (Clay): Partner company enrichment │48│ + ~~data enrichment (LinkedIn): Partner contact profiles │49│ + ~~data enrichment (LinkedIn): Partner company updates │50│ + ~~conversation intelligence (Gong): Partner call patterns │51│ + ~~conversation intelligence (Gong): Joint call recordings │52│ + ~~chat: Partner feedback and deal discussions │53└─────────────────────────────────────────────────────────────────┘54```5556---5758## Execution Flow5960### Step 0: Automatic Data Pull (Before Asking the User Anything)6162**CRITICAL:** Before asking for partner context, pull data from connected tools. Partner materials are strongest when grounded in real deal data from the partner channel.6364#### CRM Data Pull6566Check if you have access to CRM tools (look for tools containing `search_crm_objects`, `get_crm_objects`, or similar).6768If CRM tools ARE available:69701. **Pull partner-sourced deals.** Search `deals` for deals associated with the partner (by partner name, source, or deal type).71 - Properties: `dealname`, `amount`, `dealstage`, `closedate`, `createdate`, `pipeline`, `hubspot_owner_id`, `dealtype`, `description`, `closed_won_reason`, `closed_lost_reason`72 - Compute: partner channel win rate, avg deal size, avg cycle length732. **Identify partner ICP from won deals.** Pull companies associated with partner-sourced won deals.74 - Properties: `name`, `industry`, `numberofemployees`, `annualrevenue`75 - Pattern: Which company profiles win through the partner channel? → Feeds "Who To Sell This To"763. **Pull buying committee from partner wins.** Get contacts from partner-sourced won deals.77 - Properties: `firstname`, `lastname`, `jobtitle`, `email`78 - Pattern: Which titles appear in partner-closed deals? → Feeds "Best-Fit Personas"794. **Analyze partner losses.** Pull closed-lost deals from partner channel.80 - Common loss reasons → Feeds "Common Objections" and training focus areas815. **Check partner pipeline.** Pull open deals from partner channel.82 - Stage distribution → Shows where partners get stuck (enablement gap)8384#### Sales Intelligence Data Pull8586**ZoomInfo** (if available):871. **Research the partner company.** Use `zoominfo_search_company` with the partner's company name.88 - Company size, focus areas, customer base → Tailor materials to partner's context892. **Get partner customer tech stacks.** Use `zoominfo_get_tech_stack` on partner's existing customer base.90 - Common tech stacks → Integration positioning for the partner playbook9192**Clay** (if available):931. **Enrich the partner company.** Use `clay_enrich_company` with the partner domain.94 - Growth signals, recent changes, market positioning → Partner context9596**LinkedIn** (if available):971. **Get partner contact profiles.** Use `linkedin_get_profile` for partner sales leadership.98 - Background, priorities, communication style → Tailor materials to partner audience992. **Search partner company updates.** Use `linkedin_search_companies` for partner company.100 - Recent initiatives, focus areas, market positioning → Align materials to partner strategy101102#### Gong Data Pull103104Check if you have access to Gong tools (look for tools prefixed with `gong_`).105106If Gong tools ARE available:1071081. **Find partner co-sell calls.** Use `gong_search_calls` with the partner company name.109 - How do partner reps currently position your product?1102. **Analyze joint call patterns.** Use `gong_get_call_stats` on partner-involved calls.111 - Talk-to-listen ratios, topics covered → Where do partners struggle?1123. **Extract positioning gaps.** Use `gong_get_transcript` on partner-led calls.113 - Where do partners misspeak about features or value props? → Training focus114115#### Chat Data Pull116117If chat tools are available (`slack_search_public`, `slack_search_public_and_private`):1181. Search for the partner name in partner/channel channels1192. Surface partner feedback, deal questions, and enablement requests1203. Look for common questions partners ask — these reveal enablement gaps121122#### Present What You Found123124> "I pulled data for the **[Partner]** channel: **[N] partner-sourced deals** in the last [period] — **[X]% win rate** with **$[X] avg deal size**. Per CRM, partners win most with **[company profile]** companies, and common loss reasons include **[reasons]**. [If Gong:] Found **[N] joint calls** — partners tend to [positioning pattern]. [If ZoomInfo:] Partner focuses on **[market/industry]** with **[N] customers**. Building partner materials now..."125126### Step 1: Gather Remaining Context127128After the auto-pull, ask ONLY for what the tools couldn't provide:129- **Partner type** — Channel, co-sell, technology, referral, or services?130- **Deliverable** — Playbook, co-sell guide, joint value prop, onboarding kit, or battle card?131- **Partner-specific context** — Margin structure, deal registration process, support SLA132- **Relationship nuance** — What the partner cares about, their competitive landscape133134### Step 2: Generate Partner Materials135136Build using ALL evidence. Use partner-channel deal data as primary evidence. Cite sources: "Per CRM (partner deals):", "Per Gong (joint calls):", "Per ZoomInfo:", "Per Slack:". Keep materials simpler than internal equivalents — partners have less time and context.137138### Step 3: Store Insights139140- Update `memory/deal-patterns.md` with partner channel patterns discovered141- Update `memory/content-registry.md` with new partner enablement assets142- Log in `memory/changelog.md`143144---145146## Getting Started147148- "Build a partner playbook for our channel resellers"149- "Create a co-sell guide for our partnership with [Partner]"150- "Help me build a joint value proposition with [Technology Partner]"151- "Create an onboarding kit for new partners"152- "Build a partner-facing battle card for our competitive landscape"153154---155156## Output: Partner Playbook157158```markdown159# Partner Sales Playbook: [Your Product]160161**For:** [Partner Type] Partners162**Version:** [X.0]163**Last Updated:** [Date]164165---166167## Your 60-Second Pitch168169[The simplest possible explanation of what the product does, who it's for, and why they should care. If a partner can't explain this in a meeting without preparation, the pitch is too complex.]170171---172173## Who To Sell This To174175### Ideal Customer176| Attribute | Detail |177|-----------|--------|178| Company size | [Range] |179| Industry | [Top 3] |180| Trigger event | [What makes them ready to buy now] |181182### Best-Fit Personas183**Primary:** [Title] — [What they care about in one sentence]184**Secondary:** [Title] — [What they care about]185186### Qualifying Questions187Ask these three questions. If the prospect answers "yes" to two or more, they're a fit:1881. "[Simple qualifying question]"1892. "[Question]"1903. "[Question]"191192---193194## How to Position195196### Lead with this:197> "[One sentence value proposition that works in any conversation]"198199### Avoid saying:200- [Common mistake partners make when positioning]201- [Technical detail that confuses prospects at this stage]202203### Customer Proof Point204"[Customer X] deployed [your product] and saw [specific result] in [timeframe]."205206---207208## Pricing & Deal Structure209210| Tier/SKU | Price | Partner Margin | Notes |211|----------|-------|---------------|-------|212| [Tier] | $[X] | [X]% | [When to recommend] |213214---215216## Common Objections (Top 3)217218### "[Objection 1]"219> "[Simple response — one paragraph max]"220221### "[Objection 2]"222> "[Response]"223224### "[Objection 3]"225> "[Response]"226227---228229## Deal Registration & Support230231**How to register:** [Simple steps]232**Support contact:** [Who to reach out to]233**Demo support:** [How to get a demo for their prospect]234**SLA:** [Response time for partner requests]235236---237238## Resources239| Resource | What It Is | Link |240|----------|-----------|------|241| Demo video | [Description] | [Link] |242| One-pager | [Description] | [Link] |243| Case study | [Description] | [Link] |244```245246---247248## Design Principles for Partner Content2492501. **Shorter is better.** Partners won't read 20 pages. Keep it under 5.2512. **Decision-ready, not information-rich.** "Sell this to companies with 50-500 employees" not "our product scales from SMB to enterprise."2523. **Scripted, not conceptual.** Give them exact words to say, not messaging frameworks.2534. **Self-serve.** Partners won't attend your training. Make materials that work without explanation.2545. **Focus on WIIFM.** What's in it for the partner? Lead with their margin, their customer value, their competitive advantage.255256---257258## Related Skills259260- **battle-cards** → Simplified competitive cards for partner use261- **playbook-builder** → Full playbooks adapted for partner context262- **buyer-persona** → Simplified personas for partner qualification263- **campaign-to-field** → Joint marketing campaigns translated for partner field teams264265---266> Converted and distributed by [TomeVault](https://tomevault.io/claim/jbalbu01) — claim your Tome and manage your conversions.267<!-- tomevault:4.0:skill_md:2026-04-15 -->