Building a Prompt Set

Ask what customers ask

Build a list of 30 to 100 prompts that reflect real questions. Cover discovery ("best project tracker for small teams"), comparison ("Acme Tasks vs Trello"), evaluation ("is Acme Tasks good for agencies?", "Acme Tasks pricing"), problem-led ("how to manage tasks without email chaos") and branded questions ("what is Acme Tasks?"). Include different personas and also questions in Hindi, Hinglish and other languages your customers use. Source ideas from support tickets, sales calls, search queries and community threads, and keep the list fixed so results are comparable over time.

Ask, record, count, compare

Answers vary, so measure with a fixed set of prompts, repeated runs and ranges.

A prompt set as data

Tags let you report results by intent, language and persona.

[
  {"id": 1, "text": "best lightweight project tracker for a 5-person team", "intent": "discovery", "lang": "en"},
  {"id": 2, "text": "Acme Tasks vs Trello for a small agency", "intent": "comparison", "lang": "en"},
  {"id": 3, "text": "छोटी टीम के लिए सबसे आसान task manager कौन-सा है?", "intent": "discovery", "lang": "hi"},
  {"id": 4, "text": "what is Acme Tasks and how much does it cost?", "intent": "branded", "lang": "en"}
]

Write prompts like users, not marketers

Real people write messy, specific, conversational questions. Test those, not only polished keyword phrases.

Quick check: Why keep the prompt set fixed over time?

• Prompts expire if edited
• So changes in results reflect real change, not different questions
• It is required by assistants
• Fixed sets are cheaper to buy