← BUILD LOGPRODUCT-LED MOTION
BUILD LOG · THE PRODUCT CHANNEL

Our best sales channel was one we already had. We just could not see it.

Thousands of people used the product every week and nobody in sales ever knew. A product-led motion sat under the whole business, because usage was never turned into context a rep could act on.

~47%
qualified win rate, the highest of any channel
$1M+
in sales-qualified pipeline, built from zero
#1
channel for retention and expansion, the strongest of any
4x plan
the pipeline the channel actually delivered
THE STORY, FROM THE SEAT

Here is one I actually shipped. What happened, what I did, and the stack if you want to run it yourself.

This one started in a leadership conversation about outbound strategy. We were digging into where outbound pipeline actually came from, and the answer kept moving: a big share of what we called outbound had actually been sourced by the product. People were already using us and showing up in pipeline wearing an outbound label. That opened the real question. What did we actually know about our users, and how big was the channel hiding under that label?

Bigger than we thought. Thousands of people were using the product every week and nobody in sales knew. Not a strategy problem. A data problem. No event mapping, so usage never became context. No context, no motion. Usage was exhaust, going into a warehouse to die.

There were three ways to go: buy an intent tool, hand reps a raw list of active domains, or map the events ourselves. I ended up doing all three. The order is where the mistake lives.

I bought the tool first. It was powerful and it was useless in the same month, because underneath it sat a data gap we had not sized: the events were not mapped, so there was nothing real to feed it. A tool is only as powerful as the data you give it. Now there was money on the table and a clock on the wall. The raw list was the other shortcut, and it failed just as fast. Raw usage without context is a colder cold list.

So we went back to the drawing board and did it the long way. Hypotheses, tests, analysis, week after week with product and marketing. The first job was not building anything. It was figuring out what actually worked: which product behaviors correlated to a sale. One finding changed the shape of the whole thing. Specific self-serve adoption patterns correlated to enterprise opportunity too. The channel was not just self-serve revenue. The same signals pointed upmarket. Once we knew what worked, the ownership map almost drew itself: the go-to-market motions, what sales owned, what marketing owned, what product owned.

The Sales Operator
Keep Building,
Heath
FOUNDER, THE SALES OPERATOR
01 / HOW WE APPROACHED THE PROBLEM

Ran the loop.

Three options were on the table and all three eventually ran: buy the intent tool, pull the raw list, or do it the long way. The long way was the loop: hypotheses, tests, and analysis with product and marketing, week after week, until the events that actually predicted a sale were real. Here is what that looked like in order.

  1. 1
    Map the events first

    I mapped what users actually did in the product to what it meant for a sale. Not every event, the ones that predicted buying.

  2. 2
    Centralize the signal

    I centralized our Snowflake product data with enrichment and signal data by implementing Common Room and Deepline, so a usage spike at an account arrived already enriched, already scored, already routed.

  3. 3
    Build the motion on top

    The signals worth acting on, the play that worked them, and the routing that put a real user in front of a real rep with a real reason to talk.

02 / WHAT IT TOOK CROSS-FUNCTIONALLY

Nobody ships this alone. Here is who had to move.

The block was data, and the data belonged to other people. This channel only exists because product and marketing moved with sales, and because the ownership lines got drawn after we knew what worked, not before.

PRODUCT
The event schema. The analysis was joint.

We traced the customer journey together: what brought a user to the website, what they converted to, where the aha moments were. Understanding the PLG motion end to end is what unlocked the product-led sales motion.

MARKETING
The motion mix, and closing the loop.

Three go-to-market motions defined together: sales-led, sales-assisted, and no-touch. Marketing ran the in-app campaigns, and the loop-closer: a product lead not ready for commercial or enterprise did not get discarded, it went into a nurture path we built together.

03 / HOW WE TURNED IT INTO A SALES MOTION · THE PEOPLE PART

Scoring the product channel was the easy part. Teaching reps to work a product lead was the point.

A product-qualified lead is not a cold lead with a better score. It is a person already using the thing. The leadership half was retraining the team to sell to someone already inside the product, and protecting the reps from the experiment while we learned: a tiger team of reps who could execute piloted the motion, because rep time is money and the screwup budget on a new channel is finite.

THE FRAMEWORK BEHIND IT
SMART Prospecting, on a warm product lead

Show you understand their usage, Map the problem their behavior points to, Acknowledge the cracks, Reveal the impact, Take action. The signal says they are ready; SMART tells the rep what to actually say.

  1. 01
    Turned context into a why, not a helloSMART

    The usage signal became the reason for the conversation. That is permissionless outreach: the context creates the right to the conversation before the rep ever asks for time.

  2. 02
    Made the whole motion signal-ledTHE OPERATING LAYER

    Reps stopped working lists and started working reasons. Every touch began with something the account just did, so the play was always a response, never an interruption.

  3. 03
    SMART opened the door; multi-threading found the championSMART + PLAN

    A product lead is one person inside the product, not a deal. SMART earned the first conversation; the decision-dynamics work threaded from that user to the champion and the committee around them.

  4. 04
    Built the relay loopTHE RELAY LOOP

    Every deal and every call fed something back: product learned which usage patterns preceded a win, marketing learned the words converting buyers actually used, sales learned which play to run next. Product penetration accelerated because product was building from live deal evidence, not roadmap guesses.

Run SMART on a product lead
04 / WHAT I LEARNED

Not proof. Just what the build taught me.

  1. 01
    I bought the tool before I mapped the data

    Powerful tool, useless in the same month. A tool is only as powerful as the data you feed it, and the gap was mine to find before the purchase, not after.

  2. 02
    Sunk cost puts a clock on everything after it

    The wasted spend turned a build project into a race to optimize. Do the data work first and every tool decision after it gets cheaper and calmer.

  3. 03
    Figure out what works before you decide who owns what

    Once the win correlations were real, the ownership map across sales, marketing, and product almost drew itself. In the other order it is a turf negotiation.

  4. 04
    Protect the reps from the experiment

    Rep time is money and the screwup budget is finite. A tiger team piloted the motion and comp was thought through before launch, so reps did not pay for the company's experiment.

05 / THE WORKFLOW

The runnable version. Copy it into your stack.

SnowflakeCommon RoomDeeplineSalesforce
[ SALES OPERATOR ]

The Product Channel

Heath Barnett · Sales Operator
G / Groundthe problem that started all of it, with the receipt and the cost
Signal

Usage was just exhaust.

Thousands used the product every week and no one in sales knew. No event mapping, so usage never became context.

Drag

A raw list is a colder cold list.

Handing a rep active domains failed fast. Usage without context does not tell you who is ready.

A / Assignthe build, block by block, and who owns each one. Open a step to see it run.
HUMAN + AI, IN THE LOOP
The system maps, enriches, scores, and routes; the operator decides what a signal means and the rep owns the conversation.
Map the signal
Snowflake01
Read the product events
Details
Pull what users actually did every week out of the warehouse where it was dying.
AI
Snowflake02
Decide which events predict a sale
Details
Not every event. The few that predict buying. That call is judgment, not a query.
Human
Enrich and route
Common Room03
Enrich and score the spike
Details
A usage spike arrives already enriched and scored, not raw exhaust.
Powers up with
AI
Deepline04
Route the account to a rep
Details
Puts a real user in front of a real rep, already scored and routed.
AI
Work the play
Salesforce05
Land it in the CRM
Details
The routed, scored account lands where the rep already works.
AI
The rep06
Run the play
Details
A real conversation with a real reason to talk, not a cold list.
Human
N / Normalizethe motion that made it stick
A workflow without a motion is dead. This is how it became the way the team works.
1

Tiger team first

A few reps who could execute piloted the motion before the floor got it. Rep time is money and the screwup budget on a new channel is finite.

2

Trained the warm-hand difference

SMART on a product lead: open with what the account already does, coached as a response, never an interruption.

3

Made signals the default

Every touch started with something the account just did. The cold-list habit retired because the warm way kept winning.

T / Tie backthe result it drove, and how they know
RESULT · 01

47.2% SQO win rate

vs 39% blended.

RESULT · 02

~100% SQO to close

the product had already qualified them.

RESULT · 03

#1 new-business source

a channel built from nothing.

OUTPUT · 01

Event-to-intent map

The few events that predict a sale.

OUTPUT · 02

Enriched, scored signal

A spike that arrives ready to route.

OUTPUT · 03

A routed account

A real user in front of a real rep with a reason.

The Sales Operator
06 / HOW YOU DO IT TOO

Here is what I built. Here is how you build it.

The whole thing installs as one plugin. Or grab the skills a la carte. Everything on this page, runnable, on what you paste today.

EVAL PASS · 4/4
THE PLAYBOOK · ONE INSTALL
Turn product usage into booked pipeline

4 skills chained into one runnable play. Installs as a single plugin, no copy-pasting each skill. It runs on what you paste; connect your stack to go live.

SEE THE FULL PLAYBOOK →
SEE IT RUN IN CLAUDE
EXAMPLE CHATDana, AE on a product-led motion, running the loop in one sitting
D
We have thousands of free users and I have no idea which ones to call. Sales treats them like cold leads and the emails flop. Where do I even start?
R
Read· Product Usage Analyst
Let the product tell you who is ready before you spend an hour. I pulled usage across your free base and ranked accounts by the behaviors that actually precede a buy: repeat use, multiple seats on one domain, and hitting the wall on a paid feature.
Receipt
Ranked your free base. 42 accounts show buy-ready behavior: 3+ active seats on one domain, weekly use, and a paid-feature limit hit in the last 14 days.
D
Okay, that list is way more useful. When do I reach out?
T
Time it· Trigger Outreach
On the signal, not the calendar. The strongest reason to reach out is a fresh spike, so I flagged the accounts that jumped this week. You talk to them while the usage is hot, not next quarter.
Receipt
8 of the 42 spiked this week: a new seat added or a paid-feature limit hit in the last 3 days. Those are today's calls.
D
Good. What do I actually say? The templated stuff gets ignored.
S
Say it· Cold Email Writer
Open with what they are already doing in the product, not a pitch. A product lead can tell in one line whether you looked. Here is the first touch for the top account, built on their real usage.
Receipt
Drafted the first touch: it opens with the seat they just added and the feature they hit the limit on, one idea, one ask. No template smell.
D
Love it. Can you make it a real sequence so I am not doing this one at a time?
S
Sequence· Cadence Builder
Tuned to a warm product lead, not the cold playbook. Every touch has a point and there is a clean break-up. You stay in control of who gets it; the motion runs the timing.
Receipt · the play, running
A 4-touch sequence per account, each touch anchored to their usage, over 10 days with a clean exit. 8 hot accounts loaded, ready to send on your yes.
THE OTHER HALF · LEAD THE TEAM
Run SMART on a product lead
I write up one of these a week. Free, receipts only.