pricing-page-generator
The pricing-page-generator skill guides creation and optimization of pricing page content, structure, and conversion strategies. Use it when designing or auditing pricing pages, including decisions about visibility, plan tiers, models like subscription or usage-based pricing, enterprise versus self-serve approaches, and handling pricing objections. It covers initial assessment of pricing strategy, placement decisions across marketing sites and in-app interfaces, and special programs for startups and education.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/pricing-page-generator && cp -r /tmp/pricing-page-generator/skills/pages/marketing/pricing ~/.claude/skills/pricing-page-generatorSKILL.md
# Pages: Pricing
Guides pricing page content, structure, and conversion optimization. Covers self-serve plans, enterprise/contact sales, API/usage-based pricing, and special programs (startups, education).
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
## Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and pricing strategy.
Identify:
1. **Pricing model**: Subscription, one-time, usage-based, freemium, hybrid
2. **Plans**: Number of tiers, differentiation; enterprise vs self-serve
3. **Primary goal**: Sign up, contact sales, trial
4. **Objections**: Price sensitivity, "which plan?" confusion
5. **Special programs**: Startups, education, nonprofit (link or embed)
6. **Visibility**: Public page vs contact-sales-only; marketing site vs in-app
## Pricing Visibility & Placement
### Public vs Hidden Pricing
| Show public pricing | Hide (contact sales only) |
|--------------------|---------------------------|
| Self-serve / SMB; standard tiers | Enterprise; highly customized |
| Competitive market; transparency differentiates | Premium positioning; consultative sales |
| Simple pricing model | New category; value exceeds cost in prospect's mind |
| 86% of B2B buyers want transparency; hidden pricing is a top deterrent | Custom deployments, SLA, volume; fixed price misleading |
**Middle ground**: "Starting from," price ranges, or calculator—clarity without rigid commitment.
### Where Pricing Lives
| Location | Audience | Purpose |
|----------|----------|---------|
| **Marketing site** | Unlogged visitors | Acquisition; standalone /pricing page; main nav or footer |
| **In-app / Dashboard** | Logged-in users | Subscription management; Settings → Billing/Subscription in sidebar; upgrade/downgrade, payment |
**Marketing site** = conversion; **In-app billing** = retention and plan management. Not all sites need public pricing in nav—enterprise-only products may use "Contact sales" as primary CTA.
## Pricing Models
| Model | Use |
|-------|-----|
| **Subscription** | Recurring; monthly/annual; most SaaS |
| **Freemium** | Free tier + paid; adoption then conversion |
| **Usage-based** | Pay per use; API calls, tokens, credits |
| **One-time** | Perpetual license; some tools |
| **Hybrid** | Base + usage; tiered + overage |
## Pricing Page Structure
| Section | Purpose |
|---------|---------|
| **Headline** | Value-focused; "Simple pricing" or benefit-led |
| **Pricing model selector** | Monthly/annual toggle; show annual savings (15–25%); usage-based calculator if applicable |
| **Plan comparison** | Clear table or cards; feature comparison; "Best for" per tier |
| **Enterprise / Contact sales** | Separate tier; "Contact us," "Custom pricing"; SLA, dedicated support; volume discount |
| **API / Usage pricing** | If API product: token/request pricing; tiers (Standard/Flex/Batch); overage; link to /api or docs |
| **Special programs** | Startups, education, nonprofit; link to startups-page or embed block |
| **FAQ** | Billing, cancellation, refunds, API limits, enterprise |
| **Social proof** | Testimonials, logos, "X companies trust us" |
| **CTA** | Per plan or unified "Get started"; "Contact sales" for enterprise |
| **Guarantee** | Money-back, free trial, no credit card |
| **Comparison** | Brief price vs alternatives; link to alternatives-page |
## Best Practices
### Plan Presentation
- **Tier design**: 2–4 tiers; avoid too many options; 3 tiers optimal (decoy effect)
- **Anchoring**: Lead with mid-tier or annual discount; anchor high to make mid-tier feel reasonable
- **Decoy effect**: Middle tier as "Goldilocks" choice; "Most popular" or "Best value" badge
- **Differentiation**: Clear "best for" per tier; value metric (seats, API calls, projects)
- **Feature clarity**: What's included; outcome-first ("Save 10 hours/week") over feature-first ("Advanced API"); avoid vague "Advanced features"
- **Price display**: Monthly vs annual; show savings explicitly
- **Comparison**: Help user choose (quiz, comparison table)
### Usage-Based & Credits
- **Consumption visibility**: Show credits/usage clearly; avoid "bill shock" from opaque consumption
- **Wording**: Avoid vague "Unlimited" if soft limits exist; use "Extended" or state limits explicitly
### Enterprise & API Pricing
| Scenario | Use |
|----------|-----|
| **Enterprise** | Separate tier; "Contact sales," "Custom pricing"; SLA, dedicated support, volume discount |
| **API / Usage-based** | Token/request pricing; tier (Standard/Flex/Batch); overage; link to api-page or docs |
| **Hybrid** | Base subscription + usage; show base + overage clearly |
### Conversion Psychology
- **Anchor high**: Present highest tier first; mid-tier feels more reasonable
- **Loss aversion**: Money-back, no CC trial, cancel anytime—reduce perceived risk
- **Transparency**: No hidden fees; 73% of users value transparent pricing
- **Trust signals**: Logo, testimonial, "X+ companies"; guarantee near CTA
### Objection Handling
- **Price**: ROI, cost per use, comparison to alternatives
- **Commitment**: Free trial, no CC, cancel anytime
- **Uncertainty**: Guarantee, case studies, support
### Promo & Discounts
- **Annual discount**: Highlight 15–25% for annual prepay
- **Promo placement**: Top banner or promo block on page; see **top-banner-generator**
- **Startups/Education**: Link to startups-page or education-program page; or "Special plans" block on pricing page. When discount applies at registration, registration flow is P0; pricing page is P1. See **education-program** for placement priority.
### SEO
- Title: "Pricing | [Product]" or "Plans & Pricing"
- Meta: Include price range or "Start free" if applicable
- Schema: Consider Product/Offer structuredWhen the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.