gtm-technical-product-pricing
Pricing strategy for technical products. Use when choosing usage-based vs seat-based, designing freemium thresholds, structuring enterprise pricing conversations, deciding when to raise prices, or using price as a positioning signal.
Profile →npx skills add github/awesome-copilot --skill gtm-technical-product-pricing --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Technical Product Pricing ## Initial Assessment Before recommending pricing, understand: 1. **Product type**: API/platform, developer tool, SaaS application, infrastructure? 2. **Current pricing**: What do you charge now? How long has it been this way? 3. **GTM motion**: Self-serve, sales-assisted, enterprise, or hybrid? 4. **Cost structure**: What's your marginal cost per customer/user/unit? 5. **Competitive landscape**: What do alternatives cost? (Including "do nothing") --- ## Core Frameworks ### 1. The Price Increase Nobody Noticed (You're Probably Underpriced) **The Pattern:** Platform company, growth stage. Pricing hadn't changed since launch. Enterprise customers paying $15K/year for a product saving them $200K+ in engineering time. Leadership debate: "If we raise prices, we'll lose customers." **What actually happened:** Raised enterprise tier from $15K to $45K/year. Added dedicated support, SSO, audit logs to justify the jump. Lost: 0 enterprise customers. Zero. Gained: 3x revenue per enterprise account. Plus the customers who stayed started taking the product more seriously — higher adoption, more internal champions, more expansion. **Why This Happens:** Technical found
- Initial Assessment
- Core Frameworks
- 1. The Price Increase Nobody Noticed (You're Probably Underpriced)
- 2. The Three Pricing Models (And When Each Breaks)
- 3. Freemium Threshold Design (Where Free Ends and Paid Begins)
- 4. Enterprise Pricing (The Conversation, Not the Number)
- 5. Pricing as Positioning Signal
- 6. When and How to Raise Prices
- Decision Trees
- Which Pricing Model?
- Should We Raise Prices?
- Related Skills
What does the gtm-technical-product-pricing skill do?
Pricing strategy for technical products. Use when choosing usage-based vs seat-based, designing freemium thresholds, structuring enterprise pricing conversations, deciding when to raise prices, or using price as a positioning signal.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-technical-product-pricing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.