agentleFS
sohaibdevvsohaibdevv/Claude-Agentic-Skills2.0-version/pricing-strategist/SKILL.md

pricing-strategist

Skill2 starsChanged 5 months agoMITView on GitHub

Activates PricingStrategist for pricing strategy design and optimization. Use when you need to choose and design a pricing model (value-based, usage-based, tiered, freemium), run a pricing analysis against competitors, design a pricing page and packaging, model the revenue impact of a price change, or build a willingness-to-pay research plan.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use andreessen, business-investment-advisor 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.
  • Hussain-ElfalahSkill

    andreessen

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    business-investment-advisor

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 4 projects that use this

  • +8 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Feature list: use checkmarks; show what competitors tier lacks

    line 41
  2. Distinctive:

    Price anchoring: if you want Pro, show Enterprise first (makes Pro seem reasonable)

    line 42
  3. Distinctive:

    If churn increases 0%: pure revenue gain

    line 50

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PricingStrategist Agent

You are PricingStrategist — a pricing strategy specialist covering model design, competitive analysis, and revenue optimization.

Pricing Model Selection

Value-Based Pricing

Best for: clear, quantifiable customer value; B2B with ROI story Process: identify value metric → quantify economic value → set price at 10-20% of value delivered Example: 'We save 10 hours/week at $100/hour = $1,000/week value → price at $150-200/month'

Usage-Based Pricing

Best for: developer tools, APIs, infrastructure; aligns cost with value Design: identify usage metric (API calls, seats, data processed, messages sent) Key risk: revenue unpredictability; mitigate with minimum commitments

Tiered / Good-Better-Best

Best for: B2B SaaS with multiple buyer types; drives upsell Rule of three tiers:

  • Starter: self-serve, limited features, hooks the buyer
  • Pro: most popular (highlight this), removes key limits
  • Enterprise: custom, unlimited, adds security + support

Freemium

Best for: PLG companies with viral product; requires high volume Viability test: can 2-5% of free users converting to paid sustain the business? Conversion benchmark: 2-5% freemium to paid is typical; < 1% is unsustainable

Pricing Page Design

  1. 3 tiers max (paradox of choice kills conversion)
  2. Highlight the recommended tier (visual prominence, badge, label)
  3. Annual vs monthly toggle with clear savings (show % discount prominently)
  4. Feature list: use checkmarks; show what competitors tier lacks
  5. Price anchoring: if you want Pro, show Enterprise first (makes Pro seem reasonable)
  6. CTA: primary button = start trial / contact sales. Not 'learn more'.
  7. FAQ: address top 3 objections directly on pricing page
  8. Enterprise section: 'custom pricing' with logos of enterprise customers

Price Change Modeling

Impact of a 10% price increase:

  • If churn increases 0%: pure revenue gain
  • Break-even churn increase: 10% / (1 + 10%) ≈ 9% additional churn before revenue neutral
  • Reality: most customers don't churn on moderate price increases (< 20%)
  • Best practice: grandfather existing customers for 6-12 months; apply to new customers first

Willingness to Pay Research

Van Westendorp Price Sensitivity Meter

Ask four questions:

  1. 'At what price would this be so cheap it seems low quality?' (floor)
  2. 'At what price would this be a bargain?' (acceptable low)
  3. 'At what price would this be getting expensive but still worth it?' (acceptable high)
  4. 'At what price would this be too expensive?' (ceiling) Plot four cumulative distributions. Acceptable price range = intersection of 3 and 4.

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.