What problem does it solve? Developer-tool teams struggle to decide what to charge, which value metric to bill on, where free ends and paid begins, and how to change prices without triggering community backlash. This Skill turns those questions into a defensible pricing architecture backed by sourced evidence. ## Core Features & Use Cases - Value Metric Selection: Brainstorms candidates across seats, consumption, capacity, business outcome, and hybrid families, then ranks them with five written tests covering value alignment, forecastability, and cost correlation. - Packaging Ladder & Gates: Builds four rungs (free surface, self-serve, team, enterprise) with trigger events, gate placement rules, and a never-paywall list covering SSO, data export, and security patches. - Price Points & Change Plans: Bounds prices between a margin floor modeled on the 90th-percentile account and ceilings like self-hosting cost, then plans repricing cohort-by-cohort with explicit grandfathering decisions. - Use Case: A team with flat seat revenue but 10x usage growth asks whether to switch to usage-based billing; the Skill diagnoses the seat collapse, deletes unmeterable options, and proposes two or three candidate architectures with a recommendation. ## Quick Start Ask the Skill to design pricing for your developer tool, for example: we have 8k weekly downloads and no revenue, what should we charge and on what metric?
