How to turn buying signals into sales actions

Direct answer: to turn a buying signal into a sales action, run every signal through five steps. Capture the signal (from Clay, intent data, product usage or a call recording). Score it against a real sales method, SPICED for the early account picture feeding MEDDIC for deal qualification. Decide the single next move the signal earns. Surface that move inside HubSpot where the rep already works, with the reason attached. Then record what happened so the scoring gets sharper next time. Most teams collect signals and stop at step one. The action only happens when a signal is tied to a method, a next move and a place the rep will actually see it.

That is the whole loop. The rest of this guide breaks down each step, scores real worked examples against SPICED and MEDDIC, and shows where teams go wrong. This is the work we do for clients, so it is also the clearest description of the intelligence layer we build: the layer between your tools and your revenue, turning account context into the rep's next move instead of another dashboard.

Published 17 July 2026. Reviewed quarterly.

What is a buying signal, and why is it useless on its own?

A buying signal is any event that suggests an account is more likely to buy now than they were yesterday. A new VP of Sales starts. A competitor gets acquired. The account hits a usage limit on a free plan. A champion you spoke to six months ago changes jobs to a company in your ICP. Someone on the buying committee opens your pricing page three times in a week.

None of that is rare any more. Clay, intent platforms and product analytics fire signals all day. The problem was never getting signals. The problem is the gap between a signal firing and a rep knowing the right thing to do about it. We call that the context gap, and it is the thing most RevOps stacks quietly fail at.

A signal with no next move attached is just noise with a timestamp. The rep sees "intent spike on Acme Corp" in a side panel, has no idea what changed or what to do, and carries on with the sequence they were already running. The signal cost you money to source and produced nothing. That is the default state of most "signal-based" GTM setups, and it is fixable.

How do you turn a buying signal into a sales action?

Five steps. Same loop every time, whatever the signal.

1/ Capture the signal. Pull it in from wherever it lives. Clay for firmographic and hiring signals, intent platforms for surge data, your product database for usage events, Fathom or Gong transcripts for what was actually said on the last call. Normalise it so a "champion changed jobs" signal from Clay and a "usage limit hit" signal from your product look like the same kind of object the system can reason over.

2/ Score it against a real method. A signal is only worth acting on relative to where the account sits in a sales method. We run two: SPICED to build the account picture (Situation, Pain, Impact, Critical event, Decision), feeding MEDDIC for deal qualification (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion). A signal that fills a known gap in either is worth a lot. A signal that confirms something you already knew is worth almost nothing.

3/ Decide the next move. The signal plus the method gap equals one specific action, not five. If the signal reveals a Critical event (SPICED) the next move is to reach the Economic buyer (MEDDIC) about that event, not to drop another nurture email.

4/ Surface it where the rep works. Write the move and the reason back into HubSpot. A task, a deal property, a Slack ping, whatever the rep actually checks. If it lives in a separate "signals dashboard" nobody opens, you have built a museum, not a system.

5/ Learn from the outcome. Record what the rep did and what happened. Did the move book a meeting, advance the stage, go nowhere? Feed that back so the scoring improves. This is the step that turns a one-off play into something that compounds.

Steps two and three are where the real work is, and where almost everyone underinvests. Capture is a tooling problem and mostly solved. Scoring against a method and deciding the next move is a thinking problem, and that is the part you cannot buy off the shelf.

How do you score a buying signal against SPICED and MEDDIC?

You are asking one question: does this signal fill a gap in the account's qualification, or does it just repeat what I already know?

SPICED tells you whether the account is even a real opportunity and what is driving urgency. MEDDIC tells you whether the deal is qualified and what is missing to close it. A signal earns its action based on which gap it closes:

• A signal that exposes a Critical event (SPICED) or a Decision process / timeline (MEDDIC) is high value. It moves the deal.
• A signal that reveals Pain or Impact you had not quantified is high value. It gives the rep the language to sell.
• A signal that surfaces or replaces a Champion (MEDDIC) is high value. People are the deal.
• A signal that just confirms the account fits your ICP, when you already knew that, is low value. Do not interrupt a rep for it.

Same signal, different score depending on what you already know about the account. That is the whole point, and it is why generic signal scoring (everyone gets the same +10 for an intent spike) is mostly theatre. The score has to be relative to the account's method gaps, not absolute.

Worked examples: signal to action, scored

Here are real signal types, the gap each one fills, and the next move it earns. I have scored each one out of 10 the way we score them in a build, where the score is "how much does this move the deal", not "how interesting is this".

Example 1: A new VP of Sales joins a target account

• Signal: Clay flags a new VP of Sales hire at an account in your ICP.
• SPICED gap it fills: Critical event. A new leader has 90 days to make a mark and usually re-evaluates the stack. That is urgency you did not have last week.
• MEDDIC gap it fills: Economic buyer and Decision criteria. The new VP often becomes the economic buyer and brings their own criteria.
• Next move: Reach out referencing the transition specifically, not your product. "Most VPs of Sales inherit a pipeline they can't trust in week one, here's how we fixed that for a similar team." Route to the AE, not the SDR sequence.
• Score: 9/10. New economic buyer plus a built-in critical event. This is the highest-value signal class there is.

Example 2: A champion changes jobs

• Signal: A contact you had a strong relationship with moves to a new company in your ICP.
• SPICED gap it fills: Situation and Pain. They already know your value, so the situation is half-mapped before you start.
• MEDDIC gap it fills: Champion, instantly. You have an internal advocate on day one.
• Next move: Personal note from the AE who knew them, congratulating the move, then a soft "want the same setup here?" Do not send this through automation. People notice.
• Score: 8/10. A warm champion in a new account is one of the most under-worked signals in B2B. Most teams never catch it because nobody is watching their old contacts for job changes.

Example 3: A free-plan account hits a usage limit

• Signal: Product analytics shows an account on the free tier hitting the seat or usage ceiling repeatedly.
• SPICED gap it fills: Pain and Impact, with numbers attached. They are feeling the constraint right now and you can quantify it.
• MEDDIC gap it fills: Metrics and Identify pain. The usage data is the metric.
• Next move: Trigger a PLG-to-sales handoff. The AE reaches out with the specific usage pattern: "You've hit the seat limit four times this month, here's what the next tier looks like for a team your size." Lead with their data.
• Score: 8/10. Self-qualifying pain with a number on it. The only reason it is not a 9 is you still have to find the economic buyer.

Example 4: A competitor gets acquired

• Signal: A competitor serving your ICP gets acquired or announces a wind-down.
• SPICED gap it fills: Critical event, across a whole segment at once.
• MEDDIC gap it fills: Decision process. Acquisitions create forced re-evaluation, often on a deadline.
• Next move: Segment every account using that competitor and run a switch play. Acknowledge the uncertainty, make the migration look painless, give them a deadline-shaped reason to move now. This is a campaign, not a one-to-one.
• Score: 7/10. High value but lower precision. It applies to a list rather than one named buyer, so it earns a strong play rather than a single perfect move.

Example 5: Three pricing-page visits in a week from one account

• Signal: Intent or web tracking shows repeated pricing-page visits from a target account.
• SPICED gap it fills: Decision and possibly Critical event, if there is a budget cycle behind it.
• MEDDIC gap it fills: Decision process. Someone is building a business case.
• Next move: Have the AE reach out with a specific, light-touch offer: "Looks like pricing is on your mind, want me to put together what a rollout would actually cost for your team?" Helpful, not creepy. Never say "I saw you visited our pricing page."
• Score: 6/10. Genuine intent, but you do not know who is looking or why. It is a prompt to investigate, not proof of a qualified deal.

Example 6: A generic intent spike with no other context

• Signal: An intent platform flags a surge on a topic loosely related to your category.
• SPICED gap it fills: Almost none. It is anonymous and topic-level, not account-specific behaviour.
• MEDDIC gap it fills: None directly.
• Next move: Use it to prioritise research, not to trigger outreach. Have Clay enrich the account and look for a second, harder signal before a rep spends time on it.
• Score: 3/10. This is the signal everyone over-trusts. On its own it is a hint to look closer, nothing more. Acting on it directly is how reps learn to ignore the whole system.

The pattern across all six: the score tracks how much the signal closes a real method gap, and the action is always the single next move that gap earns. Not a generic sequence. Not "add to nurture". One specific thing, with the reason attached so the rep trusts it.

Where do teams go wrong with buying signals?

I have seen the same failures across a lot of GTM stacks. They are almost never a tooling problem.

They collect signal with no system to act on it. This is the big one. The team buys an intent platform, wires up Clay, lights up a signals dashboard, and then nothing changes in the rep's day. The signals fire into a void. Sourcing signal is the easy 20%. Building the system that turns it into a next move is the 80% nobody budgets for.

They treat every signal as equally important. A flat +10 for any intent event trains reps to ignore the score. If a champion job change and an anonymous topic surge get the same weight, the weight means nothing. Scoring has to be relative to the account's method gaps, or it is decoration.

They surface signals where reps don't look. A beautiful dashboard in a separate tool is a dashboard reps open once and never again. If the next move is not in HubSpot, in the flow of the work, it does not exist as far as the rep is concerned.

They send the signal, not the action. Telling a rep "intent spike on Acme" is not an action. The rep still has to work out what changed, what it means, and what to do. The system should have done that. Hand over the move and the reason, not the raw event.

They never close the loop. If you do not record what the rep did and what happened, the scoring never improves. You are running the same blunt rules forever instead of a system that gets sharper every quarter. The feedback loop is what separates a signal gimmick from an intelligence layer.

They confuse a signal with a qualified deal. A pricing-page visit is not a buyer. It is a reason to investigate. Reps who get burned chasing weak signals stop trusting the strong ones. Protect the rep's attention like it is the scarce resource it is.

What does this look like when it actually works?

When the loop is built properly, a rep opens HubSpot and sees, on the account they are working: what changed (the signal), why it matters (the method gap it fills), and the one thing to do about it (the next move), with the reasoning attached. They do the move. The outcome gets logged. The scoring adjusts. Next time, the system is a little sharper about what that kind of signal is worth for that kind of account.

That is the intelligence layer. It pulls account context together, reasons over it through SPICED feeding MEDDIC, and surfaces the next move where the rep works, then learns from what happens. The stack you already own (HubSpot and Clay at the core, with a context store and a reasoning layer behind them) stops being a place data goes to die and starts deciding what happens next.

The honest version: most teams are one or two steps into this loop, not all five. That is fine. You do not need to boil the ocean. Pick your three highest-value signal types, score them against your method, define the one next move each one earns, and write it into HubSpot. Get that working for three signals before you try to do it for thirty.

Frequently asked questions

What is the difference between a buying signal and a trigger event?

A trigger event is one kind of buying signal, usually a discrete, dateable event like a funding round, a leadership change or an acquisition. "Buying signal" is the wider bucket that also covers behavioural signals (product usage, web activity) and relationship signals (a champion changing jobs). All trigger events are buying signals. Not all buying signals are trigger events.

Do I need Clay to turn signals into actions?

No, but it helps. Clay is where we source and enrich most firmographic, hiring and relationship signals, and it is the easiest place to combine several weak signals into one strong one before a rep ever sees it. You can run the loop with intent data and product usage alone. The method, the scoring and the writeback into HubSpot matter more than any single source.

How do SPICED and MEDDIC work together?

SPICED builds the account picture and tells you whether there is a real opportunity and what is driving urgency. MEDDIC qualifies the deal once it exists and tells you what is missing to close it. We use SPICED as the early account-context picture feeding MEDDIC for deal qualification, both grounded in Winning by Design's Revenue Architecture. A signal is scored on which gap in either framework it closes.

How do you score a buying signal?

Relative to the account's method gaps, not on an absolute scale. A signal that fills a known gap (a missing critical event, an unknown economic buyer, an unquantified pain) scores high. A signal that confirms something you already knew scores low, even if it looks impressive on a dashboard. The score answers one question: how much does this move the deal?

Where should buying signals be surfaced for reps?

In the CRM the rep already lives in, which for us means HubSpot. The signal, the reason and the next move should appear as a task or property on the account or deal, in the flow of the rep's normal work. Signals that live in a separate dashboard get ignored. The whole point is to remove the step where the rep has to go looking.

What is the most common mistake teams make with buying signals?

Collecting them with no system to act on them. Sourcing signal is the easy part. The work is scoring it against a method, deciding the single next move, and surfacing that move where the rep works. Most "signal-based" setups stop at collection, which is why the rep's day never actually changes.

Can you automate the whole signal-to-action loop?

Most of it, yes, but human-executed at the sharp end. Capture, scoring and surfacing the next move can run automatically. The move itself, the email, the call, the personal note to a champion, is still better done by a rep with judgement. The system's job is to make sure the rep is always working the right account on the right thing, not to replace the selling.