Close with a partner, not just trade a lead.
Map the account across both companies, set ownership, build the joint value story, and plan the shared path to close.
Inside: The joint account map, the ownership split, and the path to close.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads your contacts, the open opportunity, and stage automatically, so the account map and the close plan match the real deal.
shows who on your side is actually engaged and who has gone quiet, so the coverage map is real, not aspirational.
fills in the roles and reporting lines so you can see the gaps only the partner can cover.
This was built for a B2B SaaS org co-selling into a buying committee with a partner. Set these to your stack:
Your co-sell motion is yours. The skill maps and splits against the model you set, not a generic one.
| Set this | What it is | Default / Example |
|---|---|---|
| PARTNER role | how the partner shows up in the deal | tech allianceresellerreferralSI |
| STAGE field | the opportunity stage | Opportunity.StageName |
| CONTACT ROLES | how you see who is on a deal | OpportunityContactRole |
| ENGAGEMENT source | where replies and touches live | TaskEventemail or meeting tool |
| OWNERSHIP model | how you split the deal | who leadswho supportswho owns close |
| ENRICHMENT | source for roles and reporting lines | your enrichment connector |
Everything the skill does, in full.
Takes one named account and a partner and builds the co-sell: it maps who each side knows and covers inside the account, sets clear ownership so the deal does not fall into the gap between two companies, writes the joint value story neither of you can tell alone, and plans the path to close so both teams are pulling. A co-sell that is just a traded lead and a hope is not a co-sell. This makes the partner a force in the deal.
- 1Map the account across both companies
Lay the account out and mark who each side knows: your contacts, the partner's contacts, and the roles still uncovered by either of you. The whole reason to co-sell is coverage neither side has alone. Find the room the partner is already in that you are not, and the reverse. Name the overlap and the gaps.
- 2Set who owns what (so nothing falls between you)
The fastest way to lose a co-sell is both sides assuming the other has it. Assign it plainly: who leads the relationship, who runs the technical proof, who owns the commercial conversation, who drives the close. Write it down where both teams can see it. Ambiguity is where joint deals go to die.
- 3Build the joint value story (neither of you tells alone)
The point of the partnership is a story bigger than either product: the combined outcome for the customer, why the two together beat either alone or a point tool. Write the version the customer hears, in their terms, with the roles each company plays. If the pitch is two vendors taking turns, you have a bake-off, not a co-sell.
- 4Plan the path to close (both teams pulling)
Lay out the steps to signature and mark which company drives each: the joint discovery, the technical validation, the business case, the procurement path. Put dates on the near ones. Flag the risks only the partner can clear and the ones only you can. A shared close plan is what turns a traded lead into a won deal.
- 5Keep both sides accountable (before the deal drifts)
Set the checkpoint that proves the co-sell is live: a joint meeting held, a partner-driven thread opened, a step the other company owns and delivered. If a side goes quiet, the deal is quietly reverting to single-company, and you re-engage now, not at the next partner sync.
- The account map names the roles uncovered by either side, not only the ones already known.
- Every deal step has one named owner, never "we will figure it out."
- The joint value story is the customer's outcome, never two vendor pitches stapled together.
- Engagement claims are grounded in real touches where that data exists, and flagged as assumption where it is not.
- Any name, role, or figure carried in is shown as given or sourced, never invented. Sample numbers are illustrative only.
CO-SELL PLAY · Acme Corp x Partner (illustrative) Account map Role You Partner Status Champion Dana - engaged (yours) Econ buyer - CFO engaged (partner's) <- lean here Tech evaluator Sam - engaged Procurement - - UNCOVERED <- neither side Ownership Relationship lead Partner (owns the CFO) Technical proof You Close / commercial You lead, partner supports Joint value story Combined outcome the CFO buys, not two product pitches Next moves: 1. Use the partner's CFO access to open the economic thread. 2. You own the technical proof; partner joins the readout. 3. Cover procurement now. Neither side has it yet.
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Connect Salesforce so the coverage map updates automatically as contacts and roles get added, instead of going stale after this snapshot.
Point a scheduled Claude task at Slack and email threads weekly and flag any owned step that's gone quiet more than 5 days.
Stand up a shared Slack canvas with the account map and ownership table so both sides see the same gaps in real time, not at the next sync.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.