Every shared account, computed.

1. 01

   Connect your CRM

   Each company connects its own Salesforce or HubSpot, or imports a CSV. Accounts stay in that company's workspace.

2. 02

   Match on both sides

   Co-Signal proposes matches from company names and domains. A person on each side confirms them, and a rejected match never comes back for that pair.

3. 03

   Share at your level

   Each side picks what the other can see, per partnership. The overlap is computed from what both sides allow, and nothing more.

• The overlap matrix

  Every population on your side laid against every population on your partner's. Each cell is a live count, and counts below 5 are never shown as a number.

  app.co-signal.com/overlaps/larkfield-dynamics

  Overlaps with Larkfield DynamicsLast computed today, 09:12

  Export

  Larkfield DynamicsReedmark

  CustomersoverlappingOpen oppsall accountsProspectscounts onlyCustomers18$1.4M pipeline7$610K pipelineFewer than 5Open opps9$2.1M pipeline11$880K pipeline8$540K pipelineProspects14$720K pipeline6$310K pipeline21$1.1M pipeline

• Account mapping

  Customers, prospects and open opportunities on both sides, with the owner of each relationship, so you know who to talk to.

  app.co-signal.com/accounts

  AccountsPartner relationships from Larkfield Dynamics and Reedmark

  Account	Partner relationship	Signal
  Meridian Loopmeridianloop.com	Larkfield Dynamics customer	Overlap
  Northgate Analyticsnorthgateanalytics.com	Reedmark open opportunity
  Briarcliff Systemsbriarcliffsystems.com	Greenfield

• Matches you confirm

  Candidate matches arrive for review. Confirm or reject each one; only confirmed matches count toward an overlap.

  app.co-signal.com/partnerships/larkfield-dynamics/matches

  Match reviewProposed matches with Larkfield Dynamics, decided by a person on your side

  Your record	Larkfield record	Why proposed	Decision
  Meridian Loopmeridianloop.com	Meridian Loopmeridianloop.com	Same domain	Confirmed
  Northgate Analyticsnorthgateanalytics.com	Northgate Analyticsnorthgateanalytics.net	Same name, different domain	Rejected

• From overlap to warm intro

  Send a co-sell request that names the account and the ask. It routes to the person on the partner side who owns that relationship.

  app.co-signal.com/requests

  Co-sell requestTo Larkfield Dynamics, routed by role

  New request

  Meridian Loopmeridianloop.comSent

  Ask

  Introduce us to the buying team

  Partner

  Larkfield Dynamics

  Routed to

  The Larkfield Dynamics account owner

• The AI co-sell agent

  Ask about your partnerships in plain language. Answers come only from the overlap you're allowed to see.

  AgentOnly what partners share with you

  Which shared accounts should we raise with our partner this quarter?

  1. Checked what Larkfield Dynamics shares with you
  2. Matched 31 shared accounts
  3. Ranked them by open pipeline and relationship

  Two stand out. Meridian Loop is a customer of your partner and has an open opportunity with you, so ask them for an introduction to the buying team. Northgate Analytics is a customer on both sides, which makes it a good place for a joint expansion conversation. Briarcliff Systems overlaps too, but nothing is open there yet, so keep it on your watch list.

  Meridian Loopmeridianloop.comYouOpen opportunityPartnerCustomer

  Northgate Analyticsnorthgateanalytics.comYouCustomerPartnerCustomer

  Draft intro requestWatch Briarcliff Systems

  Ask about accounts, partners or pipeline

  Sample question and answer, on sample data.

• MCP server and API

  Bring accounts and overlaps into your own tools and AI assistants, with the same sharing rules applied on every call.

  Read the developer guide

  Sample API call

  GET /api/v1/accounts?limit=2
  
  {
    "data": [
      { "name": "Meridian Loop", "domain": "meridianloop.com" },
      { "name": "Northgate Analytics", "domain": "northgateanalytics.com" }
    ],
    "page": { "hasMore": true }
  }

Sample data. Every name is fictional.