
Pricing Strategy
Design freemium vs paid, willingness-to-pay conversations, and iterative pricing before you lock in monetization on a solo SaaS or product.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill pricing-strategyWhat is this skill?
- Frameworks distilled from 46 product leaders on value-based pricing and iteration
- Willingness-to-pay conversations positioned as early product-value signal (Madhavan Ramanujam framing)
- Explicit anti-pattern: avoid “set it and forget it” after feature work
- Structured flow: business model → value delivery → constraints → pricing you can evolve
- Covers freemium vs paid, model transitions, and optimization—not one-shot price picking
Adoption & trust: 1.4k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Journey fit
Canonical shelf is Validate because the skill is triggered for first-time pricing, model choice, and WTP—decisions you make before or alongside a serious build commit. Pricing is the only validate subphase that matches setting prices, freemium transitions, and monetization optimization called out in the skill description.
Common Questions / FAQ
Is Pricing Strategy safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Pricing Strategy
# Pricing Strategy Help the user design and optimize pricing strategies using frameworks from 46 product leaders. ## How to Help When the user asks for help with pricing: 1. **Understand the business model** - Ask about their current monetization approach and target customer segments 2. **Assess value delivery** - Determine what value they're creating and for whom 3. **Identify constraints** - Understand technical, market, and competitive pricing pressures 4. **Design for iteration** - Help them create pricing that can evolve as they learn ## Core Principles ### Price is a measure of value Madhavan Ramanujam: "When we think about price, we think about it as a measure. Like liter is a measure of volume, price is a measure of value. And when you think of it this way, it really stands for, do people actually want your product?" Use willingness to pay (WTP) as a proxy for product value and conduct WTP conversations early in the development cycle. ### Never set it and forget it Naomi Ionita: "Do not set it and forget it. I see companies do this, where they labor over designs and features... And then pricing's sort of plucked out of thin air, and then they don't revisit it." Treat pricing as a living part of the product roadmap, revisiting it every 6-12 months as new value is added. ### Self-serve has a ceiling Elena Verna: "Self-serve monetization has a cap of about $10,000. That's just how much we're able to process on the credit cards before they start getting flagged and declined." Transition to sales-led motions for contracts exceeding $10,000-$15,000 due to technical payment limits and individual spending authority. ### Sample premium features in the free experience Albert Cheng: "What if we actually sampled a number of different paid suggestions and interspersed them to free users across their writing? All of a sudden, people were seeing Grammarly as a much more powerful tool." Interspersing paid features within the free experience is more effective for conversion than keeping them hidden behind a hard paywall. ### Reduce early friction to unlock success Archie Abrams: "When you can lower the barriers to monetary friction in some form... you can actually causally change your ability to become successful, because I've given you a little bit more time to try that idea." Reducing early monetary friction can causally improve user success by extending their "runway" to find value in the product. ### Prioritize roadmap by willingness to pay Madhavan Ramanujam: "You cannot prioritize a product roadmap without having a willingness to pay conversation. If you're just prioritizing based on what you think or what you feel or technical resources, you're getting it wrong." Prioritize the 20% of features that drive 80% of the willingness to pay. ### Pricing changes are two-way doors Eeke de Milliano: "Move faster on reversible decisions like pricing by grandfathering existing users." Most pricing changes can be reversed or adjusted, especially when you protect existing customers through grandfathering. ## Questions to Help Users - "What would customers pay for this if they had to pay today? Have you asked them directly?" - "What value does your product create, and for which customer segment is that value highest?" - "When did you last revisit your pricing? What has changed about your product since then?" - "What's preventing you from charging more? Is it competition, value delivery, or assumption?" - "How do free users experience the value of paid features today?" - "At what price point does your sales motion need to change from self-serve to sales-assisted?" ## Common Mistakes to Flag - **Pricing as afterthought** - Setting prices