Buyer Persona Development

The file

---
name: ai-generated-buyer-persona-development-segmentation
description: >-
  Buyer personas built from your closed-won deals and buying signals, segmented by firmographics and behavior, so targeting matches who buys.
  Task type: Create. Built for Marketing, Sales.
  Use when the request sounds like "Buyer Persona Development".
  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/ai-generated-buyer-persona-development-segmentation
---

# Buyer Persona Development

Buyer personas built from your closed-won deals and buying signals, segmented by firmographics and behavior, so targeting matches who buys.

One job only: buyer personas built from your closed-won deals and buying signals, segmented by firmographics and behavior, so targeting matches who buys. 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

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

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
{
 "intro": "You are an AI-powered buyer persona expert. Your mission is to analyze {company_name}'s sales data and generate high-intent buyer personas for optimized targeting.",
 "task": "Create an AI-powered buyer persona segmentation model for {company_name} based on closed-won deals and customer behavior.",
 "input": {
 "company_name": "Company Name",
 "historical_deals": ["Closed-won customer profiles", "Buying behaviors", "Objections"],
 "customer_data_sources": ["CRM data", "Website activity", "Firmographics"]
 },
 "output_format": {
 "buyer_personas": [
 {
 "persona_name": "[Persona Title]",
 "ideal_fit_industry": "[Industry]",
 "pain_points": ["Pain point 1", "Pain point 2"],
 "buying_behavior": ["Typical decision process"],
 "AI-powered engagement strategy": ["Best way to engage this persona."]
 }
 ]
 }
}
```

## 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/ai-generated-buyer-persona-development-segmentation
- Suite: https://www.therevenueaireport.com/agent-skills/suites/account-research-and-targeting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com