Create Buyer Persona Profiles in a Table

The file

---
name: create-buyer-persona-profiles-in-tabular-format
description: >-
  Buyer persona profiles in a table, with traits, goals, challenges, KPIs, and preferred tools for each, so reps and marketers share one reference. Adapted from Christian Krause.
  Task type: Create. Built for Sales, Marketing.
  Use when the request sounds like "Create Buyer Persona Profiles in a Table".
  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/create-buyer-persona-profiles-in-tabular-format
---

# Create Buyer Persona Profiles in a Table

Buyer persona profiles in a table, with traits, goals, challenges, KPIs, and preferred tools for each, so reps and marketers share one reference. Adapted from Christian Krause.

One job only: buyer persona profiles in a table, with traits, goals, challenges, KPIs, and preferred tools for each, so reps and marketers share one reference. 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

- buyer personas

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 create detailed buyer persona descriptions for each of the provided buyer personas in {$BUYER_PERSONAS}. The output should be in a tabular format, with a separate section for each buyer persona.

For each buyer persona, follow these steps:

1. Start with an overall description of the role in the first row of the table.

2. In the next row, list the top goals for this buyer persona. Clearly label this row as "Top Goals".

3. In the following row, list the top challenges faced by this buyer persona. Clearly label this row as "Top Challenges". 

4. Next, list the key performance indicators (KPIs) that this buyer persona is judged against. Label this row as "KPIs".

5. Finally, list the common software tools used by this buyer persona. Label this row as "Common Software Tools".

Structure each section in a table format with the following column headers:
"Buyer Persona", "Description"

Here's an example of how the table should look for one buyer persona:

<Buyer Persona> <Description>
Role [Role description]
Top Goals [List of top goals]
Top Challenges [List of top challenges] 
KPIs [List of KPIs]
Common Software Tools [List of common tools]

Make sure to follow this tabular format strictly for each buyer persona in {$BUYER_PERSONAS}. Do not include any other information beyond what is specified in the instructions.
```

## 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/create-buyer-persona-profiles-in-tabular-format
- Suite: https://www.therevenueaireport.com/agent-skills/suites/account-research-and-targeting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com