The Revenue AI Report

Analyze a Closed-Won CRM Report to Identify Buyer Personas

AnalyzeSalesMarketing

The buyer personas that actually close for you, pulled from your closed-won CRM report by role, behavior, and buying motive. Adapted from Christian Krause.

This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.

The file

---
name: analyze-a-closed-won-crm-report-to-identify-buyer-personas
description: >-
  The buyer personas that actually close for you, pulled from your closed-won CRM report by role, behavior, and buying motive. Adapted from Christian Krause.
  Task type: Analyze. Built for Sales, Marketing.
  Use when the request sounds like "Analyze a Closed-Won CRM Report to Identify Buyer Personas".
  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/analyze-a-closed-won-crm-report-to-identify-buyer-personas
---

# Analyze a Closed-Won CRM Report to Identify Buyer Personas

The buyer personas that actually close for you, pulled from your closed-won CRM report by role, behavior, and buying motive. Adapted from Christian Krause.

One job only: the buyer personas that actually close for you, pulled from your closed-won CRM report by role, behavior, and buying motive. 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

- crm report
- persona
- example

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 analyze a closed-won CRM report and identify the most common buyer personas represented in the data. A buyer persona is a semi-fictional representation of an ideal customer based on real data and research into customer demographics, behaviors, motivations, and goals.

Here are the steps you should follow:

1. Read through the provided <CRM_report>{$CRM_REPORT}</CRM_report> carefully and thoroughly. Take note of any patterns or commonalities you observe among the buyers.

2. Based on the patterns you identified, group the buyers into distinct personas. Common characteristics to look for include:
- Demographics (age, gender, location, income level, etc.)
- Job roles and responsibilities
- Goals and challenges
- Buying behaviors and motivations
- Communication preferences

3. For each distinct persona you identify, provide a detailed description inside <persona></persona> tags. The description should capture the key traits, behaviors, goals, and other defining characteristics of that persona group.

When describing each persona, be sure to include:
- A persona name or title that captures their essence 
- Relevant demographics and background information
- Their goals, challenges, and pain points related to your product/service
- How they prefer to research and evaluate solutions
- What motivates their buying decisions
- Any other notable details that distinguish them

<example>
<persona>
Persona Name: Cost-Conscious Operations Manager
Demographics: 35-50 years old, manufacturing or logistics company, suburban/rural area
Goals: Increase efficiency, reduce operating costs, minimize downtime
Challenges: Strict budget constraints, legacy equipment/processes, employee pushback
Buying Process: Extensively researches options, prioritizes ROI calculations, seeks testimonials
Motivations: Proven cost-savings, simple implementation, training & support
Other Notes: Very numbers-driven, skeptical of new solutions without hard data
</persona>
</example>

Aim to identify 3-5 distinct and insightful buyer personas based on the patterns in the data. Provide as much relevant detail as possible for each persona to bring them to life and differentiate their profiles.
```

## 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/analyze-a-closed-won-crm-report-to-identify-buyer-personas
- Suite: https://www.therevenueaireport.com/agent-skills/suites/account-research-and-targeting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com

Install this skill

  1. For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
  2. For another assistant that supports skills, download the file above and place it in a folder named analyze-a-closed-won-crm-report-to-identify-buyer-personas inside that assistant's skills directory.
  3. Start a new conversation and ask for the job named on this page. Review the result before using it.

For the supporting files, download the full Account Research and Targeting package too. The single-file command only installs SKILL.md.

mkdir -p "$HOME/.claude/skills/analyze-a-closed-won-crm-report-to-identify-buyer-personas" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/analyze-a-closed-won-crm-report-to-identify-buyer-personas/SKILL.md" -o "$HOME/.claude/skills/analyze-a-closed-won-crm-report-to-identify-buyer-personas/SKILL.md"

Get the Report

The research behind these skills, weekly.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.