Find the revenue model your customers will actually pay for.
Describe the product, who buys it and what you need from revenue. Your assistant brainstorms three to five distinct monetization models, works the unit economics for each, names the risks, and designs a cheap experiment to test willingness to pay before you commit.
Original instructions by Pawel Huryn (phuryn/pm-skills), preserved byte for byte.
The five models from that run with their prioritization totals out of 20 (four criteria scored 1–5). The scores are the assistant’s judgment, not measurements.
What it is
A single instruction file that casts your assistant as a business model strategist. Every strategy is written up in seven parts: description, how it works, audience fit, unit economics, risks, competitive position and a validation experiment.
It then ranks the options by strategic fit, ease, validation potential and competitive advantage, recommends one or two to test first, and lays out a testing roadmap with success criteria.
Who it is for
- Product managersdeciding how a product or feature should earn.
- Founderschoosing between subscription, usage or one-off pricing.
- Growth and pricing leadsplanning willingness-to-pay tests.
- Teams reviewing a pricing ideabefore it reaches customers.
Works well for
- Exploring revenue models for a new product
- Pressure-testing a proposed add-on or price change
- Comparing hybrid models such as subscription plus fees
- Designing low-cost pricing experiments
Not designed for
- Exact price points backed by market data
- Financial forecasts, valuations or investment advice
- Live competitor pricing; it has no built-in web research
- Running the experiments it designs
Your order, your receipt
You provide
- Product or feature description
- Target segments and customer profile
- Willingness to pay or budget constraints
- How competitors monetize
- Priorities: revenue, user growth or profitability
You receive
- 3–5 distinct strategies, each in seven parts
- CAC, LTV, break-even and margin estimates
- A validation experiment with a success metric
- A ranking across four criteria
- 1–2 strategies to test first, plus a testing roadmap
Where it runs
Any AI assistant that can read a Skill file, including Claude Code and Codex. Download the free plaintext package from Finch and install it with your assistant’s Skill method, or point the assistant at SKILL.md.
No extra API key, script or service. You still need access to an assistant model, which may carry its own subscription or usage cost. Competitor prices and market sizes must come from you or from an assistant with its own search tools.
Limits and licence
Unit economics are only as good as the numbers you supply; when CAC or elasticity is unknown, the output should say so. Treat every figure as a hypothesis for the experiment.
MIT licence, Copyright (c) 2026 Pawel Huryn. Source: phuryn/pm-skills at commit 2a12295a7717, path pm-product-strategy/skills/monetization-strategy. The package adds a README, NOTICE, provenance note and a promotional cover; the instructions are unchanged.