Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pricing Strategist

ASecurity

Develop pricing strategy — research, models, packaging, testing, and communicating price changes.

2 stars
0 votes
0 copies
2 views
Added 9/29/2026
ai-agentsgorailstesting

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill pricing-strategist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pricing Strategist?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pricing Strategist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-pricing-strategist/badge)](https://www.skillsdirectory.com/skills/aicodedecode-pricing-strategist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: pricing-strategist
description: Develop pricing strategy — research, models, packaging, testing, and communicating price changes.
category: business-marketing
---

## Overview

Pricing is the highest-leverage profit decision most companies underinvest in. This skill covers pricing strategy end to end: understanding value and willingness to pay, choosing pricing models, designing packages and tiers, testing prices, and managing price changes without revolt.

## When to use

- Setting prices for a new product
- Redesigning packaging and tiers
- Raising prices
- Choosing between pricing models (subscription, usage, freemium)
- Responding to competitor pricing pressure
- Reducing discounting

- Pricing new products or features
- Moving from perpetual to subscription pricing
- Localizing pricing for international markets
## Core concepts

**Value-based pricing.** Price on the value delivered to the customer, not your costs. Costs set the floor; value sets the ceiling; competition positions you between. Anchor every pricing conversation on customer value metrics.

**Willingness-to-pay research.** Van Westendorp (price sensitivity meter: too cheap → too expensive), Gabor-Granger (purchase intent at price points), conjoint analysis (trade-offs between features and price). Even 10 customer interviews beat guessing.

**Pricing models.** Subscription (predictable, SaaS standard), usage-based (scales with value, aligns cost and benefit), freemium (acquisition engine, monetize power users), one-time (simple, no expansion), hybrid (base + usage — increasingly popular). Match model to how customers derive and perceive value.

**Packaging and tiers.** Good-better-best (3 tiers; most choose middle), feature differentiation by customer segment (not arbitrary), the decoy effect (a premium tier makes the target tier look reasonable), and clear upgrade paths. Price the metric that scales with value (seats, usage, revenue).

**Price psychology.** Charm pricing ($99 vs $100 — weaker in B2B), anchoring (show the higher option first), partitioned pricing (base + add-ons), annual discounts (cash flow + commitment), and framing (per day/week vs. per year).

**Communicating increases.** Advance notice, grandfathering options, tying increases to added value, and enabling sales with talk tracks. Most churn from price increases comes from surprise, not the amount.


**Value-based pricing.** Price on customer value delivered, not costs incurred.
Quantify value: time saved × hourly cost, revenue generated, risk reduced.
Economic value estimation (EVE) models make value explicit — build them for enterprise deals.
Costs set the floor; value sets the ceiling; strategy picks the point.
**Behavioral pricing.** Charm pricing ($99 vs $100), decoy effects (3-tier with clear winner), anchoring (show premium first), and freemium-to-paid ladders.
These work — but only on top of sound value foundations.
Test behavioral tactics; do not assume them.
**International pricing.** Purchasing power parity adjustments, local payment methods, currency volatility hedging, and tax compliance (VAT/GST).
Straight USD conversion prices you out of emerging markets — localize deliberately.
Review annually; currencies and purchasing power shift.
## Practical workflow

1. **Research value.** Interview customers: what outcomes do they get? What's it worth? What do they pay for alternatives (including doing nothing)? Run Van Westendorp or conjoint for rigor.
2. **Choose the model.** Map how value is delivered and perceived → pick the model and the value metric (per seat, per transaction, per GB...). The metric should grow as customer value grows.
3. **Design packages.** Segment customers by needs → 3 tiers with meaningful differentiation → name the middle tier as the recommended/default → set prices from willingness-to-pay data, not round numbers.
4. **Test.** A/B test on new customers, grandfather existing ones. Or: test with a segment/region first. Measure conversion, ARPU, and mix shift — not just conversion alone.
5. **Launch and enable.** Update all surfaces (site, sales decks, contracts). Train sales on the value story and discount guardrails. Prepare FAQ for objections.
6. **Monitor and iterate.** Track: conversion rate by tier, ARPU, discount rate, win/loss reasons mentioning price, expansion revenue. Review pricing annually at minimum.

**Van Westendorp questions:** At what price is it so cheap you'd doubt quality? A bargain? Expensive but worth considering? Too expensive to consider? Plot the intersections for the acceptable range.


**Pricing research sequence:** 1) Van Westendorp (price sensitivity meter) for acceptable range, 2) conjoint or Gabor-Granger for feature/price trade-offs, 3) competitive price benchmarking (map on value, not just price), 4) willingness-to-pay interviews with economic buyers, 5) small-scale A/B test of shortlisted prices. Never skip step 4 — models without buyer conversations miss context.

**Packaging test:** present 3 tier options to 10 target buyers; ask which they would choose and why. If everyone picks the middle tier, differentiation is unclear. If everyone picks the cheapest, value communication is failing. Iterate packaging before touching prices.

**Pricing change management:** research (WTP studies, competitive analysis) → model impact (revenue, churn, acquisition scenarios) → grandfather existing customers (12+ months typical) → communicate early (60–90 days) with rationale → implement → monitor (churn, NPS, sales cycle) → adjust.
Price increases without grandfathering trigger churn waves — the short-term revenue is not worth it.
**Discount governance:** approval thresholds by discount size → deal desk for large deals → track discount rates by rep → audit quarterly.
Uncontrolled discounting trains customers to never pay list — govern early.
## Common pitfalls

- **Cost-plus pricing.** Ignoring value leaves money on the table (or prices you out of the market).
- **Too many tiers.** Five confusing plans paralyze buyers. Three, clearly differentiated.
- **Competing on price.** Racing to the bottom destroys margins and attracts the worst customers. Compete on value.
- **Uncontrolled discounting.** Sales discounting by default. Set guardrails, approval thresholds, and track discount rates.
- **Surprise increases.** Raising prices without notice or justification. Communicate early, tie to value.
- **Pricing the wrong metric.** Charging per seat when value scales with usage (or vice versa) misaligns incentives and caps expansion.
- **Set-and-forget.** Never revisiting pricing as the product and market evolve. Pricing is a living strategy.
- **Cost-plus pricing in value markets.** Pricing from costs when customers buy outcomes. Anchor on value delivered, then check costs as a floor.
- **Too many tiers and add-ons.** Complexity kills conversion. Three clear tiers beat seven clever ones.
- **Set-and-forget pricing.** Prices unchanged for years while value and markets shift. Review pricing annually minimum.
- **Sales-led discounting.** Reps discounting by default to close. Every point of discount is margin — make it visible and governed.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →