agentleFS
varunk130varunk130/claude-code-skills/skills/strategic-management/pricing-strategy-analyzer/SKILL.md

pricing-strategy-analyzer

Skill1 starsChanged 20 days agoMITView on GitHub

Analyzes a pricing strategy end to end - current pricing baseline, competitive price positioning, pricing model and value metric fit, willingness-to-pay signals, packaging, revenue scenarios, and a migration plan - and produces a pricing recommendation. Use when current pricing is losing deals or leaving money on the table; launching or restructuring pricing tiers; running an annual pricing review; moving to usage-based or outcome-based pricing; or pricing an Artificial Intelligence (AI) product.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Use the evidence available:

    line 63
  2. Distinctive:

    Treat discounting patterns as noise.

    line 122
  3. Distinctive:

    Add tiers without a clear upgrade trigger for each

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Pricing Strategy Analyzer

Price on evidence, not on gut feel or a competitor's pricing page.

What this skill is

A structured pricing review that moves from what the company charges today to what it should charge and how to get there. It combines value-based pricing (Patrick Campbell, ProfitWell), usage-based pricing (Kyle Poyar, OpenView), outcome-based pricing (as used by AI support agents such as Intercom Fin and Zendesk), Good-Better-Best packaging, Marcos Rivera's Street Pricing, and Elena Verna's work on Product-Led Growth (PLG) monetization. The output is a recommendation backed by revenue scenarios and a migration plan.

What it solves

  • Pricing set by copying competitors, with no link to the value customers receive
  • A value metric (per seat, per unit of usage) that grows slower than customer value
  • Heavy, inconsistent discounting that signals the list price is wrong
  • Too many tiers, or tiers whose feature gates do not trigger upgrades
  • Price changes modeled only for new customers, ignoring churn and expansion in the installed base
  • Migrations that surprise existing customers and the sales team

When to invoke

  • Win rates are falling on price, or deals close with little negotiation (money left on the table)
  • Launching new tiers, add-ons, or a new product line
  • Annual or post-funding pricing review
  • Moving from seat-based to usage-based, outcome-based, or hybrid pricing
  • Pricing an AI feature where inference cost scales with use

Phase 1: Document current pricing

ItemCapture
Tiers and list pricesEvery plan, add-on, and price point
Pricing modelFlat, per seat, usage, outcome, hybrid
Value metricThe unit the price scales with
DiscountingFrequency, average depth, who approves
Deal sizeAverage and median Annual Contract Value (ACV) by segment
Revenue mixShare of revenue by tier and segment

Phase 2: Analyze competitive pricing

CompetitorModelValue metricEntry priceMid-tier priceKey features gated
[Competitor A]$$

Map features to price points, then place the company on a price-versus-value chart: premium, parity, or value positioning. Note where the company charges less than competitors for equal or greater value.

Phase 3: Evaluate the pricing model and value metric

ModelFits whenWatch out for
Seat-basedValue scales with usersSeat compression as AI automates work
Usage-basedValue scales with consumptionUnpredictable bills, revenue volatility
Outcome-basedOutcomes are measurable and attributableAttribution disputes, delayed revenue
Hybrid (platform fee plus usage)Mixed value driversComplexity in quoting

A good value metric is easy to understand, grows with customer value, and is predictable enough to budget for.

Phase 4: Assess willingness to pay

Use the evidence available:

  • Win-loss data - share of losses citing price, by segment
  • Discount frequency - deals closing at list versus discounted
  • Upgrade and downgrade patterns - which tier transitions happen and why
  • Customer research - Van Westendorp price sensitivity or conjoint results where available

Segment the findings; enterprise and small business willingness to pay rarely match.

Phase 5: Analyze packaging

CheckHealthy sign
Tier countThree or four tiers (Good-Better-Best plus enterprise)
Feature gatingEach tier gates a feature tied to a clear upgrade trigger
Upgrade triggersUsage limits or capabilities that customers hit as they grow
Expansion potentialAdd-ons and usage growth create revenue without a new sale
Free or trial tierDrives qualified conversion, not unlimited free usage

Phase 6: Model revenue impact

Build scenarios across the installed base and new business.

ScenarioNew customer conversionChurn impactExpansion impact12-month revenueChange versus today
Status quo$-
Price increase$
Model change$

State the assumption that most drives each scenario and the breakeven value at which it stops paying off.

Phase 7: Plan the migration

  • Grandfathering - who keeps current pricing, and for how long
  • Timeline - announcement, effective date, and renewal-based transition
  • Communication - customer notice, rationale, and value story
  • Sales enablement - new price book, discount guardrails, objection handling
  • Risk mitigation - churn watch list, escalation path, rollback criteria

Output

  • Current pricing baseline
  • Competitive pricing map and positioning
  • Pricing model and value metric recommendation
  • Willingness-to-pay findings by segment
  • Packaging recommendation with tier structure and gates
  • Revenue scenario model with key assumptions
  • Migration plan with timeline and communication

Operating rules

Always

  • Anchor price to customer value, then check it against competitors
  • Model the effect on existing customers, not just new ones
  • Segment willingness-to-pay evidence before drawing conclusions
  • State the assumption behind every revenue scenario
  • Plan the migration and sales enablement alongside the price change

Never

  • Copy a competitor's price without understanding its value metric
  • Treat discounting patterns as noise; they are pricing evidence
  • Add tiers without a clear upgrade trigger for each
  • Price an AI feature without accounting for inference cost
  • Change pricing for existing customers without notice and a transition period

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.