# Technical product pricing

A found skill by Smit Patel, listed in github/awesome-copilot.

Helps you choose usage-based or seat-based pricing for a technical product, set where a free plan should end, and plan an enterprise conversation or a price rise from evidence you already have.

Task: Planning and reviews
Works with: GitHub Copilot, Claude, ChatGPT, Gemini
Tools: GitHub Copilot, Claude
Difficulty: Intermediate
Country: Country unknown

Use this when you are choosing a pricing model for a technical product, or deciding where a free plan ends, or how to talk about enterprise pricing or a rise.
Skip this if you want freelance service packages, or if you want a price invented without your cost, value or competitor facts.

Credit: Smit Patel, listed in github/awesome-copilot
Source: https://github.com/github/awesome-copilot/blob/main/skills/gtm-technical-product-pricing/SKILL.md
Licence: MIT

## Skill text

Please turn the text below into a reusable skill. If you are Claude, save it as a skill. If you are ChatGPT or Gemini, save it as the instructions for a Project, custom GPT or Gem. If you cannot save skills, just follow these instructions now.

Name: Technical product pricing

Description: Use this when you are choosing a pricing model for a technical product, or deciding where a free plan ends, or how to talk about enterprise pricing or a rise.

Ask me for:
1. What the product does, who it is for and how it is used.
2. My current prices, costs and any limits I already have, if I have them.
3. Public competitor prices I can point to, if any.
4. Whether I want help with the model, the free-plan threshold, an enterprise conversation or a price rise.

Steps:
1. Restate the product and the decision I asked for.
2. Compare usage-based and seat-based pricing against how customers actually use the product, and say where each model would break.
3. If I asked about a free plan, suggest where free should end, tied to a usage or value limit I already have, and say what I would need to check.
4. If I asked about enterprise deals, draft questions I can use in a sales conversation instead of leading with a number.
5. If I asked about a rise, list the evidence I already have and the risks of changing price, and draft a short notice I can edit.
6. Mark any figure I did not supply as unknown.

Output: The decision brief, the model comparison, the optional threshold, conversation or notice drafts, and the open questions.

Rules:
- Do not invent a price, conversion rate or competitor figure.
- Do not tell me to change a live price without my yes.
- Credit is due to the original skill's author, as noted in the footer.

This is our own short starter, informed by the gtm-technical-product-pricing skill by Smit Patel, listed in github/awesome-copilot. The original is at https://github.com/github/awesome-copilot/blob/main/skills/gtm-technical-product-pricing/SKILL.md. MIT licence, Copyright GitHub, Inc. Skill metadata also names Smit Patel and https://github.com/beingsmit/technical-product-gtm. Check the licence before reusing its own text. No full third-party text copied.

## More

- [This skill as a web page](https://agentstories.org/skills/gtm-technical-product-pricing.html)
- [All skills, as a Markdown list](https://agentstories.org/skills.md)
- [Skills directory](https://agentstories.org/skills/)
