Ecosystem Leads
Your warmest co-sell targets: paste a partner's book, we cross it against your accounts and rank the overlap by ecosystem fit.
Included with partnercron . A seat without it sees an upsell here instead of the page.
Overview
Ecosystem Leads answers the partner manager's core question: which of my accounts does this partner already work, and which of those are worth a co-sell push. It crosses a partner's book of accounts against your own, finds the overlap, scores each shared account 0 to 100 for ecosystem fit, and ranks the board hottest first. This is the partnercron equivalent of the account-mapping view a Crossbeam or Reveal gives you, running on the same scoring substrate as the rest of the platform.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
Why you supply the partner list
We hold no partner books ourselves, so the board takes one input: a partner list. Paste one partner per line, the partner name followed by the account domains they work, comma-separated, with an optional strength in parentheses to weight a strategic partner more heavily. That list can come from a CSV import or a Crossbeam / Reveal export. Your own accounts come from your connected CRM and stored records; the overlap is a deterministic set intersection on domains, so the same inputs always produce the same board.
How the ecosystem-fit score works
The score is deterministic and defensible. It rises with the number of partners already working an account, the strength of the strongest overlapping partner, and any community engagement tied to the account. An account with no partner overlap scores zero and sinks, so the top of the board is warm co-sell targets a partner can open the door on, not a cold list. The drivers behind each number are returned by the API, so the ranking is never a black box.
What the matrix shows
Each row is one of your accounts that a partner already works: the account with its segment and open pipeline (read from your stored records, a dash when not present), the account domain, the partners present as chips, and the ecosystem-fit score with its band. Three tiles sit above the matrix: accounts scored, how many have partner overlap, and how many landed in the hot band. Everything ranks by the same deterministic fit score the API returns to any surface.
What the board does not do
Ecosystem Leads ranks overlap; it does not send anything. It is a read surface. If no accounts overlap the partner list, the board is empty rather than filled with placeholders, check that the domains match how your accounts are stored and that your CRM is connected. Turning a ranked lead into a co-sell note stays with the partnercron drafting skills, which narrate the "why" on a ranked lead and keep a kill switch on every AI surface.
Community warm leads
Below the matrix, the community warm-leads strip lists the people in your community who sit at an account a partner already works. It reads the community events you saved through the community digest (Partners, Community) and keeps each member whose event carries an account domain on one of your saved partner lists. Each row shows the member, their account domain, the partners present, how the digest classified them (advocate, expansion, at risk, active or new) with their signal count, and their engagement score, most engaged first. The strip loads from your saved lists when you open the page and refreshes when you run a new list.
A member is matched on the account domain only. An event with an account name but no domain, or no account at all, is never guessed onto a partner. When the strip is empty it says why: no community events stored yet, no partner list saved yet, members with no account domain, or simply no overlap.
What is not shown
The design mockup also sketched a partner-attribution split (partner-sourced versus partner-influenced pipeline). It is omitted because we do not track partner-sourced pipeline, and rendering it would mean inventing the numbers.