Skip to content
Advanced 60 min 4 steps

Set Pricing Strategy with AI

Develop a rigorous, defensible pricing strategy for your product or service — from analyzing competitive benchmarks to testing price sensitivity to designing tiered packaging. Most founders leave significant revenue on the table by under-pricing. This workflow helps you price on value, not fear.

Tools You'll Need

MCP Servers for This Scenario

Browse all MCP servers →
  1. 1

    Analyze Value Drivers and Competitive Context

    Understand the economic value your product creates and map the competitive pricing landscape before touching your own price point.

    Help me build the foundation for a pricing strategy for my product.
    
    **Product/service**: [describe what you sell — be specific about the core function]
    **Customer type**: [who buys it — e.g., 'SMB marketing teams,' 'enterprise IT departments,' 'freelance designers']
    **Business model**: [e.g., 'SaaS subscription,' 'per-unit transactional,' 'professional services,' 'usage-based']
    **Current pricing** (if any): [what you currently charge, or 'not yet priced']
    **Key competitors**: [list 3-5 competitors and what you know about their pricing]
    
    Analyze:
    
    1. **Value Drivers**: What specific, measurable value does your product create for customers? Consider:
       - Time saved (hours/week × employee cost)
       - Revenue increased or deals won
       - Costs reduced or errors prevented
       - Risk mitigated (quantify if possible)
       - Competitive advantage gained
       Calculate the rough economic value your product creates per user or per customer annually. This is your theoretical price ceiling.
    
    2. **Competitive Pricing Map**: Based on what I've shared about competitors, map the pricing landscape:
       - What do competitors charge? What are their pricing models?
       - What is the price range a buyer in this market considers 'normal'?
       - Who is the price leader (cheapest intentionally) and who is the premium player?
       - What justifies premium pricing in this category — what features or outcomes are buyers paying a premium for?
    
    3. **Buyer Segments and WTP**: Are there meaningfully different segments of buyers with different willingness to pay? Describe 2-3 segments with their value drivers and estimated price sensitivity.
    
    4. **Pricing Model Options**: What pricing models are common and effective in this category? Evaluate: flat subscription, per-seat, usage-based, outcome-based, tiered, freemium+premium. Which fits my product's value delivery pattern best?

    Tip: Pricing on cost (cost + markup) and pricing on competition (what they charge) are both inferior to pricing on value (what is it worth to the buyer). To price on value, you must first know the economic value your product creates. If you've never calculated this number, start there — it will change how you think about pricing permanently.

  2. 2

    Test Price Sensitivity

    Use the Van Westendorp Price Sensitivity Meter and other frameworks to find the acceptable price range before you've committed to anything.

    Help me apply pricing research frameworks to test price sensitivity for [product name].
    
    **Product**: [description]
    **Target customer**: [description]
    **Current or planned price**: [if applicable]
    
    1. **Van Westendorp PSM Questions**: Generate the 4 Van Westendorp Price Sensitivity questions adapted specifically for my product. Also write the interpretation guide — what the answers to these questions tell me about optimal price positioning:
       - 'At what price would [product] be so inexpensive you'd question its quality?'
       - 'At what price would [product] start to feel like a bargain?'
       - 'At what price would [product] start to feel expensive, but you'd still consider it?'
       - 'At what price would [product] be too expensive to consider?'
    
    2. **Price Anchoring Analysis**: What anchors exist in the buyer's mind that shape their perception of my price? These might be: alternative solutions they're currently paying for, what their current approach costs them in time/money, competitor prices they've seen, or budget categories in their planning process. How can I use these anchors to position my price favorably?
    
    3. **Price Sensitivity by Segment**: For each buyer segment identified in Step 1, estimate:
       - Their likely acceptable price range
       - What drives their price sensitivity (budget constraints, procurement process, ROI requirements)
       - Whether they are more sensitive to sticker price or to ROI demonstration
       - What would make them pay 2x more than they'd initially offer?
    
    4. **Psychological Pricing Effects**: What psychological pricing principles are most relevant for my product and buyer? Examples: $99 vs $100, annual vs monthly framing, free trial vs freemium, decoy pricing in tiers. Give me specific recommendations, not generic principles.
    
    5. **Price Experiment Design**: Design 2-3 simple pricing experiments I could run with real prospects or customers to gather real willingness-to-pay data. How would I structure each test and what would the results tell me?

    Tip: Talk to customers before building your pricing model. Ask them the Van Westendorp questions in a customer discovery call — not 'what would you pay?' (people lie low), but the 4 questions above (which reveal the psychological price range). 10 honest conversations produce better pricing data than any framework.

  3. 3

    Design the Pricing Architecture

    Build the actual pricing tiers, features, and packaging that maximize both revenue and conversion across buyer segments.

    Design the pricing architecture for [product name].
    
    **Product features/capabilities**: [list all features you're considering offering]
    **Customer segments**: [from Step 1 — describe each segment with their needs and WTP]
    **Pricing model chosen**: [from Step 1]
    **Target price range**: [informed by Steps 1-2]
    **Business goals**: [e.g., 'maximize MRR,' 'land-and-expand into enterprise,' 'high volume at low price,' 'premium positioning']
    
    1. **Tier Structure**: Design 2-4 pricing tiers. For each tier:
       - Tier name (e.g., Starter, Growth, Pro, Enterprise)
       - Price point and billing options (monthly/annual, with annual discount recommendation)
       - Feature set (which features are included/excluded — and WHY this packaging makes sense for this segment)
       - Target customer for this tier
       - Why a customer would upgrade from the tier below
       - The 'hero feature' that makes this tier worth its price
    
    2. **Good-Better-Best Logic**: Apply the classic tier design principle: the middle tier should be where most customers land. Is your current design achieving that? If not, how would you rebalance the tiers?
    
    3. **Upgrade Triggers**: What specific customer behavior or outcome should trigger an upgrade conversation? Design the product/pricing so that customers naturally hit a ceiling that motivates them to upgrade rather than churn.
    
    4. **Freemium or Free Trial Decision**: Should I offer a free tier or free trial? Evaluate the trade-offs specifically for my product and market. If yes, what should be free and what should require payment? What is the free tier's strategic purpose?
    
    5. **Enterprise Packaging**: If selling to enterprise, what changes? Custom pricing? Volume discounts? Additional features (SSO, compliance, dedicated support)? What's the minimum deal size that justifies custom negotiation?

    Tip: The most common pricing mistake with tiered plans: putting too much in the starter tier. If the starter tier solves the core problem for most customers, you've killed your upgrade path. The starter tier should deliver real value AND make the customer feel the ceiling — they should want the next tier within 60-90 days of using the starter.

  4. 4

    Build the Pricing Communication Strategy

    Determine how to present pricing in a way that maximizes conversion — the pricing page, the sales conversation, and how to handle negotiation.

    Help me build the pricing communication strategy for [product name].
    
    **Pricing architecture**: [paste your finalized tiers from Step 3]
    **Typical buyer**: [who is making the purchase decision and how]
    **Sales motion**: [e.g., 'self-serve online purchase,' 'sales-assisted,' 'enterprise sales with procurement']
    
    1. **Pricing Page Copy**: Write the pricing page headline and sub-headline. The headline should communicate value, not just the price. Also write:
       - The 3 most important words for each tier's description
       - Feature bullets for each tier (write them as outcomes, not features: 'Process 10,000 invoices/month' not 'Batch processing')
       - The FAQ section (5 most common pricing questions for my product type)
       - A trust signal or risk reversal to add near the CTA (money-back guarantee, free trial, no credit card required)
    
    2. **Price Anchoring on the Page**: How should I order and visually weight the tiers? Should I highlight the middle tier as recommended? What design signals make the intended tier feel like the obvious choice without feeling manipulative?
    
    3. **Sales Conversation Framework**: How should a salesperson introduce and discuss pricing? Write a brief conversation guide:
       - When to mention price in the discovery process (too early kills value establishment)
       - How to handle 'what does it cost?' before you've established value
       - How to justify premium pricing without being defensive
       - How to handle 'that's more than I expected' without immediately discounting
    
    4. **Discount Policy**: Should I offer discounts? If so, under what conditions? Design a discount policy that: protects margin, doesn't teach customers to always ask for discounts, and gives the sales team clear guidelines. Include: maximum discount authority by deal size, what a customer must offer in return for a discount (annual commitment, case study, referrals), and how to document exceptions.

    Tip: Never be the first to name a price in a sales conversation. First establish the value — get the customer to articulate their pain and quantify what solving it is worth to them. Once they've said 'this would save us $200K a year,' your $30K annual price is a 15% ROI, not a number they compare to competitors.

Recommended Tools for This Scenario

Frequently Asked Questions

How often should I revisit my pricing?
Review pricing formally every 6-12 months, and informally every time you have a significant product update, a major new customer segment emerges, or your competitive landscape shifts. Most companies under-price at launch and never raise prices because it feels risky. The data consistently shows that moderate price increases (10-20%) on annual basis cause far less churn than feared, especially when paired with genuine product improvements. The best time to raise prices is when your win rate is above 80% — that's a clear signal you're leaving money on the table.
Should I show pricing on my website?
For SMB and self-serve products: yes, almost always. Hiding pricing creates friction, attracts prospects who can't afford you, and signals you have something to hide. For enterprise with complex pricing: show a starting price or a 'pricing starts at' number to qualify prospects, then use a sales conversation for custom quotes. The exception to showing pricing: if your price legitimately varies widely by use case and showing a number would consistently mislead prospects about their actual cost.
How do I raise prices without losing customers?
Give 60-90 days notice, explain the reason (product improvements, market position, or simply being honest that you underpriced), and grandfather loyal customers for 6-12 months if possible. Segment your approach: highest-value customers get a personal call from a senior person; others get email. Frame the price increase as a signal of confidence in your product's value. Most companies find that churn from price increases is significantly lower than feared — the customers most likely to leave for price were often the least profitable customers anyway.

Related Articles

Agent Skills for This Workflow

Was this helpful?

Get More Scenarios Like This

New AI guides, top MCP servers, and the best tools — curated weekly.

Related Scenarios