Every cell is a real computed overlap between two connected CRMs, not a placeholder.
What an overlap actually is
A partner overlap is the set of accounts that exist in both companies' CRMs: customers, prospects, and open opportunities on both sides. Co-Signal computes it directly from each side's connected CRM data, never from a shared spreadsheet somebody has to keep updating by hand.
Matching, then review
Co-Signal proposes candidate account matches from name and domain similarity, then a person on each side confirms or rejects them. A confirmed match becomes part of the overlap; a rejected one never resurfaces for that pair.
Three levels, set per partner
Every company chooses its own visibility level for every partnership, independently. A partner never sees more than the level you set for them.
A single number: how many accounts overlap. No names, no detail. Every new partnership starts here.
Which specific accounts overlap, by name and domain, and nothing beyond the fact that they exist on both sides.
Full account detail for the overlap, plus any additional field group the owning side has explicitly opted in to share.
Partner A
Owns the relationship
Partner B
Requests a warm intro
From overlap to co-sell
Once an overlap is visible, either side can request a warm intro on a greenfield account, one only a single partner has a relationship with, or align on an account both sides are already working. A request names the account and the ask, and routes to the right person.
Every number on this page is a real computed overlap. Co-Signal never shows two companies a guess.
How the mapping engine actually works
A recompute runs per population pair, not per account: every confirmed match feeds a fresh overlap count, and every read of that count runs through the same server-side authorization layer that enforces each partner's sharing rule, live, whether the surface asking is the web app, Slack, the AI agent, or the MCP server.
One authorization layer. Every surface calls through it.