🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
Marketing teams, Product marketers, Sales teams, Content teams, Founders
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a customer research strategist. Your task is to create a practical buyer persona that helps a team understand how a specific type of customer thinks, decides, evaluates options, and responds to messaging.
### Required Input
- Offer: [Describe the product or service. Example: “Cybersecurity training platform for small businesses”]
- Buyer Segment: [The specific buyer to profile. Example: “HR managers responsible for compliance training”]
- Customer Evidence: [Paste interviews, reviews, survey responses, sales notes, support tickets, or call summaries]
- Buying Context: [What is happening when they look for a solution. Example: “New compliance requirement after a security incident”]
- Decision Role: [Example: “Final decision-maker”, “Influencer”, “Evaluator”, “User”]
- Alternatives Considered: [Example: “Internal training, consultants, competitor platforms”]
- Main Use Case: [What they want to accomplish. Example: “Train staff and prove compliance”]
- Intended Use: [How the persona will be used. Example: “Improve landing page copy and email nurture”]
### Input Validation
Check all required fields before creating the persona. If the buyer segment, offer, evidence, or intended use is unclear, ask specific clarification questions and pause. Avoid inventing demographic details that are not useful or supported by evidence.
### Instructions
Build the persona around decision behaviour, not stereotypes. Focus on the buyer’s situation, goals, pressures, anxieties, desired outcomes, objections, internal constraints, and evaluation criteria. Avoid decorative details such as fictional hobbies unless directly relevant to buying behaviour.
Analyse the evidence for repeated phrases, pain intensity, buying triggers, internal politics, approval steps, risk concerns, and success definitions. Identify what the buyer needs to believe before they will move forward.
Distinguish between what the buyer says they want and what they are trying to avoid. For example, a buyer may say they want “easy reporting” but actually fear looking unprepared to leadership. Capture both practical and emotional motivations.
Create messaging guidance that helps teams use the persona. Include hooks, proof points, objections to address, content topics, CTA angles, and sales conversation cues. If the buyer is not the final decision-maker, explain what they need to persuade others internally.
### Output
- Persona Snapshot: clear profile of the buyer and decision role
- Situation and Trigger: what causes this buyer to seek a solution
- Goals and Desired Outcomes: practical results they care about
- Pain Points and Fears: problems, risks, and frustrations
- Buying Criteria: how they compare options and define a good choice
- Objections and Barriers: what may stop them from converting
- Language and Voice of Customer: useful phrases, themes, and wording from evidence
- Messaging Recommendations: value propositions, proof points, hooks, CTAs, and tone
- Content and Campaign Ideas: practical ideas mapped to the buyer journey
- Sales Enablement Notes: questions, talking points, and internal approval considerations
- Research Gaps: what needs more evidence before relying on the persona
Create separate messaging notes for awareness, consideration, and decision-stage campaigns.
This persona profiles the primary evaluator and day-to-day champion managing compliance automation systems. While they often hold significant influence over software selection, they must secure final financial and technical approval from a broader executive team.
Buyers rarely seek a platform like this out of casual curiosity; they act when an operational forcing event exposes systemic risks in their existing setup.
Success for this buyer means achieving high operational velocity while maintaining bulletproof accuracy and departmental independence.
Behind the analytical, data-driven exterior of a risk professional lies deep professional anxiety rooted in compliance vulnerabilities and organizational friction.
When comparing alternatives—such as building an in-house engine, hiring expensive contractors, or adopting rigid enterprise platforms—the evaluator weighs choices against four criteria:
Understanding what causes this profile to stall during a deal lifecycle is vital to keeping opportunities moving forward:
To resonate instantly with this buyer, utilize the exact operational vocabulary they use every day in internal standups. Avoid vague marketing buzzwords.
The Engineering Bottleneck: “We’re losing weeks of product development time because our compliance leads have to submit engineering tickets just to tweak a basic risk threshold on our checkout endpoint.”
The Alert Fatigue Crisis: “Our analysts are drowning in a sea of false positives. We’re spending 80% of our day reviewing identical, safe transactions just because our legacy engine can’t parse multi-variable conditional logic.”
The Core Requirement: “I don’t need a black-box AI model telling me a transaction is ‘risky’ without showing its work. I need an explicit, deterministic audit log that clearly states exactly which logic parameter triggered the alert.”
Frame your messaging around immediate operational relief, technical credibility, and risk mitigation.
Get access to all workflows, across every sector, with structured systems built for better results.