thinkhard.SI

Prompt repository Product

Design pricing tiers for a product

You need plan names, what each includes and the reasoning before you test prices.

Registry no.
PRD-010
Collection
Product
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
6
Added

ProductAny chat

The prompt

Score 10 of 10, Excellent

Use it when You need plan names, what each includes and the reasoning before you test prices.

  • {{product}}
  • {{segments}}
  • {{pricing_goal}}
  • {{usage}}
  • {{costs}}
  • {{price_references}}
Full prompt and why it works
Prompt
Background:
Product and what it does: {{product}}
Our customer groups and how they differ (size, usage, needs, budget): {{segments}}
What we want pricing to achieve (for example more upgrades, simpler sales, more revenue per customer): {{pricing_goal}}

How customers use the product (which features, how much, by which group):
"""
{{usage}}
"""

What it costs us to serve a customer, and what prices must cover:
"""
{{costs}}
"""

Our current prices, if any, and prices of alternatives we have actually seen (with source and date):
"""
{{price_references}}
"""

Task: Draft pricing tiers for this product, with plan names, what each includes and the reasoning, as hypotheses to test with customers before we decide.

Cover these, in order:
1. What we charge by: one or two options (per user, per use, per location, flat), and which grows most in line with the value customers get, with the trade-offs.
2. Tiers: usually three, each built around one customer group from above, not a random split of features. For each: who it is for, what is included, limits, and the trigger that makes a customer move up.
3. Price ranges: a range per tier, reasoned from our costs and the prices given above. Show the arithmetic, including the margin at the low end of each range.
4. Free plan or trial: whether to offer one, and why.
5. Risks: existing customers whose price changes, features in the wrong tier, and anything that makes the choice confusing.
6. What to test first and how, such as conversations about willingness to pay, or showing two price levels to different visitors.

Rules:
- Plan names should say who the plan is for. Plain names beat clever ones.
- Do not put the feature every customer needs only in the top tier unless you explain why.
- Use only prices and costs from the material. Do not quote market rates, competitor prices or benchmarks from memory.
- These are hypotheses, not final prices. The owner or finance lead decides after testing.

A good result is a set of plans a customer could place themselves in within a few seconds.

Format: a tier table with the columns Plan, For whom, Includes, Limits, Price range, Upgrade trigger, followed by the sections above, under 600 words in total.

If the cost data is missing, propose the structure but leave the price ranges as [needs cost data] and say what you need. Do not guess.

Variables

{{product}}
The product and what it does, in a sentence or two.
{{segments}}
Your customer groups and how they differ, for example "solo consultants, agencies of 5 to 20, larger firms".
{{pricing_goal}}
What you want pricing to do, for example "more customers moving to the middle plan".
{{usage}}
How each group uses the product: which features, how often, how much. Numbers from your analytics if you have them.
{{costs}}
Your cost to serve a customer or unit (hosting, support time, materials, payment fees) and any margin you need.
{{price_references}}
Your current prices and the prices of alternatives you have seen, each with its source and date.

Why it works

  • What to avoid. Prices come only from your costs and the alternatives' prices you have seen, never from memory, and every range shows its margin arithmetic.
  • What good looks like. Each tier is built around one customer group with a clear upgrade trigger, rather than an arbitrary split of features.
  • If unsure. Without cost data it proposes the structure and leaves the prices open, and the result is framed as hypotheses for the owner to test and decide on.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.