What counts as a B2B buying signal?
Your ideal customer profile tells you which companies could buy. A buying signal tells you which of them have a reason to buy now. It is an event: someone at the company asked for a tool, complained about a vendor, posted a job, announced a round, shipped a product. Something changed, and the change created a need or a budget.
Three tests separate a signal from noise. It is recent, measured in days or weeks, not years. It is verifiable: you can link to it and read it yourself. And it connects to your offer: a new head of marketing matters to a web design agency and means nothing to a payroll tool.
Some things look like signals and are not. Awards and press about strong growth make headlines without creating a purchase. A topic surge from an intent data provider is related but different: it says an account is reading more than usual about a subject, not that anyone stated a need. The intent data guide covers that difference in depth.
Which buying signal fits your offer?
Start with the signal whose middle column describes the moment your best customers were in when they bought.
| Signal | What it tells you | Act on it if you sell… |
|---|---|---|
| Competitor complaints | The company pays for your category and its current tool is failing it | A product or service that replaces a named competitor |
| Alternative seekers | The decision to leave is made; the shortlist is still open | A product that meets the requirements they list, with a clear migration path |
| Tool recommendation requests | A stated need and no vendor yet | Software or services a team can try quickly |
| Product launches | A team just shipped, and its next problems are about to land | Growth, design, video, development or sales help for young products |
| Hiring signals | Money approved for a problem, with its future owner described in the job post | Tools or services that help the new hire succeed, or cover the gap until they start |
| Funding signals | Fresh budget and a stated plan for it | Offers that match what the round pays for: hiring, product, go-to-market, compliance |
| Tech stack changes | Vendors and partners around a system are being chosen | Competing tools, integrations, migration or implementation work |
| Business expansion | A new office, region, segment or product line creates new purchases | Local services, IT, legal, HR, localization and suppliers |
| Pain-point posts | A business problem described before anyone has shopped for a fix | A solution to a process problem that you can explain plainly |
| New companies | A founder is choosing a stack, services and advisors | Accounting, legal, design, development and early-stage tools |
Not sure where to start? Six questions that pick your first signal
Answer these in order and stop at the first yes.
Do your buyers already pay for a competitor?
Start with competitor complaints and alternative searches. The budget exists and the category needs no explaining. The incumbents you beat most often become your search terms.
Can a team start using what you sell within a week?
Watch tool recommendation requests. Posters usually want an answer within days, which suits quick-to-adopt software and small service packages, not a six-month rollout.
Do you sell to companies in their first year?
Follow launches and new companies. Founders are choosing tools, advisors and providers, and early choices tend to stay.
Is your offer bought when a team grows?
Use hiring, funding and expansion, which show a budget and often the person who will own the purchase. Recruiters, HR software, IT, legal and accounting firms fit here.
Does your offer depend on a system the buyer runs?
Track tech stack changes. A migration reopens choices about competing tools, integrations and implementation partners.
Do you fix a process problem people describe but rarely shop for?
Read pain-point posts. The path to a meeting is longer, so this suits consultants and automation agencies who can explain the fix in two sentences.
How close to a decision is each signal?
Signals fall into two families. Conversation signals are things people write: a request, a complaint, a question, a description of a problem. Company events are things organizations do: hire, raise, launch, expand, migrate, incorporate. The first family is more explicit and goes stale faster. The second is easier to verify and lasts longer.
Among conversation signals, the order matters. A pain-point post describes a problem but asks for nothing, so the burden of tone is entirely on you. A tool request asks for help but names no vendor. A competitor complaint comes from someone already paying for the category. An alternative search is the furthest along: the person has decided to leave and is building a shortlist.
Company events speak to budget and ownership rather than stated intent. A job post names the problem and the person who will own it. A round says the money exists. A launch, an expansion, a stack change or a new company each say that a set of decisions is about to be made.
How long does each signal stay useful?
These response windows are starting points to test in your market, not fixed rules.
| Signal | First contact | A second good moment |
|---|---|---|
| Competitor complaint | Within 24 hours, before the vendor fixes the issue or the thread picks someone else | A few weeks before the renewal, if the post names a date |
| Alternative search | Within 24 hours; most answers arrive in the first day or two | A short note later, since switching projects often slip |
| Tool recommendation request | Within 24 to 48 hours; many posters choose within the week | Only when the post names a later deadline |
| Product launch | Within 48 hours: the day after launch, not during it | Two to four weeks later, once real numbers are in |
| Hiring | The week the role goes up | Around the new hire's start date |
| Funding | Soon after the news, tied to the stated plan | Four to eight weeks later, when hiring has started |
| Tech stack change | 24 to 48 hours for an open evaluation; early in a migration | One to three months after the move |
| Business expansion | Within a few days of the announcement | Four to six weeks before the stated opening |
| Pain-point post | Within a few days; 24 to 48 hours if a deadline is named | One respectful follow-up a few weeks later |
| New company | Within days of appearing; the first few weeks are still early | At the next milestone: a launch, a first hire, a round |
Reach companies with a reason to buy this week
Startories finds the buying signal, verifies the decision-maker and runs the outreach until they book a call.
Where can you watch for each signal yourself?
Search by hand for a week before you automate anything. You will learn how often the signal appears in your niche and what a good instance looks like. Replace the brackets with your own competitors, tasks and roles.
| Signals | Where they show up | A search to try by hand |
|---|---|---|
| Competitor complaints, alternative searches | Reddit, X, niche communities, review sites | On Reddit, "alternative to [competitor]" or "[competitor] pricing", sorted by new; on X, the competitor's name with "switching" or "cancel" |
| Tool requests, pain-point posts | Reddit, X, industry forums and communities | "what do you use for [task]", "any recommendations for [category]", "[task] takes us hours every week" |
| Product launches, new companies | Product Hunt, startup directories such as the Y Combinator company directory and BetaList | Today's launches in your categories; new listings that show a team and a working website |
| Hiring | Company careers pages, job boards, Wellfound for startups | The role that would own your problem, plus phrases such as "first hire" or "build the function" |
| Funding | Announcements, founder posts, Form D filings in SEC EDGAR full-text search | Form D filings from the last two weeks, then a check of the company's own site and news |
| Tech stack changes | Job posts, public changelogs, integration pages, DNS records | "migrating from [tool]" or "experience moving off [tool]" in job descriptions |
| Business expansion | Press releases, company news pages, local job posts | "opening our [city] office", or job posts in a city where the company had no staff |
How do we judge a signal before anyone gets an email?
Every signal page describes the same chain of checks, adapted to its trigger. Most of the work is deciding what not to send.
Classify the event
Is this a real request, complaint or announcement, or a joke, a reseller's pitch, an employee venting about their employer, or a writer collecting tools for a listicle? The type decides the angle and the urgency.
Check the date
Search results resurface threads from years ago. When a signal happened matters more than how high it ranks.
Tie it to a real company
Use public business details: a company named in the post, a linked website, a stated employer. If no company can be identified with confidence, drop the signal rather than guess.
Score it against your profile, with reasons
Check size, industry, region and use case, then write down why the lead was kept, for example "30-person agency, US, asked for a reporting tool, deadline this month". Written reasons let you correct the targeting when it drifts. The lead scoring guide turns this into a points model.
Find the person who decides
The person who posted is often a user, not the buyer. Identify who owns the budget, and verify their business email before anything is sent.
Write about the situation
Name the event plainly and lead with something useful, not with the fact that you noticed it. The cold email templates are organized by trigger.
When is one signal not enough?
Some signals are strong on their own. Others say "could buy" and need a second piece of evidence before they say "should hear from you now". Stack them when the first signal is common or vague.
| Combination | What the second signal adds | Example offer |
|---|---|---|
| Funding plus hiring for the role you serve | Proof that the money is going to your problem | A recruiting agency, or a tool for the new team |
| Expansion announcement plus local job posts | Proof that the move is real and staffed | IT setup, local legal or HR services |
| Complaint plus a named renewal date | A deadline, and a second moment to write | A competing product with a migration plan |
| Launch plus a directory listing with a team | A real business behind the product | Growth or development help for a young team |
| Stack change plus a new technical hire | An owner for the migration | Implementation help or an integration |
| Pain-point post plus an identifiable company | A buyer you can verify and reach | A consulting or automation project |
Which signals should you keep after the first month?
Run two or three signals for a month with the same profile and offer, then line them up on the same ratios. The numbers are invented for one example seller, a reporting tool sold to marketing agencies.
- Complaints booked the most meetings per company emailed, although only about a third of them (50 of 140) could be tied to a company. The fix is speed: 30 hours is slower than the 24-hour window above.
- Tool requests booked the same three meetings, and half of them (45 of 90) led to a company, so the funnel is easier to feed. Keep it.
- Hiring tied every post to a company, since job ads name the employer, but few needed a reporting tool that month. Narrow it to the role that owns reporting, or drop it.
- Sample size. Three meetings against one gives direction, not proof. Run a second month before you abandon a signal.
| Step | Tool requests | Competitor complaints | Hiring |
|---|---|---|---|
| Signals found | 90 | 140 | 60 |
| Tied to a real company | 45 | 50 | 60 |
| Passed the ICP check | 30 | 22 | 24 |
| Decision-maker verified and emailed | 27 | 20 | 20 |
| Positive replies | 5 | 4 | 2 |
| Qualified meetings | 3 | 3 | 1 |
| Meetings per 10 companies emailed | 1.1 | 1.5 | 0.5 |
| Median hours from signal to first email | 20 | 30 | 72 |
Is it fair to use public posts? Etiquette and compliance
Public does not mean fair game. These rules keep you on the right side of the law and of the people you write to.
- Stay out of the thread. Do not pitch in community replies, and do not send private messages on Reddit or X to people who did not ask. Startories does not post, comment or send direct messages; it emails a verified business address.
- Write to businesses, about business problems. Drop consumers, students and hobbyists, and be careful with sole traders, whom some privacy laws treat as individuals.
- Do not quote people back to themselves. Describe the situation ("you are moving off your current help desk") instead of pasting their words. It reads as help, not surveillance.
- Leave bad news alone. A breach, a layoff or a lawsuit is not an opener.
- Follow the email rules. In the US, the CAN-SPAM Act requires accurate headers, an honest subject line, a physical address and a working opt-out (FTC compliance guide). Startories puts an opt-out in every email and suppresses unsubscribed contacts across all campaigns.
- Respect the sources. Startories uses official APIs and compliant sources where they exist, and keeps a link to the original signal so you can check what triggered each lead.
How do you turn signals into a steady pipeline?
Pick one signal with the six questions above, pair it with one ICP and run it for a month; a narrow funnel answers faster than a broad one. The buying signals guide lists 15 examples if you want more options, and signal-based outbound explains the approach end to end.
Startories runs the loop for you. It watches Reddit, X, Product Hunt, startup and industry directories and search results built for your niche, and classifies twelve kinds of signal: someone looking for a tool, a complaint about a competitor, a search for an alternative, a recommendation request, a launch, hiring, funding, a tech stack change, an expansion, a pain point, a new company and interest in your category. Then it qualifies, verifies, writes and sends.
The homepage shows three funnels built this way: a launch funnel that reaches founders within 48 hours of a Product Hunt launch, a competitor switchers funnel that writes within 24 hours of a complaint, and niche search prospecting that delivers a steady weekly flow. Starter includes one intent source, Growth several, Scale all of them. See plans and pricing, or read about Reddit lead generation if your buyers talk there.
Frequently asked questions
What are B2B buying signals?
Recent, public events that suggest a company may need what you sell now: a request for a tool, a complaint about a vendor, a job post, a funding round, a launch, an expansion. They tell you when to reach out, while your ideal customer profile tells you who.
What is the difference between buying signals and intent data?
Intent data usually aggregates research activity into a score per account. A buying signal is a single event you can link to and read, such as a post asking for a tool. Intent helps you rank a list; a signal gives you a specific reason to write today.
Which buying signal is the strongest?
Usually the most explicit ones, such as an alternative search or a tool request, because the buyer said what they need. Strength still depends on your offer: a funding round matters more to a recruiter than a complaint about a CRM.
How fast should I act on a buying signal?
Conversation signals such as complaints and requests go stale within a day or two, so aim for 24 to 48 hours. Company events such as hiring, funding and expansions stay useful for weeks and often deserve a second, well-timed message.
Is it legal to email a company because of a public post?
In the US, B2B email is allowed when it follows the CAN-SPAM Act, including a working opt-out. Other countries have stricter rules, especially for individuals. Write to business addresses about business needs, and check the rules of each region you target.
Does Startories reply to posts on Reddit or X?
No. Startories does not post, comment or send private messages on any platform. It uses public posts as signals, ties them to a company and emails the verified decision-maker, keeping a link to the original signal for your reference.