Act as a pricing strategist for [COMPANY AND OFFER]. Build a pricing recommendation for [TARGET CUSTOMER] using the business context and evidence below. Business context: [BUSINESS CONTEXT] Current pricing and economics: [CURRENT PRICING AND ECONOMICS] Market evidence: [MARKET EVIDENCE] Goal and constraints: [GOAL AND CONSTRAINTS] First, identify the pricing decision: new-product launch, repositioning, packaging change, increase, discount policy, or renewal. State the value metric that best aligns what customers receive with how cost and value grow; explain why alternatives such as per-seat, usage, transaction, project, or flat-rate pricing fit less well.
Then produce: 1. A one-paragraph diagnosis of the buyer, their costly alternative, and the measurable value this offer creates. 2. A comparison table of three viable pricing architectures. Include package names, who each is for, included limits or features, price, overage or expansion logic, expected upside, and main risk. 3. A recommended architecture with list prices, annual-payment treatment, discount guardrails, grandfathering or migration approach, and a clear rationale grounded only in my inputs. 4. A willingness-to-pay research plan: 6 interview questions, a Van Westendorp or price-sensitivity test where suitable, sample segments, and what decision each result would change. 5. A 30-day rollout plan with owner roles, leading indicators, revenue metrics, and stop conditions. Do not infer customer demand from a competitor price alone or invent survey results, costs, conversion rates, or willingness-to-pay data. Separate facts, assumptions, and decisions. Before answering, check that every price recommendation can be traced to a stated value, cost, market fact, or labeled assumption; flag any missing unit economics that could reverse the recommendation. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [COMPANY AND OFFER] | Describe the company, the offer being priced, and whether it is new or existing. | LedgerLoop, an accounts-payable workflow SaaS adding an approval automation module. |
| [TARGET CUSTOMER] | Describe the buyer, user, company size, use case, and purchasing process. | US companies with 50-300 employees; controller is buyer, AP manager is daily user, CFO approves annual contracts. |
| [BUSINESS CONTEXT] | Provide the product's value proposition, alternatives customers use, and current growth stage. | Customers replace email-based invoice approvals and reduce late-payment errors; implementation takes two weeks. |
| [CURRENT PRICING AND ECONOMICS] | Provide current prices, costs, margins, retention, sales cycle, and any known conversion data. | Core plan is $499/month; gross margin is 78%; average customer processes 1,200 invoices monthly; 12-month retention is 91%. |
| [MARKET EVIDENCE] | Provide competitor prices, customer feedback, sales-call notes, research, and relevant market constraints. | Two competitors charge $6-$10 per user monthly plus platform fees; five prospects said audit trails matter more than invoice volume. |
| [GOAL AND CONSTRAINTS] | State the decision goal, timing, revenue target, contractual limits, and pricing constraints. | Launch in 45 days, raise average contract value without increasing churn, and avoid discounts above 15%. |
How to use
- Paste the prompt and replace every bracketed input with evidence from sales, finance, and customer research.
- Check that the recommended value metric matches how customers receive value and does not merely copy a competitor.
- Ask: “Turn the research plan into a five-call interview guide for controllers, including neutral follow-up questions.”
- Before publishing prices, have finance validate margin assumptions and have sales test the package language with live prospects.
Variations
Price increase memo
Use when changing an established price and preparing customer communication.
Draft a price-increase decision memo for [OFFER] for [CUSTOMER SEGMENT]. Current price is [CURRENT PRICE]; proposed price is [PROPOSED PRICE]; evidence is [EVIDENCE]; contract and notice rules are [CONTRACT RULES]. Produce a one-page memo with rationale, affected cohorts, grandfathering choices, renewal timing, discount exceptions, churn risks, and an approval recommendation. Write a separate customer-message outline, but do not make unsupported savings or value claims. Check that every affected cohort has a transition path and flag legal or contractual questions for counsel.
Packaging design
Use when the offer needs clearer plans before setting final price points.
Design product packaging for [PRODUCT] serving [BUYER SEGMENTS]. Features and usage drivers are [FEATURES AND USAGE]; known customer differences are [SEGMENT EVIDENCE]; constraints are [CONSTRAINTS]. Produce a three-tier package table with a named ideal customer profile, must-have features, limits, upgrade trigger, and sales risk for each tier. Recommend which features should never be used as a paywall because they are required for product trust or adoption. Do not assign prices without evidence; list the research needed to price each tier. Check for feature cliffs that would force customers into an unsuitable plan.
Consulting fees
Use when pricing a professional-services engagement rather than software.
Help price a [SERVICE TYPE] engagement for [CLIENT TYPE]. Scope is [SCOPE]; expected deliverables are [DELIVERABLES]; effort and capacity assumptions are [EFFORT]; client context is [CLIENT CONTEXT]. Produce three fee structures: fixed fee, time-and-materials, and retainer or value-based option where appropriate. For each, state scope boundaries, assumptions, change-order trigger, payment schedule, margin risk, and when it is appropriate. Recommend one structure and draft a concise scope-and-fee section. Do not promise outcomes outside my control. Check that the fixed-fee option contains explicit exclusions and acceptance criteria.
Tips
- Price around a value metric only when customers can understand, forecast, and influence it; an opaque usage metric creates billing disputes.
- Treat competitor pricing as a positioning signal, not proof of willingness to pay; their bundle, contract term, and buyer may differ.
- Set discount authority, approval thresholds, and expiration dates before sales receives the new price card.
- Run price research with customers who recently bought or seriously evaluated alternatives, not only loyal power users.
FAQ
Can AI determine the right price from competitor websites?
No. It can structure hypotheses, but competitor pages rarely reveal realized discounts, retention, implementation cost, or willingness to pay.
Should I use monthly or annual pricing?
Offer annual terms when implementation and retention justify a commitment, but keep the discount tied to cash-flow and churn economics rather than habit.
What should I do if the inputs are incomplete?
Label the unknowns, choose reversible tests, and collect evidence before making an irreversible company-wide price change.