agentsclimarketplace

Pricing strategy

Skill Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/pricing-strategy

A curated pack of custom Claude Code skills for developers — installable as a Claude Code plugin marketplace.

Install
npx -y skills add Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack --skill pricing-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

When to activate: pricing strategy, pricing model, freemium, usage-based pricing, per-seat, value metric, pricing research, Van Westendorp, packaging, price increase

SKILL.md

6.2 KB, as published. Nobody here has run it

Pricing Strategy

Pricing Model Comparison

ModelMechanicsBest forRisk
Flat rateOne price, all featuresSimple products, commoditiesLeaves money on table
Per-seatPrice × number of usersCollaboration toolsIncentivizes seat minimization
Usage-basedPay for what you useAPIs, infra, AIUnpredictable revenue
FreemiumFree tier + paid upgradePLG, high-volume acquisitionSupport cost, low conversion
TieredStarter/Pro/Enterprise packagesMost B2B SaaSTier cannibalization
HybridSeat base + usage overageModern SaaSComplexity

Hybrid Model Pattern (increasingly common)

Base fee: $500/month (includes 10 seats + 10k API calls)
Overage: $2/seat/month + $0.01/additional API call
Enterprise: Custom contract with committed minimums

Value Metric Identification

The value metric is what you charge for — it should scale with the value the customer gets.

Good Value Metric Criteria

  • Customers understand it immediately
  • It grows as customers get more value
  • It's easy to measure and invoice
  • It aligns incentives (you succeed when customer succeeds)

Finding Your Value Metric

  1. List what customers do in your product
  2. Identify what correlates with outcomes (revenue, time saved, risk reduced)
  3. Pick the one that scales most naturally with customer success
  4. Validate: do power users naturally consume more of it?

Examples by Category

ProductValue metric
CRMContacts / deals
Email toolEmails sent / subscribers
AnalyticsEvents tracked / data volume
CollaborationActive seats
AI APIAPI calls / tokens
E-commerce toolGMV processed

Pricing Research Methods

Van Westendorp Price Sensitivity Meter

Four questions:

  1. "At what price would this be so cheap you'd question quality?"
  2. "At what price would this be a bargain?"
  3. "At what price would this start to feel expensive?"
  4. "At what price would this be too expensive to consider?"

Plot responses to find:

  • Acceptable price range: between "too cheap" and "too expensive" crossovers
  • Optimal price point: intersection of "bargain" and "expensive" curves

Gabor-Granger

Present fixed price points to segments. Ask: "Would you buy at $X/month?" Calculate demand curve. Find revenue-maximizing price.

Conjoint Analysis

Show customers trade-offs between price and feature bundles. Reveals willingness to pay for specific features.

Rule of Thumb

  • Van Westendorp for early-stage directional data
  • Gabor-Granger for demand curve with existing customer base
  • Conjoint for packaging decisions with established products

3-Tier Packaging Template

StarterProEnterprise
TargetIndividuals / small teamsGrowing teamsLarge orgs
Price$X/mo$3X/moCustom
SeatsUp to 3Up to 25Unlimited
Core features
Advanced features
Admin controlsBasicAdvanced
SSO / SCIM
SLA / supportCommunityEmailDedicated CSM
Data retention30 days1 yearCustom

Tier Design Rules

  • Middle tier should be the revenue maximizer (highest conversion × highest value)
  • Enterprise tier is always "contact sales" — use to learn before pricing
  • Starter → Pro upgrade should feel obvious, not punishing
  • Limit to 3 tiers; more creates paralysis

Competitive Pricing Response Playbook

ScenarioResponse
Competitor cuts priceDo not match immediately; research if they're winning deals on price
Competitor raises priceOpportunity to position as better value; may allow your own increase
New low-cost entrantProtect enterprise with value story; let free tier compete at low end
Race to zeroShift to usage-based or outcomes-based model to break the comparison

Price Positioning Options

  • Premium: Higher price signals quality; requires differentiation evidence
  • Value: Slightly below leader, emphasize ROI
  • Penetration: Low to gain share; plan path to profitability

Price Increase Playbook

Pre-Increase Preparation

  1. Segment customers by plan, tenure, expansion potential
  2. Identify champions (power users who can advocate internally)
  3. Prepare value story: what have you shipped since last pricing?
  4. Draft FAQ: "Why is the price increasing?"
  5. Decide on grandfather policy (existing customers locked for X months?)

Communication Template

Subject: Changes to [Product] pricing

Hi [Name],

We're updating our pricing on [date]. Here's what's changing:
[Old price] → [New price] for [plan name].

Why: [Value delivered — features shipped, infrastructure improved, support added]

Your options:
- Annual plan: lock in current pricing for 12 months (save X%)
- Stay on monthly: new price applies on [date]
- Downgrade: [link]

Questions? Reply to this email — our team will help.

[Name]

Grandfather Policy

  • 3-6 month grace period for existing customers is standard
  • Annual customers: honor rate until renewal
  • Avoid indefinite grandfathering — it creates pricing complexity forever

Self-Serve vs Sales-Assisted Pricing

ScenarioSelf-serveSales-assisted
ACV < $5k/year
ACV $5k–$25kHybridHybrid
ACV > $25k
Complex procurement
High-volume, simple product

Enterprise Pricing Dynamics

  • List price is a starting point — expect 20-40% negotiation
  • Annual commitment in exchange for discount (15-30%)
  • Multi-year deal for larger discount
  • Pilot/POC before full deployment
  • Legal / security review adds 4-8 weeks to deal cycle

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.