---
name: identify-sales-triggers-buying-signals-from-company-descriptions
description: >-
  The buying signals hidden in a company's own description: pain points, inefficiencies, and goals that give reps a reason to reach out. Adapted from Christian Krause.
  Task type: Analyze. Built for Sales.
  Use when the request sounds like "Identify Sales Triggers & Buying Signals from Company Descriptions".
  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/identify-sales-triggers-buying-signals-from-company-descriptions
---

# Identify Sales Triggers & Buying Signals from Company Descriptions

The buying signals hidden in a company's own description: pain points, inefficiencies, and goals that give reps a reason to reach out. Adapted from Christian Krause.

One job only: the buying signals hidden in a company's own description: pain points, inefficiencies, and goals that give reps a reason to reach out. 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

- company description
- justification

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
As a sales professional, one of the key skills is being able to identify when a potential customer (in this case, a company) might be in need of your solution. This involves carefully analyzing information about the company to look for certain "triggers" or signals that indicate pain points or challenges they may be facing that your solution could address.

Here are the steps you should follow:

1. Read the following company description carefully:
<company_description>
{$COMPANY_DESCRIPTION}
</company_description>

2. As you read through the description, identify any potential triggers or signals that suggest this company might benefit from our solution. Triggers could include things like:
- Mentions of challenges, problems, or inefficiencies they are facing
- Descriptions of outdated processes or systems they are using
- Goals or objectives they want to achieve that our solution could help with
- Competitive pressures or changes in their industry that create new needs

3. For each potential trigger you identify, provide a brief justification explaining why you think it is a relevant signal, relating it back to how our solution could potentially help address that pain point or need.

4. Write your justifications inside <justification></justification> tags, like this:

<justification>This part of the description suggests the company is struggling with X problem, which our solution is designed to solve by doing Y.</justification>

5. After listing out all the potential triggers and justifications, provide a brief summary of your overall findings and assessment of whether this company seems like a promising potential customer for our solution based on the provided description.

Write your summary inside <summary></summary> tags.

Take your time, think it through carefully, and provide a thorough analysis. Identifying triggers and needs is crucial for effective sales.
```

## 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/identify-sales-triggers-buying-signals-from-company-descriptions
- Suite: https://www.therevenueaireport.com/agent-skills/suites/account-research-and-targeting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com