The topics your buyers research, the companies surging on them this week, the people behind the surge and the posts that reveal it, delivered as standing watches and a digest that names who to call and why. The infrastructure under intent intelligence, run by autonomous AI agents.
Topic, company and contact: what is being researched, who is researching it and which person to reach, with a timeline on each.
Intent alongside hiring, funding, technology, news, relationships, growth and leadership moves, on the same accounts.
A ranked summary of the accounts that moved, why and who to reach, posted to Slack or the CRM on the schedule you set.
Standing watches and digests are free; only the company and contact lookups they trigger bill.
The dashboard says an account is "hot" and the rep has no idea on what topic, since when or who at the company is doing the reading. A number without a reason is hard to act on and easy to ignore.
Intent in one tool, hiring in another, funding in a newsletter, posts in a feed. The account that is surging on your topic, hiring a RevOps lead and just raised looks like three unrelated alerts.
Someone checks the intent tool on Fridays, exports a CSV and sends it to the team. If Friday is busy, the surge from Monday is discovered the following week.
The intent topics that describe what your buyers research, suggested from your site and ICP, confirmed by you, and used as the standing definition of "interested" across every watch.
The companies surging, rising or steady on your topics with a week-by-week timeline, joined to hiring, funding, technology and news on the same account so one surge becomes a story.
Contacts at each surging company matched to the topic, plus posting-based intent where a person wrote about the problem, verified through a waterfall of licensed sources.
Your target accounts, your CRM segments or your whole ICP watched on a schedule, with a ranked digest of what moved and who to reach delivered to Slack, the CRM or a sheet.
The agents propose intent topics from your site and ICP; you keep, drop or add. Competitor names and category terms count as topics.
A target list, a CRM segment, the whole ICP or the open market on your topics. Suppression removes customers and open deals from the alerts.
Each run pulls the companies moving on your topics with their timeline and joins the other signal families on the same accounts.
Contacts matched to the topic at each moving account, posting-based intent added, emails verified before they count.
Accounts ranked by fit and signal strength, a digest written with the topic, the timeline and the person to reach, posted where the team reads.
Intent stage and topic written to the CRM as properties, contacts staged as a batch and drafts held for the rep, after one approval.
Every Monday, the ICP accounts that surged on your topics last week ranked by fit, with the topic, the timeline, the other signals on the account and one verified contact each, posted to Slack.
Your target accounts watched on a schedule, intent stage and topic written to HubSpot as properties after approval, so views, sequences and routing key off who is researching.
Companies researching a competitor by name, joined to any stack change or relevant hiring, with the person behind the research found and verified.
Contacts on open opportunities watched for posts about the problem you solve, so the rep sees the champion write about the pain the same week and follows up with the post in hand.
| By hand | With AstroFabric | |
|---|---|---|
| What you see | A score | Topic, stage, timeline and the person, with reasons |
| Context | Intent alone | Joined to hiring, funding, stack and news on the same account |
| People | Account-level only | Contacts matched to the topic, verified |
| Cadence | A Friday export | Standing watches with a digest on your schedule |
| Where it lands | A dashboard nobody opens | Slack, the CRM as properties, drafts for the rep |
| Cost | A platform seat per user | Watches free; only lookups bill |
ICP accounts surging on your topics ranked by fit, other signals joined, one verified contact each, posted to Slack every Monday.
Target accounts watched, intent stage and topic staged as HubSpot properties after approval, contacts added where a surge has a person behind it.
Companies researching a competitor by name, joined to stack and hiring changes, the researcher found and verified, drafts staged in Lemlist paused.
Three of a hundred. The full playbook library ships in every workspace, and anything you can describe becomes a mission.
Watches, feeds and digests run inside the credit ceiling and bill only the lookups they trigger. Writing intent properties or contacts into the CRM is staged for a person to approve.
Customers, open opportunities and the workspace suppression list are removed from digests unless you ask for them, so the team reads new opportunity.
Each account in a digest shows the topic, the timeline and the other signals that ranked it, so a rep can judge the alert before acting on it.
Intent, posting and people data come from licensed providers. The agents never scrape member networks.
The layer that turns buyer-intent data into something a rep can act on: topics mapped to your category, the companies surging on them with a timeline, the people behind the surge verified, all joined to hiring, funding, technology and news on the same accounts and delivered as standing watches and digests.
From licensed providers that observe research activity across the web by topic, plus posting-based intent where a person publicly writes about the problem. The agents join both to firmographics and other signals through a waterfall of licensed sources. No member networks are scraped.
Often, yes. Buying-intent data at the contact level identifies the people matched to a topic at a surging account, and posting-based intent adds anyone who wrote about the problem. Both are verified before they count and ranked first in the digest.
A list of accounts, a CRM segment or your whole ICP that the agents check on a schedule for intent and every other signal family. Each run produces a ranked digest of what moved and stages any CRM update for approval. Watches cost nothing to keep; only lookups bill.
Every account in a watch is resolved to a canonical domain, and intent, hiring, funding, technology changes, news and leadership moves are attached to that same record with dates. A surge that coincides with a new RevOps role and a round ranks above a surge alone.
To Slack, to a Google Sheet or into the CRM as intent stage and topic properties on each account after approval, with contacts and drafts staged for the rep. The API, MCP server and CLI return the same ranked accounts as JSON for your own agents.
Watches, feeds and digests are free. Intent lookups are a few credits per company and a verified contact is a few credits, shown before the run. Misses on contact finding cost nothing, every rate is shown in the console before a watch is saved, and plans start at $49 per month.
Confirm the topics. The first digest names the companies surging this week and the people behind it, and the watch keeps running.