Trigger Event Research for Cold Outreach

The file

---
name: trigger-event-research-for-cold-outreach
description: >-
  Recent trigger events at a target company, such as funding, expansion, or a launch, each with a reason to reach out now. Adapted from Christian Krause.
  Task type: Research. Built for Sales.
  Use when the request sounds like "Trigger Event Research for Cold Outreach".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Account Research and Targeting
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/trigger-event-research-for-cold-outreach
---

# Trigger Event Research for Cold Outreach

Recent trigger events at a target company, such as funding, expansion, or a launch, each with a reason to reach out now. Adapted from Christian Krause.

One job only: recent trigger events at a target company, such as funding, expansion, or a launch, each with a reason to reach out now. Anything outside that job belongs in another file in the Account Research and Targeting suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- product description
- company name
- background
- research instructions
- trigger event
- trigger event format
- description
- product relevance
- source

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
Your task is to research a company and identify any recent events or changes that could serve as "trigger events" prompting a meaningful cold outreach to offer our product or service. Here are the key steps:

<background>
Trigger events are significant developments in a company's situation that create new challenges or needs the company may want help addressing. Examples could include things like:
- Expanding into new markets or regions
- Launching a new product line 
- Undergoing a merger or acquisition
- Experiencing supply chain issues
- Facing increased competition
- Having a PR crisis or reputation damage
- Struggling with new regulatory requirements

By identifying these trigger events, we can tailor our cold outreach messaging to position our {$PRODUCT_DESCRIPTION} as a potential solution to the company's new challenges.
</background>

<research_instructions>
Using all available online resources like the company website, news articles, press releases, etc., research {$COMPANY_NAME} and its industry for the past 6 months. Look for any events or changes that could potentially serve as trigger events for a cold outreach pitch related to our product.
</research_instructions>

For each potential trigger event you identify, please provide the following information inside <trigger_event></trigger_event> tags:

<trigger_event_format>
<description>A brief 1-2 sentence description of the trigger event</description>
<product_relevance>1-2 paragraphs explaining how our {$PRODUCT_DESCRIPTION} could potentially help the company address challenges or needs created by this trigger event</product_relevance>
<source>A link or citation to the source(s) where you found information about this trigger event</source>
</trigger_event_format>

If you cannot find any relevant potential trigger events in your research, simply state that inside the <response> tags.

Write your overall response inside <response></response> tags.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/trigger-event-research-for-cold-outreach
- Suite: https://www.therevenueaireport.com/agent-skills/suites/account-research-and-targeting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com