A weekly machine from signal to opportunity: accounts that hired, raised or switched this week, the buyer found and verified at each, fit scored, drafts staged and a CRM batch waiting for approval every Monday morning. The infrastructure under pipeline generation, run by autonomous AI agents on a schedule.
Signals, people, verification, scoring, drafts and the CRM batch on one weekly run that reports to Slack.
Hiring, funding, technology adoption and change, news, relationships, intent, growth and leadership moves, each a reason to be in this week’s batch.
Every account in the batch carries the dated signal that qualified it, so the rep opens with the reason.
The CRM push and the sequence load wait for a person each week; the research never does.
A good prospecting week produces forty accounts; a week of demos produces none. The top of the funnel rises and falls with calendar load rather than with anything happening in the market.
Rounds close, roles post, stacks change and leaders move every day. The account that fits perfectly this week is in someone’s alert email, unread, under sixty others.
A list built in a research tool waits for an upload, a column mapping and a duplicate check. By the time the opportunity exists in the CRM, the signal that justified it is a month old.
Companies in your ICP that posted the relevant roles, closed a round, adopted or dropped a technology, announced news or surged on your topics inside the window, merged and deduplicated against the CRM.
Named people by title and seniority at every qualified account, work emails found through a waterfall of licensed sources and verified, direct phones where a source has one.
Fit scored with reasons, a first touch drafted from the signal for each buyer, and the batch staged as CRM companies, contacts and opportunities plus a paused sequence.
The whole run repeats weekly or daily, posts a digest of what it found and what changed to Slack, and waits for one approval before anything is written.
Which signals count, which roles, which window, which CRM stage the batch lands in and who approves. Ten minutes once, editable in plain language later.
Every Monday the agents pull the week’s signals for companies in the ICP, merge them on domain and drop anything already a customer or an open deal.
The buying committee at each account by title and seniority, one primary contact chosen for the opportunity, the rest attached.
Emails verified and phones found; fit scored with reasons; rows below threshold parked in the list without entering the CRM.
A first touch per primary contact that opens with the week’s signal, written in your voice, held as a draft.
Companies, contacts and opportunities staged in the CRM and a paused sequence in your outreach tool; a digest in Slack; one approval and it lands.
Every Monday at six, accounts that hired for the roles your product relieves or closed a round last week, the buyer verified, opportunities staged in HubSpot with the signal in the notes, approved before the pipeline meeting.
Companies in the ICP that announced a round yesterday, the CEO and the functional buyer found and verified, a deal staged per account with a congratulations draft attached.
The same weekly run split by region and owner, each rep’s batch staged to their queue with their name on the opportunities, one approval per manager.
Companies that adopted your integration partner’s product in the last 30 days, scored, the owner of the stack identified, staged as opportunities tagged with the partner.
| By hand | With AstroFabric | |
|---|---|---|
| Cadence | Whenever someone has a free morning | Every Monday at six, on a schedule |
| Why-now | Alert emails nobody reads | The dated signal on every opportunity |
| Buyer | Found later, if the deal gets that far | Named, verified and attached before the row exists |
| Fit | Whoever matched the alert | Scored against the ICP with reasons; misfits parked |
| CRM | Upload, map, dedupe by hand | Staged as companies, contacts and opportunities, one approval |
| Visibility | A spreadsheet in a DM | A digest in Slack and a run history anyone can open |
Accounts that hired for target roles or raised last week, the buyer verified, opportunities staged in HubSpot with the signal quoted, digest to Slack, approved once.
Every round announced yesterday in the ICP, CEO and functional buyer found, a deal staged per account with the draft attached.
Recent adopters of a partner technology scored and staged as opportunities tagged with the partner, refreshed monthly.
Three of a hundred. The full playbook library ships in every workspace, and anything you can describe becomes a mission.
The schedule runs the research inside the credit ceiling without asking. Creating opportunities, contacts or a sequence load is staged for a person each run, exactly as previewed.
Accounts already in the CRM as customers, open opportunities or recent closed-lost are recognized and excluded or attached, so a weekly machine never creates duplicates.
Each run posts what it found, what it parked and what it staged to Slack, and the full run transcript stays in the workspace.
Signals and people data come from licensed providers. The agents never scrape member networks or send messages in your name.
A scheduled machine that turns market signals into CRM opportunities: each run qualifies accounts from hiring, funding, technology, news and intent, finds and verifies the buyer, scores fit, drafts a first touch and stages a CRM batch and a paused sequence for one approval. Autonomous agents run it weekly or daily.
Roles posted by function and seniority, hiring velocity, funding rounds by stage and size, technology adopted or dropped, news such as launches, expansions and partnerships, leadership changes and buying-intent topics. You choose which count, and each row carries the one that qualified it.
Every run deduplicates against the CRM on canonical domain and email, attaches existing records where they exist, excludes customers and open opportunities, and applies the workspace suppression list. Rows below the fit threshold stay in the list without entering the CRM.
Companies with firmographics and the signal, contacts with verified emails and titles, and an opportunity in the stage you chose with the why-now in the notes, in HubSpot, Pipedrive, Attio or Zoho CRM. The draft goes to Lemlist or Instantly paused, or onto the contact as a note.
No. Drafts load paused in Lemlist or Instantly and opportunities are staged in the CRM; your team sends the first touch and works the deals. No capability on the platform sends mail or runs campaigns, and that boundary holds for the API, MCP server and CLI as well.
Yes. Split the schedule by territory, segment or signal, assign an owner per split, and each batch stages under that rep with its own approval. The digest shows every split side by side, and managers can approve all splits at once.
Qualifying and enriching an account is a few credits per row and a verified contact is a few credits; scheduling, scoring, deduplication and the CRM push are free. The schedule shows its expected cost before it is saved, misses cost nothing, and plans start at $49 per month.
Set the signals once. Every Monday a verified, scored batch waits in the CRM for one approval.