If your partner overlap data sits in a spreadsheet nobody acts on, the Claude skill to use is the Crossbeam Co Sell Partner Finder. It takes your target account list, checks which partners already have a customer, an open deal or a champion at each account in Crossbeam, scores every match against Introw partner performance data, and drafts the intro or the deal registration for the best fit. You review and approve before anything goes out. The full SKILL.md is below, free to copy, along with install steps, prompts to try and an example of what you'll get back.
Introw's partner segmentation playbook cites benchmarks showing that partner attached revenue ranges from 24% of revenue in horizontal SaaS to 47% in cybersecurity and 58% in services led businesses. And Introw's channel conflict playbook points to CSO Insights research: companies with well managed partner ecosystems win 23% more often than those with poorly managed ones.
So the upside of co selling is real. The hard part is the matching. Your AE has 40 target accounts. Your partner team has a Crossbeam report with hundreds of overlaps. Somewhere in it is the reseller who has run IT at your biggest open deal for three years. Nobody spots it, because nobody has time to read the report line by line.
What if the right partner for each account just showed up next to the deal, with a reason and a drafted intro?
This guide covers what a good co selling motion looks like, how to pick the right partner for each account, the Claude skill that does the matching, the full SKILL.md you can copy, how to install and run it, and how to stay in control of what it does.
What co selling is, and why overlap data alone isn't enough
Co selling is when two or more companies work the same deal together. Usually that's a software vendor and a partner, like a reseller, an agency or one of the managed service providers already running IT for the buyer. The partner brings trust, context and technical expertise. You bring the product and your sales process. Together you offer the customer a more comprehensive solution than either of you could alone. If you want the full primer, our guide to what co selling is walks through the models.
Co selling models at a glance
Most co selling partnerships fall into one of three co selling models:
| Model | Who leads | When it fits |
|---|---|---|
| Partner assisted | Your sales rep leads, the partner adds intros and context | The partner knows the same customer but doesn't sell your product |
| Joint deal | Both sales teams work the account with a joint sales strategy | Larger enterprise customers that need a joint solution, like software plus services |
| Partner led | The partner owns the sale, your direct sales teams support | Partners with deep customer relationships and certified people on your product |
Benefits of co selling
The benefits of co selling show up in a few places at once:
- Shorter sales cycles: a trusted partner already inside the account skips weeks of discovery for your sales team.
- Bigger deals: bundling your product with partner services tends to lift average deal size.
- New markets: partners extend your market reach into regions and customer segments your direct sales team doesn't cover.
- Stronger customer relationships: buyers get greater value across the customer journey, from evaluation to customer success after the sale.
- Mutual benefits: partners earn margin and services revenue, you get revenue growth and a healthier sales pipeline.
Plenty of SaaS companies also co sell with hyperscalers through the AWS Partner Network or the Microsoft commercial marketplace, where a cloud marketplace listing helps buyers spend committed budget. This guide focuses on the other half of the partner ecosystem: resellers, agencies and technology partners who already know your target accounts.
Where account mapping fits
The modern version of co selling runs on data. Tools like Crossbeam let you compare your account list with your partners' lists and see where they overlap, a practice usually called account mapping. It's how you identify opportunities you'd never spot by asking around. That overlap is the backbone of ecosystem led growth: using what your partners already know about potential customers to win the deal faster.
Here's the catch. Overlap tells you who could help, not who should. Most of it dies in a spreadsheet, and when teams do act on raw overlap, a few things go wrong:
- The loudest overlap wins: a partner with 200 overlaps gets every intro, even when they've never closed a deal in your vertical.
- Stale data gets acted on: an overlap from a lapsed prospect six months ago gets treated like an active customer relationship.
- Conflicts get created: a partner gets pulled into an account another partner already registered, and now you have a channel conflict to clean up.
- Dormant partners get cold handoffs: the partner with the perfect overlap hasn't logged in for three months, and the intro lands on nobody.
Good co selling partnerships start with a better question than "who overlaps?" The question is "who overlaps, has proven they can win this kind of deal, and is ready to work it right now?"
A co selling strategy that picks the right partners for each account
Embracing co selling doesn't mean pulling every partner into every deal. Successful co selling requires picking the right partners for your key accounts, one account at a time. The best co selling strategy treats every target account as its own matching problem. Here's what to weigh, roughly in order of how much it should count.
| Signal | What to look for | Why it matters |
|---|---|---|
| Overlap type | Customer, then open opportunity, then champion, then lapsed | A partner whose customer is your target is far warmer than one whose old prospect is |
| Overlap recency | Activity in the last 90 days | Fresh overlaps reflect current relationships, old ones may not |
| Historical fit | Past wins in the same vertical, deal size and product | Proven experience beats a raw overlap count |
| Current engagement | Recent portal activity, deal registrations, replies | An engaged partner can act this week, a dormant one can't |
| Tier and certification | Eligible for this product and segment | Ineligible partners are a hard pass, no matter how strong the overlap |
| Conflict status | No existing registration or direct claim on the account | Your rules of engagement still apply |
A few principles help you use that table well, on top of your rules of engagement:
- Why beats overlap: a weaker overlap with strong fit, like a partner who closed five similar healthcare deals, often beats a strong overlap with no track record.
- Match the deal to the partner type: strategic enterprise deals go to top tier partners with a proven enterprise motion. Transactional deals go to volume partners. Mismatches burn margin and partner energy.
- Pick the motion, not just the partner: a warm intro, a joint deal and a full handoff each need different messages.
- Write down why: when your AE picks up the deal next week, they need to see why this partner was chosen, not just the partner's name.
How to measure co selling success
Track a handful of key performance indicators so you know whether your co selling efforts pay off:
- Partner sourced and influenced pipeline: how much of your sales pipeline has a partner attached.
- Win rate with a partner vs. without: the clearest test of whether your co sell motions work.
- Average deal size and sales cycles: co sold deals should be bigger and close faster than direct sales.
- Partner activity: intros made, joint calls held and deal registrations submitted per partner.
Share the numbers, plus a few success stories, with your partner teams and sales team. It keeps the co selling program visible and helps you spot potential partners worth recruiting.
Done by hand, the matching part of this co selling process is days of cross checking Crossbeam, your CRM and your tier rules for a 40 account list. Most partner programs don't have a dedicated person with that kind of time, so potential co selling opportunities slip through. That's the job the skill takes over.
The skill to use: Crossbeam Co Sell Partner Finder
The Crossbeam Co Sell Partner Finder is a vendor side skill from Introw's free Claude skill library. It connects two data sources inside Claude: overlap data from Crossbeam and partner performance data from Introw, read live through Introw's MCP server. It returns a ranked partner match for every target account, a reason for each match and a drafted next step.
| Detail | Answer |
|---|---|
| Built for | Alliance managers, channel RevOps, partner development managers and AE aligned channel managers |
| Use it when | You have a list of target accounts and want to know which partner to bring into each one |
| What it reads | Your target accounts, Crossbeam overlaps (type and recency), partner records, past wins, engagement and tier rules |
| What it writes | Comments on the deal with the matched partner and rationale, tasks for the AE or partner manager, and deal registrations, after you approve |
| What you get | A match table per account, drafted partner messages, registration payloads, conflict flags and an aggregate view of your best overlapping partners |
| Skill ID | vendor-crossbeam-cosell-finder |
It fires on prompts like "who already has the customer" or "best partner for this target list", and it needs both the Introw and Crossbeam connectors in Claude.
How the skill works, step by step
The skill runs seven steps. Knowing the logic helps you trust the matches.
Step 1: Pull the target account list
The skill starts with the accounts you want to win: open deals from your CRM, an ABM list, expansion candidates, or a list you paste into Claude. For each one it notes the segment, vertical, deal value and stage.
Step 2: Pull overlap data from Crossbeam
For each account, it checks Crossbeam for partners with a customer relationship, an open opportunity or an evaluation in flight. It records the type of overlap and how recent it is, because a current customer beats a lapsed prospect every time.
Step 3: Add Introw partner performance
Next, it adds what Introw knows about each partner: tier, region, vertical focus, similar past wins, recent engagement and tier eligibility.
Step 4: Score partner and account fit
Each match gets a fit score that combines overlap strength, overlap recency, historical fit, current engagement and tier eligibility. It also checks existing deal registrations so it never places a partner on an account that's already claimed.
Step 5: Pick the best partners per account
For each account, the skill picks one to three candidates and explains each in a single sentence. For example: "Partner A has a three year customer relationship at Globex, engaged this month, closed five similar healthcare deals, Gold tier and certified on the product."
Step 6: Draft the motion
Then it drafts the next step for the motion you picked. For a warm intro, it writes a partner facing message that names the account, explains why you're asking and spells out what's in it for them, like margin, MDF eligibility or deal protection. For a co sell deal, it pre fills a deal registration for your approval. For a full handoff, it drafts the AE to partner email with the prospect context.
Step 7: Capture and queue
Finally, it adds a comment to the deal with the matched partner and the reasoning, and creates a task for the AE or partner manager to make the intro by a target date. Registrations only go through automatically if you've turned that on and the conflict check is clean.
Get the skill: the full SKILL.md
Here's the complete skill file. Copy it as is, or adapt the scoring and motions to your own program.
---
name: vendor-crossbeam-cosell-finder
description: Use when a Channel Chief, RevOps, AE-aligned Channel Manager, or PDM wants to find the best partner(s) to bring into a target account list, by combining Crossbeam overlap data with Introw partner performance signals. Trigger phrases include "find partners that overlap with these accounts", "Crossbeam co-sell", "ELG partner match", "who already has the customer", "ecosystem-led match", "best partner for this target list", "warmest overlap on Account X".
---
# Crossbeam Co-Sell Partner Finder (Vendor)
**Audience**: Vendor, uses **claude.ai Introw** MCP + **claude.ai Crossbeam** MCP.
**Use case**: 02, Partner Segmentation (with strong cross-cut to 08 Deal Registration / 11 Coaching).
## When to use this skill
Use when a Channel Chief, RevOps, AE-aligned Channel Manager, or PDM wants to find the best partner(s) to bring into a target account list, by combining Crossbeam overlap data with Introw partner performance signals.
**Sample prompts that fire this skill:**
- "find partners that overlap with these accounts"
- "Crossbeam co-sell"
- "ELG partner match"
- "who already has the customer"
- "ecosystem-led match"
- "best partner for this target list"
- "warmest overlap on Account X"
## Why this matters
Ecosystem-Led Growth (ELG) only works when the ecosystem data is operationalized. Most channel teams have Crossbeam producing overlap data weekly, and most of that data dies in a spreadsheet because no one has time to translate "Partner X has a customer relationship with Account Y" into a concrete co-sell motion. This skill closes that gap: it cross-checks a target account list against partner overlap data, scores partner-account fit using Introw performance signals (engagement, prior similar wins, certifications), and drafts the partner intro request.
For partners involved in deals: industry research consistently shows partner-influenced deals close at materially higher win rates and larger ACVs than vendor-direct equivalents in the same segment, but only when the *right* partner is matched to the *right* deal.
## Inputs to gather first
- **Target account list**: open opportunities, ABM target accounts, expansion candidates, churned-customer reactivation list, or a stage-filter on the CRM.
- **Motion intent**: warm intro from partner / co-sell / channel-led full ownership / referral / customer reference.
- **Partner constraints**: tier eligibility, region, vertical, partner type (SI, reseller, referral, MSP).
## Process
### Step 1: Pull the target account list
- `Introw:search_crm_objects`: open deals in scope, or filter by stage / segment / region.
- Or accept the account list pasted in by the user.
- Capture each target's domain, segment, vertical, deal value, stage.
### Step 2: Pull overlap data from Crossbeam
- `Crossbeam:*`: for each target account, identify which partners have a customer relationship, opp, or evaluation in flight on that account.
- Capture overlap *type* (customer / opp / champion / lapsed): not just presence. A partner whose customer is your target is much warmer than a partner whose lapsed prospect is your target.
- Capture overlap *recency*, fresh overlaps beat stale ones.
### Step 3: Enrich with Introw partner performance
For each candidate partner-account match:
- `Introw:search_partners`: partner record (tier, region, vertical specialization, partner type).
- `Introw:search_crm_objects`: has this partner closed similar deals before (vertical × deal size × product)?
- `Introw:search_partner_engagement`: recent engagement intensity. A partner with the right overlap who's been silent for 90 days is a different play than one who's actively engaged.
- `Introw:get_tier_information`: tier eligibility for the product/segment.
### Step 4: Score partner-account fit
For each candidate match, combine:
- **Overlap strength** (customer > opp > champion > lapsed)
- **Overlap recency** (last 90 days > older)
- **Partner-deal historical fit** (vertical × deal size × product match)
- **Current engagement** (active vs. dormant)
- **Tier / certification eligibility** (hard pass if not eligible)
- **Channel-conflict cleanliness**: cross-check existing registrations to avoid placing partners on contested accounts.
### Step 5: Match the right partner per account
For each target account, select 1 to 3 partner candidates with the strongest case. For each, articulate the *why* in one sentence:
- "Partner A, has a 3-year customer relationship at Globex; recent engagement; closed 5 similar healthcare deals; Gold-tier and certified on relevant product."
### Step 6: Draft the motion
- For warm intro: draft a partner-facing message with the specific account, why we're asking, what's in it for them (margin, MDF eligibility, deal protection).
- For co-sell registration: pre-fill `share_lead_or_register_deal` payload and surface for vendor approval.
- For full handoff: draft the AE-to-partner handoff email with prospect context.
### Step 7: Capture and queue
- `Introw:add_comment` on the deal record with the matched partner + rationale.
- `Introw:add_task` for the AE or PDM to make the intro by a target date.
- If auto-action is enabled and conflict is clean: submit the registration via `share_lead_or_register_deal` with the captured context.
## Output format
- **Account-by-account match table**: account, value, stage, top-1/top-3 partner candidates, overlap type, overlap recency, fit score, why.
- **Drafted partner-facing messages** per match, copy-pasteable.
- **Registration payloads** for clean matches, ready for approval.
- **Conflict flags**: accounts with existing registrations or direct claims, surfaced not auto-actioned.
- **Aggregate insight**: which partners had the most matchable overlaps (informs future ABM/recruitment targeting).
## Guardrails & PRM best practice
- **Overlap data has lag.** Crossbeam refreshes typically run nightly or weekly; flag stale data and avoid acting on overlaps > 30 days old without confirmation.
- **Privacy & data sharing rules.** Crossbeam-shared data is scoped to your population groups; only surface overlaps within authorized data-sharing agreements. Never surface partner customer names outside the vendor-internal scope.
- **Channel conflict before action.** Always run conflict detection (existing registrations, direct claim, named-account list) before recommending placement. Crossbeam overlap doesn't override rules of engagement.
- **Don't poach.** Overlap with another partner's customer doesn't mean the second partner gets the deal, surface the existing relationship as context, not as a takeover signal.
- **Why beats overlap.** A weak overlap with strong fit (vertical, prior wins) often beats a strong overlap with weak fit. Don't let raw overlap count dominate scoring.
- **Tier-aware match.** Strategic deals to top-tier partners with proven enterprise motion; transactional deals to volume partners. Mismatching destroys margin and partner energy.
- **No auto-execution on first run.** Surface matches and rationale; let the human approve the first batch. Once the user has validated the matching logic, auto-action mode (auto-registration on clean matches) can be enabled.
- **Capture decisions** via `Introw:add_comment` on each deal, the AE/CAM picking it up next week needs to see why this partner was placed.
- **Respect dormant partners' state.** A perfect-overlap partner who's silent for 90+ days needs an activation play (`vendor-activate-network-with-personalized-campaigns`) before placement, not a deal handoff cold.
- **Cross-skill handoff.** Clean placements that need coaching → `vendor-deal-coach-from-similar-wins`. Conflicts → conflict-resolution flow. Coverage gaps revealed by the analysis → `vendor-acquisition-abm-orchestrator` (we should be recruiting partners for these segments).
How to install and run the skill
You've got two ways to use it, depending on where you work. Either way, you'll need Crossbeam connected to Claude as well as Introw, because the skill reads overlap data from one and partner performance from the other. On the Introw side, the Crossbeam integration also brings shared accounts into Introw itself, and the Crossbeam setup docs show what it syncs.
Option 1: Claude Code
Create a folder called vendor-crossbeam-cosell-finder inside .claude/skills/ in your repo, and save the file above as SKILL.md inside it. Claude Code picks it up automatically and runs it whenever your prompt matches the trigger phrases in the description.
Option 2: Claude (or any MCP client) with the Introw connector
You don't need to be technical for this one. Connect Claude to Introw once, and you can run the same play in plain language from Claude, or from ChatGPT, Slack, Teams or your CRM. Introw is listed in Claude's connector directory, so it's one click plus a sign in, with no server URL to paste. Here's how connecting looks:
The step by step version lives in the Connect Claude guide, and the Claude integration page covers what you can do once you're connected.
Prompts to try
Once the skill is installed or Claude is connected, try any of these:
- "Find partners that overlap with these accounts." Paste a list and get a ranked partner match for each one.
- "Best partner for this target list: our Q1 ABM accounts in healthcare." Matches partners to a whole ABM segment.
- "Who already has the customer at Globex?" Checks a single account for the warmest relationship.
- "Warmest overlap on our five biggest open deals, warm intro only, don't register anything yet." Gives you drafted intros to review.
What you'll get back
A typical run returns five things:
- Account by account match table: account, value, stage, top partner candidates, overlap type, recency, fit score and the one sentence reason.
- Drafted partner messages: an intro request or handoff email for each match, ready to copy.
- Registration payloads: pre filled deal registrations for clean matches, waiting for your approval.
- Conflict flags: accounts with an existing registration or direct claim, surfaced so you decide, never actioned automatically.
- Aggregate insight: which partners had the most matchable overlaps, which tells you where to invest and where you need to recruit.
Here's an illustrative example of part of a match table:
| Account | Deal value | Top partner | Overlap | Fit | Why |
|---|---|---|---|---|---|
| Globex | $120K | Northwind IT (Gold) | Customer, 3 years, active this month | High | Closed 5 similar healthcare deals, certified on the product |
| Umbrella Health | $80K | Harbor Systems (Gold) | Customer, 2 years | Hold | Dormant for 95 days, run an activation play first |
| Soylent Retail | $60K | Two partners | Customer and lapsed | Conflict | Existing registration by another partner, needs review |
And a drafted intro for the first row might read like this:
- To: Northwind IT partner manager
- Subject: Globex: can we team up on their Q1 rollout?
- Body: You've supported Globex's IT for three years, and we're in an active evaluation with their operations team. Given your healthcare wins with us this year, you're the partner we'd most like alongside us. Registered co sell deals in your tier come with deal protection and MDF eligibility.
- Ask: A 20 minute call this week to compare notes on the buying group.
Staying in control: what Claude can and can't do
Handing partner placement to an AI assistant only works if you trust it. A few things are built in:
- You approve the first batch: on the first run, the skill surfaces matches and reasons only. Auto registration on clean matches is something you switch on later, once you trust the logic.
- It stays inside your access: Claude connects to Introw over OAuth as you, so it can only see and do what you can.
- It checks conflicts before anything moves: existing registrations, direct claims and named account lists are checked first. Overlap never overrides your rules of engagement.
- It doesn't poach: if another partner already has the customer, that relationship shows up as context, not as a reason to take the deal away.
- It flags stale data and respects privacy: overlaps older than 30 days are flagged for confirmation, and partner customer names stay inside your internal team.
- It doesn't hand deals to dormant partners: a perfect overlap from a partner who's been silent for 90 days or more gets an activation play first, not a cold handoff.
Prefer to do this in the Introw app?
Once you've picked the partner, you need to get them into the deal. In Introw, Share hands a deal or any CRM record to a partner in one dialog: pick the partner, add context, review the email and send. Introw writes the partner onto the record for attribution, and the deal shows up in their portal.
The full walkthrough is in the share a CRM record with a partner guide. From there, you can track what each partner contributes with partner performance reporting and see how it rolls up into partner influenced revenue.
Pair it with other Claude skills
Finding the partner is step one. These skills from the library pick up where this one stops:
- Partner is dormant: Activate the Network with Personalized Campaigns diagnoses why a partner went quiet and drafts a campaign to bring them back before you place a deal with them. Our guide to partner activation covers the wider playbook.
- Partner needs help on the deal: Deal Coach from Similar Wins coaches a partner's live deal using your past wins in the same segment.
- No partner covers the segment: the ABM acquisition orchestrator turns coverage gaps into a recruiting brief, so next quarter the match table has more to work with.
You'll find all of them in Introw's skill library, and our roundup of Claude skills for partner teams explains how they fit together.
Run co selling from Claude with Introw
Introw is a CRM first partner relationship management platform, which means it builds on top of your existing HubSpot or Salesforce setup rather than replacing it. It's also headless by design: the partner portal is one surface, but you can run the same program in plain language from Claude, ChatGPT, Slack or Teams through Introw's MCP server, with every action written back to your CRM.
That's what makes a skill like this work. Partner tiers, past wins, engagement and deal registrations all live in one place next to your CRM, so the fit score is built on real data, not a list someone exported last quarter. Add Crossbeam overlap on top and every target account gets a partner, a reason and a next step.
Connect Claude to your partner program and run your first co sell match today. Connect Claude or book a demo.
Still curious? Here are some quick answers to help clear things up
Co selling is when a vendor and a partner work the same deal together, sharing account knowledge, relationships and sales effort. It works best when the partner already has a relationship at the account and a track record with similar deals.
Start with overlap data from a tool like Crossbeam, then weigh overlap type, recency, the partner's past wins in that segment, their current engagement, tier eligibility and conflicts. The Crossbeam Co Sell Partner Finder skill does this for a whole account list at once.
No. Claude Code users can drop the SKILL.md into their skills folder. Everyone else can connect Claude to Introw and Crossbeam through the connector directory and run the same play in plain language.
Not on the first run. It drafts intros and registrations and you approve them. Auto registration on clean, conflict free matches is something you can switch on later, once you've validated the matching logic.
Yes. The full file is in this article and in Introw's skill library. You can copy it as is or adapt it, but it reads live data through Introw's MCP server and Crossbeam, so you'll need both connected to run it.
See AI-Native PRM in Action
Book a demo with one of our partner program experts, or explore Introw on your own time.
