monetizePricing, launch, and revenue strategies for indie products, SaaS, mobile apps, and creators. Concrete prices, not theory.
Install via ClawdBot CLI:
clawdbot install ivangdavila/monetizeTell me what you're building and your situation. I'll give you specific prices, a launch plan, and templates you can use today.
No "it depends." No theory. Decisions made for you.
| Situation | Read |
|-----------|------|
| Mobile app | mobile-apps.md |
| SaaS/subscription | saas.md |
| Content/creator | creator.md |
| Need pricing math | pricing.md |
| Ready to launch | launch.md |
| Need copy/templates | templates.md |
| Real success patterns | success.md |
You're probably underpriced. Data across 25K+ companies shows the median leaves 30% on the table. Price higher than comfortable, validate with real sales.
Packaging > Pricing. How you bundle features matters more than the number. Get packaging right first.
10 happy customers who'd recommend > 100 customers. Quality matters more than quantity.
Charge from day one. No "free beta." If people won't pay $1, they won't pay $100. Credit cards validate, promises don't.
Build for yourself first. You should be user #1. If you don't need it, you'll quit when it gets hard.
Before pitching anyone (VCs, partners, yourself):
| Metric | Target | How to Calculate |
|--------|--------|------------------|
| LTV:CAC | >3:1 | Lifetime value ÷ acquisition cost |
| Payback | <12 months | CAC ÷ (monthly revenue × margin) |
| Gross margin | >70% | (Revenue - variable costs) ÷ revenue |
| Monthly churn | <5% | Lost customers ÷ start customers |
If you can't answer these with data, you're not ready.
Generated Mar 1, 2026
An indie developer building a mobile app needs specific pricing strategies and a launch plan to generate revenue from day one, avoiding free betas and focusing on credit card validation to ensure market fit.
A founder creating a SaaS product requires concrete pricing tiers, packaging advice, and unit economics like LTV:CAC to attract paying customers immediately and scale sustainably.
A content creator or influencer seeks revenue strategies, such as bundling offerings and setting prices higher than comfortable, to turn followers into paying customers without relying on free tiers.
An entrepreneur launching a physical product needs help with pricing math, launch templates, and avoiding underpricing by validating with real sales data to maximize profit margins.
Focuses on recurring revenue with tiered pricing packages, emphasizing high gross margins and low churn rates. It requires charging from day one and avoiding free trials that devalue the offering.
Offers a free tier with limited value to attract users, but the core revenue comes from paid upgrades. The skill warns against free tiers having over 90% of the value to ensure conversion to paying customers.
Involves selling a base product at a fixed price with optional add-ons or bundles. It stresses packaging over pricing to increase perceived value and avoid discounting in every deal.
💬 Integration Tip
Integrate this skill early in product development to set prices and launch plans from the start, using the provided guides like pricing.md and launch.md for actionable steps.
Full Windows desktop control. Mouse, keyboard, screenshots - interact with any Windows application like a human.
Control Android devices via ADB with support for UI layout analysis (uiautomator) and visual feedback (screencap). Use when you need to interact with Android apps, perform UI automation, take screenshots, or run complex ADB command sequences.
Build, test, and ship iOS apps with Swift, Xcode, and App Store best practices.
Control macOS GUI apps visually — take screenshots, click, scroll, type. Use when the user asks to interact with any Mac desktop application's graphical interface.
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
Write safe Swift code avoiding memory leaks, optional traps, and concurrency bugs.