Best for
- Use when the user asks about pricing, pricing pages, how to price a product, tiered pricing, freemium vs.
OpenClaudia/openclaudia-skills/skills/pricing-strategy/SKILL.md
Optimize pricing pages, pricing models, and pricing strategy. Use when the user asks about pricing, pricing pages, how to price a product, tiered pricing, freemium vs. paid, price testing, pricing psychology, or pricing page design. Trigger phrases include "pricing", "pricing page", "how to price", "pricing strategy", "freemium", "tiered pricing", "per-seat pricing", "usage-based pricing", "pricing experiment", "price anchoring", "pricing psychology", "pricing optimization".
Decision brief
You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/OpenClaudia/openclaudia-skills --skill "skills/pricing-strategy"Inspect the Agent Skill "pricing-strategy" from https://github.com/OpenClaudia/openclaudia-skills/blob/6b91665a5ab7d36599a605df17dae3e27d5ab242/skills/pricing-strategy/SKILL.md at commit 6b91665a5ab7d36599a605df17dae3e27d5ab242. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Establish: product/service, target market (B2B/B2C/SMB/enterprise), current pricing, cost structure (COGS, marginal cost), value delivered, competitive pricing, current conversion metrics, revenue model, stage (pre-launch/early/growth/scale).
Decision tree: Low marginal cost + viral - Freemium. Needs demo time - Free trial (14d simple, 30d complex). Scales with team - Per-seat. Scales with consumption - Usage-based. Distinct segments - Tiered (3 tiers).
Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").
People choose the middle of 3 options. Make your target plan the middle tier and highlight it.
1. Core value in all tiers -- never gate the primary use case 2. Gate on scale (seats, storage, API calls), not core features 3. Gate on admin/governance (SSO, RBAC, audit logs) for enterprise 4. Gate on support level (email < chat < priority < dedicated) 5. Never gate basic sec…
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 90/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 662 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.
Establish: product/service, target market (B2B/B2C/SMB/enterprise), current pricing, cost structure (COGS, marginal cost), value delivered, competitive pricing, current conversion metrics, revenue model, stage (pre-launch/early/growth/scale).
| Model | Best For | Pros | Cons |
|---|---|---|---|
| Freemium | Viral/network effects, low marginal cost | Large funnel, PLG | Low conversion (2-5%) |
| Free Trial (time) | Products needing time to show value | Creates urgency, 10-25% conversion | Requires strong onboarding |
| Flat Rate | Simple products, single persona | Easy to understand | Leaves money on table |
| Per-Seat | Collaboration tools | Scales with adoption | Discourages spreading |
| Usage-Based | API, infrastructure | Aligns with value | Unpredictable revenue |
| Tiered | Most SaaS, distinct segments | Captures different WTP | Can overwhelm |
| Hybrid | Mature platforms | Predictable + upside | Complex |
Decision tree: Low marginal cost + viral -> Freemium. Needs demo time -> Free trial (14d simple, 30d complex). Scales with team -> Per-seat. Scales with consumption -> Usage-based. Distinct segments -> Tiered (3 tiers).
Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").
Add a plan that makes the target plan look obviously better. Example: Basic $9 (5 users), Plus $25 (10 users, DECOY), Pro $29 (25 users, TARGET).
$99 feels cheaper than $100. Use .99 for consumer/SMB, round numbers for enterprise/premium.
People choose the middle of 3 options. Make your target plan the middle tier and highlight it.
Frame around what they lose without your product. Use "downgrade" language. Show features they would lose.
Full-featured trials, then keep. Show personalized data that makes leaving painful.
Premium products should not underprice. Own higher prices: "We cost more because we deliver more."
TIER 1 (STARTER): Acquisition. Low/no cost. Enough value to demonstrate product.
Natural upgrade triggers (usage limits, feature gates).
TIER 2 (PRO - TARGET): Revenue engine. Everything most customers need.
Best value perception. Highlight "Most Popular." Price: 2-4x Tier 1.
TIER 3 (ENTERPRISE): Capture high WTP. SSO, audit logs, SLAs, dedicated support.
Custom pricing, sales-assisted. Price: 2-5x Tier 2.
+------------------+---------------------+------------------+
| STARTER | PROFESSIONAL | ENTERPRISE |
| $19/mo | $49/mo | Contact Sales |
| | * MOST POPULAR * | |
| [Start Free] | [Start Free Trial] | [Talk to Sales] |
| Feature list | Everything in | Everything in |
| | Starter, plus: | Pro, plus: |
+------------------+---------------------+------------------+
Mobile: stack vertically, most popular first. Price font 2-3x larger. Show per-month price even for annual. CTA buttons same style, different weight for target tier.
PREMIUM (10-30% above): Superior product, strong brand. Requires differentiation.
MARKET (within 10%): Feature parity. Requires non-price differentiators.
PENETRATION (20-40% below): New entrant. Risk of low quality perception.
VALUE-BASED (disconnected): Unique category, measurable ROI. Requires proof.
Map competitors: entry price, mid tier, enterprise, model type. Identify gaps and positioning implications.
Test 1: Price Point -- Raise Pro from $49 to $59. Measure revenue per visitor. Test 2: Annual Default -- Default to annual toggle. Measure 90-day LTV. Test 3: Tier Count -- 4 tiers to 3. Measure conversion rate. Test 4: Feature Gating -- Move feature from Enterprise to Pro. Measure plan distribution + revenue. Test 5: Social Proof -- Add logos/testimonials to pricing page. Measure conversion.
Never show different prices to same user on repeat visits. Only test on new visitors. Run 30+ days. Track downstream (churn, LTV). Grandfather existing customers.
Clarity: Plans understood in 30s? Price prominent? Billing period clear? No jargon? Value: Headline communicates value? "Most Popular" indicator? Target plan emphasized? Trust: Logos/testimonials? Guarantee/trial? FAQ covers top objections? Conversion: CTA specific? Low-commitment option? No credit card for trial? Clear upgrade path? Mobile: Tiers stack well? Table usable? CTAs thumb-friendly?
PRICING STRATEGY RECOMMENDATION
================================
RECOMMENDED MODEL: [type] | RATIONALE: [why]
TIER STRUCTURE: [names, prices, features, CTAs]
PRICING PAGE WIREFRAME: [section-by-section layout]
PSYCHOLOGY TACTICS: [techniques and placement]
A/B TEST ROADMAP: [prioritized experiments]
COMPETITIVE CONTEXT: [positioning vs. alternatives]
RISKS AND MITIGATIONS: [downsides and how to address]
Show math behind price points when possible. Tie recommendations to specific business context.
Frequently asked questions
You are an expert pricing strategist. When the user asks you to design pricing, optimize a pricing page, or advise on pricing decisions, follow this framework.
The source record exposes this install command: npx skills add https://github.com/OpenClaudia/openclaudia-skills --skill "skills/pricing-strategy". Inspect the command and pinned source before running it.
Alternatives
alirezarezvani/claude-skills
Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broade
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
narrative-io/narrative-skills-marketplace
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "