Tell us what you sell and who buys it

Pricing Strategy

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Pricing Strategy cover

Tell 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.

---
name: pricing
description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers."
metadata:
  version: 2.1.1
---

# Pricing Strategy

You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

## Before Starting

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

Overview

You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill pricing -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/pricing
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/141b987b620b370c8540/pricing.zip" -OutFile "$env:TEMP\pricing.zip"; Expand-Archive "$env:TEMP\pricing.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md12.9 KB
  • evals/1 file · 9.9 KB
  • references/4 files · 23.2 KB
Read the files here
coreyhaines31/5b2c0006 files
SKILL.md
Show the full text296 lines

Pricing Strategy

You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context
  • What type of product? (SaaS, marketplace, e-commerce, service)
  • What's your current pricing (if any)?
  • What's your target market? (SMB, mid-market, enterprise)
  • What's your go-to-market motion? (self-serve, sales-led, hybrid)
2. Value & Competition
  • What's the primary value you deliver?
  • What alternatives do customers consider?
  • How do competitors price?
3. Current Performance
  • What's your current conversion rate?
  • What's your ARPU and churn rate?
  • Any feedback on pricing from customers/prospects?
4. Goals
  • Optimizing for growth, revenue, or profitability?
  • Moving upmarket or expanding downmarket?

Pricing Fundamentals

The Three Pricing Axes

1. Packaging — What's included at each tier?

  • Features, limits, support level
  • How tiers differ from each other

2. Pricing Metric — What do you charge for?

  • Per user, per usage, flat fee
  • How price scales with value

3. Price Point — How much do you charge?

  • The actual dollar amounts
  • Perceived value vs. cost
Value-Based Pricing

Price should be based on value delivered, not cost to serve:

  • Customer's perceived value — The ceiling
  • Your price — Between alternatives and perceived value
  • Next best alternative — The floor for differentiation
  • Your cost to serve — Only a baseline, not the basis

Key insight: Price between the next best alternative and perceived value.

Don't anchor on the wrong things:

  • Not competitor-based — matching a competitor's price copies their strategy, not their economics. It's a data point, not a target.
  • Not cost-based — cost is a floor, never the basis. Value + differentiation set the price.

Initial Pricing — "Pick a Price You Can Learn From"

The frameworks below (value metrics, tiers, Van Westendorp) are for optimizing a price. On day one you don't have a price to optimize — you have a bet to place. The goal of your first price is learning, not precision. Pick a number, ship it, and let real buyers tell you if it's wrong.

The $10 / $100 / $1,000 rule of thumb

When you have nothing to go on, start with the order of magnitude that matches who you serve:

  • ~$10/mo — prosumer / individual, high volume, low touch
  • ~$100/mo — SMB / team tool, the SaaS default
  • ~$1,000/mo — mid-market / business-critical / sales-assisted

Pick the bucket by who the customer is and how much value you deliver, then start near the round number. You can move within the bucket fast once you have signal.

Avoid the $9 trap

Resist the urge to price ultra-low (e.g. $9/mo) to reduce friction. Ultra-low pricing:

  • Creates false traction — signups that look like validation but come from people who'd never pay a real price
  • Traps you — it's far harder to raise a price 5–10x later than to have started higher, and your cheapest customers churn most and complain loudest (see references/pricing-models.md on low-price retention)

Round-and-slightly-higher beats clever-and-cheap.

"Just charge $50 and see what happens"

When early Intercom agonized over pricing, Jason Fried's advice was essentially: just charge $50 and see what happens. Stop modeling; get a real signal. If people pay without flinching, raise it. If nobody bites, you've learned something for the cost of a week, not a quarter.

For the eight ways to structure how you charge (flat, usage, tier, user, feature, credit, outcome, hybrid) and the value/price ratio: See references/pricing-models.md.


Value Metrics

What is a Value Metric?

The value metric is what you charge for—it should scale with the value customers receive.

Good value metrics:

  • Align price with value delivered
  • Are easy to understand
  • Scale as customer grows
  • Are hard to game
Common Value Metrics
Metric Best For Example
Per user/seat Collaboration tools Slack, Notion
Per usage Variable consumption AWS, Twilio
Per feature Modular products HubSpot add-ons
Per contact/record CRM, email tools Mailchimp
Per transaction Payments, marketplaces Stripe
Flat fee Simple products Basecamp
Choosing Your Value Metric

Ask: "As a customer uses more of [metric], do they get more value?"

  • If yes → good value metric
  • If no → price doesn't align with value

The value metric picks the pricing model. Once you know what scales with value, choose how to charge on it — flat, usage, tier, user, feature, credit, outcome, or a hybrid. See references/pricing-models.md.


Tier Structure Overview

Good-Better-Best Framework

Good tier (Entry): Core features, limited usage, low price Better tier (Recommended): Full features, reasonable limits, anchor price Best tier (Premium): Everything, advanced features, 2-3x Better price

Tier Differentiation
  • Feature gating — Basic vs. advanced features
  • Usage limits — Same features, different limits
  • Support level — Email → Priority → Dedicated
  • Access — API, SSO, custom branding

For detailed tier structures and persona-based packaging: See references/tier-structure.md


Pricing Research

Van Westendorp Method

Four questions that identify acceptable price range:

  1. Too expensive (wouldn't consider)
  2. Too cheap (question quality)
  3. Expensive but might consider
  4. A bargain

Analyze intersections to find optimal pricing zone.

MaxDiff Analysis

Identifies which features customers value most:

  • Show sets of features
  • Ask: Most important? Least important?
  • Results inform tier packaging

For detailed research methods: See references/research-methods.md


When to Raise Prices

Signs It's Time

Market signals:

  • Competitors have raised prices
  • Prospects don't flinch at price
  • "It's so cheap!" feedback

Business signals:

  • Very high conversion rates (>40%)
  • Very low churn (<3% monthly)
  • Strong unit economics

Product signals:

  • Significant value added since last pricing
  • Product more mature/stable
Price Increase Strategies
  1. Grandfather existing — New price for new customers only
  2. Delayed increase — Announce 3-6 months out
  3. Tied to value — Raise price but add features
  4. Plan restructure — Change plans entirely
Rollout Methodology

A price change is a rollout, not a switch you flip. Sequence it to de-risk:

  1. Test on new customers first. Raise the price only for new signups and watch conversion. New customers have no anchor and no relationship at stake, so they give you a clean read on whether the market accepts the number — before you touch a single existing account.
  2. Don't reflexively grandfather forever. Grandfathering feels kind, but it can leave enormous money on the table. Run the math: a customer paying $50/mo who should be at $250/mo is a $2,400/yr gap — and $200/mo you're subsidizing indefinitely across your whole base. Grandfather as a transition (a grace period), not a permanent exemption.
  3. Roll out small, then gradually. Move 5–10% of existing customers to the new price first. Watch churn and support volume for a cycle, then expand in staggered waves. A staggered rollout contains the blast radius and gives you an off-ramp if churn spikes.
  4. Communicate the why, months ahead, with a generous offer. Tell customers why the price is changing (usually: more value shipped) well in advance. Soften it: lock-in-the-old-price-if-you-upgrade-to-annual-now, an extended grace window, or a one-time credit. Advance notice + a generous option converts a resentment moment into a loyalty one.

Expect — and accept — some churn. The customers most likely to leave over a justified increase are usually your least-profitable, highest-support, most price-sensitive accounts.


Pricing Page Best Practices

Above the Fold
  • Clear tier comparison table
  • Recommended tier highlighted
  • Monthly/annual toggle
  • Primary CTA for each tier
Common Elements
  • Feature comparison table
  • Who each tier is for
  • FAQ section
  • Annual discount callout (17-20%)
  • Money-back guarantee
  • Customer logos/trust signals
Pricing Psychology
  • Anchoring: Show higher-priced option first
  • Decoy effect: Middle tier should be best value
  • Charm pricing: $49 vs. $50 (for value-focused)
  • Round pricing: $50 vs. $49 (for premium)

Pricing Page Teardown

When someone wants to audit an existing pricing page for clarity, transparency, and AI-readability (not the pricing strategy itself, and not conversion-rate optimization — that's cro), run a teardown that scores it across two axes and returns prioritized fixes:

  • Human buyer experience — value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.
  • AI-agent readiness — whether the LLMs and agents that increasingly shortlist and compare tools can actually read and quote your pricing: machine-readable prices (not locked in an image or behind "Contact us"), extractable FAQ/objection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT/Perplexity/Claude "what's the best X and what does it cost?" before visiting — a pricing page an agent can't parse loses deals you never see.

Fast check — the "paste test": give the pricing URL to a browsing-capable AI (Perplexity, ChatGPT with search, Claude with web) — or paste the rendered page text — and ask "what are the plans and prices?" A clean miss means agents fetching your page will struggle too (a heuristic, not proof every agent fails).

The AI-readiness fixes are usually high-impact, low-effort (put prices in text, add Offer schema). Hand implementation to schema (Product/Offer JSON-LD) and ai-seo (extractability, AI-bot access, llms.txt).

For the full 10-dimension rubric, scoring, and report template: See references/pricing-page-teardown.md. (AI-agent-readiness lens adapted from Kyle Poyar / Growth Unhinged.)


Pricing Checklist

Before Setting Prices
  • Defined target customer personas
  • Researched competitor pricing
  • Identified your value metric
  • Conducted willingness-to-pay research
  • Mapped features to tiers
Pricing Structure
  • Chosen number of tiers
  • Differentiated tiers clearly
  • Set price points based on research
  • Created annual discount strategy
  • Planned enterprise/custom tier

Task-Specific Questions

  1. What pricing research have you done?
  2. What's your current ARPU and conversion rate?
  3. What's your primary value metric?
  4. Who are your main pricing personas?
  5. Are you self-serve, sales-led, or hybrid?
  6. What pricing changes are you considering?

  • churn-prevention: For cancel flows, save offers, and reducing revenue churn
  • cro: For optimizing pricing page conversion
  • ai-seo: For making the pricing page extractable/citable by AI (the teardown's AI-agent-readiness axis)
  • schema: For Product/Offer structured data so machines can read your tiers and prices
  • copywriting: For pricing page copy
  • marketing-psychology: For pricing psychology principles
  • ab-testing: For testing pricing changes
  • revops: For deal desk processes and pipeline pricing
  • sales-enablement: For proposal templates and pricing presentations
1---
2name: pricing
3description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers."
4metadata:
5 version: 2.1.1
6---
7 
8# Pricing Strategy
9 
10You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
11 
12## Before Starting
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17Gather this context (ask if not provided):
18 
19### 1. Business Context
20- What type of product? (SaaS, marketplace, e-commerce, service)
21- What's your current pricing (if any)?
22- What's your target market? (SMB, mid-market, enterprise)
23- What's your go-to-market motion? (self-serve, sales-led, hybrid)
24 
25### 2. Value & Competition
26- What's the primary value you deliver?
27- What alternatives do customers consider?
28- How do competitors price?
29 
30### 3. Current Performance
31- What's your current conversion rate?
32- What's your ARPU and churn rate?
33- Any feedback on pricing from customers/prospects?
34 
35### 4. Goals
36- Optimizing for growth, revenue, or profitability?
37- Moving upmarket or expanding downmarket?
38 
39---
40 
41## Pricing Fundamentals
42 
43### The Three Pricing Axes
44 
45**1. Packaging** — What's included at each tier?
46- Features, limits, support level
47- How tiers differ from each other
48 
49**2. Pricing Metric** — What do you charge for?
50- Per user, per usage, flat fee
51- How price scales with value
52 
53**3. Price Point** — How much do you charge?
54- The actual dollar amounts
55- Perceived value vs. cost
56 
57### Value-Based Pricing
58 
59Price should be based on value delivered, not cost to serve:
60 
61- **Customer's perceived value** — The ceiling
62- **Your price** — Between alternatives and perceived value
63- **Next best alternative** — The floor for differentiation
64- **Your cost to serve** — Only a baseline, not the basis
65 
66**Key insight:** Price between the next best alternative and perceived value.
67 
68**Don't anchor on the wrong things:**
69- **Not competitor-based** — matching a competitor's price copies their strategy, not their economics. It's a data point, not a target.
70- **Not cost-based** — cost is a floor, never the basis. Value + differentiation set the price.
71 
72---
73 
74## Initial Pricing — "Pick a Price You Can Learn From"
75 
76The frameworks below (value metrics, tiers, Van Westendorp) are for optimizing a price. **On day one you don't have a price to optimize — you have a bet to place.** The goal of your first price is *learning*, not precision. Pick a number, ship it, and let real buyers tell you if it's wrong.
77 
78### The $10 / $100 / $1,000 rule of thumb
79 
80When you have nothing to go on, start with the order of magnitude that matches who you serve:
81 
82- **~$10/mo** — prosumer / individual, high volume, low touch
83- **~$100/mo** — SMB / team tool, the SaaS default
84- **~$1,000/mo** — mid-market / business-critical / sales-assisted
85 
86Pick the bucket by **who the customer is and how much value you deliver**, then start near the round number. You can move within the bucket fast once you have signal.
87 
88### Avoid the $9 trap
89 
90Resist the urge to price ultra-low (e.g. **$9/mo**) to reduce friction. Ultra-low pricing:
91- Creates **false traction** — signups that look like validation but come from people who'd never pay a real price
92- **Traps you** — it's far harder to raise a price 5–10x later than to have started higher, and your cheapest customers churn most and complain loudest (see [references/pricing-models.md](references/pricing-models.md) on low-price retention)
93 
94Round-and-slightly-higher beats clever-and-cheap.
95 
96### "Just charge $50 and see what happens"
97 
98When early Intercom agonized over pricing, Jason Fried's advice was essentially: **just charge $50 and see what happens.** Stop modeling; get a real signal. If people pay without flinching, raise it. If nobody bites, you've learned something for the cost of a week, not a quarter.
99 
100**For the eight ways to structure how you charge (flat, usage, tier, user, feature, credit, outcome, hybrid) and the value/price ratio:** See [references/pricing-models.md](references/pricing-models.md).
101 
102---
103 
104## Value Metrics
105 
106### What is a Value Metric?
107 
108The value metric is what you charge for—it should scale with the value customers receive.
109 
110**Good value metrics:**
111- Align price with value delivered
112- Are easy to understand
113- Scale as customer grows
114- Are hard to game
115 
116### Common Value Metrics
117 
118| Metric | Best For | Example |
119|--------|----------|---------|
120| Per user/seat | Collaboration tools | Slack, Notion |
121| Per usage | Variable consumption | AWS, Twilio |
122| Per feature | Modular products | HubSpot add-ons |
123| Per contact/record | CRM, email tools | Mailchimp |
124| Per transaction | Payments, marketplaces | Stripe |
125| Flat fee | Simple products | Basecamp |
126 
127### Choosing Your Value Metric
128 
129Ask: "As a customer uses more of [metric], do they get more value?"
130- If yes → good value metric
131- If no → price doesn't align with value
132 
133**The value metric picks the pricing model.** Once you know what scales with value, choose how to charge on it — flat, usage, tier, user, feature, credit, outcome, or a hybrid. See [references/pricing-models.md](references/pricing-models.md).
134 
135---
136 
137## Tier Structure Overview
138 
139### Good-Better-Best Framework
140 
141**Good tier (Entry):** Core features, limited usage, low price
142**Better tier (Recommended):** Full features, reasonable limits, anchor price
143**Best tier (Premium):** Everything, advanced features, 2-3x Better price
144 
145### Tier Differentiation
146 
147- **Feature gating** — Basic vs. advanced features
148- **Usage limits** — Same features, different limits
149- **Support level** — Email → Priority → Dedicated
150- **Access** — API, SSO, custom branding
151 
152**For detailed tier structures and persona-based packaging**: See [references/tier-structure.md](references/tier-structure.md)
153 
154---
155 
156## Pricing Research
157 
158### Van Westendorp Method
159 
160Four questions that identify acceptable price range:
1611. Too expensive (wouldn't consider)
1622. Too cheap (question quality)
1633. Expensive but might consider
1644. A bargain
165 
166Analyze intersections to find optimal pricing zone.
167 
168### MaxDiff Analysis
169 
170Identifies which features customers value most:
171- Show sets of features
172- Ask: Most important? Least important?
173- Results inform tier packaging
174 
175**For detailed research methods**: See [references/research-methods.md](references/research-methods.md)
176 
177---
178 
179## When to Raise Prices
180 
181### Signs It's Time
182 
183**Market signals:**
184- Competitors have raised prices
185- Prospects don't flinch at price
186- "It's so cheap!" feedback
187 
188**Business signals:**
189- Very high conversion rates (>40%)
190- Very low churn (<3% monthly)
191- Strong unit economics
192 
193**Product signals:**
194- Significant value added since last pricing
195- Product more mature/stable
196 
197### Price Increase Strategies
198 
1991. **Grandfather existing** — New price for new customers only
2002. **Delayed increase** — Announce 3-6 months out
2013. **Tied to value** — Raise price but add features
2024. **Plan restructure** — Change plans entirely
203 
204### Rollout Methodology
205 
206A price change is a rollout, not a switch you flip. Sequence it to de-risk:
207 
2081. **Test on new customers first.** Raise the price only for *new* signups and watch conversion. New customers have no anchor and no relationship at stake, so they give you a clean read on whether the market accepts the number — before you touch a single existing account.
2092. **Don't reflexively grandfather forever.** Grandfathering feels kind, but it can leave enormous money on the table. Run the math: a customer paying **$50/mo** who *should* be at **$250/mo** is a **$2,400/yr** gap — and $200/mo you're subsidizing indefinitely across your whole base. Grandfather as a *transition* (a grace period), not a permanent exemption.
2103. **Roll out small, then gradually.** Move **5–10%** of existing customers to the new price first. Watch churn and support volume for a cycle, then expand in staggered waves. A staggered rollout contains the blast radius and gives you an off-ramp if churn spikes.
2114. **Communicate the *why*, months ahead, with a generous offer.** Tell customers why the price is changing (usually: more value shipped) well in advance. Soften it: lock-in-the-old-price-if-you-upgrade-to-annual-now, an extended grace window, or a one-time credit. Advance notice + a generous option converts a resentment moment into a loyalty one.
212 
213Expect — and accept — some churn. The customers most likely to leave over a justified increase are usually your least-profitable, highest-support, most price-sensitive accounts.
214 
215---
216 
217## Pricing Page Best Practices
218 
219### Above the Fold
220- Clear tier comparison table
221- Recommended tier highlighted
222- Monthly/annual toggle
223- Primary CTA for each tier
224 
225### Common Elements
226- Feature comparison table
227- Who each tier is for
228- FAQ section
229- Annual discount callout (17-20%)
230- Money-back guarantee
231- Customer logos/trust signals
232 
233### Pricing Psychology
234- **Anchoring:** Show higher-priced option first
235- **Decoy effect:** Middle tier should be best value
236- **Charm pricing:** $49 vs. $50 (for value-focused)
237- **Round pricing:** $50 vs. $49 (for premium)
238 
239---
240 
241## Pricing Page Teardown
242 
243When someone wants to audit an existing pricing *page* for **clarity, transparency, and AI-readability** (not the pricing strategy itself, and not conversion-rate optimization — that's `cro`), run a **teardown** that scores it across two axes and returns prioritized fixes:
244 
245- **Human buyer experience** — value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.
246- **AI-agent readiness** — whether the LLMs and agents that increasingly shortlist and compare tools can actually read and quote your pricing: machine-readable prices (not locked in an image or behind "Contact us"), extractable FAQ/objection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT/Perplexity/Claude "what's the best X and what does it cost?" *before* visiting — a pricing page an agent can't parse loses deals you never see.
247 
248**Fast check — the "paste test":** give the pricing URL to a browsing-capable AI (Perplexity, ChatGPT with search, Claude with web) — or paste the rendered page text — and ask "what are the plans and prices?" A clean miss means agents fetching your page will struggle too (a heuristic, not proof every agent fails).
249 
250The AI-readiness fixes are usually high-impact, low-effort (put prices in text, add `Offer` schema). Hand implementation to **schema** (Product/Offer JSON-LD) and **ai-seo** (extractability, AI-bot access, `llms.txt`).
251 
252**For the full 10-dimension rubric, scoring, and report template:** See [references/pricing-page-teardown.md](references/pricing-page-teardown.md). *(AI-agent-readiness lens adapted from Kyle Poyar / Growth Unhinged.)*
253 
254---
255 
256## Pricing Checklist
257 
258### Before Setting Prices
259- [ ] Defined target customer personas
260- [ ] Researched competitor pricing
261- [ ] Identified your value metric
262- [ ] Conducted willingness-to-pay research
263- [ ] Mapped features to tiers
264 
265### Pricing Structure
266- [ ] Chosen number of tiers
267- [ ] Differentiated tiers clearly
268- [ ] Set price points based on research
269- [ ] Created annual discount strategy
270- [ ] Planned enterprise/custom tier
271 
272---
273 
274## Task-Specific Questions
275 
2761. What pricing research have you done?
2772. What's your current ARPU and conversion rate?
2783. What's your primary value metric?
2794. Who are your main pricing personas?
2805. Are you self-serve, sales-led, or hybrid?
2816. What pricing changes are you considering?
282 
283---
284 
285## Related Skills
286 
287- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn
288- **cro**: For optimizing pricing page conversion
289- **ai-seo**: For making the pricing page extractable/citable by AI (the teardown's AI-agent-readiness axis)
290- **schema**: For Product/Offer structured data so machines can read your tiers and prices
291- **copywriting**: For pricing page copy
292- **marketing-psychology**: For pricing psychology principles
293- **ab-testing**: For testing pricing changes
294- **revops**: For deal desk processes and pipeline pricing
295- **sales-enablement**: For proposal templates and pricing presentations
296 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillDesign or optimize their app's monetizationMobile App Monetization Strategyappeeky/aso-skills · by appeekyWhen the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.★ 2.2k GitHub starsSkillDesign, test, or optimize their app's paywallPaywall Optimization (Subscription Apps)appeeky/aso-skills · by appeekyWhen the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.★ 2.2k GitHub starsSkillSets price, structures packages and tiersPricing and packagingcbrock84/headcount · by cbrock84Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.★ 2k GitHub starsSkillHelp users validate willingness-to-payPricing Strategy (Lenny's Podcast)RefoundAI/lenny-skills · by RefoundAIHelp users validate willingness-to-pay, select the right value metrics, and continuously optimize pricing and packaging to drive growth.★ 1.4k GitHub starsSkillDesigns a deliberate sequence of offers so a new customer$100M Money Modelsgetagentseal/founder-playbook · by getagentsealDesigns a deliberate sequence of offers (attraction, upsell, downsell, continuity) so a new customer generates enough cash within ~30 days to fund acquiring the next one - Alex Hormozi's client-financed acquisition. Use when customers buy once and never again, when CAC eats all the profit, when you can't afford to advertise profitably, when the business grows but cash shrinks, when you sell one product at one price, when deciding what to sell first or next, or when structuring upsells, downsells, payment plans, trials, and continuity. Covers the 30-day payback rule, attraction/upsell/downsell/continuity offer types, and cash-flow sequencing for validated markets.★ 729 GitHub starsSkillDesigns irresistible Grand Slam Offers using Alex Hormozi's$100M Offersgetagentseal/founder-playbook · by getagentsealDesigns irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns. Use when fixing low conversion rates, packaging products, pricing services, designing high-converting offers, or when prospects browse but don't buy. Covers value stacking, guarantees, scarcity, urgency, and pricing psychology for validated markets.★ 729 GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars