Gtm Technical Product Pricing
Pick and defend pricing models for APIs, dev tools, and technical SaaS before you scale GTM.
Overview
GTM Technical Product Pricing is an agent skill most often used in Validate (also Build, Grow) that structures pricing strategy for technical products—from model choice to enterprise raises and positioning.
Install
npx skills add https://github.com/github/awesome-copilot --skill gtm-technical-product-pricingWhat is this skill?
- Initial assessment checklist across product type, current pricing tenure, GTM motion, marginal cost, and competitive “do
- Frameworks for usage-based vs seat-based models, freemium thresholds, and enterprise tier justification
- Enterprise price-increase playbook with positioning via bundled value (SSO, audit logs, dedicated support)
- Guidance on when to raise prices and using price as a positioning signal in technical markets
- Written for self-serve, sales-assisted, enterprise, and hybrid GTM motions on APIs, platforms, and infra products
Adoption & trust: 1.4k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You launched with legacy pricing and no framework for usage vs seats, freemium limits, or enterprise conversations while buyers capture most of the value.
Who is it for?
Founders pricing an API, dev tool, or technical SaaS with mixed self-serve and enterprise motion who need a disciplined pricing conversation before scaling sales.
Skip if: Teams that only need Stripe SKU setup with pricing already locked, or non-technical consumer apps where competitive comps are purely retail-style.
When should I use this skill?
Choosing usage-based vs seat-based pricing, designing freemium thresholds, structuring enterprise pricing conversations, deciding when to raise prices, or using price as a positioning signal.
What do I get? / Deliverables
You leave with assessment-backed pricing recommendations and enterprise packaging rationale you can plug into positioning, sales scripts, and the next validate or grow iteration.
- Pricing model recommendation aligned to cost structure and competitive alternatives
- Enterprise tier and packaging narrative for sales conversations
- Raise-or-hold decision framing with positioning rationale
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Pricing decisions and model design belong on the validate shelf where founders prove willingness-to-pay and unit economics before full build-out. The skill’s assessment flow (product type, marginal cost, competitive alt including “do nothing”) maps directly to the pricing subphase, not generic research.
Where it fits
Compare usage-based API metering vs flat team seats before committing to billing wiring.
Frame MVP scope against a freemium ceiling that still covers marginal API cost.
Plan a justified enterprise tier increase with SSO and audit features instead of discounting.
Align public list price and packaging copy with positioning as premium vs commodity infra.
How it compares
Use instead of one-off chat opinions on “what should we charge” when you need GTM-aligned model tradeoffs and raise timing—not a billing integration skill.
Common Questions / FAQ
Who is gtm-technical-product-pricing for?
Solo builders and indie technical founders (and small GTM leads) shipping APIs, platforms, developer tools, or infra SaaS who own pricing before a dedicated revenue ops hire.
When should I use gtm-technical-product-pricing?
During validate when scoping pricing and freemium; before enterprise deals in build; and in grow when revisiting tiers, raises, or usage-based alignment to cost structure.
Is gtm-technical-product-pricing safe to install?
It is advisory Markdown guidance with no shell or network hooks by default; review the Security Audits panel on this Prism page before trusting any third-party skill source.
SKILL.md
READMESKILL.md - Gtm Technical Product Pricing
# 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: ``` Value Ratio = Customer's alternative cost / Your price If Value Ratio > 10x → You're massively underpriced If Value Ratio > 5x → You're underpriced (most startups are here) If Value Ratio 3-5x → Healthy pricing If Value Ratio < 3x → Approaching ceiling If Value Ratio < 2x → You're expensive (need strong differentiation) ``` **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. The Three Pricing Models (And When Each Breaks) **Model 1: Seat-Based ($X/user/month)** **Works when:** - Value scales with number of users (collaboration tools, communication) - Usage is relatively uniform across users - You want predictable revenue **Breaks when:** - Power users and casual users get same price (casual users churn) - Product value doesn't scale with seats (one admin configures for 1,000 users) - Customers consolidate seats to reduce cost (usage goes up, revenue doesn't) **Model 2: Usage-Based ($X/unit)** **Works when:** - Usage varies significantly by customer (API calls, compute, storage) - Marginal cost is meaningful (you need usage to track with revenue) - Value directly correlates with usage **Breaks when:** - Customers can't predict bills (sticker shock at month-end) - Low-usage customers aren't worth supporting - High-usage customers negotiate volume discounts that compress margins **Model 3: Outcome-Based ($X/result)** **Works when:** - You can measure outcomes reliably (leads generated, tickets resolved, code deployed) - Outcomes directly create customer value - You have confidence in your product's effectiveness **Breaks when:** - Outcomes depend on factors outside your control - Measurement is disput