partnerships-channel-coach

Coach a B2B SaaS team on building a real partnerships-and-channel motion. Most partnership programs fail not because partnerships are bad, but because the company started before they had product readiness, sales-motion clarity, or organizational capacity to support partners. Done well, partnerships can become 30-60% of revenue at maturity. Done badly, partnerships consume exec time, generate channel conflict with direct sales, and produce no measurable revenue.

This is not about ad-hoc integrations or one-off referral arrangements. This is about a structured program with multiple partners, defined economics, and operational machinery.

When to engage

Trigger when:

• "Should we build a partnerships team?"
• "We have 3 informal partner relationships — should we formalize?"
• "Reseller program design"
• "Channel motion for international expansion"
• "Co-sell motion with [Salesforce / HubSpot / AWS]"
• "Our partnerships team has 5 people but is producing zero revenue"
• "Sales reps are fighting with channel reps over the same deals"
• "Strategic partnership with [name] — how do we structure it?"
• "We're hiring our first VP of Partnerships — what should they do first?"

Do not engage for: pure affiliate / referral programs (different mechanics), influencer marketing partnerships (different audience model), or biz-dev for one-off deals (use a different framework).

The 4 partnership archetypes

These are not interchangeable. Most failed programs try to be all four at once.

1. Technology / integration partners (ISV partners)

What: Other SaaS companies whose product you integrate with (or vice versa). E.g., Slack integrating with 2000+ apps; HubSpot integrating with 1000+ apps. Revenue mechanism: Mostly indirect. Joint customers are stickier; you appear in their marketplace; co-marketing. Best when: You have a product where ecosystem integrations drive customer wins (CRM, communications, infrastructure). Doesn't work for: Standalone products with limited integration surface.

2. Referral partners

What: Consultancies, individual consultants, agencies, or aligned-but-non-competing vendors who refer leads to you. Revenue mechanism: Commission on closed referred leads, typically 10-15%. Best when: You have a clear ICP that other service providers serve (e.g., agencies recommending marketing-tech to their clients). Doesn't work for: Self-serve products where referrals are weak; commodity products.

3. Reseller / channel partners (VARs, MSPs, SIs)

What: Partners who sell your product as part of their offering, often bundling services. They own the customer relationship. Revenue mechanism: Margin (15-30%) on resold license + their services. Best when: Your product is part of a larger solution; international expansion; vertical depth. Doesn't work for: Product-led-growth-first companies; very low ACV products.

4. Strategic alliances

What: Deep relationship with a much-larger partner (e.g., AWS, Microsoft, Salesforce) where you co-sell into their customer base. Revenue mechanism: Co-sell on enterprise deals; marketplace transactions; referral fees. Best when: You have product-market-fit and the partner's ecosystem is your ICP's natural buying environment. Doesn't work for: Early-stage companies (resourcing imbalance is brutal).

Are you ready for a partnership program?

Pre-conditions

• Product maturity: Onboarding works without hand-holding. Implementation time is bounded. Documentation is solid.
• Sales motion clarity: You know your ICP, your pricing, your sales cycle. Partners can't sell what you can't sell.
• Differentiated positioning: Partners need a reason to push you over alternatives. "We're cheaper than [competitor]" isn't enough.
• Margin headroom: You have to give 10-30% margin without breaking unit economics.
• Organizational capacity: Someone (ideally a VP or strong director) can own the program full-time. "I'll do it on the side" doesn't scale.
• Direct-sales discipline: A direct-sales motion that won't sabotage channel deals out of competitive fear.

Common red-flag indicators

• "We're at $1M ARR; we should build a channel to grow faster." Almost always wrong; partnerships work post-PMF, not pre.
• "Our enterprise deals take 18 months — partners can speed them up." Partners may speed up access, but the underlying sales-motion problems aren't solved.
• "The board wants a partnerships story." Build for revenue, not narrative.
• "We don't have a partnerships team but we have 30 partners listed on our website." Listing partners is not partnering.

Program design

Tiering

Most successful programs have 2-4 tiers, e.g.:

• Bronze / Registered: any partner who's signed up. Light commitment. Access to portal, basic enablement.
• Silver / Certified: partners who've completed certification, have at least 1 closed deal in last 12 months. More margin, MDF access.
• Gold / Premier: top-tier partners with multiple certifications, named-account model, multiple closed deals annually. Higher margin, dedicated channel manager, joint roadmap input.
• Platinum / Strategic: the few partners who deliver 10%+ of channel revenue. Custom terms; exec-to-exec relationship.

Tiering is critical because it creates aspiration and clarity. Without tiering, partners don't know what to chase.

Margin / commission structure

Standard ranges:

• Referral: 10-15% of first-year ACV (sometimes recurring 1-2 years).
• Reseller: 15-30% margin on license; partner adds services revenue on top.
• Co-sell: variable; sometimes flat referral, sometimes shared deal credit.
• Strategic alliance: bespoke; sometimes pure marketplace economics.

Don't over-pay early; you'll never get the rate down later. Don't under-pay; partners won't push you.

Deal registration

A formal mechanism to:

• Register a deal as partner-led (claim the deal upfront).
• Get protection from direct-sales conflict.
• Lock in margin / commission.

Deal-reg programs need:

• Clear submission form (account, contact, deal stage, expected close).
• Approval SLA (24-48 hours typical).
• Conflict resolution process when two partners (or partner vs direct sales) register the same account.
• Expiration (typically 90-180 days).

MDF (market development funds)

Funds the company gives partners to invest in joint marketing — events, campaigns, content. Typical: 2-5% of partner-generated revenue.

• Requires submission of marketing plan; reimburses on completion.
• Builds joint brand; demonstrates company commitment.
• Without MDF, top-tier partners often won't invest.

Pricing protection

Partners need confidence that direct sales won't undercut them on price. Common policies:

• Approved-customer-list (partner-named accounts that direct sales can't pursue).
• Discount governance (max discount, partner-deals-respected).
• Conflict-resolution escalation path.

Partner recruiting

Who to recruit

By archetype:

• ISV/tech partners: companies whose customers overlap with your ICP and whose product is complementary (not competitive).
• Referral partners: agencies and consultancies serving your ICP. Look for: 5-50 person firms, 3+ years in market, established practice.
• Reseller/channel: firms with existing customer relationships in your target verticals or geos. Often regional MSPs, SIs, or vertical specialists.
• Strategic alliances: the 1-3 platform vendors whose ecosystem your ICP lives in.

Recruiting motion

Not unlike sales:

• Target list (50-100 candidate partners).
• Outreach to senior decision-maker (often founder / VP-level).
• Discovery: do they have customers who match your ICP? Bandwidth to take on a new partner? What's their customer-acquisition motion?
• Pitch: market opportunity, your product fit, partnership economics, support level.
• Pilot: typical 90-day evaluation period with limited commitment from both sides.
• Formalize: signed agreement, certification path, first joint-marketing initiative.

Qualifying questions

• "How many of your customers fit our ICP today?"
• "Do you have one or more reps committed to selling our product?"
• "What's your typical sales cycle and ACV in the relevant segment?"
• "How are you compensated internally for partner-product sales?"
• "What's your previous experience with technology partnerships?"

A partner who can't answer these specifically is not committed. Be honest with yourself.

Partner enablement

The work between "signed agreement" and "real revenue."

Onboarding (first 30-60 days)

• Kickoff: senior exec meeting, joint goals, named relationship contacts.
• Technical training: product overview, demo training, technical certification (often 8-16 hours of content).
• Sales training: ICP, value proposition, competitive positioning, pricing, deal-registration process.
• Joint go-to-market plan: 90-day actions for both sides.

Ongoing enablement

• Quarterly business reviews (QBRs) with each top-tier partner.
• Regular content updates (new features, new positioning, competitive intel).
• Sales-rep-level engagement (you should know the names of partners' best reps).
• Joint marketing: at least 1-2 campaigns per partner per year.
• Co-customer-success: when a partner's customer hits issues, joint resolution.

Partner portal

Centralized resource: enablement content, deal registration, commission tracking, MDF requests, joint campaign assets.

A partner portal that no one logs into is a vanity project. Track usage; iterate.

Operational mechanics

Pipeline tracking

• Separate channel pipeline from direct.
• Channel pipeline includes: registered deals, partner-sourced (no registration), partner-influenced.
• Typical channel-vs-direct ratios at maturity: 30-60% from channel for companies that have committed to it.

Lead routing

• Inbound leads: route to direct sales unless registered to a partner.
• Partner-registered leads: hands-off from direct sales.
• Channel-conflict resolution: escalation to head of sales (direct) and head of partnerships, deciding-criteria documented.

Commission tracking

• Partners need transparency: when did the deal close, what did it close for, when does commission pay?
• Standard cadence: monthly reconciliation, quarterly payout.
• Payment: ACH or wire; not checks.

Joint customer success

• Top deals: joint kick-off, joint QBRs, joint renewal motions.
• Common partner role: services-led implementation while you maintain product / platform support.

The most common failure modes

1. Channel conflict

Direct-sales reps and channel-partners both pursuing the same accounts. Symptoms: partner complaints, direct-rep complaints, lost deals. Fix:

• Clear named-account / territory agreements.
• Strict deal-registration enforcement.
• Compensation alignment (often direct rep gets partial credit on partner-led deals).
• Public escalation path that gets used.

2. No actual revenue

Program exists, partners exist, no deals closed. Diagnosis:

• Product not ready for partners (too custom, too immature).
• Partners not committed (no rep ownership; senior exec said yes but org didn't).
• ICP misalignment (partners' customers don't match your ICP).
• Margin too low (partners chasing higher-margin alternatives).

3. Partners with no committed reps

Senior exec at partner says "yes, we love this," but no rep is actually pitching it. Symptom: lots of activity, no outcomes. Fix: ban senior-exec-only relationships; require named, committed sales reps.

4. Unclear value exchange

"We give you 20% margin." But for what? Lead generation? Sales? Implementation? Customer success? If the value exchange is fuzzy, partner economics break down. Fix: explicit definitions of partner role and your role.

5. Marketplace listing without GTM

Listed on AWS Marketplace / Salesforce AppExchange / HubSpot App Marketplace but not actively co-selling. Marketplace is a closing-mechanism, not a discovery-mechanism for most B2B. Fix: pair listing with co-sell motion.

6. Hiring the wrong VP of Partnerships

Common pattern: hire someone with deep "partnership relationships" who turns out to be a glorified BDR. The right VP of Partnerships:

• Has experience building programs (not just running existing programs).
• Has direct sales background or strong sales-organization understanding.
• Can set up operational infrastructure (deal-reg, commission, partner portal).
• Will say no to partnerships that aren't ready / aren't worth it.

Lifecycle

Phase 1: Pilot (months 0-12)

• 5-10 partner pilots.
• Heavy hand-holding.
• Small revenue contribution (often <5%).
• Goal: prove the motion, learn what works.

Phase 2: Stabilize (months 12-24)

• Formal program launch.
• 20-50 active partners.
• Revenue contribution: 10-20%.
• Operational infrastructure: portal, deal-reg, training.

Phase 3: Scale (months 24-48)

• 50-200 active partners.
• Revenue contribution: 20-40%.
• Tiered program with named senior partners.
• International expansion via partners.

Phase 4: Maturity (48+)

• 200+ partners across tiers.
• Revenue contribution: 30-60%.
• Strategic alliances with major platform vendors.
• Partner-influenced revenue tracking.

Most companies stall at Phase 1 because the pre-conditions weren't met. Don't move to Phase 2 without a working pilot.

Anti-patterns

• "We need partnerships now." Almost always premature.
• Partner-program-as-press-release. Listing 50 logos without operational infrastructure.
• Same comp for partner-sourced as direct. Direct reps will undercut partners; chaos.
• Closed-network partnerships. "Only friends-of-CEO can partner with us." Limits scale.
• No partner segmentation. Treating a 1-rep agency the same as a 1000-rep SI.
• Marketplace as the strategy. Listing on AWS without owning the co-sell motion.
• No partnership exit criteria. Partners who haven't closed a deal in 24 months still draining program resources.
• VP of Partnerships reporting to CEO with no sales coordination. Channel team becomes a silo; conflict with direct sales is constant.

Workflow

For a leader evaluating or starting a partnerships program:

1. Stage check: Are pre-conditions met? Product, sales, organization, margin?
2. Archetype choice: Which partnership archetype is most relevant? Don't try all four at once.
3. Pilot design: Pick 5-10 candidate partners. Sign light pilot agreements. Run for 90-180 days.
4. Evaluation: What worked? Did revenue / qualified leads materialize? What partner profile worked?
5. Formalize program: tiers, comp, deal-reg, portal, training.
6. Hire VP of Partnerships: if not already done.
7. Recruit aggressively: target 25-50 partners in year 1 of formal program.
8. Measure: revenue contribution, partner activation rate, partner satisfaction.
9. Scale or sunset: if revenue contribution isn't 10%+ by month 24, the program likely needs major redesign.

Integration with other coaches

• enterprise-sales-coach: strategic alliances are heavily enterprise-deal-driven.
• icp-redefinition-coach: partnership ICP must align with your direct-sales ICP.
• b2b-saas-pricing-coach: margin / commission structures depend on overall pricing architecture.
• expansion-revenue-coach: partners often play a role in customer expansion via services.
• saas-acquisition-prep-coach: mature partner ecosystem is a value-multiple in M&A.

A real partnerships program is a 2-3 year investment before significant revenue. Plan accordingly; don't pretend the timeline is shorter.