Partner Enablement Package

Create a partner enablement package that helps external sellers represent the product accurately and consistently.

Confirm Inputs First

• Confirm whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• Confirm the partner type and motion: referral, reseller, services, marketplace, or channel.
• Confirm the product scope, target use cases, and target customer segment.
• Confirm what the partner must be able to do after enablement: position, qualify, demo, sell, or support handoff.
• Confirm the packaging needed: onboarding guide, talk track, deck outline, certification guidance, launch update, or all of the above.
• Confirm co-sell economics and governance constraints: lead registration, split rules, discount authority, and conflict escalation.
• Confirm known partner constraints, such as limited product access, services expectations, or compliance boundaries.
• Confirm approved source-of-truth assets partners are allowed to use.

If critical inputs are missing, ask for the smallest missing set. If the user prefers speed, proceed with labeled assumptions.

Read The Right Reference

• Read references/partner-package-blueprint.md before defining archetype variants and co-sell controls.

Default Workflow

1. Review the source material and isolate what partners truly need versus what only internal sellers need.
2. Translate positioning, qualification, and proof into partner-safe language that avoids internal jargon and unsupported claims.
3. Define the minimum enablement package by partner role: what to say, what to ask, how to qualify, when to escalate, and what not to promise.
4. Structure onboarding, core assets, and certification guidance around the partner's actual motion and access level.
5. Map approved source assets and identify restricted internal-only content.
6. Add co-sell economics and governance visibility: lead registration, ownership, conflict handling, and approval thresholds.
7. Add clear boundaries for handoff points, services expectations, pricing caveats, and support responsibilities.
8. Return a package that can be delivered directly to partner managers, enablement leads, or channel teams.

Tool Notes

• Keep the default workflow tool-agnostic.
• If the user already works in PRM, LMS, Docs, or partner portals, use those systems as delivery channels rather than as workflow requirements.
• If direct partner data is limited, work from existing direct-sales materials and clearly label what still needs partner validation.

Output Contract

• Default to these deliverables unless the user asks for a narrower package:
• Partner positioning and talk track summary
• Qualification and handoff guidance
• Partner onboarding outline
• Core enablement asset list with purpose by asset
• Certification or readiness guidance
• Co-sell economics and governance summary
• Approved source-asset map with restricted-content notes
• Assumptions, gaps, and partner-specific risks

Quality Bar

• Package is usable by real partners, not copied directly from internal sales enablement.
• Messaging is accurate, bounded, and safe for external use.
• Qualification, escalation, and handoff logic are explicit.
• Assets match the partner motion and level of product access.
• Restricted internal-only information is clearly separated from partner-safe material.
• Output avoids channel theater and focuses on partner execution.