Agent skill · product strategy · github
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.
Why this skill is useful
Provides a structured framework for pricing technical products that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 founders anchor pricing to cost ("it costs us $X to serve them, so we charge $2X"). Enterprise buyers anchor pricing to value ("this saves us $200K, so $45K is cheap"). The Pricing Sanity Check: For every customer segment, calculate: How to Calculate Alternative Cost: Hours spent on manual process × hourly rate × frequency Cost of building in-house (engineers × months × loaded cost) Cost of existing tool + switching cost + productivity loss during transition Cost of not solving the problem (incidents, downtime, churn) Common Mistake: Comparing your price to competitors instead of to customer's alternative cost. Competitors anchor you to a race to the bottom. Value anchors you to what the customer actually saves. --- 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gtm-technical-product-pricing