agentleFS
Natan-MohartNatan-Mohart/24-strategy-skills-for-claude/skills/pricing-strategy/SKILL.md

pricing-strategy

Skill41 starsChanged 3 months agoMITView on GitHub

Sets or tests pricing using willingness-to-pay research (Van Westendorp) and price elasticity revenue/margin modeling, both run through a bundled calculator, instead of cost-plus guessing or copying a competitor's price. Use whenever the user wants to set, raise, lower, or test a price, is launching a new product/tier, asks "what should we charge," or is about to price based on cost-plus or "what competitors charge" alone.

116 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

Files
SKILL.md

Pricing Strategy

When to use

Use whenever a price needs to be set or changed and the current approach is cost-plus (price = cost + target margin, ignoring what the customer will actually pay) or competitor-matching (copying a rival's price without checking whether your value proposition is comparable). Also use to test a proposed price change before committing to it.

What it does

Grounds pricing in two independent, complementary methods run through a bundled calculator: Van Westendorp Price Sensitivity (four-question willingness-to-pay survey, giving an acceptable price range and a floor below which customers doubt quality) and price elasticity modeling (revenue and margin at each price point given an estimated or tested elasticity coefficient) — so the recommendation is bounded by real customer behavior, not internal cost structure alone.

Method

  1. Run or collect Van Westendorp responses: ask a representative sample four questions per product — at what price is this so cheap you'd doubt the quality; a bargain; starting to feel expensive; so expensive you wouldn't consider it. Minimum ~30 responses for a directional read, 100+ before a launch-critical decision.
  2. Run the bundled calculator's Van Westendorp module (scripts/pricing_calculator.py) to get the four crossing points and the acceptable price range — the floor (below which quality is doubted) and ceiling (above which it's rejected outright) bound your pricing options before elasticity is even considered.
  3. Estimate or obtain a price elasticity coefficient — from a real price test if you have one, from category benchmarks if you don't (call this out explicitly as an assumption, not a fact, if it's a benchmark).
  4. Run the elasticity module across a realistic price-test range to see revenue and margin at each point — these two often peak at different prices, and the choice between them is a real strategic call, not a math problem.
  5. Overlay the Van Westendorp range on the elasticity table: discard any price points outside the acceptable range regardless of what the elasticity model says, since a price outside the willingness-to-pay range risks brand/quality perception damage the elasticity model doesn't capture.
  6. Check for a Kano-style structure if pricing tiers/packaging: which features are must-haves (expected, don't differentiate price), performance features (linear value, price scales with them), and delighters (disproportionate willingness to pay) — use this to decide what goes in which tier, not just what's cheap to build.
  7. Recommend a price with the explicit trade-off named: "recommend $X, which is the revenue-maximizing point within the Van Westendorp acceptable range; margin-maximizing would be $Y but falls outside/inside the range for reason Z."

Inputs

  • Van Westendorp survey responses (or a plan to collect them) as arrays of four values per respondent
  • Current price, volume, and unit cost
  • An elasticity coefficient (measured or benchmarked) and a realistic price-test range
  • Config saved as JSON matching the format documented at the top of scripts/pricing_calculator.py

Output format

Van Westendorp acceptable price range with all four crossing points; elasticity table showing volume/revenue/margin at each tested price with the revenue-max and margin-max points flagged; a single recommended price with the trade-off named explicitly; any tier/packaging implications from the Kano check.

Example

A SaaS product currently priced at $29 shows a Van Westendorp acceptable range of $24-$37, and the elasticity table shows revenue peaks at $24 but margin peaks at $29. Since both are inside the acceptable range, the recommendation names the actual choice: hold at $29 for margin, or move to $24 to prioritize growth/market share — a decision for the business, not a number the model can pick alone.

Common pitfalls

  • Setting price purely from cost-plus math, ignoring what customers will actually pay.
  • Treating an elasticity coefficient pulled from a generic benchmark as if it were measured for this specific product and audience.
  • Optimizing for revenue or margin without checking the price against the Van Westendorp range, risking a technically "optimal" price that customers reject on sight.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.