Your CRO just put ecosystem-sourced pipeline on your goal sheet. You have 12 technology partners, 4 consulting partners, and a Crossbeam account you check twice a week. Your co-sell motion with the top partner has produced 3 joint opportunities in 6 months, which isn’t enough.
I am Nicolas. I work on the ecosystem and partnerships side at Leadpipe. Partner managers who use intent data and visitor identification turn co-sell from a reactive motion into a proactive one. Here is the playbook.
Who this post is for
You are a partner manager, partnerships lead, or head of alliances at a B2B SaaS company between $10M and $100M ARR. You have 5 to 30 partners on your roster. You carry a pipeline or revenue number, not just a partner count. You have access to at least one co-sell tool (Crossbeam, Reveal, PartnerTap) and a CRM.
The answer up front: use intent data for 3 ecosystem plays. Find accounts researching your category that overlap with a partner’s customer base. Route partner-sourced leads to named reps with warm-intro language. Prove ecosystem-influenced pipeline by overlaying partner touchpoints with visitor identification signals. Everything else in partnerships marketing is secondary until these 3 work.
The 3 plays
| Play | Outcome | Frequency |
|---|---|---|
| 1. Overlap watchlist | Shared in-market accounts with partners | Weekly |
| 2. Warm-intro routing | Partner’s customers who visit your site | Daily |
| 3. Influence attribution | Ecosystem-sourced pipeline proof | Monthly |
Play 1: the overlap watchlist
Co-sell breaks when partner managers ask sales teams to “work an account together” without a signal the account is in-market. It works when both sides of the partnership can see the same buying signal at the same time.
Build the overlap watchlist weekly.
Step 1: get a list of accounts researching your category in the last 30 days. Orbit produces this by reading intent across 5M websites. If you don’t have Orbit, pull from your visitor identification tool filtered to ICP and high-intent pages.
Step 2: cross-reference against your partner’s customer list in Crossbeam or Reveal. The intersection is the watchlist.
Step 3: rank the intersection by intent score and number of identified visits.
What the watchlist looks like:
| Account | Intent source | Partner | Visits last 30 days | Next action |
|---|---|---|---|---|
| Acme Corp | Pricing page + Orbit research | Partner A | 7 | Joint intro email |
| Beta Inc | Comparison page | Partner A | 3 | Partner warm intro |
| Gamma Co | Category pages | Partner B | 2 | Add to nurture |
Share the watchlist with your partner manager counterpart at the partner company. The conversation changes from “want to work some accounts together” to “here are 6 accounts actively researching our shared category, 3 are already your customers, let’s decide who reaches out first.”
Play 2: warm-intro routing
Your partner has 400 customers. Some percentage of those customers are going to visit your website in any given month. Without visitor identification, that visit is invisible. With it, every one is an opportunity for a warm intro.
The workflow:
- Import your partner’s customer list into your CRM as a custom Account segment called “Partner A Ecosystem.”
- Set up a rule in your visitor identification tool: if an identified visitor’s Account matches the ecosystem segment, tag and route.
- Route the tagged visit to your partner manager (you), not to the cold SDR queue.
- You ping your counterpart at the partner with context: “Your customer [Acme] is looking at our [specific category page]. Want to make a warm intro or want us to reach out on our own with your context?”
Why this works:
The partner’s customer is already warm to the partner. If the partner facilitates the intro, you skip 3 cold-email steps and land in a conversation. In the best case, it is a co-sell. In the minimum case, it is an identified visitor that gets handled with partner context instead of a cold template.
Guardrail:
Don’t route these to your cold SDR queue. The partner will lose trust if their customers are getting cold-emailed by your BDR without context.
See how to track when target accounts visit your site for the routing logic.
Play 3: influence attribution
Your CRO wants to know how much pipeline the partner program generates. Last-touch attribution says “partner-sourced = 4 deals in Q1.” Reality, if you overlay visitor identification, is usually 3 to 4 times that.
The monthly overlay:
Pull every closed-won Opportunity from the last 90 days. For each, check:
- Did the Account appear on any partner’s overlap watchlist in the 90 days before close?
- Did any identified visitor from the Account have a partner co-marketing page view (a joint webinar registration, a co-branded case study)?
- Was there any logged partner touchpoint in the CRM timeline?
Any yes = ecosystem-influenced. You will typically find 20-30% of Opportunities had ecosystem influence even when sourced credit went elsewhere.
The 3-column report:
| Category | Count | ACV | Pipeline |
|---|---|---|---|
| Partner-sourced (partner attributed) | |||
| Partner-influenced (any touch in journey) | |||
| Net-new direct (no partner touch) |
This replaces the single-line “partner-sourced” number with the real ecosystem picture. It is what your CRO needs to fund the program at the right level.
For the broader attribution framework, see the CRO’s pipeline source audit.
The weekly rhythm
| Day | Task | Time |
|---|---|---|
| Mon | Pull overlap watchlist for top 3 partners | 45 min |
| Mon | Send watchlist + intros to partner counterparts | 30 min |
| Tue-Thu | Work warm-intro alerts as they come in | Ad hoc |
| Wed | Partner counterpart sync (rotating) | 30 min |
| Fri | Log ecosystem-influenced opportunities for the week | 30 min |
| Monthly | 3-column attribution report | 2 hours |
Roughly 4 to 6 hours per week on the plays, plus meetings with partner counterparts.
How to pitch this to your partners
You will want your partner managers at partner companies to build the same motion. They should, because the intent signal is bidirectional.
What to say in the pitch:
- “I’ll share our in-market account watchlist with you weekly. You share yours with me. The overlap is where we focus.”
- “When one of your customers visits our site, I’ll tell you, and ask you how you want me to handle it.”
- “When one of our customers visits your site, tell me. Same deal.”
- “We both track ecosystem-influenced pipeline using behavioral data, not just last-touch.”
Most partner managers will say yes because the alternative is vague quarterly QBRs without real accounts to work.
ICP-fit vs partner-fit
One nuance: a partner manager filters differently than a core GTM team.
Core GTM filter: ICP-fit (industry, size, geography, titles).
Partner filter: ICP-fit AND partner-compatibility (uses the partner’s product, is in the partner’s target segment, is a stage where both products make sense).
A series A company may be an ICP-fit for your product but too small for your enterprise consulting partner. Filter the overlap watchlist accordingly before sharing.
Common failure modes
Failure: dumping partner customer lists into the cold SDR queue. Effect: the partner loses trust when their customers report spam. Fix: route ecosystem-flagged visits to you or an AE, never to a cold BDR.
Failure: sharing the same overlap watchlist with all 12 partners every week. Effect: watchlist fatigue. Partners stop reading. Fix: prioritize the top 3 partners, send tailored lists per partner.
Failure: counting every shared Slack channel as “partner-influenced.” Effect: attribution inflates, your CRO calls it out. Fix: require a specific signal (joint marketing event, co-branded content visit, partner touchpoint in CRM) before flagging as influenced.
Failure: building this motion in isolation from marketing. Effect: duplicate outreach, conflicting messages. Fix: loop marketing in on the overlap watchlist so paid and content campaigns can amplify the list.
Failure: launching with 15 partners at once. Effect: nothing works well. Fix: start with 2 or 3 partners where you have existing trust and a real target account set.
Tools and workflows
| Function | What to use |
|---|---|
| Co-sell data | Crossbeam, Reveal, or PartnerTap |
| Intent on shared accounts | Orbit person-level intent |
| Visitor identification | Leadpipe Growth $299/mo or Scale $599/mo (partner programs usually generate enough volume to need Growth plus) |
| CRM routing | Native Salesforce or HubSpot integration |
| Partner comms | Slack shared channels + monthly syncs |
The agency and white-label angle
If you work for an agency running partner programs for clients, the Agency plan at $1,279/mo gives you 20,000 identifications across clients in a white-label dashboard. That enables running the same 3 plays on behalf of multiple clients simultaneously. See the agency owners guide.
What NOT to do as a partner manager
- Don’t commit to a co-sell motion without a real signal. “Let’s work accounts together” without intent data produces zero pipeline.
- Don’t send the overlap list to the wrong side. Partners want leads from your data, not the other way around. Send shared watchlists, not one-way takes.
- Don’t skip the monthly attribution pass. If you can’t show ecosystem-influenced pipeline, the program will be cut at the next planning cycle.
- Don’t forget the customer success angle. Identified visits from your current customers to a partner’s site may signal expansion or churn risk. Route those to CS, not co-sell.
- Don’t treat this as a replacement for trust-building. The playbook accelerates a relationship. It doesn’t create one.
What good looks like at quarter-end
You end the quarter with 3 active partners working the same overlap watchlist every Monday. Ecosystem-influenced pipeline doubled from Q1. Your partner counterparts can name 5 accounts each where your intent data changed the conversation. That’s a partner program that deserves the next round of investment.
The partner managers who run intent plays compound faster than the ones who rely on quarterly QBRs and shared Slack channels. Intent data is what turns a partnership from a marketing logo into a pipeline engine.
Spin up an Orbit watchlist for the accounts you actually care about and see who is researching your category right now. Get started with Orbit →
