Stage 1: Founder-led (0-10 active partners)
One person, usually the founder or VP Sales, spending 25-50% of their time on partner work. No dedicated headcount, no PRM tool, no MDF budget. The partnership is the founder's relationship.
What this stage handles well: high-touch first-partner onboarding, deep customization to the early partners. What breaks: the first time the founder is in a customer crisis and partner emails go unanswered for a week.
Transition signal: the founder spending more than 50% of their time on partner work, or the program approaching 10 active partners.
Stage 2: First dedicated hire (10-25 active partners)
One full-time Partner Manager owning end-to-end: recruitment, onboarding, ongoing relationships, deal registration, conflict resolution. Reports to VP Sales or COO. Often the first hire is a generalist with some channel background, not a specialist.
Tooling typically added: PRM (Crossbeam, PartnerStack, or HubSpot Partner) and a deal registration workflow.
Transition signal: 25+ active partners or partner-sourced revenue above $1M ARR.
Stage 3: Specialized partner org (25-100 active partners)
The single Partner Manager role splits into specialized functions:
- Director of Partnerships (program leadership, strategy)
- Partner Account Managers (relationship management, typically 10-15 partners per PAM)
- Partner Marketing Manager (joint campaigns, MDF management, partner-facing content)
- Partner Operations Manager (PRM, reporting, commission processing)
Reporting line: Director reports to CRO or COO. Partner team total: 5-10 FTE depending on partner mix.
Stage 4: Multi-motion enterprise org (100+ active partners)
At 100+ active partners across multiple motions (reseller, SI, tech), the org splits by motion or by region:
- VP of Channels (P&L owner, reports to CRO)
- Heads of Channel per motion (Reseller, SI, Tech) or per region
- Partner Account Managers aligned to motion or geography
- Partner Marketing team (5+ FTE)
- Partner Enablement team (separate from product enablement)
- Partner Operations and Analytics team
- Channel Engineers / Solution Architects (technical partner support)
Total: 15-50 FTE depending on motion mix. Reports through CRO or sometimes through a standalone Chief Channel Officer.
Cross-functional roles outside the partner org
Even at Stage 4, the partner program depends on roles outside the partner org. The Cross Program RACI (in the Foundations Pack) names who owns what across:
- Legal (partner agreement updates, conflict adjudication)
- Finance (commission processing, MDF approval)
- Product / Engineering (API maintenance, integration partner support)
- Customer Success (partner-delivered customer transitions)
- Sales Operations (deal registration in CRM, attribution rules)
Without the RACI, the partner team becomes the bottleneck for everything partner-related. With it, the program scales without the partner team becoming a kingdom.