Buying signals examples for SDR managers: what every account your SDRs own is living through

Buying signals examples fall into six groups by source: research intent, website visits, job changes and hiring, funding and news, technology installs, and what an account sends its own customers. The first five suggest an account may be ready to buy; the sixth, such as a welcome email that stopped, shows the exact step a vendor’s product would fix, with a date, and only the account’s customers see it. Obsession keeps what each account you name sends its customers, dated with the email or screenshot, by API, MCP (the standard way AI agents call tools) or a table.

Buying signals examples fall into six groups by source: research intent, website visits, job changes and hiring, funding and news, technology installs, and what an account sends its own customers. The first five suggest that an account may be ready to buy. The sixth shows the exact step a vendor’s product would fix, with a date and a screenshot, and only someone signed up to the account sees it.

An SDR manager’s week turns on which accounts get a first line today and what that line says. Every group has its place in that decision. The sixth usually ranks first for a vendor whose product touches what its prospects’ customers see, such as an email and SMS platform, a help desk, a checkout or an identity provider. It names the problem in the account’s own emails, texts and support replies.

Buying signals meaning, and signal based selling

A buying signal is a dated event at an account that makes a conversation with a vendor more likely to be welcome now. In B2B sales the event is about the company. It might be researching a category, hiring for a team, raising money or changing a tool. It might also be failing its own customers at a step another company sells a fix for.

Signal based selling means an SDR team works the accounts that show a signal first and opens each email on the signal itself. It turns a territory list into a daily queue, and it changes the first line from a compliment to a fact the prospect recognises.

A signal earns a first line when it passes three tests. It is specific to this account, so no other company would receive the same email. It has a date, so the SDR can say when it happened. It ties to the problem your product solves, so the next sentence follows from it.

Buying signals examples from intent, visits, hiring and funding

Most sales teams use similar data, from contact databases and intent tools to Exa’s search of the public web. Each provider is strong at its own part of the job.

• Research intent. Intent data records which companies are reading about a topic across many websites. Bombora says its Company Surge data “reflects real research across 14B+ monthly events and 5M company domains”, drawn from a data co-op of publishers, brand sites and data providers. G2 Buyer Intent captures activity on G2 itself: product and category page views, competitor comparisons and pricing page visits. G2 says that lets a seller “see who’s researching you, your category, or your competitors”.
• Website visits. Dealfront names the companies visiting a team’s own website. It shows “the companies behind your traffic, scored by ICP fit and intent”, where ICP means ideal customer profile, with page views, time spent and gated content requests.
• Job changes and hiring. UserGems lists more than 30 native signals, among them job changes, contact-level intent, website visits, M&A and hiring, and says its Gem-E learns from a team’s open opportunities and closed-won deals. Hiring itself is public on each account’s careers page and on job boards.
• Funding and news. Crunchbase tells sales teams to “anticipate private company funding and growth, and reach high-fit accounts before the window closes”, and says it monitors 39 billion live private company signals.
• Technology installs. BuiltWith covers more than 128,309 internet technologies and builds lists “using tech signals, spend, and lifecycle events”, so an SDR can see which accounts run the platform next to theirs.
• Public web research. Exa calls itself “The world’s data for AI agents”, says it searches “the largest index of public web and private information” and lists GTM intelligence among its strengths. Exa says its FindAll tool finds more of the companies and people that match a list-building query, which suits building and researching a list in one call.

Each of these reads what an account researches, publishes, installs or announces. None of their pages describes signing up as the account’s customer and keeping what the account sends. Teams on the same feed see the same surge or funding round on the same morning, so their first lines sound alike. Obsession vs Exa sets out what Exa holds and what sits behind a sign-up.

B2B buying signals in what an account sends its customers

The second family of signals comes from the account’s own customer experience: the emails, texts, codes, trial messages and support answers it sends the people who sign up. These sit behind a login wall, any step a site puts between a visitor and what it shows customers, so search crawlers and intent feeds don’t collect them. For a vendor whose product runs that step, each one is the prospect’s problem in the prospect’s own words, with a date.

1. A welcome email that stopped

• What it means. A welcome series is the set of automated emails a company sends a new subscriber, starting with a welcome that often carries a first-order code. When nothing arrives, every new subscriber that week meets silence.
• Who it matters to. Email and SMS platforms, deliverability tools and the agencies that build flows.
• How an SDR opens. “I signed up to your list on Monday to see your welcome emails, and nothing had arrived by Wednesday, though the form said ‘Check your inbox’. I kept the screenshots if your team wants to trace it.”
• How to check it by hand. Sign up with an inbox used for nothing else, confirm the sign-up if asked, check spam and Promotions, and log every email with its arrival time for 7 days.

The gap is common. In a test Joy Joya published in July 2026, fresh email addresses and phone numbers were signed up to 362 ecommerce brands. Of those brands, 158 (43.6%) never sent a welcome email, and 53 (14.6%) never sent the text they promised. It also costs money. In Klaviyo’s 2026 benchmarks, automated flows, the triggered flows such as a welcome series and cart reminders, “generate nearly 41% of total email revenue from just 5.3% of sends”.

2. A cart reminder gone quiet after a site change

• What it means. An abandoned cart email goes to a shopper who left items in a basket. A relaunch, a new theme or a new checkout often breaks the trigger, and the brand sees it only as a quieter recovery line weeks later.
• Who it matters to. Email and SMS platforms, cart recovery tools, and checkout and payment providers.
• How an SDR opens. “I left a basket on your new site last Monday and no reminder came in 48 hours. The week before the relaunch, the same basket got one in an hour. Worth a look before Black Friday on the 27th?”
• How to check it by hand. Give an email address at checkout, leave a basket and wait 48 hours. Note what changed on the site and when; a new checkout platform also shows up in BuiltWith’s list of the technologies a site runs.

Rejoiner studied 1,000 direct to consumer brands for a report published in February 2025. It found that 68% of abandoned carts triggered a follow-up email, and that 40% of brands sent the first one within an hour. A reminder that stops after a relaunch moves a brand from the first group to the second without anyone deciding it.

3. Texts that never come after an opt-in

• What it means. The sign-up form asks for a phone number and consent to texts, then no text follows. The account pays for the opt-in and gets nothing from it.
• Who it matters to. SMS platforms, messaging APIs and the email platforms that sell texts beside email.
• How an SDR opens. “I ticked the text box when I joined your list 10 days ago, and no text has come yet, though the emails arrive fine. Is the SMS side still being set up?”
• How to check it by hand. Opt in with a number used for nothing else, send it a control text from another phone to prove it receives, and wait 7 days.

4. A trial that goes silent after day 1

• What it means. A software account’s trial sends a welcome, then nothing: no prompt to invite a teammate, connect data or reach the step where users usually upgrade.
• Who it matters to. Onboarding and product adoption tools, lifecycle email for software companies, and in-app messaging.
• How an SDR opens. “I started a trial of your app on the 2nd. The welcome email came within a minute, then nothing for 9 days, not even a nudge to invite a teammate. Is that the onboarding you planned?”
• How to check it by hand. Start a trial with a work address you control, use the product once, then log every email and in-app message by trial day for 14 days.

5. A new sending platform

• What it means. The account’s emails now come from a different email platform. For the platform it left, that is a lost account; for every tool that plugs into the new one, it is the month integrations get chosen again.
• Who it matters to. Deliverability tools, and the review, loyalty and SMS apps that connect to an email platform.
• How an SDR opens. “I’m on your list, and your emails have come from a new platform since 9 November. Teams usually reconnect reviews, loyalty and texts in the month after a move. Is that on the list for this quarter?”
• How to check it by hand. Open two of the account’s emails a few weeks apart. In Gmail, click More beside Reply, then Show original, to see the full header. Compare the d= domain in the DKIM-Signature line and the Return-Path, the address bounces go back to; between them they often name the platform that sent the email.

Gmail’s help page shows the steps to open a full header. DKIM is a signature checked on arrival, and its standard, RFC 6376, defines the d= tag as the domain “claiming responsibility for an introduction of a message into the mail stream”.

6. A checkout code refused

• What it means. The welcome email or the pop-up promises a code, and checkout rejects it, often on a subscription or a sale item the offer didn’t exclude in writing.
• Who it matters to. Checkout and payment providers, promotions tools and loyalty programmes.
• How an SDR opens. “Your welcome email gave me a 15% code last week, and checkout rejected it on the subscription option, while one-off items took it. Want the screenshot of the error?”
• How to check it by hand. Sign up for the code, add an item, enter the code at checkout and stop before paying. Try a one-off item and a subscription, because codes often treat them differently.

7. Support slower than it promises

• What it means. The help page promises a reply within a set time, and the reply takes longer, or the chat answers wrongly.
• Who it matters to. Help desk software and AI support agents.
• How an SDR opens. “I asked your support team a delivery question on Monday at 10:00, and the reply came 31 hours later. Your help page says 24. Is the queue busier than usual this month?”
• How to check it by hand. Ask one plain question through the site’s help form or chat, and time the reply against the promise on the help page.

8. A sign-up that fails on a phone

• What it means. Account creation works on a laptop and breaks on a phone, often at a verification or one-time code step, so new customers drop there.
• Who it matters to. Identity, verification and onboarding providers.
• How an SDR opens. “I tried to create an account on my phone last week, and the verification step sent me back to the start twice. It worked on a laptop. Have you seen drop-off at that step?”
• How to check it by hand. Create an account on a phone and on a laptop with an address you control, and screenshot each step until the account is open or the step fails.

Every opener follows the same four parts, so an SDR team can write its own for any signal. The parts are when you saw it, what you saw in a customer’s words, the step it touches, and one question the prospect can answer in a line. Each opener says the SDR signed up, which keeps the fact true and the tone friendly. Our guide to cold email first line examples gives more of them, grouped by what each vendor sells.

How to rank buying signals in sales

An SDR manager’s queue holds more signals than reps have hours, so the order decides the week. Four rules sort it.

1. Fit first. A signal at the step your product runs outranks a sign of general activity. An email platform’s best signal is a welcome series that stopped; a help desk’s is a reply that missed its promise.
2. Proof second. A signal with a date and a screenshot an SDR can quote outranks a score the SDR can’t explain to the prospect.
3. Freshness third. Research intent and site visits describe a week of activity. A customer-facing gap lasts until the account fixes it, so re-check it weekly and stop writing the week it closes.
4. Stack them. An account with a customer-facing gap and research intent in the same month goes to the top of the queue, and the gap goes in the first line.

The same signals time other moves too: sales trigger events examples covers when to start a sequence, and Clay custom signals covers putting each one in a column your router reads.

How to check customer-facing signals by hand

A team can run this with an inbox, a spare phone and a shared sheet, starting with 20 accounts this week.

1. Pick the signal that matches your product

Choose one or two signals from the template that sit at the step your product runs. That means welcome and cart emails for an email platform, texts for an SMS platform, support replies for a help desk, and the sign-up on a phone for an identity provider. Fewer signals checked properly beat many checked once.

2. Give each account its own inbox and number

A separate address and phone number per account means every message arrives labelled. Use addresses and numbers your team controls, and never enter details that aren’t true.

3. Set off the journey and screenshot each step

Sign up, opt in to texts, leave a basket, start a trial or ask support a question, as the signal needs. Stop before any payment. Screenshot each step with the time on screen.

4. Set the window and log what arrives

Decide in advance how long counts as missing: an hour for a welcome email, 48 hours for a cart reminder, 7 days for texts. Log every message in one row per check.

5. Read the headers once a month

Open one email per account each month with Show original and note the DKIM d= domain and the Return-Path. A change from one month to the next is the new sending platform signal, dated to the first email that shows it.

6. Re-check before anyone writes

Run the check again the day before an SDR sends. A gap that closed is no longer an opener, and a line about a problem the account already fixed costs more trust than it earns.

7. Work out the hours

Each account takes about 25 minutes a month: the sign-up and opt-in, a basket or a trial, logging what arrives, a header check and a weekly re-check. Multiply by the accounts your SDRs own.

The same sum gives 208 hours a month for 500 accounts and 42 hours for 100. By hand, the method holds for 20 to 50 priority accounts. Past that, it needs an inbox and a number per account, kept open for months, with every email and screenshot saved and every gap re-checked before a rep writes.

Obsession collects what companies show only to customers, step by step: their screens, emails and texts, member prices, trial limits, quotes and cancel offers, each dated with a screenshot. Teams and AI agents look up any company through the API or MCP, and a company not yet covered is added on request. For sales teams, it keeps each of these customer-facing signals for every account you name, every morning, from the welcome email and the cart reminder to support replies and the platform behind each email. Prospect intelligence writes each fact, its date and a screenshot link back to the same rows in Clay, your CRM or a sheet. Exa gives reps and their agents the public web in one call; Obsession gives them what an account shows only to its customers, and an agent can call both. Start with the 50 accounts your SDRs most want to win, so you can see what it does to reply rates, meetings booked and opportunities.

Buying signal sources compared

Each option reads a different source of signals, and many teams combine several. We make Obsession, so every other option is described from its provider’s own pages as of 11 November 2026.

For what each account sends its own customers, use Obsession. It keeps every welcome, cart and trial email, text, checkout code, support reply and sending platform, dated, for every account you name and for as long as you follow it. Bombora and G2 show which accounts are researching your category, and Dealfront shows which companies read your own pages. UserGems tracks job changes and other people signals, BuiltWith shows the tools a site runs, and Exa gives an agent the public web in one call. By hand covers 20 to 50 priority accounts well.

Limits and next steps

• One profile sees one customer’s view. A new UK subscriber on a phone sees what the account shows new UK subscribers on phones. Record the profile, the country and the device with every signal.
• A quiet email counts as missing only once its window closes. Set the window per signal before the check starts, and re-check before an SDR writes.
• Checks stop before payment. Signals that need a real order, such as a delivery email, stay with your own customers’ feedback.
• Software trials come with terms. Read them before starting a trial for research, and use it as a prospect would.

Once an account becomes a customer, the same outside view becomes an early warning. Churn risk indicators covers that for customer success teams, and external account signals puts each change on the account in your CRM. Start with one signal that matches the step your product runs, check it at 20 accounts this week, and write first to the ones with a dated gap. Sales intelligence from behind the login shows the same view for every role on a revenue team, with an example for each.

Frequently asked questions