Build a partner channel that produces pipeline
Partnerships that stop at a signed agreement produce nothing. Recruit, activate, and co-sell.
Build a partner channel that produces pipeline
Partnerships that stop at a signed agreement produce nothing.
Recruit, activate, and co-sell.
The right partners
A first joint motion
A named-account co-sell
Events that convert
The recruit-score-activate pattern
Not a partner-specific receipt, there is no dedicated partner-channel build yet: this is the same recruit-score-activate pattern that took product usage from nothing to our top channel, applied here to partner recruitment instead.
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Score the fit, pitch mutual value in their terms, enable them, and ship a first joint motion instead of going dark after kickoff.
Map the account across both companies, set ownership, build the joint value story, and plan the shared path to close.
Tier it, set the research angle, build the multi-thread across marketing and sales, and orchestrate touches so the account feels one motion.
The right guest list, a real draw, an on-site conversation plan, and follow-up that converts.
The right partners, a first joint motion, a named-account co-sell, and events that convert.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: Marcus, Head of Partnerships, has 40 agencies signed and nothing happening, needs to pick who to work and land a real joint motion.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
If you sell a product people can use before they buy, you already have a product-led channel. The question is never whether it exists. It is whether your usage data has been turned into context a rep can act on. Map the events first. The motion comes after.
Dig into the full build →One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.