pricing-strategy
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".
What this skill does
# Pricing Strategy and Page Optimization
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.
## Step 1: Gather Context
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).
## Step 2: Pricing Model Selection
| 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).
## Step 3: Pricing Psychology
### 1. Price Anchoring
Show highest tier first, compare to alternatives ("vs. hiring at $80K/year"), compare to outcome value ("Generates $10K savings. Costs $99/month").
### 2. Decoy Effect
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).
### 3. Charm Pricing
$99 feels cheaper than $100. Use .99 for consumer/SMB, round numbers for enterprise/premium.
### 4. Center-Stage Effect
People choose the middle of 3 options. Make your target plan the middle tier and highlight it.
### 5. Loss Aversion
Frame around what they lose without your product. Use "downgrade" language. Show features they would lose.
### 6. Endowment Effect
Full-featured trials, then keep. Show personalized data that makes leaving painful.
### 7. Price-Quality Signal
Premium products should not underprice. Own higher prices: "We cost more because we deliver more."
## Step 4: Tier Design
### 3-Tier Framework
```
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.
```
### Feature Gating Rules
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 security
6. Create natural upgrade triggers during normal usage
## Step 5: Pricing Page Design
### 3-Column Layout
```
+------------------+---------------------+------------------+
| 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: |
+------------------+---------------------+------------------+
```
### Page Elements (Top to Bottom)
1. **Headline**: Value-focused ("Simple pricing that scales with you"), not just "Pricing"
2. **Billing toggle**: Monthly/Annual with savings shown as % and $
3. **Tier cards**: Highlighted middle tier, checkmarks/dashes for features
4. **Feature comparison table**: Expandable, grouped by category
5. **Social proof**: Logos, testimonials addressing pricing objections
6. **FAQ**: Can I switch plans? What happens after trial? Discounts? Refunds? Cancel anytime?
7. **Final CTA**: Repeat with value message
### Design Rules
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.
## Step 6: Competitive Pricing Analysis
```
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.
## Step 7: Pricing A/B Tests
**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.
### Safety Rules
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.
## Step 8: Pricing Page Audit Checklist
**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?
## Output Format
```
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.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".