monetization-strategy
Revenue models, pricing strategies, and business monetization. Use when designing pricing, choosing business models, or optimizing revenue for products and services.
What this skill does
# Monetization Strategy
Comprehensive guide for monetizing products and services effectively.
## Revenue Model Types
### Overview
| Model | How It Works | Best For |
| ----------------- | -------------------------- | ------------------------- |
| **Subscription** | Recurring payment | SaaS, content, services |
| **Transactional** | Pay per use/purchase | E-commerce, marketplaces |
| **Freemium** | Free tier + paid upgrades | Consumer apps, tools |
| **Advertising** | Sponsors pay for attention | Media, social, free tools |
| **Marketplace** | Take % of transactions | Two-sided platforms |
| **Licensing** | Pay for usage rights | Software, IP, content |
| **Affiliate** | Commission on referrals | Content, reviews |
| **Data** | Sell insights/data | Analytics, research |
---
## Subscription Models
### Pricing Tiers
```
GOOD-BETTER-BEST Framework:
┌─────────────────────────────────────────┐
│ BASIC (Good) │
│ Entry point, core features only │
│ Price anchor, volume driver │
├─────────────────────────────────────────┤
│ PROFESSIONAL (Better) ← Target tier │
│ Most popular, best value │
│ Features most users need │
├─────────────────────────────────────────┤
│ ENTERPRISE (Best) │
│ Premium features, support, SLAs │
│ High-value customers, custom pricing │
└─────────────────────────────────────────┘
Typical ratio: 1x : 2.5x : 6x+ pricing
```
### SaaS Metrics
| Metric | Formula | Target |
| --------- | --------------------------------------- | ----------- |
| **MRR** | Monthly Recurring Revenue | Growing |
| **ARR** | MRR × 12 | Growing |
| **ARPU** | Revenue / Users | Increasing |
| **Churn** | Lost Revenue / Total | <5% monthly |
| **LTV** | ARPU × Average Lifespan | > 3× CAC |
| **CAC** | Sales+Marketing / New Customers | < ⅓ LTV |
| **NRR** | (Start MRR + Expansion - Churn) / Start | >100% |
### Subscription Best Practices
```
DO:
✓ Offer annual discount (15-20%)
✓ Make cancellation friction-free
✓ Send value reminders (usage emails)
✓ Offer downgrade before cancel
✓ Build expansion revenue paths
DON'T:
✗ Hide pricing
✗ Make cancellation difficult
✗ Surprise users with charges
✗ Neglect failed payment recovery
✗ Ignore inactive subscribers
```
---
## Freemium Models
### Freemium Types
| Type | Free Tier Limit | Examples |
| ------------------- | --------------- | ------------------ |
| **Feature-limited** | Core only | Slack, Notion |
| **Usage-limited** | Quantity caps | Mailchimp, Dropbox |
| **Time-limited** | Trial period | Netflix, Spotify |
| **Seat-limited** | User count | Figma, Zoom |
| **Support-limited** | Community only | Open source tools |
### Conversion Funnel
```
Free Users (100%)
│
▼
Active Users (40-60%)
│
▼
Engaged Users (10-20%)
│
▼
Conversion Ready (3-5%)
│
▼
Paid Users (2-5%)
Target: 2-5% free-to-paid conversion
Top performers: 10%+
```
### Designing the Free Tier
```
Free tier should:
┌─────────────────────────────────────────┐
│ ✓ Deliver real value (not crippled) │
│ ✓ Showcase premium features naturally │
│ ✓ Create habit/dependency │
│ ✓ Encourage sharing/virality │
│ ✓ Cost nearly nothing to serve │
└─────────────────────────────────────────┘
Upgrade triggers:
- Usage limits (storage, API calls)
- Collaboration (team features)
- Advanced features (analytics, exports)
- Support (priority, SLA)
- Integration (API access, SSO)
```
---
## Pricing Psychology
### Key Principles
| Principle | Application |
| --------------------- | ----------------------------------- |
| **Anchoring** | Show expensive option first |
| **Decoy** | Add inferior option to guide choice |
| **Charm pricing** | $99 vs $100 |
| **Round pricing** | $100 for premium feel |
| **Price bundling** | Combined value perception |
| **Left-digit effect** | $3.99 seems much less than $4 |
### Price Presentation
```
DO:
✓ Highlight "most popular" option
✓ Show savings for annual plans
✓ Use social proof at each tier
✓ Display price per user/month
✓ List features in value order
DON'T:
✗ Too many tiers (max 4)
✗ Overwhelming feature lists
✗ Hide important limitations
✗ Make comparison difficult
```
### The Decoy Effect
```
Without decoy:
┌─────────────┬─────────────┐
│ Basic $10 │ Pro $25 │ Most choose Basic
└─────────────┴─────────────┘
With decoy:
┌─────────────┬─────────────┬─────────────┐
│ Basic $10 │ Plus $24 │ Pro $25 │
│ 5 features │ 8 features │ 15 features │
└─────────────┴─────────────┴─────────────┘
↑
Now Pro looks like best value
```
---
## Pricing Strategy
### Cost-Based vs. Value-Based
```
COST-BASED:
Price = Costs + Desired Margin
Problem: Ignores what customers will pay
Use when: Commoditized market, thin margins
VALUE-BASED:
Price = Customer's perceived value × capture %
Better because: Captures willingness to pay
Use when: Differentiated product, clear value
```
### Value-Based Pricing Process
```
Step 1: Understand customer's alternative
What would they pay without you?
Step 2: Quantify your differentiated value
How much better/faster/cheaper?
Step 3: Calculate customer's willingness to pay
What % of value can you capture?
Example:
- Alternative costs customer $1000/month
- Your solution saves 50% ($500/month value)
- Capture 30% of value = $150/month price
```
### Pricing Research Methods
| Method | How It Works | Accuracy |
| ----------------------- | --------------------- | -------- |
| **Van Westendorp** | Ask 4 price questions | Medium |
| **Conjoint Analysis** | Trade-off choices | High |
| **A/B Testing** | Test live prices | Highest |
| **Competitor Analysis** | Market benchmarks | Low |
| **Customer Interviews** | Qualitative insight | Low |
### Van Westendorp Questions
```
Ask potential customers:
1. At what price would it be too expensive?
2. At what price would it be too cheap (suspicious)?
3. At what price would it be getting expensive but still okay?
4. At what price would it be a bargain?
Plot responses to find optimal price range.
```
---
## Revenue Optimization
### Expansion Revenue
```
Paths to expansion:
┌─────────────────────────────────────────┐
│ UPSELL: Upgrade to higher tier │
│ CROSS-SELL: Additional products │
│ ADD-ONS: Premium features à la carte │
│ SEATS: More users on account │
│ USAGE: Pay for increased usage │
└─────────────────────────────────────────┘
Goal: Net Revenue Retention > 100%
Top companies: 120-150% NRR
```
### Reducing Churn
```
PROACTIVE MEASURES:
- Track engagement health scores
- Identify at-risk accounts early
- Reach out before renewal
- Offer value consultations
- Build switching costs (integrations)
REACTIVE MEASURES:
- Exit surveys (learn why)
- Pause option vs. cancel
- Downgrade path available
- Win-back campaigns
```
### Failed Payment Recovery
```
DUNNING SEQUENCE:
Day 0: Payment fails → Auto-retry
Day 1: Email: "Update payment method"
Day 3: Email: "Action required"
Day 7: Email: "Service interruption soon"
Day 14: Downgrade to free / pause
Day 30: Account suspension
Recovers 30-50% of failed payments
```
---
## Marketplace Monetization
### Take Rate Models
| Model | Typical Rate | Examples Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.