The prompt
Score 10 of 10, Excellent
Use it when You need evidence of what customers would pay before pricing a new product or plan, and want a research plan with the right questions and sample.
- {{audience}}
- {{timeframe}}
- {{product}}
- {{customers}}
- {{current_prices}}
- {{reach}}
- {{resources}}
- {{decision}}
Full prompt and why it works
Prompt
Plan research into what customers would pay for the product below, for {{audience}}, so that the pricing decision rests on what customers say and do rather than on what the team hopes. The plan should be one we can run in {{timeframe}} with the people and budget we have. The product or plan we are pricing: """ {{product}} """ Who we would sell it to: {{customers}} What customers pay today for this or for alternatives, as far as we know: {{current_prices}} Who we can reach for research (customer list, panel, sales calls, website visitors): {{reach}} Budget and people for the research: {{resources}} The pricing decision we need to make: {{decision}} Use these headings: 1. Questions the research must answer: up to 4, each tied to the decision. 2. Method: which methods fit, from price sensitivity questions (the Van Westendorp four questions), interviews about value and current spending, a choice-based study comparing packages, or a live test of prices on a page, with one line on why each fits or does not fit our reach and budget. 3. Sample: who, how many and how we recruit them, and who to leave out, such as customers on discounted contracts if their answers would skew the results. 4. Questions to ask: the exact wording, in order. Ask about past behavior and current spending before any price question, because people asked first what they would pay tend to anchor on the first number they hear. 5. Analysis: how we will read the answers, and what result would change the decision. 6. Timeline: a table with the columns Week, Activity, Owner. Keep the plan under 700 words. For example, a behavior question reads: "The last time you paid for a tool like this, what did it cost and who approved it?" This shows the form only. A good plan makes clear what each answer will tell us and how it bears on the decision. Do not suggest a price or a price range yourself, and do not use competitor prices that are not in the context. Say plainly that what people say they would pay is often higher than what they do pay, and show how the plan checks stated answers against behavior. If our reach is too small for a method to give a usable result, say so and suggest one that fits. If the decision or the customer is unclear, ask before planning.
Variables
- {{audience}}
- Who will use the findings, for example "the founders and the head of sales".
- {{timeframe}}
- How long you have, for example "four weeks".
- {{product}}
- What you are pricing: what it does, who it is for, and how it differs from what they use now.
- {{customers}}
- The buyers you have in mind, for example "operations managers at clinics with 5 to 50 staff".
- {{current_prices}}
- What buyers pay now for this or for alternatives, with sources, or "not known".
- {{reach}}
- Who you can actually contact for research, with rough numbers, for example "1,200 trial users by email; 20 sales calls a week".
- {{resources}}
- Budget and people for the research, for example "$2,000 for incentives; one PM half time".
- {{decision}}
- The pricing decision to make, for example "whether to charge per user or per location, and roughly at what level".
Why it works
- What to avoid. The model does not suggest a price or borrow competitor prices you did not give, so the research stays a test rather than a guess.
- What good looks like. Behavior questions come before any price question, and the plan says how stated answers will be checked against what people actually do.
- If unsure. If your reach is too small for a method to give a usable result, the plan says so and swaps in one that fits.