pricing-strategy
Pricing Strategy Guide
Pricing Models
One-Time Purchase
- Best for: Desktop software, physical goods, courses
- Pros: Simple, high upfront revenue
- Cons: No recurring revenue, harder to update
Subscription (SaaS)
- Best for: Software, services, content
- Pros: Predictable revenue, ongoing relationship
- Cons: Higher churn risk, constant value delivery needed
Freemium
- Best for: Products with network effects, low marginal cost
- Pros: Low barrier to entry, viral potential
- Cons: Conversion optimization critical, free users cost money
More from jamelna-apps/claude-dash
cost-tracking
When user mentions "spending", "usage", "tokens", "API cost", "budget", "expensive", or wants to understand Claude API costs. Provides cost awareness and optimization guidance.
11page-cro
When the user mentions "conversion", "CRO", "landing page", "not converting", "bounce rate", "optimize page", or asks about improving page performance.
7session-handoff
When user says "continue", "pick up where we left off", "last time", "previous session", "what were we doing", or wants explicit session continuity. Provides structured context handoff between sessions.
4error-diagnosis
When user encounters "error", "exception", "failed", "stack trace", "crashed", or needs error categorization. Provides structured root cause analysis and prevention strategies.
4code-review
When the user mentions "review", "PR", "pull request", "code review", "check my code", "feedback on", or asks for code quality assessment.
3smart-routing
When deciding which Claude model (Opus/Sonnet/Haiku) to use, or when "route", "which model", "complex task", "multi-file", "architectural", or "deep debugging" is mentioned. Guides quality-first model selection.
3