Intent Watcher: AI buying signals that fire only on warm prospects

Cold outbound dies in volume. The 2026 stack of mature AI GTM engines moves the other direction — surgical, signal-triggered outreach against tiny lists of accounts that have a reason to buy this week. Intent Watcher is the agent that builds those lists.

This post is part of the complete guide to AI GTM engines. See how Intent Watcher fits into the 3-pillar architecture and the other 7 agents.

What Intent Watcher actually does

It watches a curated set of public sources — LinkedIn activity, job listings, funding announcements, review-site moves, tech-stack changes, content engagement — and fires when an account crosses a signal threshold you defined.

Output is not a CSV. Output is a structured event: account ID, the signal that fired, signal confidence, recency, and the context payload (so Sequence Composer can write outreach that references the actual signal, not “I noticed you’re a leader in X”).

Why this matters

The single highest-leverage decision in B2B outbound is which accounts to contact this week. Most teams skip it. They buy a list, hit send, and watch reply rates flatline at 1%.

A working intent layer collapses your reachable list from “the full TAM” (cold, noisy, ignored) to “the 40–80 accounts currently showing buyer behavior” (warm, focused, replied-to). Reply rates jump 5–10× because you stopped wasting reach on accounts that had no reason to buy.

How it works under the hood

Intent Watcher runs on a scheduled poll loop. Each source has its own connector — LinkedIn Sales Nav for activity, Google Job Search APIs for hiring posts, Crunchbase for funding, G2/Capterra for review moves. Signals stream into a Supabase event table.

An ICP-scoring function (defined at sprint kickoff, tunable per industry) reads the events, multiplies by signal weights, and emits a "fire" event when the account crosses threshold. Account Mapper takes it from there.

Common failure modes

• Too many signals weighted equally — fires too often, dilutes the warm list back into noise.
• Polling too slowly — signal goes cold before Sequence Composer reaches the prospect.
• No suppression logic — same account fires twice in a week, looks spammy to the prospect.
• Treating every signal as equal — a funding round is not the same buying intent as a job post.

When to deploy first

If you have an existing outbound motion with low reply rates, Intent Watcher is the highest-ROI agent to ship first — it makes every other agent more effective without changing anything else in your stack. If you’re starting from scratch, ship it alongside Inbox Operator (no point watching intent if your emails land in spam).

The pillar guide covers the full 14-day shipping playbook with where Intent Watcher slots into days 2–3.

FAQ