Turn product usage into booked pipeline
Your best-fit buyers are already using the product for free, and reps keep treating them like cold leads. Work the product channel like the warm one it is.
Turn product usage into booked pipeline
Your best-fit buyers are already using the product for free, and reps keep treating them like cold leads.
Work the product channel like the warm one it is.
Details
Details
Details
Details
0 to our top channel
The product channel that was hiding in plain sight, scored and worked like the warm lead it was.
Score the whole market
One rubric across every account, so a rep works a ranked list instead of guessing.
The behavior that predicts a buyer
Backtested against real wins and losses: usage beat firmographics.
A read on who is ready by how they use you
A timely reason to reach out
A first touch that opens with their usage instead of a template
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.
Turns raw usage into per-capability adoption tiers, a 12-week trend on each, power-user IDs, and a ghost-active flag.
Read the trigger (funding, hire, launch, job posting, tech change), pick the one angle it earns, and write the touch while it is still fresh.
From a prospect and a specific angle, writes a short email or 3-touch sequence built on one idea, no filler.
The steps, timing, channel, and intent of each touch, tuned to the segment's value.
A read on who is ready by how they use you, a timely reason to reach out, and a first touch that opens with their usage instead of a template.
- 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: An AE on a product-led motion has thousands of free users and no way to tell which ones are worth a call; templated emails to the whole list are getting ignored.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: The channel is a hunch about who logged in.
Without it: Warm accounts queue until they are cold.
Without it: The buyer gets a drip and a rep the same day.
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 →WHAT I DID ›
You cannot prioritize a market by scoring one deal at a time. Put the entire TAM through one rubric, fit for the base, product for the lift, intent capped so it can only help, and make reps work the ranked list top-down. The teams that do book more of the right pipeline and stop burning a quarter of their capacity on accounts that were never going to buy.
Dig into the full build →WHAT I DID ›
Before you trust a scoring model, backtest it against the deals you actually won and lost. Measure lift per signal. The ones that feel important and the ones that are important are rarely the same list.
Dig into the full build →A warm lead is only warm if the rep opens warm
The usage read and the trigger hand reps who is ready and why now; the meeting comes from a first line that proves someone actually looked. Here is how a sales leader keeps the warmest channel from being worked like a cold list.
Before a rep touches a product-qualified account, they state the usage story in two sentences: what the account is doing in the product and what that usually means next. Reps drill the readback on real accounts until the cold-template reflex is gone.
- 01Teach the usage reads
Walk the team through what product-usage-analyst's patterns mean: a spike, a stall at a limit, a second team joining. Each pattern has a different next move, and reps should name it before they write.
- 02Hold the freshness SLA
Trigger-outreach flags the window; the rule is the touch goes out inside it or the account waits for the next signal. A usage signal from last month reads as surveillance, not relevance.
- 03Rehearse the warm open
Roleplay the first line of the cold-email-writer touch: usage first, template never. If the line could have been sent to any account, it fails the drill.
- 04Inspect the channel against cold
Review reply and meeting rates on product-channel touches next to the cold baseline every month, and feed what converts back into the usage read and the cadence-builder sequence. The channel stays warm only if the motion respects it.
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.