Buying Signals Examples: 24 Real Ones, Each With a Reply

The most useful buying signals examples are the ones you can see before a conversation exists: a founder commenting "we're replacing our CRM in January" under someone else's post, a job ad for the role that would use your product, a question in a community asking which tool to pick. Below are 24 examples sorted by where you see them, each with the exact wording or event, a strength rating with the reason, one check to run first, and the reply it earns.

What counts as a buying signal, in one line

A buying signal is one observable action by a specific person or company that shows they are moving toward a purchase. A market trend is not one. A company that fits your profile is not one. Someone at that company doing or saying something recent and specific is. The lesson on what a buying signal is has a three-question test; this page assumes the definition and gets to the examples.

The ratings below use three words. Strong means the person named the problem or the purchase themselves. Medium means the action points at the problem but could have another explanation. Weak means it narrows timing or budget without naming a need. The rating is never a reason to skip the check next to it.

The 24 buying signals examples at a glance

All example wording on this page is illustrative. None of it is a quote from a real prospect.

Thirteen of the 24 are strong or medium and either public or first-party, which is why most small teams get more from reading other people's posts than from buying a company-level intent feed.

Buying signals you can see in public before any conversation (1 to 8)

These are the ones a founder or a two-person sales team can act on today with a free account, which is why they come first.

1. A post describing the problem you solve. Example wording: "Third month in a row our outbound reply rate dropped. Anyone fixed this without hiring more SDRs?" Strong, because the person named the pain. Check: open their profile and confirm they hold a role that owns the budget for that problem; a junior person venting is context, not a signal. Reply: answer the question in the comments first, with no link, then message them two days later referencing your comment.

2. A comment asking for tool recommendations. Example wording: "Which tool are people using for this now?" under any post in your category. Strong, because they asked for a shortlist in public. Check: read the post above the comment to confirm the category is yours, not an adjacent one. Reply: a message naming two options including yours, with one sentence on when each is the wrong choice. Being fair is what gets you a reply.

3. A comment under a competitor's post that complains or compares. Example wording: "We tried this for six months and the data was stale" or "How does this compare with X?" Strong, because the person named a vendor and a gap. Check: look at their last few posts to make sure they are a user and not the competitor's partner or employee. Reply: ask what they needed the data for; do not mention your product until they answer. The guide on tracking who engages with competitor posts covers how to see these comments without scrolling all day.

4. A question in a community or subreddit. Example wording: "Small agency, 8 clients, what do you use to find prospects who are actually in-market?" Strong, because the asker will read every reply. Check: the thread's date. Questions older than a few weeks have usually been answered. Reply: answer in the thread with specifics and no link; the direct message comes only if they ask.

5. A job ad for the role that would use your product. Example event: a listing for an SDR, a demand-gen manager, a recruiter, whoever would sit in front of your tool. Medium, because the budget is real but the hire may be the whole solution. Check: whether the listing names tools or tasks you replace. Reply: message the hiring manager, not the recruiter, with one line on what the new hire's first month looks like with and without your product. The weekly routine for hiring signals has the search operators.

6. A new hire into the role that owns your category. Example event: a new head of sales, head of marketing, head of people. Medium, because new owners review their stack, but typically after they have learned the old one. Check: how long they have been in the seat. In the first month they are listening; after the first quarter they are deciding. Reply: in month one, a congratulations with one useful observation about their new company's public activity and no ask. Come back later with the ask.

7. A funding round with a stated plan. Example event: a seed or Series A announcement whose post says what the money is for. Weak on its own, because money is not a need. It becomes medium when the stated plan names your problem ("hiring our first sales team"). Check: the founder's own post, not the press release, which is where the plan is usually spelled out. Reply: congratulate, then ask one question about the plan, not about your product. The difference between this and a signal is explained in what a trigger event is in sales.

8. A former customer moves to a new company. Example event: someone who used your product at their last job starts a new role. Medium, because the preference is known but the new company's situation is not. Check: whether the new company matches your profile at all; a champion at the wrong company is a friend, not a lead. Reply: a message that asks about the new role before it mentions the product they already know.

Buying signals on your own site and in your product (9 to 14)

These are first-party and precise, and they only ever cover people who already found you. That is their limit, not a flaw.

9. Repeat visits to your pricing page. Example event: three visits from the same company in a week. Medium, because someone is costing you out, but a single visit can be a competitor or a job seeker. Check: whether the company is identified and whether anyone from it has replied to anything. Reply: if you have a named person, a short message offering the number they were looking for. If you only have a company, do nothing yet; add it to the watch list.

10. A trial started. Medium. Browsers and buyers both start trials. Check: what they did in the first session. Connecting an account or importing data is a buyer; opening the dashboard once is a browser. Reply: to the buyer, a message that asks what they are trying to get done this week; to the browser, nothing but the onboarding emails.

11. A teammate invited into the trial. Strong, because the person is now selling you internally. Check: the invitee's role; a manager invited is stronger than a peer. Reply: offer a 15-minute call for both of them, framed around the manager's question, not a product tour.

12. A demo or quote requested. Strong and explicit. Check: the free-text field. "Just looking" and "need this before our renewal on the 30th" are both demo requests with very different timing. Reply: within the hour if you can, with the first available slot and the one question whose answer will shape the demo.

13. Integration or security documentation opened. Example event: your API docs, a SOC 2 page, a data-processing page. Medium, because this is a fit check that usually comes late, but it is also what a competitor's engineer reads. Check: whether the same company has any other signal on this list. Alone, it is a note; with number 10 or 12, it is a late-stage deal. Reply: send the specific document they were looking for before they ask.

14. A second person from the same company signs up. Strong, because a group is forming around a decision. Check: whether both are in the same team or the second is from procurement or IT, which says the decision is further along. Reply: a message to the first person asking whether it would help to loop in the second.

Buying signals in replies to your outreach (15 to 18)

Replies are the cheapest signals to read and the most commonly misread. "Interested, send more info" is not on this list because it is usually polite closure.

15. A reply with a question about how it works. Example wording: "Does this work with HubSpot?" Medium, because a question shows interest and not yet a need. Check: whether the question is about fit (an integration, a language) or about outcome ("would this find agencies in Germany?"). Outcome questions are closer to strong. Reply: answer in two sentences, then ask what they would do with the answer.

16. A reply naming a deadline or budget. Example wording: "We have budget approved for Q1 and want this running by February." Strong, because they told you the timing. Check: nothing before replying; check the details on the call. Reply: propose the call in the same message with two time options.

17. "Not now, try me in Q1." Weak, because it is a real date with no stated need. Check: whether they said why (a renewal, a hire, a launch). With a reason, it is medium. Reply: thank them, ask what changes in Q1, and set a reminder for the first week of that quarter, not the last.

18. A reply forwarding you to a colleague. Example wording: "This is Maria's area, copying her." Medium, because routing is not refusal and the colleague may own the budget. Check: the colleague's role before you write. Reply: a fresh message to the colleague that references the handoff in the first line and asks one question specific to her role.

Verbal buying signals on a call (19 to 24)

Most ranking pages cover only these, and HubSpot's list of phrases that signal a prospect is ready to buy has more call wording in the same categories. They are strong because they come late, which also means they are not where a small team finds new pipeline.

19. Asks what the price or contract looks like. Example wording: "Is this monthly or annual?" or "What would it cost for three seats?" Strong, because the purchase is on the table. Check: whether they are comparing against a competitor's quote; ask directly. Reply: give the number clearly, then ask which option fits the way they buy.

20. Talks as if they already own it. Example wording: "I'd have Jonas run this for the EU accounts." Strong, because mental ownership precedes signing. Check: whether Jonas exists and will be on the next call. Reply: ask to include him.

21. Asks what happens if it fails or if they cancel. Example wording: "If this doesn't work in the first month, what happens?" Strong, because risk questions come after the yes-in-principle. Check: what "doesn't work" would mean to them, so the answer is about their definition. Reply: state the cancellation terms plainly and the first-month milestone you would measure against.

22. Volunteers what their current vendor gets wrong. Example wording: "Our current tool flags everyone who follows our competitor, which is useless." Medium, because the need exists but a decision to switch may not. Check: the contract end date, which decides whether this is a deal this quarter or next year. Reply: ask what the vendor does well too; a prospect who only complains sometimes just wants a better price from the vendor they have.

23. Asks for the next step or who else should join. Example wording: "What do you need from us to move forward?" Strong, because they are driving the process. Check: whether the people they want to bring in include whoever signs. Reply: a written next-step list in the follow-up email, three items at most.

24. Takes notes or asks you to repeat a point. Weak. It shows attention, not intent, and an evaluator comparing five vendors takes notes on all five. Check: which point they wrote down; that is the one to follow up on. Reply: send that specific point in writing the same day.

Which look-alikes are not buying signals?

Five things appear on other lists and fail the test of being a specific, recent action by a person who named a need. To their credit, Clearbit's 15 examples rate content engagement and downloads as low, and Common Room's list says a single low-strength signal may be noise; both still keep them on the list.

• A like on your post. Attention for a second, from anyone, for any reason. It is a reason to look at the profile, not a reason to message.
• A follow of your company page. Followers include job seekers, competitors, and people who liked one post.
• A content download. Someone wanted the checklist. That is all you know.
• "Interesting, send me more info." Polite closure in most cases. Treat it as weak at best and ask one question instead of sending the deck.
• Firmographic fit alone. The right size and industry tells you who could buy, never who is buying this month.

Our own playbook counts 12 buying signals worth chasing and 8 to ignore, with a script for each of the 12; the full list is in the Buying Signal Playbook.

How do you score buying signals before you act?

Three questions sort any example on this page in under a minute. Did a named person act, or only a company? Did they name the problem or the purchase, or only something adjacent? Did it happen this week? Two yes answers mean message them today. One yes means watch for a second signal. Zero means you have context for a message you have not yet earned.

Stacking matters more than any single rating. A pricing-page visit (9) is medium. A pricing-page visit from a company whose head of sales commented under a competitor's post last week (3) is a deal to work this afternoon. The article on how to qualify leads before outreach turns this into a five-minute check you can run on every signal.

Reading the public signals by hand is the part that does not scale past a handful of accounts: when you want signals 1 to 3 caught across the competitors and keywords you choose and scored against your ideal customer profile, LinkedIn intent signals do that watching for you and hand you the ranked list.

What we measured when we ran the public signals on ourselves

When we launched, we ran our own LinkedIn signals and AI SDR on ourselves instead of a cold list, targeting founders who were posting about cold outreach burnout, which is signal number 1 on this page. The result was 14 qualified demos in 14 days with zero manual outreach, and a reply rate 4x our previous cold campaigns. Most of those leads came from signals caught in real time rather than from any list we had built.

The honest limit: that was LinkedIn only, and it worked because our buyers describe their problem in public. If yours do not, the first-party signals (9 to 14) and reply signals (15 to 18) carry more weight, and the public ones become a supplement.

What to do this week

Pick the three examples from the table that your buyers actually produce, write the reply for each before you need it (the LinkedIn message templates for buying signals cover the public ones), and spend 20 minutes a day reading rather than sending. If you want to see who is producing signals 1 to 3 for your category right now, try the AI; it shows matching buyers without an account, so you can judge the quality of the signals before you decide anything.

FAQ

What are examples of buying signals?

Buying signals examples include a public post describing the problem you solve, a comment asking for tool recommendations, a job ad for the role that would use your product, repeat visits to your pricing page, a teammate invited into a trial, a reply naming a deadline, and a call question about price or contract terms. Each is a specific, recent action by a named person or company.

What are verbal buying signals?

Verbal buying signals are things a prospect says, on a call or in writing, that show they are moving toward buying: asking about price or contract length, talking about the product as if they already own it, asking what happens if they cancel, and asking for the next step. They are strong because they come late, after the prospect has already decided to evaluate you.

What are negative buying signals?

Negative buying signals are actions that show the prospect is not moving: not replying, declining to share a budget or a timeline, saying they are still looking at other options without naming criteria, and never bringing anyone else into the conversation. One of them is a reason to ask a direct question; several together are a reason to stop chasing and set a reminder.

How many buying signals do you need before reaching out?

One strong signal from a named person is enough: a comment asking for recommendations or a reply naming a deadline earns a message today. Medium signals usually need a second one from the same person or company before you write. Weak signals such as a funding round or a "try me later" go on a watch list rather than into a sequence.

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

A trigger event is a change in a company's situation, such as a funding round or a new executive, that often precedes buying. A buying signal is one action by a person that points at a purchase, such as asking which tool to pick. Trigger events tell you where to look; buying signals tell you whom to message and what to say.

How fast should you respond to a buying signal?

Respond while the signal is still true. A public question or a demo request is answered the same day, because the asker is reading replies now. A job ad or a new hire gives you weeks. A "try me in Q1" gives you until the first week of that quarter. The rule is to reply before the person has solved the problem another way.