Menu
Design SaaS tiers, value metrics, and packaging that grow with the customer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Map competitors across product, pricing, and positioning and produce sales-ready battle cards.
Build a focused GTM plan — ICP, positioning, channels, and a sequenced launch — instead of a scattershot.
Use when you are running an actual launch day in real time across channels. Triggers on "launch day runbook", "we launch tomorrow", "Product Hunt launch day plan", "hour by hour launch schedule", "who does what on launch day", "PH / Hacker News / Twitter / email sequencing", "launch day checklist", "our launch is going sideways", "contingency if we get rate-limited / Show HN flops / site goes down". Turns the plan into a minute-by-minute war room. Do NOT use when you are still picking the launch date, beats, or channel mix — use [[launch-plan-sequencer]] for the calendar first; this is the execution companion that runs the day it lands on.
Use when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself — use launch-day-runbook instead. Do NOT use to write the core message — use positioning-statement and messaging-hierarchy. Do NOT use to design the self-serve adoption motion — use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script — use sales-enablement-kit.
Use when turning a positioning statement into actual copy — building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning — use positioning-statement first. Do NOT use when you need the actual hero/landing page words — use landing-page-copy. Do NOT use to sequence launch phases — use launch-plan-sequencer; for the hour-by-hour go-live — use launch-day-runbook; for the sales deck/talk track — use sales-enablement-kit; for the in-product activation flow — use plg-motion-designer.
Use when designing a product-led, self-serve activation motion for signups. Triggers on "design our PLG motion", "self-serve onboarding", "what is our aha moment", "define activation", "activation rate", "time-to-value", "onboarding funnel", "in-product nudges", "set activation milestones", "signup to value", "free-to-paid", "PQL". Defines the aha moment, the activation milestones to it, and the in-product nudges and metric gates between each step. Do NOT use for outbound/sales-led launch sequencing — use [[launch-plan-sequencer]] instead; for arming a human sales team with collateral, use [[sales-enablement-kit]] instead; for the page that captures the signup, use [[landing-page-copy]]; for pricing tiers and the paywall, use [[saas-pricing]] and [[pricing-strategy]].
| name | SaaS Pricing Model |
| description | Design SaaS tiers, value metrics, and packaging that grow with the customer. |
Pricing is the highest-leverage growth lever and the least-tested. A 1% price improvement often beats a 1% gain in acquisition or retention. This skill designs pricing that aligns what you charge with the value you create.
The value metric is the unit you charge by — seats, events, GB, transactions. A good value metric:
Per-seat is simple but caps with headcount. Usage-based aligns with value but hurts predictability. Hybrid (platform fee + usage) is increasingly standard.
Use three tiers as the default. The middle tier should be the one you want most customers to choose — anchor it with a deliberately under-featured low tier and a premium high tier.
Gate features by buyer sophistication and willingness to pay, not by cost to build. SSO and audit logs belong in the top tier because they signal budget.
Net revenue retention above 100% is the engine of SaaS compounding. Build expansion in from the start:
Produce a pricing page spec: the value metric and its rationale, three tiers with feature gates, list prices, annual discount, and the expansion path with target net revenue retention.
