What problem does it solve? Developer tools often achieve wide adoption but no revenue because nobody defined what gets sold, who signs, or where the free-to-paid boundary sits. This Skill guides founders and execs through choosing a monetization model and writing an executable decision memo. ## Core Features & Use Cases - Model selection across nine archetypes: proprietary SaaS, open core, hosted open source, support/LTS, dual licensing, source-available, consumption metering, ecosystem take-rate, and OEM licensing, each ranked by value per unit of founder effort. - Paid-boundary validation: five written tests (organization-only, defensibility, observable trigger, cost-to-serve, licence compatibility) that block unviable models before commitment. - Decision memo output: constraints, rejected models with reasons, primary model, value metric, GTM consequence, leading indicator, risks, and revisit triggers. - Use Case: A team with 12,000 weekly downloads and zero revenue uses the Skill to eliminate blocked archetypes, test two candidate models, and commit to hosted open source with a dated validation experiment. ## Quick Start Ask the assistant to help decide how your open-source developer tool should make money, describing your licence, deployment model, and current revenue.
