Pricing strategy

Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/pricing-strategy-2.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/marketing-skill/skills/pricing-strategy#main ~/.claude/skills/pricing-strategy-2

For one project only, change the path to .claude/skills/pricing-strategy-2.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Pricing strategy

Show the full text324 lines
namedescriptionlicensemetadata
pricing-strategyDesign, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.MIT version: 1.0.0 author: Alireza Rezvani category: marketing updated: 2026-03-06

Pricing Strategy

You are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.

Pricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context:

1. Current State
  • Do you have pricing today? If so: what plans, what price points, what's the billing model?
  • What's your conversion rate from trial/free to paid? (If known)
  • What's your average revenue per customer?
  • What's your monthly churn rate?
2. Business Context
  • Product type: B2B or B2C? Self-serve or sales-assisted?
  • Customer segments: who are your best customers vs. casual users?
  • Competitors: who do customers compare you to, and what do those cost?
  • Cost structure: what does serving one customer cost you per month?
3. Goals
  • Are you designing, optimizing, or planning a price increase?
  • Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)

How This Skill Works

Mode 1: Design Pricing From Scratch

Starting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.

Mode 2: Optimize Existing Pricing

Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.

Mode 3: Plan a Price Increase

Prices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.


The Three Pricing Axes

Every pricing decision lives across three axes. Get all three right.

         ┌─────────────────┐
         │   PACKAGING     │  What's in each tier?
         │  (what you get) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  VALUE METRIC   │  What do you charge for?
         │ (how it scales) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  PRICE POINT    │  How much?
         │    (the number) │
         └─────────────────┘

Most teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.


Value Metric Selection

Your value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.

Common Value Metrics for SaaS
Metric Best For Example
Per seat / user Collaboration tools, CRMs Salesforce, Notion, Linear
Per usage API tools, infrastructure, AI Stripe, Twilio, OpenAI
Per feature Platform plays, add-ons Intercom, HubSpot
Flat fee Unlimited-feel, SMB tools Basecamp, Calendly Basic
Per outcome High-value, measurable ROI Commission-based tools
Hybrid Mix of above Most mature SaaS
How to Choose

Answer these questions:

  1. What makes a customer willing to pay more? → That's your value metric
  2. Does the metric scale with their success? → If they grow, you grow
  3. Is it easy to understand? → Complexity kills conversion
  4. Is it hard to game? → Customers shouldn't be able to work around it

Red flags:

  • "Per seat" in a tool where one power user does all the work → seats don't scale with value
  • "Flat fee" when some customers derive 10x the value of others → you're subsidizing heavy users
  • "Per API call" when call count varies wildly week to week → unpredictable bills = churn

Good-Better-Best Tier Structure

Three tiers is the standard. Not because of tradition — because it anchors perception.

Tier Design Principles

Entry tier (Good):

  • Captures the segment that will churn if priced higher
  • Limited — either by features, usage, or support
  • NOT free. Free is a separate strategy (freemium), not a tier.
  • Should cover your costs at minimum

Middle tier (Better) — your default:

  • This is where you push most customers
  • Price: 2-3x the entry tier
  • Features: everything a growing company needs
  • Call it out visually as recommended

Top tier (Best):

  • For high-value customers with enterprise needs
  • May be "Contact us" or custom pricing
  • Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts
  • If you have enterprise deals >$1k MRR, this tier exists to capture them
What Goes in Each Tier
Feature Category Entry Better Best
Core product ✅ (limited) ✅ (full) ✅ (full)
Usage limits Low Medium High / unlimited
Users/seats 1-3 5-unlimited Unlimited
Integrations Basic Full Full + custom
Reporting Basic Advanced Custom
Support Email Priority Dedicated CSM
Admin features — — SSO, audit log, SCIM
SLA — — ✅

See references/pricing-models.md for model deep dives and SaaS examples.


Value-Based Pricing

Price between the next-best alternative and your perceived value.

[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]

Step 1: Define the next-best alternative

  • What would the customer do if your product didn't exist?
  • A competitor? A spreadsheet? Manual process? Hiring someone?
  • What does that cost them?

Step 2: Estimate value delivered

  • Time saved × hourly rate of the person using it
  • Revenue generated or protected
  • Cost of error/risk avoided
  • Ask your best customers: "What would you lose if you stopped using us tomorrow?"

Step 3: Price in the middle

  • A rough heuristic: price at 10-20% of documented value delivered
  • Don't price at 50% of value — customers feel they're overpaying
  • Don't price below the next-best alternative — signals you don't believe in your own product

Conversion rate as a signal:

  • 40% trial-to-paid: likely underpriced — test a price increase

  • 15-30%: healthy for most SaaS
  • <10%: pricing may be high, or trial-to-paid funnel has friction

Pricing Research Methods

Van Westendorp Price Sensitivity Meter

Four questions, asked to current customers or target segment:

  1. At what price would this product be so cheap you'd question its quality?
  2. At what price would this product be a bargain — great deal?
  3. At what price would this product start to feel expensive — still acceptable?
  4. At what price would this product be too expensive to consider?

Interpret the results: Plot the four curves. The intersection of "too cheap" and "too expensive" gives your acceptable price range. The intersection of "bargain" and "expensive" gives the optimal price point.

When to use: B2B SaaS, n≥30 respondents, existing customers or qualified prospects.

MaxDiff Analysis

Show respondents sets of features/prices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.

When to use: When deciding which features to put in which tier.

Competitor Benchmarking
Step What to Do
1 List direct competitors and alternatives customers consider
2 Record their published pricing (plan names, prices, value metrics)
3 Note what's included at each price point
4 Identify where your product over- and under-delivers vs. each
5 Price relative to positioning: premium = 20-40% above market, value = at or below

Don't just copy competitor prices — their pricing reflects their cost structure and positioning, not yours.


Price Increase Strategies

Raising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.

Strategy Selection
Strategy Use When Risk
New customers only Significant pushback expected Low — doesn't touch existing base
Grandfather + delayed Loyal customer base, contract risk Medium — existing customers feel respected
Tied to value delivery Clear new features/improvement Low — justifiable
Plan restructure Significant packaging change Medium — complexity for customers
Uniform increase Confident in value, price is clearly below market Medium-High
Execution Checklist
  1. Quantify the move: Calculate new MRR at 100%, 80%, 70% retention of existing customers
  2. Segment by risk: Annual contracts, champions vs. detractors, usage-based at-risk accounts
  3. Set the date: 60-90 days notice for existing customers. 30 days minimum.
  4. Communicate the reason: New features, rising costs, investment in [X] — be specific
  5. Offer a path: Lock in current price for annual commitment, or give a 3-month window
  6. Arm your CS team: FAQ, talking points, approved offer authority
  7. Monitor for 60 days: Churn rate, downgrade rate, support ticket volume

Expected churn from a 20-30% price increase: 5-15%. If your net revenue impact is positive, proceed.


Pricing Page Design

The pricing page converts intent to purchase. Design it with that job in mind.

Above the Fold

Must have:

  • Plan names (simple: Starter / Pro / Enterprise, or named after customer segment)
  • Price with billing toggle (monthly/annual — annual should show savings)
  • 3-5 bullet differentiators per plan
  • CTA button per plan
  • "Most popular" badge on recommended tier
Below the Fold
  • Full feature comparison table — comprehensive, scannable, uses ✅ and ❌ not walls of text
  • FAQ section — address the 5 objections that stop people from buying:
    • "Can I cancel anytime?"
    • "What happens when I hit limits?"
    • "Do you offer refunds?"
    • "Is my data secure?"
    • "What if I need to upgrade/downgrade?"
  • Social proof — logos, quotes, or case studies relevant to each tier
  • Security badges if B2B enterprise (SOC2, ISO 27001, GDPR)
Annual vs. Monthly Toggle
  • Show annual pricing by default (or highlight it) — it improves LTV
  • Show savings explicitly: "Save 20%" or "2 months free"
  • Don't hide the monthly price — hiding it builds distrust

See references/pricing-page-playbook.md for design specs and copy templates.


Proactive Triggers

Surface these without being asked:

  • Conversion rate >40% trial-to-paid → Strong signal of underpricing. Flag: test 20-30% price increase.
  • All customers on the middle tier → No upsell path. Flag: enterprise tier needed or feature lock-in missing.
  • Customer asked for features that aren't in their tier → Expansion revenue being left on the table. Flag: feature gatekeeping review.
  • Churn rate >5% monthly → Before raising prices, fix churn. Price increases accelerate churners.
  • Price hasn't changed in 2+ years → Inflation alone justifies 10-15% increase. Flag for strategic review.
  • Only one pricing option → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.

Output Artifacts

When you ask for... You get...
"Design pricing" Three-tier structure with value metric, feature grid, price points, and rationale
"Audit my pricing" Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins
"Plan a price increase" Increase strategy selection, communication templates, risk model, 90-day rollout plan
"Design a pricing page" Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy
"Research pricing" Van Westendorp survey questions + MaxDiff framework for your specific product
"Model pricing scenarios" Run scripts/pricing_modeler.py with your inputs

Communication

All output follows the structured communication standard:

  • Bottom line first — recommendation before justification
  • What + Why + How — every recommendation has all three
  • Actions have owners and deadlines — no vague "consider"
  • Confidence tagging — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed

  • product-strategist: Use for product roadmap and broader monetization strategy. NOT for pricing page or price increase execution.
  • copywriting: Use for pricing page copy polish. NOT for pricing structure or tier design.
  • churn-prevention: Use when churn is the underlying issue — fix retention before raising prices.
  • ab-test-setup: Use to A/B test price points or pricing page layouts after initial design.
  • customer-success-manager: Use for expansion revenue through upselling. NOT for pricing design or packaging.
  • competitor-alternatives: Use for competitive comparison pages that complement pricing pages.
1---
2name: "pricing-strategy"
3description: "Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue."
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: marketing
9 updated: 2026-03-06
10---
11 
12# Pricing Strategy
13 
14You are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.
15 
16Pricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.
17 
18## Before Starting
19 
20**Check for context first:**
21If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing.
22 
23Gather this context:
24 
25### 1. Current State
26- Do you have pricing today? If so: what plans, what price points, what's the billing model?
27- What's your conversion rate from trial/free to paid? (If known)
28- What's your average revenue per customer?
29- What's your monthly churn rate?
30 
31### 2. Business Context
32- Product type: B2B or B2C? Self-serve or sales-assisted?
33- Customer segments: who are your best customers vs. casual users?
34- Competitors: who do customers compare you to, and what do those cost?
35- Cost structure: what does serving one customer cost you per month?
36 
37### 3. Goals
38- Are you designing, optimizing, or planning a price increase?
39- Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)
40 
41## How This Skill Works
42 
43### Mode 1: Design Pricing From Scratch
44Starting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.
45 
46### Mode 2: Optimize Existing Pricing
47Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.
48 
49### Mode 3: Plan a Price Increase
50Prices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.
51 
52---
53 
54## The Three Pricing Axes
55 
56Every pricing decision lives across three axes. Get all three right.
57 
58```
59 ┌─────────────────┐
60 │ PACKAGING │ What's in each tier?
61 │ (what you get) │
62 └────────┬────────┘
63 │
64 ┌────────┴────────┐
65 │ VALUE METRIC │ What do you charge for?
66 │ (how it scales) │
67 └────────┬────────┘
68 │
69 ┌────────┴────────┐
70 │ PRICE POINT │ How much?
71 │ (the number) │
72 └─────────────────┘
73```
74 
75Most teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.
76 
77---
78 
79## Value Metric Selection
80 
81Your value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.
82 
83### Common Value Metrics for SaaS
84 
85| Metric | Best For | Example |
86|--------|---------|---------|
87| **Per seat / user** | Collaboration tools, CRMs | Salesforce, Notion, Linear |
88| **Per usage** | API tools, infrastructure, AI | Stripe, Twilio, OpenAI |
89| **Per feature** | Platform plays, add-ons | Intercom, HubSpot |
90| **Flat fee** | Unlimited-feel, SMB tools | Basecamp, Calendly Basic |
91| **Per outcome** | High-value, measurable ROI | Commission-based tools |
92| **Hybrid** | Mix of above | Most mature SaaS |
93 
94### How to Choose
95 
96Answer these questions:
97 
981. **What makes a customer willing to pay more?** → That's your value metric
992. **Does the metric scale with their success?** → If they grow, you grow
1003. **Is it easy to understand?** → Complexity kills conversion
1014. **Is it hard to game?** → Customers shouldn't be able to work around it
102 
103**Red flags:**
104- "Per seat" in a tool where one power user does all the work → seats don't scale with value
105- "Flat fee" when some customers derive 10x the value of others → you're subsidizing heavy users
106- "Per API call" when call count varies wildly week to week → unpredictable bills = churn
107 
108---
109 
110## Good-Better-Best Tier Structure
111 
112Three tiers is the standard. Not because of tradition — because it anchors perception.
113 
114### Tier Design Principles
115 
116**Entry tier (Good):**
117- Captures the segment that will churn if priced higher
118- Limited — either by features, usage, or support
119- NOT free. Free is a separate strategy (freemium), not a tier.
120- Should cover your costs at minimum
121 
122**Middle tier (Better) — your default:**
123- This is where you push most customers
124- Price: 2-3x the entry tier
125- Features: everything a growing company needs
126- Call it out visually as recommended
127 
128**Top tier (Best):**
129- For high-value customers with enterprise needs
130- May be "Contact us" or custom pricing
131- Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts
132- If you have enterprise deals >$1k MRR, this tier exists to capture them
133 
134### What Goes in Each Tier
135 
136| Feature Category | Entry | Better | Best |
137|----------------|-------|--------|------|
138| Core product | ✅ (limited) | ✅ (full) | ✅ (full) |
139| Usage limits | Low | Medium | High / unlimited |
140| Users/seats | 1-3 | 5-unlimited | Unlimited |
141| Integrations | Basic | Full | Full + custom |
142| Reporting | Basic | Advanced | Custom |
143| Support | Email | Priority | Dedicated CSM |
144| Admin features | — | — | SSO, audit log, SCIM |
145| SLA | — | — | ✅ |
146 
147See [references/pricing-models.md](references/pricing-models.md) for model deep dives and SaaS examples.
148 
149---
150 
151## Value-Based Pricing
152 
153Price between the next-best alternative and your perceived value.
154 
155```
156[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]
157```
158 
159**Step 1: Define the next-best alternative**
160- What would the customer do if your product didn't exist?
161- A competitor? A spreadsheet? Manual process? Hiring someone?
162- What does that cost them?
163 
164**Step 2: Estimate value delivered**
165- Time saved × hourly rate of the person using it
166- Revenue generated or protected
167- Cost of error/risk avoided
168- Ask your best customers: "What would you lose if you stopped using us tomorrow?"
169 
170**Step 3: Price in the middle**
171- A rough heuristic: price at 10-20% of documented value delivered
172- Don't price at 50% of value — customers feel they're overpaying
173- Don't price below the next-best alternative — signals you don't believe in your own product
174 
175**Conversion rate as a signal:**
176- >40% trial-to-paid: likely underpriced — test a price increase
177- 15-30%: healthy for most SaaS
178- <10%: pricing may be high, or trial-to-paid funnel has friction
179 
180---
181 
182## Pricing Research Methods
183 
184### Van Westendorp Price Sensitivity Meter
185 
186Four questions, asked to current customers or target segment:
187 
1881. At what price would this product be so cheap you'd question its quality?
1892. At what price would this product be a bargain — great deal?
1903. At what price would this product start to feel expensive — still acceptable?
1914. At what price would this product be too expensive to consider?
192 
193**Interpret the results:** Plot the four curves. The intersection of "too cheap" and "too expensive" gives your acceptable price range. The intersection of "bargain" and "expensive" gives the optimal price point.
194 
195**When to use:** B2B SaaS, n≥30 respondents, existing customers or qualified prospects.
196 
197### MaxDiff Analysis
198 
199Show respondents sets of features/prices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.
200 
201**When to use:** When deciding which features to put in which tier.
202 
203### Competitor Benchmarking
204 
205| Step | What to Do |
206|------|-----------|
207| 1 | List direct competitors and alternatives customers consider |
208| 2 | Record their published pricing (plan names, prices, value metrics) |
209| 3 | Note what's included at each price point |
210| 4 | Identify where your product over- and under-delivers vs. each |
211| 5 | Price relative to positioning: premium = 20-40% above market, value = at or below |
212 
213**Don't just copy competitor prices** — their pricing reflects their cost structure and positioning, not yours.
214 
215---
216 
217## Price Increase Strategies
218 
219Raising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.
220 
221### Strategy Selection
222 
223| Strategy | Use When | Risk |
224|---------|---------|------|
225| **New customers only** | Significant pushback expected | Low — doesn't touch existing base |
226| **Grandfather + delayed** | Loyal customer base, contract risk | Medium — existing customers feel respected |
227| **Tied to value delivery** | Clear new features/improvement | Low — justifiable |
228| **Plan restructure** | Significant packaging change | Medium — complexity for customers |
229| **Uniform increase** | Confident in value, price is clearly below market | Medium-High |
230 
231### Execution Checklist
232 
2331. **Quantify the move:** Calculate new MRR at 100%, 80%, 70% retention of existing customers
2342. **Segment by risk:** Annual contracts, champions vs. detractors, usage-based at-risk accounts
2353. **Set the date:** 60-90 days notice for existing customers. 30 days minimum.
2364. **Communicate the reason:** New features, rising costs, investment in [X] — be specific
2375. **Offer a path:** Lock in current price for annual commitment, or give a 3-month window
2386. **Arm your CS team:** FAQ, talking points, approved offer authority
2397. **Monitor for 60 days:** Churn rate, downgrade rate, support ticket volume
240 
241**Expected churn from a 20-30% price increase:** 5-15%. If your net revenue impact is positive, proceed.
242 
243---
244 
245## Pricing Page Design
246 
247The pricing page converts intent to purchase. Design it with that job in mind.
248 
249### Above the Fold
250 
251Must have:
252- Plan names (simple: Starter / Pro / Enterprise, or named after customer segment)
253- Price with billing toggle (monthly/annual — annual should show savings)
254- 3-5 bullet differentiators per plan
255- CTA button per plan
256- "Most popular" badge on recommended tier
257 
258### Below the Fold
259 
260- **Full feature comparison table** — comprehensive, scannable, uses ✅ and ❌ not walls of text
261- **FAQ section** — address the 5 objections that stop people from buying:
262 - "Can I cancel anytime?"
263 - "What happens when I hit limits?"
264 - "Do you offer refunds?"
265 - "Is my data secure?"
266 - "What if I need to upgrade/downgrade?"
267- **Social proof** — logos, quotes, or case studies relevant to each tier
268- **Security badges** if B2B enterprise (SOC2, ISO 27001, GDPR)
269 
270### Annual vs. Monthly Toggle
271 
272- Show annual pricing by default (or highlight it) — it improves LTV
273- Show savings explicitly: "Save 20%" or "2 months free"
274- Don't hide the monthly price — hiding it builds distrust
275 
276See [references/pricing-page-playbook.md](references/pricing-page-playbook.md) for design specs and copy templates.
277 
278---
279 
280## Proactive Triggers
281 
282Surface these without being asked:
283 
284- **Conversion rate >40% trial-to-paid** → Strong signal of underpricing. Flag: test 20-30% price increase.
285- **All customers on the middle tier** → No upsell path. Flag: enterprise tier needed or feature lock-in missing.
286- **Customer asked for features that aren't in their tier** → Expansion revenue being left on the table. Flag: feature gatekeeping review.
287- **Churn rate >5% monthly** → Before raising prices, fix churn. Price increases accelerate churners.
288- **Price hasn't changed in 2+ years** → Inflation alone justifies 10-15% increase. Flag for strategic review.
289- **Only one pricing option** → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.
290 
291---
292 
293## Output Artifacts
294 
295| When you ask for... | You get... |
296|--------------------|-----------|
297| "Design pricing" | Three-tier structure with value metric, feature grid, price points, and rationale |
298| "Audit my pricing" | Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins |
299| "Plan a price increase" | Increase strategy selection, communication templates, risk model, 90-day rollout plan |
300| "Design a pricing page" | Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy |
301| "Research pricing" | Van Westendorp survey questions + MaxDiff framework for your specific product |
302| "Model pricing scenarios" | Run `scripts/pricing_modeler.py` with your inputs |
303 
304---
305 
306## Communication
307 
308All output follows the structured communication standard:
309- **Bottom line first** — recommendation before justification
310- **What + Why + How** — every recommendation has all three
311- **Actions have owners and deadlines** — no vague "consider"
312- **Confidence tagging** — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed
313 
314---
315 
316## Related Skills
317 
318- **product-strategist**: Use for product roadmap and broader monetization strategy. NOT for pricing page or price increase execution.
319- **copywriting**: Use for pricing page copy polish. NOT for pricing structure or tier design.
320- **churn-prevention**: Use when churn is the underlying issue — fix retention before raising prices.
321- **ab-test-setup**: Use to A/B test price points or pricing page layouts after initial design.
322- **customer-success-manager**: Use for expansion revenue through upselling. NOT for pricing design or packaging.
323- **competitor-alternatives**: Use for competitive comparison pages that complement pricing pages.
324 

Discussion

Alternatives

Also in Pricing & offersSee all 138 in Sales →
Dynamic Pricing Intelligence Agent — RAISE / HOLD / LOWERData-driven pricing strategy engine for Amazon sellers. Given one or more ASINs, auto-detects each product's leaf category, analyzes the pricing landscape, and delivers RAISE/HOLD/LOWER signals with profit simulation. Supports single ASIN or batch (multiple ASINs, auto-grouped by category). Uses ZooData API endpoints with cross-validation. Use when user asks about: pricing strategy, how much to price, optimal price, price optimization, competitor pricing, price war, BuyBox strategy, profit margin, pricing analysis, should I raise price, should I lower price, price comparison, price positioning, repricing, should I raise or lower price. Requires ZOODATA_API_KEY.Sales & ecommerce · MITOffer DesignTell us what you sell, your price, and who it's for. Get back a stronger deal: better bonuses, a fair guarantee, an honest reason to buy now, and a sharper name and price.Business & ops · MITPaywall and Upgrade Screen CROWhen the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.Marketing · MITPricing StrategyTell us what you sell and who buys it, and get back a clear pricing plan with tiers, price points, and the reasoning behind each number.Business & ops · MIT