pricing
Pricing strategy - tiers, feature gating. Use when designing pricing.
When & Why to Use This Skill
This Claude skill provides a robust architectural framework for designing and implementing SaaS pricing strategies, including multi-tier structures and feature gating. It emphasizes a code-first approach where the platform serves as the single source of truth, separating pricing logic from billing mechanics to ensure scalability, testability, and seamless integration with providers like Stripe.
Use Cases
- Designing a multi-tier SaaS subscription model with granular feature gating managed directly in the codebase.
- Implementing a 'code-as-source-of-truth' pricing system to prevent configuration drift and eliminate manual Stripe dashboard errors.
- Architecting a decoupled billing system that allows for switching payment processors or A/B testing pricing without refactoring core business logic.
- Developing automated synchronization workflows between application databases (Neon/Postgres) and payment platforms to ensure data integrity.
- Creating a scalable entitlement system where user access levels are derived from internal platform state rather than external metadata.
| name | pricing |
|---|---|
| description | Pricing strategy - tiers, feature gating. Use when designing pricing. |
Pricing Guideline
Tech Stack
- Payments: Stripe
- Database: Neon (Postgres)
- ORM: Drizzle
Non-Negotiables
- Platform is source of truth — Stripe syncs FROM platform, never reverse
- All pricing/product configuration must be in code
- Feature entitlements derived from platform state, not Stripe metadata
- Pricing drift must be detectable and auto-correctable
- No manual Stripe dashboard configuration
Context
Pricing owns strategy — what tiers exist, what features each tier gets, how upgrades work. Billing handles the payment mechanics. This separation allows switching payment processors without repricing.
Driving Questions
- Is all pricing defined in code?
- How do we test pricing changes before going live?
- What would make upgrading feel like an obvious decision?
- How do we communicate value at each tier?
- Can we A/B test pricing without Stripe changes?