Free AI Buyer Persona Template (Make My Persona)

You don’t need a 3-hour workshop to create buyer personas that actually move pipeline. You need a repeatable template, the right inputs, and a simple way to ship personas into your GTM, content, paid, and sales workflows. This article gives you a free AI-driven buyer persona template (“Make My Persona”), data-backed prompts, examples, and a field-by-field playbook to go from vague avatars to revenue-grade personas in a few hours - not weeks.

Most personas die because they’re written as creative briefs, not operating documents. A revenue-grade persona is specific, falsifiable, and mapped to systems you already use: CRM, ad platforms, outreach tools, and editorial calendars. If a persona can’t be used to filter a list in your CRM or to write an ad that a real buyer will click, it’s not ready.

It’s helpful to separate three layers you’ll see in this guide: ICP (firmographic boundaries), Persona (the human who buys), and JTBD (the job they’re trying to get done). ICP keeps you from chasing the wrong companies. Persona helps you understand who inside those companies will say yes, stall, or kill the deal. JTBD gives you the language to write copy that feels native to their problem.

Good personas are also measurable. You should be able to trace how a persona-informed change (subject line, landing page hook, new ad angle) changes awareness, CTR, SQLs, win rate, or sales cycle time. That’s why the template below includes a “measurables” section and not just biography fluff.

Before you run prompts, align definitions so your team stops arguing in Slack. ICP defines the account-level criteria: industry, geography, size, model, compliance requirements, and critical stack dependencies. For example: “US-based logistics tech companies, 50–500 employees, running HubSpot + NetSuite, with at least 10-person ops teams.”

Persona defines the human reality: the person’s role, daily metrics, blockers, motivation, and political capital. Example: “Director of Operations who owns pick-pack-ship SLAs, reports to VP Ops, misses targets when returns spike; risk-averse with new vendors; hates black-box tools.”

JTBD is the high-friction moment they’re trying to fix and the progress they want. It’s their single-sentence story. Example: “Reduce warehouse mis-picks by 50% without hiring 10 more pickers.” That sentence should drive your ad headlines, landing page subheads, and discovery call agenda.

Here’s the “Make My Persona” field set I use. It’s AI-friendly (for prompting) and ops-friendly (to map into your CRM and content workflows). You can paste this structure into your LLM of choice, replace the brackets with your context, and get a consistent persona draft in minutes.

Core fields to include:

• Role & seniority: title(s), reporting line, influence in buying committee
• Company context: industry, size band, tech stack dependencies
• Primary job-to-be-done (JTBD): the progress they need this quarter
• Critical KPIs: 3–5 metrics they’re graded on (with benchmark ranges if you have them)
• Trigger events: moments that start the search (missed goal, leadership change, tool change)
• Objections & risks: political, budgetary, technical
• Selection criteria: 5–7 non-negotiables in their vendor scorecard
• Buying committee map: who influences, who signs, who blocks
• Message angles: top 5 hooks that differentiate and de-risk
• Search and channel habits: keywords, communities, formats they trust
• Proof they believe: what case study shape moves them (logo, metric, vertical)
• Sales enablement: discovery questions, demo checklist, red flags
• Measure & iterate: what you’ll track to validate this persona (CTR, SQL rate, win-rate lift)

Keep it to one page per persona. If your team can’t skim it in 90 seconds before a campaign or call, it’s too long.

AI is only as good as the inputs. Borrow signals from your stack so the model drafts a persona that sounds like your market - not your marketing team.

Use these sources before prompting:

• CRM won/lost notes: what reasons show up repeatedly in close-lost?
• Call transcripts: Gong/Zoom words buyers actually use to describe pain
• Support tickets: recurring issues that block value or activation
• Ad comments and DMs: blunt feedback from real humans about offers and claims
• Search Console + site search: problem language your qualified users type
• Proposal Q&A: terms, redlines, procurement hurdles

Don’t overfit on a single loud deal. If you’re early, sample 10–20 conversations. If you’re later-stage, partition by segment (mid-market vs enterprise) and acquisition channel (inbound vs outbound), then do personas per segment.

Here’s the fastest path to usable output in one working session. You can adapt this to any LLM (Claude, GPT, open-source). The goal is a draft you can immediately test in ads and sales, not a pretty slide.

Step 1: Prime the model with your ICP and real snippets. Paste 3–5 bullets for ICP, 10–20 quotes from transcripts, and a short summary of product value. Keep it raw; don’t sanitize buyer language.

Step 2: Paste the field list above and ask for a one-page persona. Request bullets, not essays. Ask the model to cite which input evidence informed each section (this reduces hallucinations and keeps you honest).

Step 3: Ask for two variants: a “Decider” (economic buyer) and a “Doer” (day-to-day user). Their KPIs and objections differ. You’ll likely need different hooks for each.

Step 4: Convert the persona to formats you can ship now: ad angles, cold email opener lines, landing page subheads, discovery questions, and a CRM property mapping.

Step 5: Run a micro-test within 72 hours. Update your ad copy, an outbound sequence, or a landing page hero using the new persona language. Track baseline vs new within a small budget or a subset of accounts.

Use these verbatim, then tweak for your market. Wherever you see [BRACKETS], add your details. Keep the inputs tight - 200–400 words per section is usually enough to avoid model drift.

Prompt 1: Draft the revenue-grade persona

Context: You are a senior B2B marketer and sales operator. Build a revenue-grade buyer persona. Use only the evidence in my notes. If a field is unclear, flag it as "Unknown" (don’t invent).

ICP:
- Industry: [INDUSTRY]
- Company size: [SIZE]
- Region: [REGION]
- Tech stack: [STACK]
- Notes: [ANY BOUNDARIES]

Evidence quotes (buyer language):
1) "[QUOTE]"
2) "[QUOTE]"
...

Product value summary:
- [1–3 bullets]

Output fields (bullet points, max 1 page):
- Role & seniority
- Company context
- JTBD (one sentence)
- Critical KPIs (with ranges if possible)
- Trigger events (top 5)
- Objections & risks (top 7)
- Selection criteria (top 7)
- Buying committee map
- Message angles (top 5)
- Search and channel habits
- Proof they believe
- Sales enablement: discovery questions, demo checklist, red flags
- Measure & iterate: 3 metrics to watch

For each field, cite which input informed it in brackets, e.g., [Quote #3].

Prompt 2: Create activation assets from the persona

Using the persona above, output:
1) 7 ad headline angles (max 40 chars each)
2) 5 LinkedIn primary text variations (max 140 chars)
3) 5 cold email openers (max 20 words, no fluff)
4) Landing page: hero H1 (max 7 words) + subhead (max 14 words)
5) Discovery call: 7 questions to expose the JTBD and risks
Keep language direct and specific. Avoid buzzwords.

Prompt 3: CRM mapping

Map the persona fields to CRM properties for HubSpot/Salesforce. Propose property names, field types (dropdown, text, number), and example options. Aim for minimalism so reps actually fill them in.

To make this concrete, here’s a shortened example based on a fictional but realistic segment. The point isn’t the industry - it’s the shape of the output.

Role & seniority: Director of Operations, reports to VP Ops, manages 4 team leads; influences vendor shortlist, co-signs with VP.

JTBD: Cut mis-picks and returns by 50% this quarter without adding headcount.

Critical KPIs: Order accuracy %, return rate, pick time per order, SLA adherence, overtime hours.

Trigger events: Peak season forecast shows 30% volume spike; CFO freezes backfill; legacy WMS update slips; customer churn risk flagged; new marketplace integration adds complexity.

Objections & risks: “Rips and replaces scare me”; IT bandwidth; change management risk; ROI skepticism; fear of onboarding chaos; vendor lock-in; security review.

Selection criteria: Proven integrations with NetSuite; 90-day ROI plan; on-site enablement; transparent pricing; audited security; referenceable logos in logistics; performance SLAs.

Message angles: “40% fewer mis-picks in 60 days”; “Your NetSuite stays - ours snaps in”; “Pilot 2 lanes before full roll-out”; “Operators first - no black box”; “On-site go-live, not slideware.”

Sales enablement: Discovery questions that expose process breakpoints; demo checklist focused on pick-path optimization and exception handling; red flag if IT is not in the first two calls.

What to measure: Ad CTR against mis-pick angle; SQL rate for ops titles; win-rate lift vs prior 90 days.

Personas are only valuable when they collide with channels. Here’s where the template outputs should land in the next 1–2 sprints.

Content and SEO: Convert JTBD and trigger events into article clusters, landing page variants, and case study angles. If your persona searches for “reduce mis-picks NetSuite,” that’s a bottom-funnel page you can ship this week. If you need help packaging those angles at scale, see how AI-assisted content operations can build topic clusters and briefs that map to persona pain across the funnel on our AI SEO content service.

Paid media: Map message angles to ad sets by intent: proof-driven (metrics and logos) vs risk-reduction (integration and rollout). Use the persona’s channel habits to pick placements. Operators often convert on search and retargeting; deciders on LinkedIn thought units with crisp ROI hooks.

Sales and success: Add the discovery questions and red flags to your call guide. Update the demo sequence to hit the persona’s selection criteria in the first 7 minutes. Feed “unknowns” back into the template after 10 calls.

Personas stall when the people who write them aren’t the ones changing ads, pages, and sequences. Anton Chisliuk · AI Marketing Ops runs as an operator model - one senior person ships GTM, content, ads, CRM, and automation in a 90-day cycle. Proof over pitch: for Cleverence (B2B SaaS), we went from 0 to 80K organic visits per month and 0 to 2K inbound leads per month. If you want a quick outside view and a working plan (not slides), book a short Growth Audit.

Editorial: Turn the persona’s top problems into a 12-week calendar. Each week ships one problem-explainer (TOFU), one tactic post (MOFU), and one proof piece (BOFU). Your headline bank comes straight from “message angles” and “trigger events.”

Ads: Choose three angles from the persona: outcome metric, risk reversal, and integration. Run a 2x2 split by persona role (Doer vs Decider) and device (mobile vs desktop). Kill losers fast.

Outbound: Use trigger events to time campaigns - new funding, hiring spikes, tech migrations. Personalize the opener with a JTBD insight, not a name-stitch. If you’re building outbound infrastructure and want volume without getting blocked, the systems described here are what we deploy in our email outbound service.

Overfitting to anecdotes: That one loud enterprise deal isn’t your market. Segment and test. Don’t take a single CMO’s quote as universal truth.

Writing biographies, not playbooks: “Likes Peloton and oat lattes” won’t help sales. Keep fields tied to channel actions and measurable outcomes.

One-and-done persona files: Markets shift. Set a cadence to revalidate every 90 days. If win rates drop for a persona, figure out if the persona changed or your promise did.

If personas only exist in Docs, your team will ignore them. Add 2–3 fields in your CRM to tag persona role (Doer/Decider), primary JTBD, and top objection faced in discovery. Keep it simple or reps won’t fill it out.

Then build a dashboard cut by persona: lead volume, SQL rate, win rate, ACV, sales cycle length. When ops sees that Decider-led deals close 20% faster at +15% ACV, they’ll prioritize executive touch in sequences.

If you need help structuring fields, properties, and reports in HubSpot or Salesforce so this data sticks, our CRM implementation service page breaks down the model and handoffs we deploy.

Personas are content accelerators when you translate JTBD into clusters. Example for “Reduce mis-picks 50%”:

• TOFU: “Why mis-picks spike after peak season (and how to predict it)”
• MOFU: “NetSuite + WMS: 5 mis-pick pitfalls and how to avoid them”
• BOFU: “Case study: 42% fewer mis-picks in 60 days - Ops playbook”

Offer strategy changes too. A generic “Book a demo” won’t convert like a persona-tuned offer: “Get a 90-day mis-pick reduction plan (free).” Same product, different promise. Personas inform this difference.

Want to turn persona angles into a 50-article plan with briefs and outlines in under a week? That’s the sort of pipeline-focused packaging we do on our GTM strategy service, where persona, ICP, and offer stack line up before spend goes up.

Don’t argue personas in meetings; test them in-market. Here’s a lean validation plan you can repeat quarterly.

Channel tests: Run three ad angles from the persona across two channels for seven days. Success is CTR lift of 20–30% against your baseline and a statistically meaningful CPL improvement. For outbound, a 20% lift in positive reply rate is a good early marker.

Sales tests: Add the persona’s discovery questions to five calls per rep. Track the rate of “clear JTBD articulated” and objection type frequency. If objection mix changes, your persona is wrong or your demo is mis-sequenced.

Landing page tests: Swap your hero and subhead to the persona’s JTBD. Time-to-scroll and demo start rate will tell you quickly if it lands. No need for a full redesign.

Most growth-stage companies need two to four personas: one Decider, one Doer, and perhaps a Specialist or Compliance influence. If you have more, you probably have a segmentation problem or you’re early and guessing. Start narrow, earn the right to expand.

Split personas by materially different jobs-to-be-done and sales motions. If the Doer in SMB buys self-serve but enterprise requires a security review and procurement dance, those are different personas and likely different funnel shapes.

When in doubt, pick the persona that dominates your pipeline or has the highest win rate and build around them first.

Cadence: Review persona performance every 90 days. Keep a rolling doc where reps drop fresh quotes and product flags new friction. Update the template only when data accumulates, not after every call.

Ownership: One person owns the source of truth. Marketing edits language; sales owns objections and discovery; ops owns CRM fields and dashboards. Don’t let it diffuse.

Change control: If you change a persona angle that touches ads, pages, or sequences, tag it in your changelog. Tie performance deltas back to the change. Personas are hypotheses - treat them like product releases.

You don’t need committee time to get buyer personas that move deals forward. You need a compact template, real inputs, and a bias to test. Use the fields and prompts above to produce two working personas this week. Ship the first ad angles, a new landing page hero, and updated discovery questions within 72 hours. Then measure what changes and adjust.

If you want a second set of senior eyes to turn your ICP, personas, and offers into a 90-day operating plan, start with a short Growth Audit. And if you want to see who’s behind the keyboard, this article was written by Anton Chisliuk - operator, not agency.

- Do I really need personas if I already have an ICP?

Yes. ICP tells you where to hunt; personas tell you how to win. ICP is account-level; personas are human-level. Without personas, your copy, demos, and offers will be generic and underperform with the people who actually sign or use your product.

- How many personas should a growth-stage company create first?

Two. Start with one Decider and one Doer. Add more only if they represent materially different jobs-to-be-done or sales motions. This keeps your team focused and makes testing faster.

- What’s the fastest way to validate a new persona?

Run a seven-day micro-test: swap your ad angles and landing page hero to the persona’s JTBD. Watch CTR, CPL, and demo start rates. If you see a 20–30% lift, keep iterating. If not, adjust angles or revisit inputs.

- Should personas be different for inbound and outbound?

Often yes. The same human behaves differently depending on how they find you. Inbound personas tend to be further along and respond to proof and clarity. Outbound personas need sharper problem framing, risk reversals, and credible hooks in the first lines.

- How do I prevent personas from getting fluffy over time?

Enforce the one-page limit and evidence citations. Tie each field to a data source. If a claim isn’t tied to call notes, CRM data, or performance results, mark it as “Unknown” and design a test to learn it.

- Where should personas live so the team actually uses them?

Three places: a shared one-pager (Docs/Notion), CRM fields (so you can slice pipeline by persona), and your ad/content brief template (so messaging stays consistent). Make them part of the workflow, not a separate artifact.