30 Claude Prompts That Build Buyer Personas

You are a B2B demand-generation strategist who builds research-backed buyer personas. <context> I need a single B2B buyer persona for the economic decision-maker who signs off on my product, delivered as one self-contained HTML card with inline CSS so I can preview it instantly as an artifact. </context> <inputs> - Product and category: [WHAT IT DOES, E.G. PAYROLL SOFTWARE] - Industry and company size: [E.G. MID-MARKET RETAIL, 200-1000 STAFF] - The persona's likely job title: [E.G. VP OF FINANCE] - The problem we solve for them: [PAIN] - Budget and buying authority: [WHO SIGNS, RANGE] - What I already know about them: [ANY NOTES] </inputs> <task> Build one persona card with: a header (persona name, photo placeholder, role, company archetype), a demographics and firmographics block, primary goals and success metrics, top pains and frustrations, key objections to buying, where they get information and which channels reach them, their buying-committee role, and one realistic first-person quote that captures their mindset. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Every trait must be specific and plausible for this role and industry; no generic filler like "wants efficiency". - Accessible contrast and semantic markup; the quote must sound like a real person, not a brochure. </constraints> <format> Return the persona card as an artifact, then list the two assumptions you are least sure about so I can validate them with a real interview. </format>

You are a B2B go-to-market strategist who defines tight ideal customer profiles. <context> I need an account-level ICP (not a person, the company) defining who we should target, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and core value: [WHAT IT DOES] - Our best current customers: [3-5 EXAMPLES OR TRAITS] - Deal size and sales cycle: [RANGE] - Industries that fit: [LIST] - Disqualifiers (who is a bad fit): [NOTES] - Trigger events that signal a need: [E.G. RAISED FUNDING, NEW VP] </inputs> <task> Build an ICP sheet with: a one-line ICP statement, firmographics (industry, size, revenue, geography, tech stack), the situational triggers that make them ready to buy, the pains the ICP feels, the value they get, clear fit and disqualifying criteria, and a fit-scoring rubric (3-4 weighted signals) I can apply to a prospect list. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - The disqualifiers and the scoring rubric must be concrete enough to actually filter a list, not vague. - Accessible, scannable layout; no marketing fluff. </constraints> <format> Return the ICP sheet as an artifact, then suggest three database filters (e.g. in Apollo or LinkedIn Sales Navigator) that would surface accounts matching this ICP. </format>

You are a B2B product marketer who maps the buying committee. <context> I need a persona for the technical champion who evaluates and advocates for my product internally but does not hold the budget, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and what it touches technically: [E.G. API, DATA PIPELINE] - The champion's role: [E.G. SENIOR ENGINEER, IT MANAGER] - What they care about most: [SECURITY, EASE OF INTEGRATION, ETC] - How they evaluate tools: [DOCS, TRIALS, PEER REVIEWS] - The risk they fear: [E.G. BAD MIGRATION, VENDOR LOCK-IN] </inputs> <task> Build the persona card with: header (name, role, photo placeholder), how they discover and evaluate tools, their technical success criteria, the questions they will grill us on, what makes them champion a product to their boss, what makes them quietly veto one, the proof and content they trust, and a first-person quote capturing their skeptical, hands-on mindset. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Frame everything from the technical evaluator's POV; show what wins their trust versus what triggers doubt. - Accessible contrast and semantic markup; the quote should sound like an engineer, not a marketer. </constraints> <format> Return the persona card as an artifact, then list the top three pieces of content (e.g. a docs page, a benchmark) that would move this champion most. </format>

You are an enterprise sales strategist who navigates procurement and legal gatekeepers. <context> I need a persona for the procurement, security, or legal gatekeeper who can stall or kill my deal, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and data it handles: [WHAT IT DOES, WHAT DATA] - Typical deal size: [RANGE] - The gatekeeper's role: [E.G. PROCUREMENT MANAGER, CISO] - Their mandate: [COST CONTROL, RISK, COMPLIANCE] - Common hurdles they raise: [E.G. SOC 2, DPA, SECURITY REVIEW] </inputs> <task> Build the persona card with: header, their core mandate and incentives, what "a good outcome" looks like to them, the specific requirements and documents they will demand, the objections and friction they introduce, what makes them approve faster, what makes them dig in, and a first-person quote capturing their risk-first mindset. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be concrete about the actual artifacts they request (security questionnaire, DPA, references) for this kind of product. - Accessible, professional layout; no fluff. </constraints> <format> Return the persona card as an artifact, then list a short pre-emptive checklist of documents to prepare before this persona ever enters the deal. </format>

You are a small-business marketing strategist who sells to busy owner-operators. <context> I sell to small-business owners who are also the buyer, the user, and the budget holder. I need that persona as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and outcome: [WHAT IT DOES] - Type of business: [E.G. INDEPENDENT GYM, AGENCY, CAFE] - Owner's biggest daily headache: [PAIN] - How they buy software: [WORD OF MOUTH, GOOGLE, ETC] - Their attitude to new tools: [SKEPTICAL, EAGER, TIME-POOR] - Price sensitivity: [NOTES] </inputs> <task> Build the persona card with: header, a day-in-the-life snapshot, the goals they juggle, the pains stealing their time and money, why they hesitate to adopt a new tool, the objections about price and time-to-value, where they hang out and who they trust, and a first-person quote in their plainspoken, time-pressed voice. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Reflect that this buyer wears every hat and has no patience for setup; tie pains to time and revenue. - Accessible, warm, scannable layout; the quote must sound like a real overworked owner. </constraints> <format> Return the persona card as an artifact, then suggest the single message angle most likely to cut through for a time-poor owner-operator. </format>

You are a consumer-brand strategist who builds vivid, behavior-driven customer personas. <context> I need a single B2C customer persona for my product, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and category: [WHAT IT IS] - Price point: [RANGE] - Rough target audience: [WHO] - The need or desire it satisfies: [FUNCTIONAL AND EMOTIONAL] - How people typically discover it: [CHANNELS] - A real customer detail I know: [ANY NOTE] </inputs> <task> Build the persona card with: header (name, age, location, photo placeholder, a one-line tagline), lifestyle and demographics, the functional and emotional jobs the product does for them, their goals and aspirations, frustrations with current options, purchase triggers and hesitations, the brands and channels they trust, and a natural first-person quote. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Capture both the practical need and the emotional driver; avoid stereotypes and clichés. - Accessible contrast and semantic markup; the quote should sound like a real person on social media. </constraints> <format> Return the persona card as an artifact, then name the one emotional driver you would lead with in ad creative for this persona. </format>

You are a customer-insights analyst who synthesizes personas from voice-of-customer data. <context> I will paste real reviews, support tickets, or social comments. Turn the dominant pattern into one persona, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The raw feedback (paste below): [REVIEWS / TICKETS / COMMENTS] - What I want to learn: [E.G. WHY THEY CHURN, WHAT THEY LOVE] </inputs> <task> Read the feedback, identify the most common type of customer, and build their persona card: header, the recurring goals and delights they express, the recurring complaints and pains, the exact phrases they use (verbatim language bank), what made them buy, what makes them stay or leave, and a representative first-person quote stitched from their real language. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Ground every trait in the supplied feedback; do not invent traits that have no support in the text. - Include a short note flagging anything you inferred versus saw directly; accessible markup. </constraints> <format> Return the persona card as an artifact, then list the three most frequent verbatim phrases so I can reuse them in marketing copy. </format>

You are a brand planner who builds psychographic personas around values and identity. <context> I need a persona defined less by demographics and more by values, identity, and lifestyle, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or brand: [WHAT IT IS] - The identity it lets people express: [E.G. ECO-CONSCIOUS, MINIMALIST] - Values that matter to this audience: [LIST] - Where they spend attention: [PLATFORMS, COMMUNITIES] - A brand they already love: [EXAMPLE] </inputs> <task> Build the psychographic persona card with: header and a one-line identity statement, core values and beliefs, what they want to signal to others, the lifestyle and habits behind the purchase, the tensions or guilt they feel about choices, the communities and creators they follow, the brands they consider "their people", and a first-person quote expressing their worldview. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Lead with psychographics over demographics; show the identity the product helps them perform. - Accessible, expressive but legible layout; the quote should feel authentic, not preachy. </constraints> <format> Return the persona card as an artifact, then suggest one brand-values message that would resonate without sounding performative. </format>

You are a growth-focused product marketer for consumer mobile apps. <context> I need a persona for the typical user of my consumer mobile app, focused on how and when they use it, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - App and core job: [WHAT IT DOES] - Platform and price model: [IOS/ANDROID, FREE/FREEMIUM/PAID] - Primary use occasion: [E.G. COMMUTE, BEFORE BED] - The habit it builds or replaces: [NOTE] - Why people might churn: [NOTE] </inputs> <task> Build the persona card with: header, the trigger and moment they open the app, their goal in a single session, the friction in onboarding or daily use, what makes them form a habit versus uninstall, the notifications and nudges they tolerate, how they found the app, their willingness to pay or upgrade, and a first-person quote about how the app fits their day. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Center the persona on usage occasions and retention behavior, not just demographics. - Accessible markup; the quote should sound like an app-store review in real life. </constraints> <format> Return the persona card as an artifact, then suggest the one onboarding moment most likely to determine whether this user sticks. </format>

You are an e-commerce conversion strategist who studies buyers who purchase for someone else. <context> Many of my buyers are not the end user, they are buying a gift. I need that gift-buyer persona as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - Who the gift is usually for: [RECIPIENT] - The gifting occasion: [BIRTHDAY, HOLIDAYS, ETC] - The buyer's relationship to recipient: [E.G. PARENT, PARTNER] - Their worry when gifting: [E.G. WILL THEY LIKE IT] </inputs> <task> Build the persona card with: header, what they are really trying to achieve emotionally (be a thoughtful giver), how they shop differently than a self-buyer, the reassurances they need (returns, sizing, will it land), the time pressure of the occasion, the channels and signals that make them trust a product as a safe gift, the price comfort zone, and a first-person quote about the gifting stress. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Distinguish clearly how a gift-buyer's motivations and anxieties differ from the end user's. - Accessible, scannable layout; the quote should sound like someone gift-shopping under a deadline. </constraints> <format> Return the persona card as an artifact, then suggest the one trust signal (e.g. easy returns, gift receipt) that would most lift gift conversions. </format>

You are a senior UX researcher who builds design-ready user personas. <context> I need a UX persona to anchor product design decisions for a feature or product, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - The user's role or context: [E.G. FREELANCE DESIGNER] - Their primary goal with it: [JOB TO ACCOMPLISH] - Their technical comfort: [NOVICE / POWER USER] - Devices and environment: [WHERE THEY USE IT] - Known frustrations: [NOTES] </inputs> <task> Build the UX persona card with: header (name, role, photo placeholder, one-line bio), goals and motivations, key tasks and the contexts in which they happen, frustrations and pain points in the current flow, their tech proficiency and accessibility needs, the tools they already use, behaviors and mental models, and a first-person quote summarizing what they need from the product. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Make it actionable for designers: tie pains to specific tasks, not vague feelings; note any accessibility considerations. - Accessible markup and contrast; the quote should be need-focused, not promotional. </constraints> <format> Return the persona card as an artifact, then list three design implications (what to prioritize or simplify) that follow from this persona. </format>

You are a product strategist trained in the Jobs-to-Be-Done framework. <context> I want a persona built around the job the customer is hiring my product to do, not their demographics, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The struggle or moment that triggers a search: [SITUATION] - What they currently use instead: [WORKAROUND OR COMPETITOR] - The progress they want to make: [DESIRED OUTCOME] - What holds them back from switching: [ANXIETIES, HABITS] </inputs> <task> Build a JTBD persona card with: a job statement in the form "When [situation], I want to [motivation], so I can [expected outcome]", the functional, emotional, and social dimensions of the job, the triggering struggle, the push and pull forces (what pushes them from the old way, what pulls them to the new, and the anxieties and habits resisting change), the hiring criteria they judge solutions on, and a first-person quote about the moment they decided to look for something better. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Frame everything around the job and the four forces of progress, not demographics. - Accessible, structured layout; the quote should describe a concrete struggling moment. </constraints> <format> Return the JTBD persona card as an artifact, then suggest the one message that best speaks to the moment of struggle. </format>

You are a UX researcher who turns raw research notes into a defensible persona. <context> I will paste notes from user interviews or open-ended survey responses. Synthesize them into one persona, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or research goal: [WHAT WE WANTED TO LEARN] - Number of participants: [N] - The raw notes (paste below): [INTERVIEW / SURVEY NOTES] </inputs> <task> Analyze the notes, cluster recurring patterns, and build a persona card: header, goals and motivations supported by the data, pains and frustrations with quotes, behaviors and workarounds observed, the decision criteria they voiced, contradictions or tensions across participants, a confidence note on how strongly the data supports each trait, and a first-person quote drawn from real responses. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Every claim must trace to the notes; clearly separate observed data from inference. - Flag where the sample is thin or contradictory; accessible markup. </constraints> <format> Return the persona card as an artifact, then list the two open questions a follow-up study should answer to firm up this persona. </format>

You are an inclusive-design specialist who builds personas for users with diverse abilities. <context> I need a persona that centers accessibility needs so my team designs inclusively, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product or feature: [WHAT IT IS] - The user context: [E.G. SCREEN-READER USER, LOW VISION, MOTOR] - Their primary goal: [JOB TO DO] - Assistive tech they use: [E.G. VOICEOVER, SWITCH CONTROL] - Environment and constraints: [NOTES] </inputs> <task> Build the persona card with: header, the user's goals and the tasks they need to complete, the assistive technologies and settings they rely on, the specific barriers they hit in typical interfaces, what good and bad experiences feel like to them, the WCAG-aligned needs this implies (contrast, focus order, labels, timing), and a respectful first-person quote about being designed for, not around. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - Be specific and respectful; avoid inspiration tropes; tie needs to concrete design requirements. - The card itself must be a model of accessibility: high contrast, semantic markup, clear focus. </constraints> <format> Return the persona card as an artifact, then list four concrete accessibility requirements this persona makes non-negotiable. </format>

You are a product designer who maps how users evolve from first-run to mastery. <context> I need two contrasting personas for the same product, a brand-new user and a power user, side by side, delivered as one self-contained HTML card with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product: [WHAT IT IS] - The new user's first goal: [INITIAL JOB] - The power user's advanced goals: [DEEP JOBS] - The biggest first-run obstacle: [NOTE] - The features power users live in: [LIST] </inputs> <task> Build a two-column card comparing: each persona's goal, mental model and expectations, the friction they feel, what "value" means to each, the features that matter to each, the support they need, the risk of losing each (early churn vs. plateau), and a first-person quote per persona. Make the contrast obvious so the team sees the gap. </task> <constraints> - One self-contained, responsive HTML file; Google Fonts only. - The two personas must feel genuinely different in needs and risks, not just labeled new and advanced. - Accessible, balanced two-column layout that stacks cleanly on mobile. </constraints> <format> Return the paired persona card as an artifact, then name the single feature or moment that should help the new user become the power user. </format>