
Pricing Strategy
Compare SaaS pricing models and pick a structure that matches how solo builders deliver value before you set launch prices.
Overview
Pricing Strategy is an agent skill most often used in Validate (also Grow, Operate) that explains SaaS pricing models—with variants and failure modes—so you can choose how to charge before you commit to billing and posit
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill pricing-strategyWhat is this skill?
- Per-seat / per-user model with named, concurrent, and creator/viewer variants in a comparison table
- Expansion mechanics (automatic seat growth) and failure modes (single power user, credential sharing)
- Benchmarked examples: Salesforce, Linear, Figma, Notion with indicative price bands
- Guidance on creator/viewer splits for B2B tools where one team builds and many stakeholders view
- Documents per-seat model with a variants comparison table (named, concurrent, creator/viewer, minimum seats)
- Lists four reference products: Salesforce, Linear, Figma, Notion
Adoption & trust: 535 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you will sell a subscription product but cannot tell whether per-seat, usage, or hybrid pricing will match how people actually use your app.
Who is it for?
Indie SaaS founders validating packaging and price before Stripe products, tiers, and landing-page tables are finalized.
Skip if: Teams that already have locked enterprise contracts, heavy custom quoting, or regulated billing where legal and finance must own the model without agent guidance.
When should I use this skill?
You are designing, comparing, or revising SaaS pricing models and need model-specific tradeoffs rather than a single guessed price point.
What do I get? / Deliverables
You leave with a clearer shortlist of pricing models, known tradeoffs, and real-world anchors so you can set tiers, trials, and expansion paths without backing into the wrong unit of value.
- Shortlist of viable pricing models with fit notes
- Packaging implications (seats, viewers, minimums) aligned to your workflow
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is validate/pricing because the skill is a pricing-model deep dive used when you are still deciding how to charge, not after billing is live. Subphase pricing is where model choice (per-seat vs usage vs tiers) directly gates landing-page copy, Stripe setup, and willingness-to-pay tests.
Where it fits
Pick per-seat vs creator/viewer before you publish tier names on a validation landing page.
Revisit seat pricing when power users share one login and expansion revenue stalls.
Adjust minimum seats or viewer pricing after onboarding patterns differ from your initial assumption.
How it compares
Use as structured pricing-model research instead of guessing a single monthly number in chat without model tradeoffs.
Common Questions / FAQ
Who is pricing-strategy for?
Solo and indie builders shipping B2B or prosumer SaaS who need to choose a pricing unit (seats, usage, tiers) before launch or a major packaging change.
When should I use pricing-strategy?
In validate/pricing when comparing models for a new product; in grow/lifecycle when seat expansion or churn suggests misfit pricing; in operate/iterate when you revisit creator vs viewer splits or minimum seats after real usage data.
Is pricing-strategy safe to install?
It is reference-style procedural knowledge without mandatory shell or network calls in the excerpt; review the Security Audits panel on this Prism page before installing from any third-party skills repo.
SKILL.md
READMESKILL.md - Pricing Strategy
# Pricing Models — Deep Dive Comprehensive reference for SaaS pricing models with real-world examples and when to use each. --- ## Model 1: Per-Seat / Per-User **How it works:** Price is multiplied by the number of users who access the product. **Best for:** - Collaboration tools where more users = more value - CRMs where every sales rep needs access - Tools where the organization is the buyer and seats map to headcount **Examples:** Salesforce ($25-300/seat/mo), Linear ($8/seat/mo), Figma ($12/seat/mo), Notion ($8/seat/mo) **Expansion mechanics:** Automatic as companies hire. No upsell conversation needed — new hire gets a seat, revenue grows. **Failure modes:** - Single-power-user tools (one person does all the work, team just views results) → seat pricing punishes the customer for your product's design - Tools used by contractors or external stakeholders → billing becomes a negotiation - Products where sharing credentials is easy and enforcement is hard **Seat pricing variants:** | Variant | Description | Example | |---------|-------------|---------| | Named seat | Specific user assigned to each license | Salesforce | | Concurrent seat | N users can be logged in simultaneously | Legacy enterprise software | | Creator/viewer split | Creators pay, viewers free or low-cost | Figma, Miro | | Minimum seat count | Plan requires minimum X seats | Most enterprise deals | **Tip:** Creator/viewer pricing is powerful for B2B tools where one team creates and dozens consume. It drives virality (free viewers) while capturing revenue from actual users. --- ## Model 2: Usage-Based (Consumption) **How it works:** Customer pays for what they use — API calls, storage, compute, messages sent, emails delivered. **Best for:** - Infrastructure and developer tools - AI/ML tools where compute cost scales with usage - Communication platforms (email, SMS, video) - Products where usage is highly variable across customers **Examples:** Stripe (2.9% + $0.30/transaction), Twilio ($0.0075/SMS), AWS (varies), OpenAI ($0.002-0.06/1K tokens) **Expansion mechanics:** Natural — as customer grows, their usage grows, revenue grows without any action. Best CAC:LTV dynamics in SaaS. **Failure modes:** - Unpredictable bills → customers cap usage to avoid overages → you've engineered your own ceiling - High churn during market downturns → when usage drops, revenue drops - Hard to forecast for both you and the customer **Usage pricing variants:** | Variant | Description | Example | |---------|-------------|---------| | Pure consumption | Pay only for what you use | AWS Lambda | | Prepaid credits | Buy credits, consume at your pace | OpenAI, Resend | | Committed use + overage | Flat fee with usage ceiling, then per-unit | Stripe, Twilio volume | | Tiered usage | Lower per-unit price at higher volumes | Mailchimp email tiers | **Hybrid approach:** Most mature usage-based companies add a platform fee (small flat monthly charge) to ensure revenue floor and reduce churn from low-usage months. --- ## Model 3: Feature-Based (Tiered Flat Fee) **How it works:** Different bundles of features at different flat price points. The Good-Better-Best model. **Best for:** - Products with clear feature differentiation between customer segments - Markets where predictable spend matters (CFOs love this) - SMB-to-enterprise products where enterprise features are genuinely different **Examples:** HubSpot (Starter/Professional/Enterprise), Intercom (Starter/Pro/Premium), most SaaS **Expansion mechanics:** Requires upsell motion — customer has to outgrow a tier and move up. Less automatic than usage-based but more predictable. **Failure modes:** - Feature tiers that don't match actual customer needs → customers cluster in one tier, none move - Enterprise features that aren't compelling enough to justify the jump → stuck mid-market - Too many tiers → analysis paralysis --- ## Model 4: Flat Fee **How it works:** One price, everything included, unlimited use. **B