At any moment a small share of your market is in motion - studying the category, hiring the role that will own the purchase, raising the money that funds it, replacing the tool yours sits beside - and everyone else is not. Buying intent data and business signals are the two ways of seeing that motion from outside. Intent observes research behavior; business signals observe the events a company performs in public. Used together, scored honestly and routed to the right action, they change every downstream number in a go-to-market motion, from reply rates to audience match rates to the accuracy of an account plan.
This is the pillar for the signals cluster: what each family actually observes and what it cannot, a catalog of the business signals worth watching, the three axes for judging any signal, the combination rule that turns signals into a momentum score, the routing table that sends each signal to the action it deserves, and the standing monitor that makes all of it a weekly habit instead of a quarterly project. It reflects how the signals agent watches an account set.
Two families: intent and business signals
The word signal covers two different kinds of evidence, and conflating them is the first mistake most programs make. Buying intent data is inferred: a provider observes content consumption across a network of publisher sites or resolves research traffic to companies, aggregates it by topic, and reports that a company's interest in "contract lifecycle management" is elevated this week relative to its baseline. Nobody at the company announced anything; the signal is a statistical reading of behavior. Business signals are observed: a job posting went live, a funding round was announced, a technology appeared on the company's site, a new VP was named, a partnership was published. Each is a discrete event with a date and a source you can show a prospect.
The families complement each other precisely because they differ. Intent is early and broad - it can surface an account before it does anything public - and it is noisy for the same reason. Business signals are specific and citable, and they arrive later, once a company has committed money or headcount. A program that runs only intent chases ghosts; a program that runs only business signals arrives after the shortlist is written. The signal-based selling guide covers the selling method built on both; this guide covers the signals themselves.
Buying intent data, explained honestly
Intent data comes in three sources. First-party intent is your own: visits to the pricing page, repeat sessions from one company, a demo request. It is the most predictive and the smallest. Third-party intent aggregates research behavior across a publisher co-op or a resolved traffic network, reported by topic and company; it covers the whole market and it is where the statistical noise lives. Search-derived intent sizes the demand around a topic without naming companies at all. The buying intent data guide takes the vendor-evaluation questions in depth; the operating rules are shorter.
Read trajectory, never spikes. A single elevated week is usually one curious person; a rising, broadening pattern across topics and sessions over a window is a buying process with several participants. Treat third-party intent as a reason to look, never a fact to cite: it shapes the offer and moves an account up the queue, and it never appears in copy, because "we noticed your company researching X" reads as surveillance. And calibrate against outcomes: the topics that preceded your closed-won deals are the topics worth weighting, and the rest are decoration.
The business signals catalog
| Signal | What it reveals | Typical freshness window |
|---|---|---|
| Hiring | A funded initiative, described in the company's own words: the role, the stack, the pain | While the posting is open, plus a quarter after it fills |
| Funding | Budget appeared and priorities are being set; the follow-on hiring says where the money goes | About a quarter |
| Technology adoption | An architecture decision was made; adjacent purchases follow | Months to years |
| Technology change or removal | A tool left the stack; the replacement conversation is happening now | Weeks |
| Executive moves | New owners rebuild stacks in their first two quarters | Two quarters |
| News and expansion | Launches, new offices, new markets - context that sharpens every other signal | Weeks |
| Partnerships and relationships | Who a company integrates with, sells through and buys from - the ecosystem the deal will move in | Slow |
Hiring deserves its reputation as the most underrated family: a posting is a needs analysis the company wrote itself, searchable and dated, which is why tracking account hiring and funding signals and technographic and hiring-signal prospecting each get their own treatment. Technology change is the most time-sensitive: a tool disappearing from a site is a replacement decision in progress, and the window is measured in weeks.
Judging a signal: strength, freshness, specificity
Signals are unequal, and treating them as equal reproduces the cold-list problem with extra steps. Strength is how tightly the signal predicts a purchase in your category: a company hiring a RevOps lead is a strong signal for RevOps tooling and a weak one for most other things. Freshness is how fast it decays, and the table above shows the range - intent fades in weeks, funding stays relevant for a quarter, an adoption matters for years. Specificity is how precisely the signal names the need: "hiring in engineering" says little, while "hiring a data platform lead with a named warehouse in the requirements" names the initiative and the stack. Score all three per signal family, and score them in code, because the whole point is to compare hundreds of accounts identically.
3axes on every signal: strength, freshness, specificity
Combining signals into a momentum score
Single signals mislead. Companies hire speculatively, consume content idly, raise money and freeze it. Combinations convict: an account showing category intent and a relevant posting and a fresh raise is a different object from an account showing any one alone, because the signals are independent lines of evidence converging on the same conclusion. The scoring rubric weights strength, freshness and specificity per family, sums converging signals with a bonus for independence, and decays every term on its own clock, so the score this week reflects this week.
Routing each signal to an action
The second mistake programs make is routing every signal to the same action, usually a cold email. Different signals deserve different responses, and the response should match what the signal says about the company's state.
| When you see | Route to | Because |
|---|---|---|
| A fresh, specific posting | Outreach, with the posting as the opener | Public, professional, recent evidence supports a direct reference |
| A rising intent trajectory | A matched audience, and a watch for a business signal | Interest without a citable event is best met with ads, then timed outreach |
| A funding round | An account plan and a two-week wait for the follow-on hiring | The raise says money exists; the hiring says where it goes |
| A rival's technology adopted | Suppression for now, a watch for renewal-window signals | The decision just happened; the next window is a year out |
| A technology removed | Immediate outreach and a displacement audience | The replacement conversation is live this month |
| An executive arrival in the owning function | Account plan refresh, outreach in the second month | New owners audit first, then buy |
Two of those routes reach outside the sales motion. Audiences are where intent belongs while it is still unciteable: the matched and custom audiences guide covers how a signal-qualified list becomes an ad audience. Account plans are where funding and executive moves belong, and the company and person data guide covers what an account plan is built from.
Standing monitoring: the watch and the digest
Every signal family is available to your competitors, so the advantage goes to whoever acts while the signal is young. That is an argument about cadence, and it rules out the quarterly project. The standing shape has three parts. A watch: a named account set - the ICP list, the open opportunities, the customers up for renewal - and the families to monitor for each. A sweep: weekly for postings and technology change, daily for intent trajectories and news, event-driven for funding and executive moves, each sweep scoring what changed against the rubric and deduplicating against what was already reported. A digest: the ranked movers, with the evidence and the routed action, delivered where the team already talks - a Slack channel, a Telegram thread, an email on Monday morning - with the option to say "take 3 and 7" and have the outreach or the audience built from the thread.
The digest is the product of the whole program. A signal that reaches a channel nobody reads is a signal that decayed unused, which is why delivery belongs in the design and never as an afterthought.
How AstroFabric does it
The signals agent runs the standing watch. Give it an account set - a persistent list, a CRM segment, a CSV - and the families that matter, and it monitors intent topics, hiring, technology adoption and change, funding, news, executive moves and relationships, scores the movers on strength, freshness and specificity, and pings the channel when something moves, with the evidence attached to every row. Digests land in Slack, Telegram or email on the cadence you set, and each mover carries its routed action: the prospecting agent builds the list, the personalization agent writes the first touch from the signal, the audience agent shapes the matched audience, the company intelligence agent refreshes the account plan.
Every write into a CRM, outreach tool or ad account passes an approval gate, every sweep runs under a credit ceiling enforced before the spend, and the audit log records why each account moved. The AI agents for business signal monitoring and agentic AI for intent pages map the two halves of the motion.
Go deeper in this cluster
- Technographic and hiring-signal prospecting: the complete guide - The two public signals that name a company’s stack and its next initiative, how to read each, the matrix that combines them into a ranked list, and the weekly machine that turns the list into verified people with an evidence-first opener.
- Buying intent data: sources, quality and how to act on it - What intent data actually observes, the quality questions vendors hope you skip, trajectory versus spikes, and the routing patterns that turn signals into pipeline instead of dashboards.
- Tracking account hiring and funding signals: strategy in public - Postings and raises are companies describing their plans on the record. How to read hiring shape, interpret funding behavior, and turn both into the momentum read that times outreach and account plans.
- AstroFabric vs Common Room: signals from your own community or signals across the whole market - Common Room stitches signals from your community, product and web presence into one person-and-account graph for sellers. AstroFabric watches the whole market for hiring, funding, technology and intent signals and runs the data work behind them as agent missions. The honest map, with September 2026 pricing.
Frequently asked questions
What is the difference between intent data and business signals?
Intent data infers interest from research behavior aggregated by topic and company; it is probabilistic and early. Business signals are observed events a company performed in public - a posting, a raise, a technology change, an executive move - each a fact with a date and a source. Programs need both.
What are the strongest business signals?
Converging combinations beat any single family. Among individual signals, a specific job posting is the workhorse because it is a needs analysis the company wrote itself, and a technology removal is the most time-sensitive because the replacement conversation is happening within weeks.
How should intent data be used in outreach?
As a reason to look and a way to shape the offer, never as a fact to cite. Intent moves an account up the queue and points it at an audience or a watch; the message itself references public, professional evidence such as a posting or an announcement.
How fresh does a signal need to be?
It depends on the family: intent trajectories decay in weeks, postings matter while open plus a quarter, funding stays relevant for about a quarter, executive arrivals for two quarters, technology adoptions for years. Score freshness per family and decay every term on its own clock.
How often should signal monitoring run?
Weekly for postings and technology change, daily for intent trajectories and news, event-driven for funding and executive moves, with a digest delivered where the team already talks. Anything slower forfeits the freshness that is the entire edge.
Can signal monitoring run without a data team?
Yes. A signals agent sweeps every family on schedule, scores the account set identically, deduplicates against what was already reported and delivers the ranked digest with routed actions, while a person approves the writes that follow.
Sources
- Gartner - the B2B buying journey research behind multi-stakeholder buying groups
- Ehrenberg-Bass Institute - the 95-5 framing of how much of a market is in motion
- Crunchbase - the funding-data reference most watches read
Every playbook on this blog ships as a runnable mission.
Open a workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, on your plan's monthly credits.