What Is a Buying Signal? Types and How to Detect Them

What a buying signal actually is

A buying signal is an event. Not a score, not a demographic, not a feeling. A thing that happened on a real day, to a real person, at a real company \u2014 one you can name in the first sentence of your outreach without sounding like you read a template back to the buyer.

Three words do the heavy lifting in that sentence. Specific \u2014 "Sarah just joined Acme as VP Sales on April 8" is a signal; "Acme is probably in market" is not. Recent \u2014 the usable window is under 14 days, the sharp window is under 7. Tied to a decision-maker \u2014 a new SWE hire at the target account is not a signal for a sales-ops tool. A new VP Sales is.

The definition is useful because it gates out the noise. Three concrete scenarios. (1) A rep sees "Acme is hiring for a RevOps Lead" on LinkedIn. Specific, recent, tied to a role your product supports \u2014 a real signal. (2) A rep sees "Acme grew headcount 12% this quarter." Specific-ish, lagged, tied to nobody. Not a signal. (3) A rep sees "Acme is in our ICP." Not an event. Not a signal at all \u2014 it is a list criterion.

Reps who lead their first touch with a real buying signal hit reply rates of 8 to 15%. Reps sending templates to static ICP lists sit under 2%, with deliverability decaying week over week as engagement drops. The signal is the difference between an outbound motion that compounds and one that gradually becomes spam.

Why buying signals matter more in 2026 than ever

Three things happened in the last 24 months and all three push reps toward signals, away from spray. First, AI lowered the cost of sending from roughly $0.10 per personalized email (with a human writer) to almost zero. Everyone can now send 10,000 "personalized" emails a week. The buyer\u2019s inbox did not get 10,000 times wider. The signal-to-noise ratio collapsed.

Second, deliverability tightened. Google and Microsoft rolled out stricter bulk-sender rules in 2024 \u2014 SPF, DKIM, DMARC, one-click unsubscribe, complaint-rate ceilings under 0.3% (Google bulk-sender guidelines, 2024). A rep on a saturated list watches open rates crash inside a quarter. A rep on a signal-led list stays clean because every touch has a reason.

Third, the buying committee expanded. Gartner\u2019s B2B buying research has put the average committee at 6 to 10 people (Gartner, 2024). Every committee member takes their own path to research. The timing of a signal \u2014 "VP was just hired, first 60 days is the window" \u2014 is the only thing that picks the right door, on the right day, for the right contact.

Concrete scenario. Two reps, same territory, same ICP, same product. Rep A picks 20 accounts by firmographics and sends a weekly sequence. Rep B picks 20 accounts where a buying signal fired this week and writes one email per account with the signal in the first line. Rep A books 1 meeting. Rep B books 4\u20136. The difference is not the copy; it is that Rep B has a reason to write each email and a reason for the buyer to open it.

The 3 types of buying signals: first, second, third-party

Not all buying signals carry the same weight. The taxonomy below is the one every rep should carry mentally before they open their prospecting tab. The type tells you how much evidence you already have \u2014 and how much work the outreach has to do to earn the reply.

First-party signals are the cleanest because the buyer already touched your asset. A pricing-page visit from a named account is permission to reach out fast \u2014 the work you still have to do is be faster than the inbound AE queue. Reps who respond to pricing-page visits inside an hour see conversion rates 7\u00d7 higher than reps who wait until the next business day, per Harvard Business Review\u2019s classic lead-response study (Oldroyd, 2011, still the most-cited benchmark).

Second-party signals are public but buyer-originated \u2014 a LinkedIn post about the pain, a podcast comment, a complaint about a competitor. The buyer named the problem on the record. Your job is to acknowledge the specific post, add a non-obvious perspective, and ask one small question. Second-party signals reward reps who read, not reps who scrape.

Third-party signals are the biggest source of volume \u2014 funding rounds, exec hires, job postings, G2 intent, tech-stack changes \u2014 and the easiest to over-index on. Every rep with Crunchbase access gets the same funding alert you do. The differentiator is the ICP-fit gate: a Series B round at a company that will never buy your product is a waste of your morning. Run firmographics before the scoring rubric, not after.

Explicit vs implicit buying signals

The second axis is intent visibility. Explicit signals state the intent. Implicit signals imply it. Most reps miss the difference and write the same email for both \u2014 which is why same-day explicit signals get buried in a batch queue and same-day implicit signals get over-asked ("want to hop on a 30-minute demo?" after one LinkedIn post).

Rule of thumb. On an explicit signal, lead with the ask and make it easy to say yes \u2014 "you were on pricing yesterday, want the 10-minute version before the AE routes you?" On an implicit signal, lead with relevance and make the ask small \u2014 "noticed the raise; most teams in your stage hit [pain] in the first 90 days; worth a 12-minute conversation in the next two weeks?"

The single highest-ROI move most reps miss: treat an explicit signal as time-critical. A same-day reply to an inbound signal converts at roughly 5\u20137\u00d7 the rate of a next-day reply (Oldroyd, HBR). A Slack notification, a rule that pages the owning AE, and a 2-line email template are the difference between "we got 48 inbound signals last quarter" and "we booked 18 meetings from them."

9 buying signal examples that drive reply rates

Nine signals cover roughly 85% of the buying events a B2B rep will see in a given quarter. Reply-lift figures below come from Gangly internal rep data (Q1 2026, n = 1,180 rep-sends, paired with ICP-matched cold-sequence baselines). Your numbers will move with category and ICP, but the ranking order is stable across every cohort we have measured.

Three things to notice. First, the top two (past champion, new VP) are relationship or role signals \u2014 they work because the buyer already has a reason to care. Second, funding and hiring sit in the 4\u20135\u00d7 band \u2014 meaningful but they need a concrete pain map to clear the "congratulations email" trap. Third, pricing-page visits score lower in the table than you might expect \u2014 not because intent is weak, but because speed eats the lift within an hour. Same-day pricing-page response converts at 5\u20137\u00d7 cold; next-day converts at under 2\u00d7.

Deeper treatment of the seven high-volume signals is in buying signals in B2B sales, and the full outbound playbook built around signal-first targeting lives in the signal-based selling playbook.

The 4 attributes every real buying signal has

A signal has to clear all four gates below before it earns a spot in today\u2019s queue. Three out of four is not enough \u2014 the missing attribute is usually where the reply dies. Run the four checks before you write the first line. It takes 30 seconds and saves the 12 minutes you would have spent writing a dead-on-arrival email.

• 01

  Recency

  Under 14 days is the usable window. Under 7 days is twice as strong. Past 30 days, it’s historic data — use it for context, not as a lead-in.

• 02

  Role match

  Tied to a decision-maker or direct influencer, not a random employee. A new SWE hire is not a buying signal for a sales-ops tool. A new VP Sales is.

• 03

  Intent depth

  Maps to a decision (hire, funding, switch, post about the pain) — not a shallow action (a like, a page view with no follow-through, a company mention on the radio).

• 04

  Pain map

  The signal must map to a concrete pain your product fixes. A company opening a Singapore office is not a buying signal for a CRM. It is for a payroll tool.

The most skipped gate is the pain map. Reps act on any hire, any round, any post \u2014 because the CRM alert fired. But a hire for a Head of Design is not a signal for a sales-intelligence tool. A round at a 4-person pre-PMF startup is not a signal for an enterprise data-governance platform. The rep who asks "what pain does this event make live?" before writing cuts the dead sends out of their day.

How to detect buying signals (the 5-source stack)

Five sources cover 95% of useful buying signals for a B2B SaaS rep. None require a six-figure data budget. What they do require is the discipline to check them every morning \u2014 the rep who checks signals before the 9am coffee books 3\u20134\u00d7 more meetings than the rep who checks signals at 4pm when the day\u2019s prospecting slot has already been burned.

A practical sequence for the first week. Day 1: connect the CRM and set up saved Sales Navigator searches for the top 10 personas in your ICP \u2014 job-change filter on, past-90-days. Day 2: subscribe to Crunchbase daily updates for your industry segments. Day 3: set BuiltWith or Wappalyzer alerts for the 5 tech categories your product integrates with. Day 4: add a pricing-page visit webhook that pings Slack with the company name. Day 5: stack signals \u2014 if the same account fires two sources in a week, promote it to same-day outreach.

Common detection mistakes: (1) monitoring too many sources at the start \u2014 five is enough, pick two to master first; (2) no de-duplication \u2014 one account with three signals in a week is one account, not three meetings; (3) treating LinkedIn scraping as detection \u2014 it is data, not a signal, until a rep scores it against ICP and pain.

How to score and rank buying signals

Scoring is the step most signal programs skip. Without it, every signal looks equal and the rep spends an hour on a score-40 account that should have been a 10-minute watchlist entry. The 5-factor rubric below is the one we run inside Gangly. It is simple on purpose \u2014 a rubric the rep cannot hold in their head at 8:47am on Monday is a rubric the rep will stop using by Wednesday.

Worked example. A new VP Sales is hired at a 200-person Series B SaaS company in your exact ICP, 6 days ago, and their predecessor was a ghosted champion from 2024. Score: recency 3 (under 7 days) \u00d7 full + role match 2 \u00d7 full + intent depth 2 \u00d7 full + ICP fit 2 \u00d7 full + prior relationship 1 \u00d7 full = a clean 90. That is a same-day phone call, not a queued email. Meanwhile, a 30-day-old LinkedIn post about a tangentially related pain at a 30-person company adjacent to your ICP scores a 22 and belongs on the watchlist.

The scoring does two jobs. It tells the rep when to act, and it tells the rep how much to invest per touch. A score 85 earns a 15-minute research block and a phone dial. A score 45 earns a 3-minute email and a LinkedIn connect. The instinct to treat every signal like a score 85 is the fastest way to burn a rep\u2019s morning and end the week with 40 unread replies and 2 meetings booked.

When to act on a buying signal (and when to wait)

Speed is the part of signal-based selling with the steepest payoff curve. The half-life of a hiring or funding signal is measured in days, not weeks. By day 7 of a VP-hire signal, four to six competing reps have typically reached out and the buyer\u2019s inbox has saturated. By day 14, the signal is historic context, not a reason to email today.

The rough rule. Signals scored 80+ get same-day outreach \u2014 inside 24 hours, ideally inside 4. Signals scored 60\u201379 get touched within 48\u201372 hours. Signals scored 40\u201359 get a one-touch this week. Signals under 40 go on a 14-day watchlist and only move if a second signal fires. Internal Gangly rep data (Q1 2026) shows reps who follow this cadence book 3.4\u00d7 more meetings per signal than reps who batch their signal queue into a Friday afternoon block.

Two exceptions are worth knowing. First, on an executive-hire signal, the window is actually 30\u201360 days long \u2014 new leaders need roughly four weeks to take stock before they start committing budget. Day 7 outreach is welcome; day 1 outreach can read as "congratulations-spam." Second, on a funding signal, the 30-day window opens for hiring pushes but the 12-month window is where the budget actually lands \u2014 a follow-up at day 60 with a fresh angle often beats the flood of day-1 congratulations emails.

The rep playbook: signal to outreach in under 10 minutes

The gap between "I have a signal" and "I sent the email" is where most signal programs die. The playbook below takes the rep from raw signal to sent outreach in under 10 minutes \u2014 the rhythm that turns signal-based selling from a quarterly initiative into a daily habit.

1. 01

   Verify the signal

   Open LinkedIn or the source. Confirm the event, the date, and the person. If the signal is older than 14 days, stack it with a second signal or pass.

2. 02

   Score it

   Run the 5-factor rubric. Write the number at the top of the draft. A 74 and a 32 do not get the same treatment.

3. 03

   Find the second buyer

   One contact is a thread. Two contacts is a conversation. Pull the second buyer from LinkedIn — usually the boss, the peer, or the champion.

4. 04

   Draft the first touch

   Name the signal in the first sentence. Name the pain in the second. Make the ask small — a one-screen summary, not a 30-minute demo.

5. 05

   Send and log

   Send from the rep’s inbox, not a sequencer. Log the signal, the score, and the touch in the CRM — so next week’s signal stacks cleanly on top.

Before / after. Without the playbook: "Hi Sarah, congrats on the new role. Would love to show you our platform \u2014 are you free for a 30-minute demo next week?" Generic. No signal-specific reason. Asks for 30 minutes on a cold first touch. Reply rate: under 2%.

With the playbook: "Hi Sarah \u2014 saw you joined Acme last week. Most new VP Sales I work with look at pipeline visibility inside the first 60 days; a peer at [company] ran the same playbook and caught $1.2M stuck in stage-3 limbo. Worth a 12-minute conversation in the next two weeks, or too early?" Specific. Signal in line one. Concrete proof. Small ask, time-bounded. Reply rate in our data: 14%.

Full walkthrough of the prep block is in the 5-minute call prep workflow. Fast-dial version in research any prospect in under 5 minutes.

Common mistakes reps make with buying signals

Five mistakes account for roughly 80% of failed signal programs. None of them are about copy or cadence. All of them are about discipline at the signal step itself \u2014 the 60 seconds before the rep opens the email draft.

1. 1

   Treating every signal the same

   A new VP hire and a like on a LinkedIn post are not equivalent. Score first. Route second. Write third.

2. 2

   Acting on signals older than 14 days

   The half-life is short. By day 14, 4–6 other reps have already reached out. Stack with a fresh signal or pass — do not lead with a stale event.

3. 3

   Skipping ICP fit as a gate

   A funding round at a company that will never buy you is not a buying signal. Run the firmographic check before the scoring rubric.

4. 4

   Batching signals into a weekly cadence

   Weekly cadence on time-sensitive signals is a way to miss every one. Reps who touch hot signals the same day book 3–4× more meetings than reps who batch.

5. 5

   Leading with the signal only

   The signal is the hook, not the pitch. Pair it with the pain and the proof. "Saw the raise" without a reason to care reads like flattery, not relevance.

The meta-mistake under all five: confusing "I have a data source" with "I have a signal." A firehose of LinkedIn job-change alerts is not a signal program \u2014 it is a noise problem. A signal program is the discipline of filtering that firehose through ICP fit, recency, role match, intent depth, and pain map \u2014 then acting, fast, on the accounts that survive. The rep who applies the filter wins the account. The rep who drinks from the firehose drowns.

Buying signals vs intent data vs lead scoring

Three terms get used interchangeably and they should not. Buying signals, intent data, and lead scoring solve related but different problems. Reps who treat them as synonyms waste budget on tools that answer a question they are not currently asking.

How they fit together. Intent data narrows the territory \u2014 "these 120 accounts are researching our category this month." Buying signals pick the day \u2014 "these 11 of the 120 had an event this week that makes today the day to send." Lead scoring handles the inbound queue \u2014 "when this form is filled, route to this AE based on fit + behavior." A team running all three is playing a different game than a team running one.

Where reps go wrong is using intent data as the outreach trigger. An account-level intent score does not tell you which contact cares, what they care about, or whether a real event happened. It tells you a company is warm-ish. That is useful for a list pull. It is not enough to open an email with.

How Gangly turns buying signals into booked meetings

Gangly runs the five-source detection stack, scores every signal on the 5-factor rubric, and hands the rep a ranked morning feed \u2014 then drafts the first-touch in the rep\u2019s voice, tied to the signal, before the rep opens their inbox. The rep reads, edits, sends. Nothing leaves the tool without a rep click.

• Signal Detection \u2014 watches CRM, LinkedIn, news feeds, job boards, and web visits. Scores each account on recency, role match, intent depth, ICP fit, and prior relationship.
• Outreach Writer \u2014 takes the signal plus 5 of the rep\u2019s past sent messages and drafts a signal-led first touch. Rep reviews and sends; nothing auto-sends.
• Workflow Sequencer \u2014 connects the signal to the rest of the rep\u2019s day: call prep, live coaching, post-call notes, CRM sync. One motion, not six tabs.

Full pricing lives at /pricing. Seats start at $99/month with a 14-day free trial and no credit card. Related reading: buying signals in B2B for the how-to companion, the signal-based selling playbook for the full outbound motion, and what is an AI sales workflow for how signal detection fits into the bigger pipeline.

Frequently asked questions