Glossary · Targeting and signals

What are buying signals?

The short answer

Buying signals are clues that a company or a prospect may be ready to buy: at the account level, observable changes such as a first sales hire, a new leader or a funding round; in a conversation, cues such as questions about pricing or timing. Sales teams use them to decide whom to contact now and what to say.

Updated
Read
4 min
Written by
Antoine Blitz
On this page8 sections
  1. Real data
  2. What are examples of buying signals?
  3. Why do job postings make good buying signals?
  4. Is a job posting the same as an account?
  5. Buying signals vs intent signals: what is the difference?
  6. How do you track buying signals at scale?
  7. Related terms
  8. Questions people ask

Real data

Hiring signals in this month's job postings

Four hires that often come before a purchase, counted across US job postings from the last 30 days. Then the companies behind one of them, once confirmed staffing agencies are set aside.

Returned by the BlitzAPI API on

POST/v2/jobs/search

US job postings from the last 30 days, by title

Sales Development Representative
2,328
Founding Account Executive
155
Head of Revenue Operations
26
Founding Data Engineer
15

One request per title, read from total_results. A posting counts when its title holds every word of the searched title, in any order. Postings from staffing agencies and from vendors are included.

POST/v2/company/tam-by-jobs

Who posted the Founding Account Executive roles, confirmed staffing agencies excluded

Matching postings
112
Companies behind them
84
Of which 1–50 employees
69

Read by paging until the cursor came back empty. Each company appears once, with its number of matching postings; the size band is the one the company declares on its own page.

What are examples of buying signals?

Most buying signals fall into five families. The first four are changes at the account. The fifth happens inside a sales conversation.

Family Example What it can mean
Hiring A first Founding Account Executive, a wave of SDR roles A sales team is being built, and its tools with it
Leadership change A new Head of Revenue Operations or a new CFO New leaders review the stack they inherit
Company events A funding round, a new office, an acquisition New budget, a new region, systems to merge
Technology change New roles that ask for a tool the company did not use before A platform is being adopted or replaced
Conversation cues Questions about pricing, onboarding or contract terms The prospect is picturing the purchase

The last family is what sales trainers call verbal buying signals, and it only appears once a conversation exists. The first four tell you which conversations to start, which is why they are also called trigger events.

Why do job postings make good buying signals?

Job postings make good buying signals because they are public, dated and specific. A company writes its plans into its hiring.

A startup that posts its first Founding Account Executive role is about to build a sales process, and usually a CRM and a prospecting stack around it. A team that opens a dozen SDR roles needs data, sequences and dialers for every new seat. A first Head of Revenue Operations tends to rebuild reporting, and the tools behind it.

The counts above put numbers on it. In the 30 days through October 28, 2026, US job postings included 2,328 for Sales Development Representatives, 155 for Founding Account Executives and 26 for a Head of Revenue Operations. Broad roles are common and say little on their own. A first hire is rare, and says a lot.

Is a job posting the same as an account?

No, a job posting is not the same as an account, and the difference matters when you build a list. Set aside the postings of confirmed staffing agencies, which often recruit for clients they do not name, and 112 of the 155 Founding Account Executive postings remain, from 84 companies. Of those 84, 69 declare between 1 and 50 employees on their company page: this signal points mostly at small companies.

That step turns a signal into a list of accounts: group the postings by company, count what each one posted, then check fit. When the same company turns up in several searches, for example a first sales hire and a new RevOps leader in the same month, it moves up the list. Ranking accounts that way is account scoring, and the TAM guide calls the overlap signal convergence.

Buying signals vs intent signals: what is the difference?

Intent signals are one kind of buying signal: the kind read from research behavior rather than from public events. Both differ from fit, which says who an account is, not what it is doing.

What it shows Example Where it comes from
Fit Who the account is Software company, 200 to 500 employees, based in Texas Firmographic data and technographic data
Intent signal What its people are researching A burst of reading about CRM migration Online behavior, tied to the company by IP address or cookies
Event signal What the account just did Its first Head of Revenue Operations role, posted this week Job postings, announcements, filings

Fit decides whether an account belongs on your list at all; signals decide when to reach out. Signals without fit fill the pipeline with busy companies that will never buy. Fit without signals sends good accounts the right message at the wrong time. Intent data has its own page, with its strengths and its limits.

Which is which?

Six facts about accounts you might call this week. Which are fit, and which are buying signals?

  1. A software company with 200 to 500 employees

  2. Posted its first Founding Account Executive role this month

  3. Headquartered in Chicago

  4. Opened twelve SDR roles in the last 30 days

  5. Runs HubSpot as its CRM

  6. Its people have been reading about CRM migrations all week

Show the answers
  1. A software company with 200 to 500 employeesFitIndustry and size say who the company is; they were true last quarter and will be next quarter.
  2. Posted its first Founding Account Executive role this monthBuying signalA dated change: a first sales hire usually comes with a first CRM and prospecting stack.
  3. Headquartered in ChicagoFitA stable fact you filter on. Nothing in it says that something changed.
  4. Opened twelve SDR roles in the last 30 daysBuying signalA wave of hiring in one team is dated, and it tells you which team is growing.
  5. Runs HubSpot as its CRMFitA technographic fact about the stack. Starting to hire HubSpot admins this month would be the signal.
  6. Its people have been reading about CRM migrations all weekBuying signalAn intent signal: inferred from research rather than published, but still a dated change in behavior.

How do you track buying signals at scale?

To track buying signals at scale, write each signal as a search and run it on a schedule. Pick the events that come before a purchase of what you sell, then match each one to a source: job postings for hiring and technology changes, press releases and filings for funding and acquisitions.

For hiring, TAM by Jobs returns the companies behind the matching postings, each once, with its number of matching roles, as in the evidence above. Jobs Signal follows the postings of the accounts already on your list, so you can spot a new role at a target account. Then combine several signals per account and rank the accounts, as the TAM guide shows step by step.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on October 28, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests.

The first group counts job postings, not companies. The second pages through every result until the cursor comes back empty, with confirmed staffing agencies excluded (is_agency set to false).

Size bands are the ones companies declare on their own page, shown as returned.

Questions people ask

What does buying signals mean?

The phrase has two uses in sales. At the account level, it means an observable change that raises the odds of a purchase, such as a new hire, a funding round or a new tool. In a conversation, it means a cue from the prospect, such as a question about price, onboarding or contract length. The first tells you whom to call; the second tells you how the call is going.

What are verbal buying signals?

Things a prospect says that show they are picturing the purchase: questions about pricing, implementation time, contract terms or who else needs to sign, a request for references, a comparison with the tool they use today. Vague interest and a request to "send some information" are usually not buying signals.

What are hiring signals?

Buying signals read from job postings: a first hire in a function, a new leader, a wave of openings in one team or one region. They are public and dated, which makes them easy to automate. Their limit is reach: a company that is not hiring says nothing through this channel, however ready it is to buy.

What are customer buying signals?

The same idea applied to accounts that already buy from you: usage growing toward a plan limit, a new team adopting the product, a request for a feature from a higher tier, a new executive sponsor. Account managers and customer success teams watch them to time an upgrade or an expansion conversation.

With BlitzAPI

Put it to work

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

Count the US postings for one title (the same request runs for each title)

curl -X POST https://api.blitz-api.ai/v2/jobs/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": ["Founding Account Executive"]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "max_results": 1
  }'

API reference

List the companies behind those postings, confirmed staffing agencies excluded (page on with the cursor)

curl -X POST https://api.blitz-api.ai/v2/company/tam-by-jobs \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": ["Founding Account Executive"]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "company": {"is_agency": false},
    "max_results": 50
  }'

API reference

The same list, kept to companies with 1 to 50 employees

curl -X POST https://api.blitz-api.ai/v2/company/tam-by-jobs \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": ["Founding Account Executive"]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "company": {"is_agency": false, "size": {"include": ["1-10", "11-50"]}},
    "max_results": 50
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.