The prompt
Score 10 of 10, Excellent
Use it when You want to know whether your product has found its market, using the "very disappointed" survey question, and what to do with the answers.
- {{product}}
- {{audience}}
- {{user_base}}
- {{channel}}
- {{min_responses}}
- {{results}}
Full prompt and why it works
Prompt
Help me run a product-market fit survey for {{product}} and read the results, for {{audience}}, so that we know which customers would miss the product most and what to build or fix next for the people most like them. Who uses the product today, with rough numbers: {{user_base}} How we can reach them: {{channel}} The fewest responses a segment needs before we read it: {{min_responses}} Survey results, if we have them yet (one row per response, with the answers and any segment fields such as role, plan or how long they have been a customer): """ {{results}} """ Part A: the survey 1. These questions, in this order: - "How would you feel if you could no longer use {{product}}?" with the options Very disappointed, Somewhat disappointed, Not disappointed, I no longer use it. - "What type of person do you think would benefit most from {{product}}?" - "What is the main benefit you get from {{product}}?" - "How could we improve {{product}} for you?" - Up to 2 segment questions we cannot already get from our own data, such as role. 2. Who to send it to: people who have used the core of the product recently, for example at least twice in the last two weeks, and not people still in onboarding or long inactive. Say how to pick them from what we have. 3. A short invitation, under 80 words, that does not hint at the answer we hope for. Part B: reading the results. Write it only if results are pasted above; if they say "none yet", write Part A only. 1. The very disappointed share: very disappointed answers divided by everyone who answered, leaving out "I no longer use it", with the counts and the arithmetic shown. The often-quoted 40 percent mark from Sean Ellis is a rule of thumb, not a pass mark; say how far the result is from it, and why the trend across surveys matters more. 2. A table by segment with the columns Segment, Responses, Very disappointed, Somewhat disappointed, Not disappointed, each as a count and a percentage. Mark segments below the minimum "too few to read". 3. Who loves it: the segment with the highest very disappointed share, described in the words those customers use, with up to 5 short quotes about the main benefit. 4. What holds others back: what somewhat disappointed customers who name the same main benefit say would improve it. 5. Next steps: up to 4, each tied to a finding above. Keep Part B under 700 words, not counting the table. A good reading makes every number traceable to its counts and keeps the not disappointed group as context, not a to-do list. Do not round before dividing, do not offer rewards for particular answers, and do not claim fit or no fit from one survey alone. If a segment field is missing or a response is unreadable, leave it out of that count and say how many were left out.
Variables
- {{product}}
- Your product's name, as customers know it.
- {{audience}}
- Who will act on the results, for example "the founders and the product team".
- {{user_base}}
- Who uses it and roughly how many, for example "about 2,000 active accounts, mostly small agencies".
- {{channel}}
- How you can reach users, for example "email and an in-app message".
- {{min_responses}}
- The fewest responses a segment needs before you read it on its own, for example 30.
- {{results}}
- The survey responses, one row each, with segment fields. Write "none yet" if you have not run it.
Why it works
- An example. The four questions use the standard wording of this survey, so your result can be compared over time and with how others run it.
- What good looks like. The share is shown with its counts and arithmetic, segments below your minimum are not read, and the 40 percent mark is treated as a rule of thumb.
- If unsure. Part B is written only when results exist, and unreadable responses are counted out and reported rather than guessed.