pricing-strategist
Expert pricing strategy and monetization guidance for SaaS and digital products. Use when designing pricing tiers, creating pricing pages, setting value metrics, developing bundle strategies, planning price increases, writing pricing copy, analyzing competitive pricing, or optimizing annual vs monthly positioning. Use for packaging decisions, discount policies, enterprise pricing, and behavioral pricing tactics.
What this skill does
# Pricing Strategist
Expert pricing strategy and monetization guidance for SaaS and digital products — from psychology-driven pricing to enterprise negotiation tactics.
## Philosophy
Pricing is the most powerful lever in your business:
1. **Price is a signal** — It communicates value, market position, and customer fit
2. **Packaging is product** — How you bundle features shapes perceived value
3. **Simplicity wins** — Confused buyers don't buy
4. **Test everything** — Intuition about willingness-to-pay is usually wrong
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `psychology-*` — Behavioral economics, anchoring, framing, decoy pricing
- `packaging-*` — Tier structure, bundles, good/better/best frameworks
- `metrics-*` — Value metrics, usage-based, per-seat, flat-rate models
- `page-*` — Pricing page copy, design, and conversion optimization
- `enterprise-*` — Enterprise pricing, negotiation, custom deals
- `lifecycle-*` — Discounts, promotions, price increases, grandfathering
## Core Frameworks
### The Pricing Stack
```
┌─────────────────────────────────────────────────────────┐
│ VALUE CREATION │
│ What problem do you solve? How well? │
├─────────────────────────────────────────────────────────┤
│ VALUE COMMUNICATION │
│ How do you convey value through pricing? │
├─────────────────────────────────────────────────────────┤
│ VALUE CAPTURE │
│ How much value do you extract as price? │
└─────────────────────────────────────────────────────────┘
```
### Pricing Model Comparison
| Model | Best For | Pros | Cons |
|-------|----------|------|------|
| **Per-seat** | Collaboration tools | Predictable, scales with adoption | Discourages sharing |
| **Usage-based** | Infrastructure, API | Aligns with value, low entry | Unpredictable revenue |
| **Flat-rate** | Simple products | Easy to understand | Leaves money on table |
| **Tiered** | Most SaaS | Captures segments | Can be complex |
| **Hybrid** | Mature products | Flexible, optimized | Harder to communicate |
### Value Metric Selection
Your value metric should be:
| Criteria | Question | Example |
|----------|----------|---------|
| **Easy to understand** | Can you explain it in 5 words? | "Pay per user per month" |
| **Aligned with value** | Does customer pay more as they get more value? | More emails sent = more conversions |
| **Predictable** | Can customer forecast their bill? | Seat count is predictable |
| **Scalable** | Does it grow with the customer? | API calls scale with usage |
### The Willingness-to-Pay Curve
```
High WTP │ ●●● Enterprise
│ ●●●●●
│ ●●●●●●● Pro
│ ●●●●●●●●●
│●●●●●●●●●●● Starter
Low WTP │●●●●●●●●●●●●●
└────────────────────
Few Many
Customers
```
Capture value at each segment with differentiated packaging.
## Pricing Psychology Principles
| Principle | How It Works | Application |
|-----------|--------------|-------------|
| **Anchoring** | First price sets expectations | Show enterprise price first |
| **Decoy effect** | Third option makes one look better | Middle tier becomes attractive |
| **Charm pricing** | 9-ending feels cheaper | $99 vs $100 |
| **Price partitioning** | Split price seems smaller | $50/mo + $20 support |
| **Round numbers** | Feel more premium | $1,000 for enterprise |
## Packaging Framework
### Good/Better/Best Structure
| Tier | Target | Feature Strategy | Pricing |
|------|--------|------------------|---------|
| **Good (Starter)** | Entry-level, price-sensitive | Core features, limited usage | Low anchor |
| **Better (Pro)** | Growth, main target | Full features, higher limits | Optimal margin |
| **Best (Enterprise)** | High-value, complex needs | Unlimited, premium support | Value-based |
### Feature Fencing Strategies
| Strategy | Description | Example |
|----------|-------------|---------|
| **Usage limits** | Cap quantity/volume | 1,000 vs 10,000 emails |
| **Feature gates** | Reserve features for higher tiers | SSO in Enterprise |
| **Support tiers** | Differentiate service level | Email vs dedicated CSM |
| **SLA guarantees** | Higher uptime commitments | 99.9% vs 99.99% |
| **Integration access** | Limit connection types | Basic vs premium integrations |
## Annual vs Monthly Framework
| Factor | Monthly | Annual |
|--------|---------|--------|
| **Discount** | Baseline | 15-20% off (2 months free) |
| **Cash flow** | Spread out | Upfront capital |
| **Churn** | Higher (monthly exit) | Lower (commitment) |
| **Target** | Skeptics, small biz | Confident, enterprise |
| **Positioning** | "Flexibility" | "Best value" |
## Anti-Patterns
- **Race to bottom** — Competing on price alone destroys margins
- **Complexity overload** — 6+ tiers confuse buyers
- **Feature stuffing** — More features ≠ higher perceived value
- **Discount addiction** — Training customers to wait for sales
- **One-size pricing** — Leaving money on table from high-value customers
- **Hidden fees** — Surprise charges destroy trust
- **Anchoring backwards** — Showing cheapest option first
- **Ignoring segments** — Same price for SMB and enterprise
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.