[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWDX29X4920TP35FGQ08DV":3,"skill-same:01M7CWDX29X4920TP35FGQ08DV":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CWDX29X4920TP35FGQ08DV","pricing",null,"When the user wants to set pricing and packaging, or asks what to charge, whether to raise prices, or how to move existing customers: tiers, value metrics, per-seat vs usage, freemium and trials, willingness to pay, pricing pages. For in-app upgrade screens, see paywalls. For offers on services, courses, and high-ticket B2B, see offers.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pricing\ndescription: \"When the user wants to set pricing and packaging, or asks what to charge, whether to raise prices, or how to move existing customers: tiers, value metrics, per-seat vs usage, freemium and trials, willingness to pay, pricing pages. For in-app upgrade screens, see paywalls. For offers on services, courses, and high-ticket B2B, see offers.\"\nmetadata:\n  version: 2.1.7\n---\n\n# Pricing Strategy\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What type of product? (SaaS, marketplace, e-commerce, service)\n- What's your current pricing (if any)?\n- What's your target market? (SMB, mid-market, enterprise)\n- What's your go-to-market motion? (self-serve, sales-led, hybrid)\n\n### 2. Value & Competition\n- What's the primary value you deliver?\n- What alternatives do customers consider?\n- How do competitors price?\n\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your ARPU and churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Optimizing for growth, revenue, or profitability?\n- Moving upmarket or expanding downmarket?\n\n---\n\n## Pricing Fundamentals\n\n### The Three Pricing Axes\n\n**1. Packaging** — What's included at each tier?\n- Features, limits, support level\n- How tiers differ from each other\n\n**2. Pricing Metric** — What do you charge for?\n- Per user, per usage, flat fee\n- How price scales with value\n\n**3. Price Point** — How much do you charge?\n- The actual dollar amounts\n- Perceived value vs. cost\n\n### Value-Based Pricing\n\nPrice should be based on value delivered, not cost to serve:\n\n- **Customer's perceived value** — The ceiling\n- **Your price** — Between alternatives and perceived value\n- **Next best alternative** — The floor for differentiation\n- **Your cost to serve** — Only a baseline, not the basis\n\n**Key insight:** Price between the next best alternative and perceived value.\n\n**Don't anchor on the wrong things:**\n- **Not competitor-based** — matching a competitor's price copies their strategy, not their economics. It's a data point, not a target.\n- **Not cost-based** — cost is a floor, never the basis. Value + differentiation set the price.\n\n---\n\n## Initial Pricing — \"Pick a Price You Can Learn From\"\n\nThe 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.\n\n### The $10 \u002F $100 \u002F $1,000 rule of thumb\n\nWhen you have nothing to go on, start with the order of magnitude that matches who you serve:\n\n- **~$10\u002Fmo** — prosumer \u002F individual, high volume, low touch\n- **~$100\u002Fmo** — SMB \u002F team tool, the SaaS default\n- **~$1,000\u002Fmo** — mid-market \u002F business-critical \u002F sales-assisted\n\nPick 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.\n\n### Avoid the $9 trap\n\nResist the urge to price ultra-low (e.g. **$9\u002Fmo**) to reduce friction. Ultra-low pricing:\n- Creates **false traction** — signups that look like validation but come from people who'd never pay a real price\n- **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\u002Fpricing-models.md](references\u002Fpricing-models.md) on low-price retention)\n\nRound-and-slightly-higher beats clever-and-cheap.\n\n### \"Just charge $50 and see what happens\"\n\nWhen 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.\n\n**For the eight ways to structure how you charge (flat, usage, tier, user, feature, credit, outcome, hybrid) and the value\u002Fprice ratio:** See [references\u002Fpricing-models.md](references\u002Fpricing-models.md).\n\n---\n\n## Value Metrics\n\n### What is a Value Metric?\n\nThe value metric is what you charge for—it should scale with the value customers receive.\n\n**Good value metrics:**\n- Align price with value delivered\n- Are easy to understand\n- Scale as customer grows\n- Are hard to game\n\n### Common Value Metrics\n\n| Metric | Best For | Example |\n|--------|----------|---------|\n| Per user\u002Fseat | Collaboration tools | Slack, Notion |\n| Per usage | Variable consumption | AWS, Twilio |\n| Per feature | Modular products | HubSpot add-ons |\n| Per contact\u002Frecord | CRM, email tools | Mailchimp |\n| Per transaction | Payments, marketplaces | Stripe |\n| Flat fee | Simple products | Basecamp |\n\n### Choosing Your Value Metric\n\nAsk: \"As a customer uses more of [metric], do they get more value?\"\n- If yes → good value metric\n- If no → price doesn't align with value\n\n**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\u002Fpricing-models.md](references\u002Fpricing-models.md).\n\n---\n\n## Tier Structure Overview\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):** Core features, limited usage, low price\n**Better tier (Recommended):** Full features, reasonable limits, anchor price\n**Best tier (Premium):** Everything, advanced features, 2-3x Better price\n\n### Tier Differentiation\n\n- **Feature gating** — Basic vs. advanced features\n- **Usage limits** — Same features, different limits\n- **Support level** — Email → Priority → Dedicated\n- **Access** — API, SSO, custom branding\n\n**For detailed tier structures and persona-based packaging**: See [references\u002Ftier-structure.md](references\u002Ftier-structure.md)\n\n---\n\n## Pricing Research\n\n### Van Westendorp Method\n\nFour questions that identify acceptable price range:\n1. Too expensive (wouldn't consider)\n2. Too cheap (question quality)\n3. Expensive but might consider\n4. A bargain\n\nUse intersections to identify perceived price acceptability and candidate prices to test. The named \"Optimal Price Point\" is a survey intersection, not proof of revenue or profit maximization. The four questions alone do not estimate conversion, churn or demand at a new price.\n\n### MaxDiff Analysis\n\nIdentifies which features customers value most:\n- Show sets of features\n- Ask: Most important? Least important?\n- Results inform tier packaging\n\n**For detailed research methods**: See [references\u002Fresearch-methods.md](references\u002Fresearch-methods.md)\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Very high conversion rates (>40%)\n- Very low churn (\u003C3% monthly)\n- Strong unit economics\n\n**Product signals:**\n- Significant value added since last pricing\n- Product more mature\u002Fstable\n\n### Price Increase Strategies\n\n1. **Grandfather existing** — New price for new customers only\n2. **Delayed increase** — Announce 3-6 months out\n3. **Tied to value** — Raise price but add features\n4. **Plan restructure** — Change plans entirely\n\n### Rollout Methodology\n\nA price change is a rollout, not a switch you flip. Sequence it to de-risk:\n\n1. **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.\n2. **Don't reflexively grandfather forever.** Grandfathering feels kind, but it can leave enormous money on the table. Run the math: a customer paying **$50\u002Fmo** who *should* be at **$250\u002Fmo** is a **$2,400\u002Fyr** gap — and $200\u002Fmo you're subsidizing indefinitely across your whole base. Grandfather as a *transition* (a grace period), not a permanent exemption.\n3. **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.\n4. **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.\n\nExpect — 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.\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Common Elements\n- Feature comparison table\n- Who each tier is for\n- FAQ section\n- Annual discount callout (17-20%)\n- Money-back guarantee\n- Customer logos\u002Ftrust signals\n\n### Pricing Psychology\n- **Anchoring:** Show higher-priced option first\n- **Decoy effect:** Middle tier should be best value\n- **Charm pricing:** $49 vs. $50 (for value-focused)\n- **Round pricing:** $50 vs. $49 (for premium)\n\n---\n\n## Pricing Page Teardown\n\nWhen 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:\n\n- **Human buyer experience** — value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.\n- **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\u002Fobjection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT\u002FPerplexity\u002FClaude \"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.\n\n**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).\n\nThe AI-readiness fixes are usually high-impact, low-effort (put prices in text, add `Offer` schema). Hand implementation to **schema** (Product\u002FOffer JSON-LD) and **ai-seo** (extractability, AI-bot access, `llms.txt`).\n\n**For the full 10-dimension rubric, scoring, and report template:** See [references\u002Fpricing-page-teardown.md](references\u002Fpricing-page-teardown.md). *(AI-agent-readiness lens adapted from Kyle Poyar \u002F Growth Unhinged.)*\n\n---\n\n## Pricing Checklist\n\n### Before Setting Prices\n- [ ] Defined target customer personas\n- [ ] Researched competitor pricing\n- [ ] Identified your value metric\n- [ ] Conducted willingness-to-pay research\n- [ ] Mapped features to tiers\n\n### Pricing Structure\n- [ ] Chosen number of tiers\n- [ ] Differentiated tiers clearly\n- [ ] Set price points based on research\n- [ ] Created annual discount strategy\n- [ ] Planned enterprise\u002Fcustom tier\n\n---\n\n## Task-Specific Questions\n\n1. What pricing research have you done?\n2. What's your current ARPU and conversion rate?\n3. What's your primary value metric?\n4. Who are your main pricing personas?\n5. Are you self-serve, sales-led, or hybrid?\n6. What pricing changes are you considering?\n\n---\n\n## Related Skills\n\n- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn\n- **cro**: For optimizing pricing page conversion\n- **ai-seo**: For making the pricing page extractable\u002Fcitable by AI (the teardown's AI-agent-readiness axis)\n- **schema**: For Product\u002FOffer structured data so machines can read your tiers and prices\n- **copywriting**: For pricing page copy\n- **marketing-psychology**: For pricing psychology principles\n- **ab-testing**: For testing pricing changes\n- **revops**: For deal desk processes and pipeline pricing\n- **sales-enablement**: For proposal templates and pricing presentations\n","# Pricing Strategy\n\nYou 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.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-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.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What type of product? (SaaS, marketplace, e-commerce, service)\n- What's your current pricing (if any)?\n- What's your target market? (SMB, mid-market, enterprise)\n- What's your go-to-market motion? (self-serve, sales-led, hybrid)\n\n### 2. Value & Competition\n- What's the primary value you deliver?\n- What alternatives do customers consider?\n- How do competitors price?\n\n### 3. Current Performance\n- What's your current conversion rate?\n- What's your ARPU and churn rate?\n- Any feedback on pricing from customers\u002Fprospects?\n\n### 4. Goals\n- Optimizing for growth, revenue, or profitability?\n- Moving upmarket or expanding downmarket?\n\n---\n\n## Pricing Fundamentals\n\n### The Three Pricing Axes\n\n**1. Packaging** — What's included at each tier?\n- Features, limits, support level\n- How tiers differ from each other\n\n**2. Pricing Metric** — What do you charge for?\n- Per user, per usage, flat fee\n- How price scales with value\n\n**3. Price Point** — How much do you charge?\n- The actual dollar amounts\n- Perceived value vs. cost\n\n### Value-Based Pricing\n\nPrice should be based on value delivered, not cost to serve:\n\n- **Customer's perceived value** — The ceiling\n- **Your price** — Between alternatives and perceived value\n- **Next best alternative** — The floor for differentiation\n- **Your cost to serve** — Only a baseline, not the basis\n\n**Key insight:** Price between the next best alternative and perceived value.\n\n**Don't anchor on the wrong things:**\n- **Not competitor-based** — matching a competitor's price copies their strategy, not their economics. It's a data point, not a target.\n- **Not cost-based** — cost is a floor, never the basis. Value + differentiation set the price.\n\n---\n\n## Initial Pricing — \"Pick a Price You Can Learn From\"\n\nThe 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.\n\n### The $10 \u002F $100 \u002F $1,000 rule of thumb\n\nWhen you have nothing to go on, start with the order of magnitude that matches who you serve:\n\n- **~$10\u002Fmo** — prosumer \u002F individual, high volume, low touch\n- **~$100\u002Fmo** — SMB \u002F team tool, the SaaS default\n- **~$1,000\u002Fmo** — mid-market \u002F business-critical \u002F sales-assisted\n\nPick 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.\n\n### Avoid the $9 trap\n\nResist the urge to price ultra-low (e.g. **$9\u002Fmo**) to reduce friction. Ultra-low pricing:\n- Creates **false traction** — signups that look like validation but come from people who'd never pay a real price\n- **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\u002Fpricing-models.md](references\u002Fpricing-models.md) on low-price retention)\n\nRound-and-slightly-higher beats clever-and-cheap.\n\n### \"Just charge $50 and see what happens\"\n\nWhen 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.\n\n**For the eight ways to structure how you charge (flat, usage, tier, user, feature, credit, outcome, hybrid) and the value\u002Fprice ratio:** See [references\u002Fpricing-models.md](references\u002Fpricing-models.md).\n\n---\n\n## Value Metrics\n\n### What is a Value Metric?\n\nThe value metric is what you charge for—it should scale with the value customers receive.\n\n**Good value metrics:**\n- Align price with value delivered\n- Are easy to understand\n- Scale as customer grows\n- Are hard to game\n\n### Common Value Metrics\n\n| Metric | Best For | Example |\n|--------|----------|---------|\n| Per user\u002Fseat | Collaboration tools | Slack, Notion |\n| Per usage | Variable consumption | AWS, Twilio |\n| Per feature | Modular products | HubSpot add-ons |\n| Per contact\u002Frecord | CRM, email tools | Mailchimp |\n| Per transaction | Payments, marketplaces | Stripe |\n| Flat fee | Simple products | Basecamp |\n\n### Choosing Your Value Metric\n\nAsk: \"As a customer uses more of [metric], do they get more value?\"\n- If yes → good value metric\n- If no → price doesn't align with value\n\n**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\u002Fpricing-models.md](references\u002Fpricing-models.md).\n\n---\n\n## Tier Structure Overview\n\n### Good-Better-Best Framework\n\n**Good tier (Entry):** Core features, limited usage, low price\n**Better tier (Recommended):** Full features, reasonable limits, anchor price\n**Best tier (Premium):** Everything, advanced features, 2-3x Better price\n\n### Tier Differentiation\n\n- **Feature gating** — Basic vs. advanced features\n- **Usage limits** — Same features, different limits\n- **Support level** — Email → Priority → Dedicated\n- **Access** — API, SSO, custom branding\n\n**For detailed tier structures and persona-based packaging**: See [references\u002Ftier-structure.md](references\u002Ftier-structure.md)\n\n---\n\n## Pricing Research\n\n### Van Westendorp Method\n\nFour questions that identify acceptable price range:\n1. Too expensive (wouldn't consider)\n2. Too cheap (question quality)\n3. Expensive but might consider\n4. A bargain\n\nUse intersections to identify perceived price acceptability and candidate prices to test. The named \"Optimal Price Point\" is a survey intersection, not proof of revenue or profit maximization. The four questions alone do not estimate conversion, churn or demand at a new price.\n\n### MaxDiff Analysis\n\nIdentifies which features customers value most:\n- Show sets of features\n- Ask: Most important? Least important?\n- Results inform tier packaging\n\n**For detailed research methods**: See [references\u002Fresearch-methods.md](references\u002Fresearch-methods.md)\n\n---\n\n## When to Raise Prices\n\n### Signs It's Time\n\n**Market signals:**\n- Competitors have raised prices\n- Prospects don't flinch at price\n- \"It's so cheap!\" feedback\n\n**Business signals:**\n- Very high conversion rates (>40%)\n- Very low churn (\u003C3% monthly)\n- Strong unit economics\n\n**Product signals:**\n- Significant value added since last pricing\n- Product more mature\u002Fstable\n\n### Price Increase Strategies\n\n1. **Grandfather existing** — New price for new customers only\n2. **Delayed increase** — Announce 3-6 months out\n3. **Tied to value** — Raise price but add features\n4. **Plan restructure** — Change plans entirely\n\n### Rollout Methodology\n\nA price change is a rollout, not a switch you flip. Sequence it to de-risk:\n\n1. **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.\n2. **Don't reflexively grandfather forever.** Grandfathering feels kind, but it can leave enormous money on the table. Run the math: a customer paying **$50\u002Fmo** who *should* be at **$250\u002Fmo** is a **$2,400\u002Fyr** gap — and $200\u002Fmo you're subsidizing indefinitely across your whole base. Grandfather as a *transition* (a grace period), not a permanent exemption.\n3. **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.\n4. **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.\n\nExpect — 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.\n\n---\n\n## Pricing Page Best Practices\n\n### Above the Fold\n- Clear tier comparison table\n- Recommended tier highlighted\n- Monthly\u002Fannual toggle\n- Primary CTA for each tier\n\n### Common Elements\n- Feature comparison table\n- Who each tier is for\n- FAQ section\n- Annual discount callout (17-20%)\n- Money-back guarantee\n- Customer logos\u002Ftrust signals\n\n### Pricing Psychology\n- **Anchoring:** Show higher-priced option first\n- **Decoy effect:** Middle tier should be best value\n- **Charm pricing:** $49 vs. $50 (for value-focused)\n- **Round pricing:** $50 vs. $49 (for premium)\n\n---\n\n## Pricing Page Teardown\n\nWhen 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:\n\n- **Human buyer experience** — value-prop clarity, plan differentiation, cognitive load, trust signals, pricing psychology, and price transparency.\n- **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\u002Fobjection coverage, per-tier depth stated in text, and structured data. Buyers now ask ChatGPT\u002FPerplexity\u002FClaude \"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.\n\n**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).\n\nThe AI-readiness fixes are usually high-impact, low-effort (put prices in text, add `Offer` schema). Hand implementation to **schema** (Product\u002FOffer JSON-LD) and **ai-seo** (extractability, AI-bot access, `llms.txt`).\n\n**For the full 10-dimension rubric, scoring, and report template:** See [references\u002Fpricing-page-teardown.md](references\u002Fpricing-page-teardown.md). *(AI-agent-readiness lens adapted from Kyle Poyar \u002F Growth Unhinged.)*\n\n---\n\n## Pricing Checklist\n\n### Before Setting Prices\n- [ ] Defined target customer personas\n- [ ] Researched competitor pricing\n- [ ] Identified your value metric\n- [ ] Conducted willingness-to-pay research\n- [ ] Mapped features to tiers\n\n### Pricing Structure\n- [ ] Chosen number of tiers\n- [ ] Differentiated tiers clearly\n- [ ] Set price points based on research\n- [ ] Created annual discount strategy\n- [ ] Planned enterprise\u002Fcustom tier\n\n---\n\n## Task-Specific Questions\n\n1. What pricing research have you done?\n2. What's your current ARPU and conversion rate?\n3. What's your primary value metric?\n4. Who are your main pricing personas?\n5. Are you self-serve, sales-led, or hybrid?\n6. What pricing changes are you considering?\n\n---\n\n## Related Skills\n\n- **churn-prevention**: For cancel flows, save offers, and reducing revenue churn\n- **cro**: For optimizing pricing page conversion\n- **ai-seo**: For making the pricing page extractable\u002Fcitable by AI (the teardown's AI-agent-readiness axis)\n- **schema**: For Product\u002FOffer structured data so machines can read your tiers and prices\n- **copywriting**: For pricing page copy\n- **marketing-psychology**: For pricing psychology principles\n- **ab-testing**: For testing pricing changes\n- **revops**: For deal desk processes and pipeline pricing\n- **sales-enablement**: For proposal templates and pricing presentations\n",{"name":5,"metadata":24,"description":7},{"version":25},"2.1.7","main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Fpricing","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill pricing",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill pricing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill pricing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",11295,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fpricing-models.md",4681,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002Freferences\u002Fpricing-models.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fpricing-page-teardown.md",7283,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002Freferences\u002Fpricing-page-teardown.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fresearch-methods.md",6677,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002Freferences\u002Fresearch-methods.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ftier-structure.md",7199,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fpricing\u002Freferences\u002Ftier-structure.md",[71,78,85,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]