Hiring-signal prospecting
Companies in your ICP that posted the roles your product relieves this week, the executive who owns the pain identified and verified, the posting quoted on the record.
Describe who should buy and agents identify the companies by firmographics, technology, hiring, funding, similarity or location, find the right people, verify how to reach them, and deliver a scored list into your CRM, sheet or outreach tool.
Firmographics, technology, hiring, funding, similarity to your best customers or a map radius, combined in one objective.
The qualifying signal, the fit score and the reasons ride on every row into the CRM.
A contact lookup that finds nothing costs nothing; only found, verified rows bill.
Every write into a CRM, sequence or ad account waits for a person; research never does.
Industry and headcount filters find companies that looked right last year. The account that just became a fit, because it raised, hired or switched tools, is invisible to a static filter.
Company search here, people search there, verification somewhere else. Three exports and a VLOOKUP before anyone makes a call.
A rep opens the record and sees a name. The reason it qualified, the signal, the fit, lives in a spreadsheet column that did not survive the import.
Firmographics, technology in use, active hiring, recent funding, similarity to your best customers, or a map radius, combined in one objective.
Titles, seniority and department resolved to named people, with work emails and direct phones found and verified before the row counts.
Fit scores against the ICP you described, duplicates removed against your CRM, customers and competitors held out.
The list lands in the CRM, the sequence tool or the sheet with the qualifying signal and the score on every row.
A sentence with the industries, size, stack, roles, countries and titles, or nothing at all: the workspace ICP already holds them.
Companies matched by firmographics, technology in use, hiring, funding, lookalike similarity or location, then filtered by the ICP.
Titles, seniorities and departments resolved to named people at each account, with a reference the next step can buy details for.
Emails and phones found through licensed sources and verified before they count; risky addresses held aside and labeled.
Fit scores with reasons, duplicates merged against the CRM, customers and competitors suppressed, role accounts removed.
A persistent list you can refresh, exported as CSV or pushed into the CRM, sheet or sequence tool after a one-click approval.
Companies in your ICP that posted the roles your product relieves this week, the executive who owns the pain identified and verified, the posting quoted on the record.
Ten reference accounts expanded to two hundred companies that share their size band, stack and buying signals, scored for fit and deduplicated against the CRM.
Companies that adopted a complementary or competing product in the last thirty days, with the person most likely to own it, so the pitch lands while the decision is fresh.
Every business of a category in a city with a 4.5 rating and a website, resolved to a domain, with an owner or manager contact found where one exists.
| By hand | With AstroFabric | |
|---|---|---|
| Building the list | Three tools, a spreadsheet and a morning | One objective, a few minutes of agent time |
| Why-now | Guessed, or skipped | The signal that qualified the account, dated, on every row |
| Contact quality | Pattern guesses and old exports | Waterfall-found emails, verified before they count |
| Fit | Whoever matched the filter | Scored against your ICP, with reasons |
| Cost of a miss | Paid whether or not it was found | Free; only found rows bill |
| Delivery | CSV upload, column mapping, duplicates | Approved push into CRM or sequence, deduped |
Companies posting the roles that signal your problem, the buyer verified, pushed to the CRM with the posting quoted.
Three best accounts as the seed, a hundred companies that look like them, scored and explained.
Fifty agencies running a specific pair of technologies, founders verified, delivered as a CSV with the highlights posted to the channel.
Three of a hundred. The full playbook library ships in every workspace, and anything you can describe becomes a mission.
Where the company came from, which signal qualified it, when the email verified: answerable on every record.
Lists land as approval batches with the exact records shown until you enable autonomous writes.
Every run states its cost first, reserves against your ceiling, and charges only for the fields a source actually filled.
In a sentence, the way you would to a new SDR: the industries, the size, the technology they run, the roles they are hiring, the countries, the titles you sell to. The Prospecting Agent turns that into searches, crosses the signals and reports what it excluded and why, so you can tighten the description in plain language.
The agent composes and iterates searches from an objective, crosses results with live signals a static database does not hold, verifies contacts, deduplicates against your CRM and delivers with evidence. The workflow around the search is the product, and it ends inside the tools your team uses.
Every mission states its estimated cost before it runs and reserves it against the ceiling you set. Paid sources are charged only when they fill a field, so a two-hundred-row list costs what it resolves, and the ledger shows every credit and the source it went to.
Hiring for specific roles, funding rounds, technology adoption or replacement, buying-intent topics, news such as launches and expansions, leadership changes and similarity to your best customers. Any of them can seed a list or attach to rows as the why-now, with the source and date recorded.
Emails are found through a waterfall of licensed sources and checked by a verifier before the row counts; catch-all and risky addresses are held aside and labeled. Direct phones are found where a licensed source has one and checked for validity. A lookup that finds nothing costs nothing.
In a persistent list you can refresh and export, and, after a one-click approval, in HubSpot, Pipedrive or Attio as contacts and companies, in Lemlist or Instantly as a paused campaign, or in a Google Sheet. The console, the REST API, the MCP server and the CLI read the same list.
Yes. Any prospecting mission can run as a standing schedule, weekly or daily, adding newly qualified accounts, dropping ones that no longer fit and reverifying contacts, with the delta posted to Slack or the CRM. Suppression and deduplication run on every refresh, so the list never re-adds a customer.
Yes. Every capability is a tool on the REST API, the MCP server and the CLI, so an outbound agent you already run can ask for the twenty best-fit accounts from a list as JSON, with signals and verified contacts attached, under a scoped key and the workspace ceiling.
The first verified prospecting list minutes after signup.