Partner Ecosystem

Partner Ecosystem Mapping

Map the full partner and channel landscape of one business area. No single canonical framework owns this discipline.

The map covers:

• Which partner types touch your customers.
• Who overlaps with your market.
• Where the coverage gaps and conflict zones sit.
• Which ecosystem segments deserve investment attention.

Built from:

• A role taxonomy: Jay McBain's trifurcation of the channel.
• An overlap mechanic: account mapping, popularized by Ecosystem-Led Growth.
• A mapping technique: Verna Allee's Value Network Analysis, Ron Adner's value blueprint.
• A prioritization pass: weighted scorecard plus 2×2.

The output is a decision artifact, never a partner program:

• Ecosystem map.
• Coverage/whitespace view.
• Prioritization view.
• A short ecosystem strategy memo.

Program design, tier criteria, conflict rules of engagement, and per-partner economics hand off to sibling skills instead (see Reference).

Interview

Ask before mapping anything. One question per message; offer multiple-choice answers when possible. Skip a question only when the user already gave the answer.

• B2B, B2C, or hybrid? What does the company sell, to whom (ICP), at what price band, through which motion (self-serve or sales-led)?
• Which single business area or product line should the map cover? (Never the whole company at once - offer the 2-3 plausible scopes as choices.)
• What is the goal of the map: choose a channel strategy, find coverage gaps, diagnose conflict, size the ecosystem for an executive ask, or landscape before building a program?
• Current partner mix: which partner types exist today, roughly how many per type, and how many are actually active?
• What data exists: CRM closed-won history, sourced/influenced attribution fields, account-overlap data with any partner, customer tech-stack or purchase-channel information?
• Are you the platform others build on, or a participant in someone else's ecosystem? (Both can be true in different areas.)
• Constraints: who sponsors this, who must approve it, and how much capacity exists to act on it?
• By what date must the map land, and what decision is waiting on it? (A date inside a week promotes the closed-won review and the interview-based overlap proxy; a quarter of runway makes permissioned account mapping and a convened workshop affordable.)
• One-off win or compounding asset? (A single exec ask stops at a static matrix and a memo; a compounding mandate justifies the CRM field definitions, the overlap infrastructure, and the recurring review cadence that keep the map alive after the meeting.)
• What is the effort ceiling - your own hours, whose calendars you can command, and how much political capital you can spend convening stakeholders or asking a partner for their account list? (A solo ceiling rules out both the participative workshop and partner data sharing; both need other people to say yes.)

Carry these three answers into every ranking below. They are the only inputs that can reorder the defaults for this user.

Workflow

Hold one discipline across every step below, wherever a real choice exists:

• Which business area to scope.
• Which overlap proxy to accept.
• How to weight a scorecard.
• Which visualization to build.
• Which categories make the cut.

Put 2-3 candidate approaches to the user with their trade-offs and your recommendation, then wait. Never present a single option as if it were the only one. Never let an assumption harden into the map unstated.

Every ordering in the steps below is a default, not a law. It ranks by value returned per unit of effort, never the same ordering as cheapest-first, and it shifts with context and with who executes it. Re-rank it against what you already know about this user before recommending anything.

Signals that move the reordering:

• A CRM that already carries structured partner-influence fields moves the internal data pull further ahead of everything else.
• A designer on hand moves the network diagram up.
• An audience that reads spreadsheets rather than diagrams moves it back down.
• An existing partner already sharing account data makes account mapping the cheap option rather than the expensive one.

Say which of their answers moved which option, so the reordering is auditable rather than a preference you asserted.

1. Run the Interview; confirm the scope is one business area with a stated goal before touching data.
2. Inventory every third party that touches customers of that area, working the evidence sources in this order. Never build the inventory from inbound partnership requests or the team's personal network; teams that do sign partners with no shared accounts, no shared ICP, and no path to joint pipeline.

• Internal data pull - CRM records, closed-won notes, support tickets, integration and product usage. An hour or two on data you already own, and every name it returns is evidence that the player touched a real customer. Start here always.
• Customer interviews - a week of scheduling and conversations. The only source that finds the advisors, communities, and unlogged influencers nothing in your systems ever recorded, which is exactly the band a transaction-only view misses.
• Public sweep - competitor partner directories, marketplace listings, review-site category neighbors, conference sponsor lists. Near-zero effort where you can browse the web, and it returns breadth fast, but nothing it finds is evidence that any of those players touch _your_ customers. Treat its output as candidates to verify, never as inventory.
• Value Network Analysis participative workshop - a week of calendars plus the political capital to convene stakeholders. It buys the intangible exchanges (trust, market insight, brand association) and, more importantly, shared ownership of the map by people outside partnerships. See references/discovery-workshops.md.

• effort: workshop > customer interviews > internal data pull == public sweep
• value: customer interviews > workshop > internal data pull > public sweep
• efficiency: internal data pull > customer interviews > public sweep > workshop

The internal data pull and the public sweep tie on effort: each is an hour or two of one person working alone, with no permission to obtain and no calendar to negotiate. They are nowhere near equal on value: the pull wins that axis because only its output is evidence about _your_ customers.

Where you cannot browse the web, the sweep is not cheap but impossible: delete it and say so, rather than listing a source nobody can reach.

• Default: the internal data pull alone.
• Escalate to customer interviews when closed-won notes name third parties you cannot classify, or the influence band comes back empty. It usually does; that is a gap in your logging, not in the ecosystem.
• What this order starves: the workshop. It is second on value, first on effort, last on efficiency, so a ratio never once convenes it, and it is the only source that makes people outside partnerships own the map instead of receive it.
• Promote the workshop when the map has to be owned by sales, product, or an exec sponsor rather than merely read by them; the map is drafted there, not after it has been scored.
• Delete the workshop when the Interview gave a solo effort ceiling. Name it as deleted: it needs other people to say yes, and one carried at the bottom of the list returns as a week of calendars nobody agreed to.

1. Classify each player on two axes:

• Role in the customer journey: influence, transact, or integrate-and-deliver (McBain's trifurcation, Canalys).
• Engagement depth: from listing through embedded.

Include competitors. Coopetition and the partners you share with them are signal, not noise. See references/partner-type-taxonomy.md.