Partner Ecosystem Expansion

Partner Ecosystem Expansion

Plan which categories of partner to add next and in what order, as a staged roadmap with gates.

Be honest about the evidence before anything else:

• No peer-reviewed optimal partner-category sequence exists.
• Most published "frameworks" for this decision are borrowed strategy grids force-fit onto channels.
• Nearly every quoted benchmark comes from a vendor or consultant that profits when the number looks good.

What the evidence genuinely supports:

• Adner's minimum viable ecosystem (MVE) + staged expansion + value blueprint (_The Wide Lens_; _Winning the Right Game_) - the one framework designed for exactly this problem: prove the smallest partner configuration that evidences joint value, then add categories in a deliberate order, gated on evidence.
• The alliance-portfolio-diversity inverted-U (Jiang, Tao & Santoro 2010, _SMJ_; Lee et al. 2017 meta-analysis) - the field's only independent evidence: partner-type diversity helps firm performance up to a point, then coordination and governance costs dominate. It argues for restraint and sequencing; it prescribes no order.
• Operational coverage/capacity math and stage-gate pilots - unbranded, but the actual working method: gate every category on capacity, not enthusiasm.

McBain/Canalys' channel trifurcation supplies the category taxonomy (never a sequence), and Moore's whole product / bowling alley partially transfers. Name and reject the force-fits when a user brings one: Ansoff applied to channels, McKinsey three horizons, BCG growth-share, Iansiti & Levien for category selection. See references/sequencing-frameworks.md.

This skill sequences categories, never named companies. Related decisions live in sibling skills:

• Ranking named candidates: mbfinotti/partnerships-skills@alliance-prioritization
• Mapping the current ecosystem: mbfinotti/partnerships-skills@partner-ecosystem
• Program structure (tiers, benefits, requirements): mbfinotti/partnerships-skills@partner-channel-program

Interview

Ask before sequencing anything. One question per message; offer multiple-choice options; skip whatever the user already answered.

• B2B, B2C, or hybrid? What do you sell, to whom, at what price band, through which motion?
• Current ecosystem shape: which partner categories are live today, how many partners per category, and what share are actually active? (An ecosystem map from the mapping sibling is the ideal input.)
• Which existing category is proven - repeatable joint wins, not just signings? Any category still a half-built stub?
• Product readiness: API maturity and multi-tenancy, certification/training content, deal registration, margin structure, support model, contracting - which exist today, which are still on the roadmap?
• Internal capacity: partner managers and their current load, enablement content bandwidth, tooling, program budget?
• How does your buyer actually buy - self-serve, sales-led, through implementers, through retail or marketplaces?
• Goal of the expansion: coverage of a segment/geography/journey stage, a whole-product gap, new-logo pipeline, retention/expansion, margin capture?
• Geography and segment coverage today vs target?
• Budget and sign-off: who funds this, who approves, and is there a planning cycle it must land in?
• Time horizon for the roadmap - 12, 24, or 36 months?

Three answers re-rank the category order before any sequencing starts - ask them here, never beside the ranking:

• By what date must the first result land? A hard near-term date promotes the fast-acting categories (referral/affiliate, creator, agency) and deletes the standing-job ones from stage 1 - a category whose first revenue arrives after the date cannot be stage 1 whatever its ratio.
• A one-off win, or a compounding asset? Compounding promotes tech/ISV and the categories it makes cheap later (marketplace, MSP); one-off promotes referral/affiliate, creator and co-branding, and demotes everything that only pays back across years.
• What is the effort ceiling - hours, headcount, political capital, reversibility? A ceiling below one standing job deletes MSP, SI/GSI, reseller, retail and distributor outright; a ceiling that includes an existing services arm promotes SI/GSI to the front.

Workflow

Wherever a real choice exists - candidate pool, sequence order, gate thresholds, where the capacity line falls - present 2-3 candidate approaches with trade-offs and your recommendation, then wait. Never let an assumption harden into the roadmap unstated.

1. Run the Interview. Confirm the input is a current-ecosystem picture (a map, or an honest mix description). No picture at all → route to the ecosystem-mapping sibling first.
2. State the evidence posture up front: the roadmap is a reasoned, gated bet, not a validated formula - and every benchmark used will carry a provenance flag.
3. Define the MVE: the smallest partner configuration that creates enough evidence of value to attract the next category. If the current motion is not yet an MVE with repeatable joint wins, the honest roadmap's stage 1 is finishing it, not adding.
4. Run the ego-system check: draft the value blueprint from the customer's position, not yours. A sequence that presumes your own centrality (Adner's ego-system trap) recruits categories that have no reason to show up.
5. Build the candidate pool from the trifurcation buckets - influence, transact, retain-and-deliver - plus the B2C vocabulary where relevant, and from the whole-product gaps each category would close. See references/partner-category-economics.md.
6. Fix the capacity numbers before sequencing: partner-manager-to-partner ratios, enablement bandwidth, budget. These cap the roadmap; a sequence without them is a wish list.
7. Score each candidate category's readiness and economics: commercial model, relative time-to-first-revenue, effort to stand up, standing load, compliance exposure, prerequisites met vs missing. See references/readiness-and-capacity-gates.md.
8. Rank the pool by efficiency: value returned per unit of effort, never cheapest-first. Use the ordering and the per-axis lines in references/partner-category-economics.md, then re-rank it against this user: their three interview answers above, an existing services arm, a product needing no implementation, a partner team of one. Delete every category their constraints rule out, with the reason, instead of parking it at the bottom; it lands in Not now with a re-entry trigger. Say the ordering out loud, and say what it starves. Draft 2-3 candidate sequences from the re-ranked pool with trade-offs and your recommendation.
9. Argue the strongest case against your own recommended sequence before presenting it: the inverted-U cost of another category, the conflict it creates, the capacity it steals from the proven motion.
10. Attach a stage gate to every stage: pilot cohort shape, a partner-market-fit threshold (repeatable joint wins), and explicit kill criteria. Gates trigger on evidence, never on a calendar date alone.
11. Pre-check channel conflict for any category that overlaps an existing route (direct, or another partner category). Detect and size it here; writing the rules of engagement belongs to mbfinotti/partnerships-skills@partner-channel-conflict - but a launch scheduled before rules exist is a roadmap defect.
12. Cost each stage as a capital request: total loaded cost (headcount, enablement build, incentives, tooling, program spend), never headcount alone, with the funding mechanism named.
13. Run the brainstorming discipline below; present the roadmap section by section, validating each with the user before drafting the next. Require explicit approval of the assembled roadmap before finalizing.