Skill: pricing-and-wtp

Purpose

Determine what users would actually pay, not what the developer hopes to charge. Anchor WTP to pain intensity, desire strength, competitive pricing, and real monetization signals from market_insights — never to the cost of building. Pricing is the single decision with the highest leverage on unit economics: a $1/mo difference at 1,000 users is $12K/year.

Input

• Idea slug
• memory/ideas/<slug>/idea.md (app concept, key features)
• memory/ideas/<slug>/user_extraction.json (pain intensity)
• memory/ideas/<slug>/competitors.json (competitive pricing, pricing models in use)
• memory/ideas/<slug>/desire_scores.json (desire strength, primary/secondary drivers)
• memory/market_insights/<niche>-*-<YYYY>-<MM>.md (trend data — use all available platform files)

Using Market Insights