How to use the Buyer Persona Generator.
Base personas on observed needs and behaviors. Mark inferred preferences clearly instead of inventing a demographic biography to fill empty sections.
Make the workflow fit your task.
Group observed customer needs, behaviors and obstacles, keeping supporting interview notes nearby. Describe the pattern without filling gaps with invented demographics, then list the unknowns that further research should resolve.
- What you provide
- Supplied customer research.
- What you get
- Evidence-linked customer profile with unknowns marked.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Interviews show shop owners update catalogs weekly and worry about incorrect prices.
Completed example
Primary need: accurate catalog updates. Friction: checking changes manually. Unknown: preferred reporting format and budget.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a persona include age and hobbies?
Include them only when evidence shows they affect the relevant behavior or decision. Decorative biography can create misleading assumptions.
Why does the persona sound specific but lack evidence?
Label inferred details and remove unsupported ones. A smaller profile grounded in actual observations is easier to use responsibly.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑