Sales triggers at your target accounts, scored and queued for outreach.

Every week it scans the trade press for trigger events at the accounts you sell to: leadership changes, funding, expansions, new systems, regulatory shifts. It scores each signal one to ten for how much it should move a rep this week, drops the noise, and queues what clears the bar for outreach. It works with the CRM and the channel you already use, and it works with neither: a pasted account list and this chat are enough to start.

What it does

• Read the trade press for events at those accounts.
• Score each event one to ten against what you sell.
• Queue what clears the bar and file what does not.

What you get

• A short queue of accounts worth a call this week.
• Every signal scored, with its source and the next step.
• A Monday digest, or one line when the week is quiet.

What it needs

• What you sell, and who you sell it to
• The segments and regions you cover
• The accounts you want watched

Weekly, Monday morning by default, in your time zone.

You set the bar and work the queue. Every signal cites the page it was read from.

Who runs it

Sales and RevOps read the same queue. The Monday note lands in the chat they already share, and a row a rep takes shows as taken.

• One queue, not six inboxes: Every rep filters to the accounts they own on the same board. A signal someone is working shows who has it, so two people never open the same account.
• The source is on every row: Each signal carries the page it was read from and the date on it. A rep checks the claim before they call, instead of trusting a summary.
• Anyone can scan before a pipeline review: Press the button and the desk reads the window again. A scan already running is shown rather than started twice.

What stays yours

• Your bar, not ours: You set the score a signal has to clear before it reaches the queue. Everything below it is still filed, so the board shows what was seen and set aside.
• Your account list stays yours: Accounts, signals and notes live in the desk's own store inside your workspace. Connect a CRM and it stays current; connect nothing and a pasted list is enough.
• Scoring is one reading, not a verdict: A single AI scores each event against what you sell and writes one line saying why. It never sends anything and never decides who to call.

Questions

Do I need a CRM?

No. Paste or upload an account list and the desk matches signals against it. A connected CRM keeps that list current and syncs status back, but the desk works fully without one.

What counts as a signal?

A specific, dated event at a named company in your segments: a leadership change, funding, an acquisition, an expansion, a new system, a regulatory shift. A think-piece with no event is not a signal.

Why are most scores low?

Because most events are not a reason to call this week. A board that is all nines is a board nobody trusts. High scores need a named buyer, a dated event and a clear line to what you sell.

What happens in a quiet week?

The scan closes with its counts and the digest says so in one line. A closed scan with nothing above the bar is a real result, not a failure.

Where do signals land?

In the chat this was installed in, unless you connect a channel. Connect one and the app's own delivery takes over, so a digest never has two senders.

Can the same event be filed twice?

No. Duplicate reports of one event are consolidated into a single row, and the brief the scan reads carries what has already been filed.

Open Monday with six reasons to call, not a news feed.

Install it, say what you sell and to whom, and the first scan runs at boot.

Browse all Bolter blueprints