Find AI Prompts
Home›Sales›Buying Signals and Trigger Event Analysis
SalesAccount Intelligence

AI Prompts for Buying Signals and Trigger Event Analysis

Buying signals are events that make a purchase more likely now than it was last month: a new leader, a funding round, a hiring surge in the function you sell to, a competitor's contract ending, a regulatory change, repeat visits to your pricing page. The value is in timing — the same message lands differently in the week after the trigger. The risk is noise: without a taxonomy and scoring, every event looks like intent.

These prompts build the taxonomy for your specific market, score the signals you actually receive, and define what happens when a signal fires. They depend on your knowledge of why customers bought; the model can structure and challenge it but cannot know your market's triggers.

Before you use these

Have these ready to replace the highlighted [variables]:

The prompts

1. Build the trigger-event taxonomy

Best forA list of the events that actually preceded purchases in your market, with how to observe each.
Inputs needed
  • Win context data
  • Product and market
How to use itGive real examples of what was happening at customers when they bought. The model generalizes them into a taxonomy and tells you which are observable.
Expected outputTrigger taxonomy with category, event, why it creates need, observability, source, typical lead time, and the ones to prioritize.
Act as a revenue intelligence analyst building a trigger-event taxonomy for [product / market].

Win context: [for recent customers: what was happening at the company when they bought — events, changes, pressures]
Signal sources available: [list]

1. Group the win contexts into trigger categories: leadership change, funding/financial event, growth (hiring, expansion, new market), technology change (new system, contract expiry, migration), regulatory/compliance, operational pain becoming visible (job posts for the pain, public complaints), competitive event, engagement with us.
2. For each specific trigger: why it creates or accelerates need for our product; how observable it is; the source that would surface it; typical lead time from trigger to purchase decision; and how many of the win contexts it appeared in.
3. Rank triggers by frequency in wins × observability × lead time usefulness.
4. False-positive risk per trigger: events that look like the trigger but do not create need.
5. Gaps: triggers that mattered but we have no source for, and the cheapest way to observe them.
6. The five triggers to monitor first and the exact source/query for each.

Do not include generic triggers that would apply to any product. Every trigger must trace to at least one real win context or a stated reason it should.

2. Score intent signals by strength and recency

Best forTurning a feed of signals into a ranked action list rather than a wall of alerts.
Inputs needed
  • Signal feed
  • Taxonomy with weights
  • Recency rules
How to use itPaste the raw signals. Ask for a score that combines signal type, specificity, recency and whether multiple signals stack on the same account.
Expected outputScored account list with the signals behind each score, the stacking effect, and the accounts that crossed the action threshold.
You are scoring intent signals for a target account list.

Signals received: [paste: account, signal type, detail, source, date]
Taxonomy weights: [trigger → base score]
Rules: [recency decay (e.g. full weight within 14 days, half at 30, zero at 60); specificity bonus (named function or project); stacking bonus for multiple distinct signals; source reliability adjustments]

1. Score each signal: base × recency × specificity × source reliability. Show the calculation for three examples.
2. Aggregate per account with the stacking rule; list the signals behind each account score.
3. Rank accounts and mark those above the action threshold [score].
4. Flag accounts whose score comes from a single weak source, and accounts with contradictory signals (e.g. hiring surge plus layoffs).
5. Note signals that should trigger a specific play rather than generic outreach (e.g. new leader → 30-day onboarding angle; contract expiry → competitive displacement).
6. Summary: accounts to act on this week, accounts to watch, and the sources generating the most actionable signals.

Do not treat high volume of weak signals as strong intent. Recency matters more than count.

3. Define signal-to-action rules

Best forDeciding in advance what happens when each signal fires, so monitoring produces outreach instead of a dashboard.
Inputs needed
  • Taxonomy and scoring
  • Available plays
  • Capacity
How to use itMatch each strong trigger to a play, an owner and a response time. Include what not to do — some signals are best left for a week.
Expected outputRules table: trigger → play → owner → response window → message angle → what to avoid, plus the capacity check.
Act as a sales operations lead defining signal-to-action rules for [team].

Triggers and scores: [taxonomy with thresholds]
Plays: [e.g. same-week researched outreach; executive note; content share; add to sequence; hand to AE; watch]
Capacity: [signal-driven actions per rep per week]

1. For each prioritized trigger: the play, the owner, the response window (hours/days), the message angle that references the trigger without being creepy, and the specific thing to avoid (e.g. congratulating on a leadership change before it is public, pitching during a layoff).
2. Combination rules: which stacked signals escalate to a higher-touch play or an AE.
3. Suppression rules: signals to ignore or delay — open opportunities, recent losses, customers in a support escalation, accounts contacted in the last [n] days.
4. Capacity check: expected signal volume per week versus capacity; the threshold to raise if volume exceeds it.
5. Feedback loop: how outcomes (reply, meeting, opportunity) are recorded against the triggering signal so weights can be corrected quarterly.
6. A one-page rule card for reps.

Present as a rules table. Every rule must have an owner and a time window; rules without them do not execute.

Related prompts

Logical next step

After this, most sales teams move on to Account Prioritization.

B2B Sales Prospecting System ($39) — goes further: trigger detection built into a repeatable prospecting system with sequences, objections and follow-up. See what's inside →
Get the free B2B Sales AI Starter Kit → Nine of these prompts as a target → engage → qualify workflow with an intake worksheet, delivered by email. See what's inside

All Sales prompts · Search the full library