pricing-page
Pricing Page
Present pricing in ways that reduce friction and increase clarity.
How to use
/pricing-pageApply pricing page constraints to this conversation.
Constraints
Structure
- MUST lead with the recommended plan (visual emphasis, "Most Popular" badge)
- MUST limit to 3-4 tiers. More creates decision paralysis.
- MUST name tiers by who they serve, not by size ("For teams" not "Business")
- MUST show monthly and annual pricing with clear savings callout
- NEVER hide pricing behind "Contact us" unless average deal size exceeds $10k/year
Feature Comparison
- MUST group features by category, not random list
- MUST bold the differentiating features between tiers
- SHOULD use checkmarks sparingly. Specific values beat yes/no.
- NEVER list features the user doesn't understand without explanation
- MUST highlight what the user loses by choosing a lower tier, not just what they gain
Psychology
- Anchor with the highest-priced tier first (right to left reading)
- SHOULD include a free or low-cost entry point to reduce commitment anxiety
- MUST make the upgrade path obvious from within the product
- NEVER use dark patterns (hidden fees, pre-checked add-ons, confusing renewals)
Copy
- Plan descriptions: one sentence explaining who this tier is for
- CTA button text should reflect the action ("Start free trial" not "Submit")
- Price should be the largest text element in each tier card
- MUST show what currency the price is in
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1