Build a partner account map for co-selling
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha and Gmail connector output, but were not pulled from a live session. Run the prompt with your own account lists to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A partner account map for co-selling identifies which target accounts appear on both companies’ lists, which side has the stronger relationship at each overlapping account, and where a joint approach is the fastest path to a conversation. This Claude prompt compares the two account lists, validates every overlapping account via Lusha, checks Gmail for existing relationship history, and returns a prioritized co-sell list with a specific classification per account — so both sides know who opens the door before the first joint outreach goes out.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I'm setting up a co-selling motion with a partner. Before we start, I want to map which of our target accounts overlap with their target accounts — so we can identify where to co-sell, where I have relationships they can leverage, and where they have relationships I can benefit from.
My partner mapping:
- Partner company: [PARTNER NAME]
- My target account list: [PASTE COMPANY NAMES OR DOMAINS — one per line]
- Partner's target account list: [PASTE COMPANY NAMES OR DOMAINS — or "ask partner to share"]
- What I sell: [PRODUCT / SOLUTION]
- What the partner sells: [PARTNER PRODUCT / SOLUTION]
- Target function at overlapping accounts: [e.g. "Sales, RevOps, IT"]
- Slack channel: [CHANNEL NAME OR "skip"]
</context>
<task>
1. Compare the two account lists and identify overlapping accounts:
- Which companies appear on both lists?
- Which appear on my list only?
- Which appear on the partner's list only?
2. For every overlapping account, use Lusha to:
- Validate the company — current headcount, industry, signal in the last 30 days
- Find the most senior verified contact in the target function
- Check Gmail for active deal or prior contact at this account
3. Classify each overlapping account:
- WE HAVE A RELATIONSHIP: I have prior contact or active deal — I introduce the partner
- PARTNER HAS A RELATIONSHIP: partner is on the account, I have no prior contact —
partner introduces me
- BOTH ACTIVE: both have relationships — coordinate before reaching out
- NEITHER ACTIVE: overlapping ICP, no prior relationship — joint outreach opportunity
4. For my-list-only accounts:
- Flag the top 5 where the partner's product would be complementary
- These are accounts where I can offer a warm intro to the partner
5. Build the partner account map:
## Overlap summary
## Priority co-sell accounts (top 10, sorted by signal + ACV potential)
## My accounts — where partner can help
## Partner's accounts — where I can add value
## Joint opportunity accounts
6. Post overlap summary to Slack if channel specified.
</task>
<constraints>
- BOTH ACTIVE classification requires coordination before any outreach — flag prominently.
- Verified contacts only from Lusha.
- Priority co-sell list limited to top 10 — quality over quantity.
- Partner account list may be manually provided — don't assume Lusha has it.
</constraints>What you'll get back
The situation: A channel sales manager is setting up a co-selling motion with a technology integration partner. Both companies sell into RevOps and Sales Operations at mid-market SaaS.
Overlap summary
My list: 12 accounts · Partner’s list: 10 accounts · Overlapping: 5 accounts
We have a relationship: 2 · Partner has a relationship: 1 · Both active: 1 · Neither active: 1
Priority co-sell accounts
1. Dunmore Analytics · 580 employees · Signal: Series B 18 days ago
Classification: WE HAVE A RELATIONSHIP Our contact: T.K., VP of Sales ✓ — active pipeline, Proposal stage Partner’s contact: none confirmed
Action: We introduce the partner to T.K. The Series B timing makes both products relevant — the conversation is natural. Coordinate with partner on sequencing before the next call.
2. Crestline Software · 340 employees · Signal: Hiring surge +22%
Classification: BOTH ACTIVE — coordinate before outreach
Our contact: R.V., VP RevOps ✓ — active deal, Discovery stage Partner’s contact: confirmed via partner
⚠ Both sides have an active thread at Crestline. Do not reach out independently. Schedule a co-sell sync with the partner this week to agree on a joint approach before either side sends another email.
3. Ashford Platforms · 420 employees · No signal
Classification: PARTNER HAS A RELATIONSHIP Our contact: no prior contact confirmed via Gmail Partner’s contact: confirmed at Director level
Action: Partner introduces us to Ashford. Provide the partner with our value proposition for Sales Operations teams at Ashford’s size — let the partner make the intro.
4. Halcyon Data · 470 employees · No signal
Classification: NEITHER ACTIVE — joint outreach opportunity Most senior contact via Lusha: S.P., VP RevOps ✓
Action: Joint cold outreach. Lead with the combined integration story — “we work together and both products are relevant to your RevOps stack.”
5. Greenway Cloud · 510 employees · No signal
Classification: WE HAVE A RELATIONSHIP Our contact: J.A., SVP Sales ✓ — prior outreach, no active deal Action: We introduce the partner to J.A. Re-engage the thread with a reason to reconnect — the partnership and integration story is the angle.
My accounts where partner can help
Top 5 from my list where the partner’s product is complementary:
Briarway SaaS · Elmont Systems · Falcrest Tech · Meridian Analytics · Vantage Enablement
All five have our primary contact verified. Offer warm intros to the partner for each.
Joint opportunity accounts
Halcyon Data — neither side has a relationship. Signal: none. Approach jointly — combined integration message is the opening angle.
Illustrative example — fictional company names used. Run with your own account lists to see live results.
Why use Lusha in Claude
Lusha in Claude maps the overlap in minutes and adds the relationship intelligence that makes co-selling actually work. The BOTH ACTIVE flag at Crestline is the critical finding — both sides have an active thread, and without coordination, the next email from either side will confuse or irritate the prospect. The flag surfaces it before anyone sends anything. The partner-has-a-relationship classification at Ashford means the right move is to let the partner make the introduction rather than cold-approaching an account where the partner already has credibility. Without the Gmail check, both of these findings are invisible. With them, the co-sell motion starts from a shared understanding of who owns which relationship.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if the partner doesn't want to share the account list?
The mapping still works with your list only — Lusha validates each account and Gmail checks for prior contact. Without the partner’s list, every account defaults to WE HAVE A RELATIONSHIP (if Gmail shows prior contact) or JOINT OPPORTUNITY (if no prior contact). The partner provides the list to unlock the full four-way classification.
How do we handle the BOTH ACTIVE accounts?
Coordinate before the next outreach — agree which side leads on which account, what the combined message is, and who the primary contact will be going forward. BOTH ACTIVE without coordination is a relationship risk, not an asset.
Can I run this for multiple partners at once?
Run a separate prompt per partner. Account lists and relationship histories are partner-specific — combining into one run produces a classification mess. One prompt, one partner, one clean output.
How is this different from just sharing spreadsheets with the partner?
A shared spreadsheet shows which company names overlap. This prompt adds three things a spreadsheet doesn’t have: Lusha’s verified contact at each overlapping account, Gmail’s relationship history per account, and a specific classification that tells both sides who opens the door. The output is actionable rather than just informational.
Ready to build this?
Get started with Lusha and set up this play in minutes.
