Skip to content

Buying signals examples in B2B and how to act on each

Buying signals examples by type, from funding and hiring to plan changes and support tickets, with the move each one should trigger.

Photo of Utku Zihnioglu

By

ยท CEO & co-founder

Updated Oct 16, 2026

ยท 12 min read

Worked example moved to an invented company, unsourced anecdotes restated as scenarios, product links added.

Blog cover: 7 buying signals you already own, beside the Stripe, Zendesk, and Gong logos

Buying signals examples come in three kinds. Some are public, like a Series A announced last week or three new SDR roles. Some only your own tools record, like a trial account going from six seats to eleven, or a ticket asking whether you offer SSO. The rest are said out loud on a sales call. Each one is dated and specific, and almost none of them is on the account record your rep opens tomorrow morning.

Most of what gets written about signals covers the public kind, bought from a feed that every other subscriber reads too. The kind nobody can sell you sits in billing, support, and product tools that sales rarely opens.

If you would rather see which of these your own tools already hold, connect one and score your first accounts.

How fit and intent combine into one number is covered in the guide to lead scoring. This piece stays on where each signal lives and what should happen when one fires. For one signal at a time, such as a job change, an open role, or a launch, our buyer intent signals guide says what each tells a seller and what to discard.

What buying signals mean in B2B

A buying signal is a change that makes a purchase more likely soon. The word doing the work is change. A 150-person SaaS company in your target industry is a fit. That same company posting its first RevOps job is a signal, because something moved and it has a date on it.

Fit barely moves from one month to the next. Signals decay: a funding round from last week means something different from one eighteen months old, even though both fill the same field. A LinkedIn post is the same: read its real date with the LinkedIn post date extractor before you quote it in a first line.

A quick test for any candidate signal:

  • It has a timestamp. You can say when it happened, not just that it is true.

  • It points at a problem you solve. A new CFO is a signal for a billing tool and trivia for a design tool.

  • Someone can act on it this week. If nobody would change who they call, it is a report.

"Sales signals" is the umbrella most reps use for everything above. Buyer intent signals usually means research behavior, like someone reading comparison pages or searching your category.

Intent data is narrower still: a commercial product that watches content consumption across publisher sites and sells account-level topic surges. It probably suits teams with long enterprise cycles best. Signal-based selling is the practice of timing outreach to any of these. Marketing textbooks map the whole thing onto the stages of the buyer decision process, and honestly, we would not lose sleep over which stage a given signal belongs to.

Buying signals examples by type

Sort any signal by who else can see it. Funding, hiring, launches, job changes, and stack changes are public sales trigger events. Usage, billing, and support events are recorded only by your own tools.

Type

Example

What to do this week

Funding

A Series A announced last week

Write to the budget owner before the new plan is set

Hiring

Three open SDR roles

Pitch the team being built, before the hires start

Launch

Listed on a startup board this week

Offer what a newly public team is missing first

Job change

A past champion starts at a new company

A personal note from the rep who sold to them

Tech stack

Dropped the tool yours replaces

Open on the switch, not on your feature list

Product usage

Active seats up 50% in two weeks

The account owner calls about a wider rollout

Billing

A plan downgrade after a usage drop

A retention call before the renewal date

Support

A ticket asking about SSO

The account owner raises the enterprise plan

Sales trigger events worth a same-week email

These are public events about a company, detected by someone else and sold to you:

  • Funding. New money usually turns into new headcount and new budget lines.

  • Hiring. A job post is the most honest document a company publishes. Three open SDR roles tell you what they are about to spend on before any press release does. Our guide to using hiring signals for outbound walks through finding and ranking them.

  • Launches. A startup board listing dates the week a company starts selling in public.

  • Job changes. A champion who bought from you at one company and just started at another is the warmest cold account you will ever find.

"Sales comes down to timing and to having the right data, and most of that data is already online. Years of building web scraping infrastructure showed me that."

Utku Zihnioglu, CEO of Oneprofile

All four events share one weakness: everyone else can see them too. Say a company announces its Series A on a Monday. By Wednesday its founders have a pile of congratulations emails, most of them from tools reading the same funding feed. The signal is real, but your timing advantage is gone.

A tangent, since we are here. The job-change play has been run so hard that "congrats on the new role" reads as a template the second it lands, and we suspect it will be the first signal play to stop working outright.

Buying signals examples from your own systems

Your billing system, support desk, and product analytics log signals every day, with timestamps, about accounts that already know your name. Almost none of it reaches the CRM, because each tool belongs to a different team: finance watches billing, support owns the tickets, and product owns the event stream.

How to collect them is covered in our piece on first party intent data.

Signal

Where it lives

What it usually means

Active seats up 50% in two weeks

Product analytics

The team is rolling you out wider

Hit a plan limit or tried a gated feature

Product database

The upgrade conversation is overdue

Plan upgraded or downgraded

Billing

Budget moved, and either direction warrants a call

Ticket asking about SSO, audit logs, or API limits

Support desk

Enterprise requirements are forming

Competitor named on a sales call

Call recordings

An evaluation is running whether you started it or not

Closed-lost domain starts a new trial

CRM plus product database

The deal you lost is open again

Payment failed after months of steady use

Billing

A card problem, not churn, if someone calls in time

A few of these as plays.

The SSO ticket. A 40-seat customer on your mid plan asks support whether SSO is available. Support answers, links the pricing page, and marks the ticket solved.

That ticket is the clearest expansion signal you will get all quarter. The account owner never hears about it.

The second signup. A company went closed-lost in March over timing. In August, someone new at the same domain starts a trial. Nothing joins the old deal to the new user, so the trial gets the same onboarding emails as a stranger.

The quiet downgrade. Billing records a plan change the moment it happens, and Stripe's subscription webhook events fire for it. A downgrade after a usage drop is churn risk. A downgrade the same week a new finance lead joined is a budget review, and that call needs a different opener.

The usage spike. Weekly active users on a free workspace go from two to seven. Product-led teams call that a product qualified lead, and it should move the account's score, not only the user's.

The question on the call. The sales conversation is a source of its own, and the recording keeps it. A buyer who asks any of these has started planning around you:

  • How long implementation takes, or who sets it up.

  • What the contract terms are, or whether annual billing comes with a discount.

  • Whether a colleague from security or finance can join the next call.

Send the answer in writing the same day.

What these signals have that no feed can match is exclusivity. A funding round goes to every tool with the same subscription. The ticket about SSO went to you.

Stacking buying signals into an account score

One signal on its own is a coin flip with better odds. Three, from different sources, and the account is telling you something.

Rules we would start with:

  • Score the account, not the person. The trial user, the ticket filer, and the new VP are often three people at one company, and only the account sees all three.

  • Decay every signal. Usage and tickets fade in days, funding in weeks, a job change over about a quarter.

  • Let combinations outweigh sums. A raise, a hiring push, and a usage spike together are worth more than three separate points.

  • Keep negative signals. A cancelled subscription or a month without logins should pull the score down.

  • Gate on fit first. A signal on a company you cannot serve is noise with a timestamp.

Take Cleardue, an invented company at cleardue.example. It raised a Series A five months ago and has two open SDR roles. Inside your own systems, its workspace went from four active seats to eleven in three weeks, and last Tuesday its ops lead asked support about a Salesforce sync.

Individually, each of those is a maybe. Together they score 88, and the reason attached reads "funded, hiring SDRs, seats tripled, asked about Salesforce." A rep can check every clause of that in under a minute, which is why the reason matters as much as the number.

Past a few hundred accounts, a ranking only means something if every account is held to the same standard. That is the case for scoring every account against your ICP, and for a ranked TAM list before any signal fires.

Anyway.

How to act on buying signals examples

A Slack channel of every signal fills with messages and almost no calls. Sales signals only pay off where the next action already happens, so the way to respond to a buying signal is to route each kind somewhere specific:

  • Score and reason onto the CRM record. A number reps sort by, and a sentence they read before dialing.

  • New-logo accounts above your threshold into a sequence, where the first message opens with the signal instead of a line about their industry.

  • Expansion signals from paying customers to the account owner, not the SDR queue. An SSO ticket from a customer is an upsell.

  • Negative signals to whoever owns retention, before the renewal date.

Oneprofile runs this loop. Connect Stripe, Zendesk, PostHog, Gong, or your Postgres database, and each account picks up its plan changes, tickets, usage, and calls, matched on the tool's own ID or an email address. Firmographics come from a waterfall of data sources ordered most accurate first, and a lookup that finds nothing costs nothing.

To find B2B companies by buying signals you cannot see from inside, search for companies hiring for a role, filter employers by funding, or list the companies launching on eight startup boards. You pick what to enrich before any of them are added.

AI then scores every account against your ICP and writes the reason next to the score. Both write back to your CRM, and accounts above your line can join an email and LinkedIn sequence through a saved view. An import from a connected tool refreshes on a schedule you set, and with automatic runs switched on, the score reruns for every account the refresh changed. With a daily refresh, an account that upgrades on Thursday is re-scored before Friday's call list is built.

Team starts at $20 a month for 1,000 credits, with unlimited integrations. Free gives you 200 credits a month with up to 3 integrations, 3 tables, and 100 rows per table.

One thing to try before any tool. Open your support desk, search the last 90 days of tickets for "SSO", "seats", "API" and "invoice", and count how many came from accounts nobody in sales has spoken to this quarter. That count is your backlog of buying signals nobody acted on. Get started free when you would rather it stopped being a manual search.

Do this in Oneprofile

Signals from your own tools on every account

Connect Stripe, Zendesk, or PostHog, and each account picks up its plan changes, tickets, and usage. AI then scores it against your ICP with the reason written down.

  • Stripe logo
  • Zendesk logo
  • PostHog logo
  • Gong logo

Buying signals examples: common questions

What are buying signals in B2B sales?

Buying signals are dated changes that make a purchase more likely soon: a funding round, a new hire, a usage spike, a plan change, a ticket asking about a higher-tier feature. Where fit says who could buy, a signal adds the when.

What are the main types of buying signals?

There are four: public events such as funding, hiring, and launches; changes your own billing, support, and product tools record; what a buyer asks on a sales call; and intent data, sold as topic surges. Only the middle two are yours alone.

What are customer buying signals?

They are changes inside accounts that already pay you or trial your product: active seats climbing week over week, a plan limit hit, an upgrade or downgrade in billing, a ticket asking about SSO, or a closed-lost company starting a new trial. Only your own tools record them.

How should a sales rep respond to a buying signal?

Act the same week and name the signal in the first line, so the message could not have been sent last month. Then route it by who sent it: a new account goes into a sequence, a paying customer goes to its account owner, and a downgrade goes to whoever owns retention.

Do buying signals replace lead scoring?

No. Signals are inputs to a score, not a substitute for one. A strong signal on an account outside your ICP is still a poor use of a rep's day, so most teams gate on fit first and let signals decide the order within it.

What are examples of buying signals in sales?

Examples include a Series A announced last week, a new VP of Sales in their first 90 days, three open SDR roles, seats doubling in a month, repeat pricing page visits, and a ticket asking about SSO. Anyone can see the first three. The last three live in your billing, analytics, and support tools.

About this article

Photo of Utku Zihnioglu

Utku Zihnioglu

CEO & co-founder

Serial entrepreneur who built infrastructure companies handling billions of requests. Now leads engineering at Oneprofile, which finds the people worth talking to, researches each one, and follows up until they reply.

Drafted with AI from our product docs and code. Utku Zihnioglu answers for what it says.

Put your own buying signals to work

Read plan changes, tickets, and usage beside public signals. Free gives you 200 credits a month, 3 integrations, 3 tables, and 100 rows per table.

Free plan: 200 credits a month, 3 integrations, no card

Read next

What is lead scoring? Models and examples

Put your own buying signals to work

Read plan changes, tickets, and usage beside public signals. Free gives you 200 credits a month, 3 integrations, 3 tables, and 100 rows per table.

Free plan: 200 credits a month, 3 integrations, no card

Read next

What is lead scoring? Models and examples