Key takeaways
- A persona describes one role in the buying group: its goals, worries, the questions it asks and the proof it needs. Write one per role, not one per customer.
- In a typical factory purchase, four roles matter: the plant manager, purchasing, the engineer and the owner. Each one can stop the deal for a different reason.
- Build personas from interviews and sales notes, not from imagination. Five conversations per role are often enough to start.
- Each role now asks AI assistants different questions. Map those questions per persona and make sure your site answers them.
What a B2B buyer persona is
A buyer persona is a one-page description of a role that takes part in a purchase. It is built on top of your ideal customer profile: the profile says which companies to pursue, and the personas say who inside those companies you need to convince and how.
Consumer personas often focus on age, hobbies and lifestyle. Those details rarely matter in B2B. What matters is the job: what the person is measured on, what goes wrong if a purchase fails, which documents they need and which questions they ask before they agree to a meeting.
The example: a fictional compressor maker
To keep this concrete, imagine a fictional Korean company that makes energy-saving air compressors. Its ideal customers are mid-sized plants with two or more shifts, where compressed air is a large share of the electricity bill. The company, the plants and the people below are invented for illustration.
A typical deal starts when an old compressor breaks down or the electricity bill rises. It involves at least four people at the customer, and it can take several months from the first inquiry to the purchase order.
Four personas at a glance
| Role | Main goal | Main worry | Proof they need |
|---|---|---|---|
| Plant manager | Stable output, fewer stops | Downtime during installation | Installation plan and a reference from a similar plant |
| Purchasing | Fair price, reliable supply | Choosing a vendor that later fails | Comparable quotes, terms, company information |
| Engineer | Equipment that fits and works | Hidden incompatibility | Detailed specifications, drawings, test data |
| Owner | Return on investment | Spending money that does not pay back | Payback estimate and total cost of ownership |
The table is the summary. Each persona below adds the questions the person asks and what your team should give them.
Persona 1: the plant manager
The plant manager is usually the first to feel the problem and the one who starts the search. In the example, it is a manager responsible for output and maintenance across two lines, who has just dealt with a compressor failure on a night shift.
- Asks: how long installation takes, whether the line must stop, who comes on site if something breaks.
- Needs from you: an installation plan, a service response promise and an example from a similar plant.
- Reached through: trade shows, distributors, industry forums and, more and more, AI assistants.
Persona 2: purchasing
Purchasing joins once the plant manager has a shortlist. Their job is to compare suppliers on equal terms and protect the company from a bad contract. They rarely care about technical detail, but they care a great deal about clarity.
- Asks: what is included in the price, the warranty terms, the lead time, how long the supplier has been in business.
- Needs from you: a quote in a format that is easy to compare, standard terms and basic company information.
- Stops the deal when: quotes are vague, terms change late, or the supplier cannot be verified.
Persona 3: the engineer
The engineer checks whether the product really fits: air pressure, flow, piping, power supply, control integration and space. Engineers often read more of your website than anyone else, and they leave quickly if the numbers are missing or hidden inside an image.
- Asks: exact specifications, compatibility with existing equipment, how efficiency was measured.
- Needs from you: spec sheets as text, drawings, test conditions and a direct line to a technical person.
- Stops the deal when: a claim cannot be checked or the answer to a technical question takes a week.
Persona 4: the owner
In many small and mid-sized Korean manufacturers, the owner approves every significant investment. The owner may meet you only once, late in the process, and decides largely on the summary the team presents.
- Asks: how soon the investment pays back, what happens if it does not, whether subsidies or energy programs apply.
- Needs from you: a one-page business case the plant manager can present internally.
- Stops the deal when: the savings are not explained in money, or the risk seems open-ended.
What each persona asks AI
Each of these people may now start with ChatGPT, Gemini or Naver AI Briefing, and each asks differently. Listing the questions per persona shows which pages your site needs and where AI answers may leave you out.
| Persona | Example question to AI | Page that should answer it |
|---|---|---|
| Plant manager | Which energy-saving compressor suppliers offer fast on-site service in Korea? | Service and support page with regions and response times |
| Purchasing | How do I compare quotes for industrial air compressors? | Buying guide and FAQ on pricing and terms |
| Engineer | What specifications matter when replacing an old compressor? | Product pages with specifications as text |
| Owner | Is replacing a compressor worth it for a mid-sized plant? | Article on payback and total cost of ownership |
flowgen helps with exactly this mapping: Prompt Demand groups the questions buyers ask AI so you can see which ones matter, and Content Agent drafts the page each persona needs from your verified product facts.
How to build your own personas
Personas are not only for marketing. Share them with distributors and agents, who often meet the plant manager or the engineer long before you do, and with the people who prepare quotes, so every document a buyer receives speaks to the role that will read it.
- List the roles that appeared in your last ten won and lost deals.
- Talk to about five people per role: customers, distributors and your own salespeople.
- Write each persona on one page: goal, worry, questions, proof needed, where you reach them.
- Check each page and sales document against the personas and fill the gaps.
- Review once a year, or when a new kind of buyer starts appearing in deals.
Keep the personas short and grounded in what you have heard. A persona full of guesses looks polished but sends the team in the wrong direction.