Automation · Revenue operations

How to build partner account mapping

Q: What is partner account mapping?

Finding the accounts you and a partner have in common, what each of you has there, and using that to decide where to work together. Built properly, the overlaps show on the CRM account where reps already look.

A rep spends a quarter breaking into an account where a partner has worked for three years, and finds out when the partner registers the deal. How to put account overlaps where reps work, the prompts that build it, and what to share with partners without giving away the pipeline.

Built with Tray Headless

System Crossbeam
Step Match to the account
Step Which overlaps matter
Step Write to the account
System Salesforce

Also Slack

Overlaps from the account mapping tool are written to the CRM account, and the rep and the partner manager hear about the ones that matter.

The short answer

What is partner account mapping?

Partner account mapping has four parts: overlaps between your accounts and each partner's, read from the account mapping tool and matched to the right CRM account; a rule for which overlaps matter (your open opportunity and their customer, for example, matters more than two prospect lists overlapping); the partner and the relationship written onto the account, where reps already look; and a rule for what you share back with partners, decided before the first share. Most teams stop at the mapping tool. The overlaps sit in a separate app the reps never open, so the partner who could introduce them is found after the deal.

Stage 3 of 6: Map shared accounts. Part of Partner integrations, end to end : every stage, the systems it runs on and the guide that builds it.

What matters here

Put overlaps on the CRM account. Reps won't open another app before a call.
Rank by what each side has: your opportunity and their customer is the overlap worth a conversation.
Tell the rep and the partner manager at the moment it matters, when an opportunity opens on an overlapping account.
Decide what you share before you share it. Overlaps, not pipeline values, unless both sides agree.
Track introductions made from overlaps. It is the number that shows the mapping is used.

Who this is for

You run partner operations or revenue operations. Account overlaps live in a mapping tool that partner managers use, and reps find out about a partner's relationship after the fact.

How it works in practice

From two companies' account lists overlapping to a rep asking for an introduction.

1

Overlaps are found in the mapping tool

Your accounts against each partner's, with what each side has: customer, open opportunity, prospect.
2

Each is matched to the CRM account

By domain, so the overlap lands on the account the rep owns.
3

Each is ranked

Your open opportunity and their customer first, then your customer and their opportunity, then the rest.
4

The account shows the partner

Which partner, what they have there, and who the partner manager is.
5

The rep hears when it matters

When an opportunity opens on an account where a partner has a customer, in Slack, with how to ask for an introduction.
6

Introductions are tracked

Asked, made, and the opportunity they touched.

What account mapping is made of

Four parts. The fourth is the one partners will ask about.

Overlaps on the account

Read from the mapping tool, matched by domain, and written to the CRM account rather than left in another app.

A ranking

Which combinations of your status and theirs are worth a conversation, held in a table partner operations owns.

A moment to tell the rep

An opportunity opening on a ranked overlap, so the alert arrives when the rep is about to need it.

A sharing rule

What you show partners and what you don't, agreed per partner and applied the same way every time.

The Tray Headless prompts

Paste these into Claude Code or Codex with the Tray Headless plugin installed. Each stage runs on its own. The systems named in them are the worked example rather than a requirement, and every prompt says so.

Once per project, run /tray-workflows:set-workspace to pick the workspace these build in. Point it at a sandbox first.

See what the overlaps hold

Before writing anything, see what each side shares.

Headless skills build-workflow

Use build-workflow. The systems in play are Crossbeam, Salesforce,
HubSpot and Slack, or whatever we run in those seats. Before you plan
anything, tell me which are already authenticated.

Show me our current overlaps with three partners: the account, what
we have there (customer, open opportunity, prospect), what they have
there, and what fields each partner shares with us.

Match overlaps to CRM accounts and rank them

Your opportunity and their customer is the overlap worth a call.

Headless skills build-workflow tray-gotchas

Use build-workflow and tray-gotchas. Match each overlap to a Salesforce
account by domain. Where one domain matches several accounts, use the
parent account. Where none match, skip it.

Rank each overlap from a table partner operations owns. Start with:

  Our open opportunity, their customer: high
  Our customer, their open opportunity: high, for the partner
  Both open opportunities: medium, and a conflict to watch
  Both prospects: low

Write to the account: each partner with an overlap, what they have,
the rank, and the partner manager. Update daily, and remove a partner
when the overlap ends.

Tell the rep when it matters

An alert that arrives when they need it gets read.

When an opportunity is created on an account with a high-ranked
overlap, tell the opportunity owner in Slack: which partner, what they
have there, and a button to ask the partner manager for an
introduction.

When the rep asks, tell the partner manager with the account and the
opportunity stage. Record the request, and whether an introduction
happened, on the opportunity.

Share back by rule, and report

Partners will ask what you share. Have the answer first.

Keep a sharing rule per partner: which overlaps we show them and
which fields. By default share the account and that it overlaps,
never our opportunity value or stage.

Once a week, report per partner: overlaps by rank, introductions
asked and made, and opportunities touched by an introduction, with
their value.

Introductions made is the number that shows reps use the mapping. Overlap counts alone don't.

What it connects to

The overlaps come from the mapping tool. The rep works in the CRM.

Crossbeam

Read overlaps between your accounts and each partner's, with what each side has there.

Reads

Salesforce

Write each partner overlap to the account, and record introductions asked and made on the opportunity.

Reads and writes

HubSpot

Where a partner team works in HubSpot, write the same overlaps to the company record there.

Writes

Slack

Tell the rep about a ranked overlap when an opportunity opens, and pass introduction requests to the partner manager.

Writes

Same build, other stacks

The design does not change if you run something else in one of these seats. The same prompts build it against Microsoft Dynamics 365, Microsoft Teams, Marketo, Google Chat or Braze.

Connections in this build

Field mapping, templates and common problems for each pairing: Crossbeam + Salesforce, Crossbeam + HubSpot, HubSpot + Salesforce and Crossbeam + Slack.

Named systems are the ones most teams run, not the only ones that work. Each is an authentication in your Tray workspace, referenced by name, so the workflow never holds a credential. Where we have a connector page, the name links to it.

Running it in production

This decides what you tell partners about your own accounts. Treat it that way.

It runs daily, and on every new opportunity

The account is current each morning, and the rep hears at the moment an overlap becomes useful.

Sharing follows a rule

What each partner sees is set per partner and applied the same way, never decided by whoever is asked.

Credentials stay in the workspace

The mapping tool and the CRM are separate authentications, scoped to what each step needs.

Partner ops own the ranking

The rank table and sharing rules open in Tray Build, so a change in policy is an edit.

Questions people ask

Which overlaps matter most?

Your open opportunity at an account where the partner has a customer. The partner can introduce you, and often knows how the customer buys.

What should we share with partners?

Decide per partner before the first share. A sensible default is the account and that it overlaps, without your opportunity value or stage.

How does this relate to deal registration?

Mapping shows where you could work together. Registration settles who gets credit for a deal. An overlap with both sides holding open opportunities is a registration conflict worth watching.

How do you know reps use it?

Count introductions asked and made from overlaps, and the opportunities they touched. Overlap counts alone show the mapping exists, not that it is used.

Related guides

Revenue operations