A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.

MITAuto-check passedSales & Support

Install Setting Pricing

skills CLI
$ npx skills add GTM-Strategist/gtm-strategist-skills --skill setting-pricing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install GTM-Strategist/gtm-strategist-skills setting-pricing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/setting-pricing .claude/skills/setting-pricing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
setting-pricing
GitHub stars
264
Token cost
~5.4k tokens
SKILL.md length
2,586 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.

  • Works in 3 steps: Read my-gtm-context.md — especially… → Check outputs/ for prior phase… → Determine product type context. Pricing…
  • The user asks about pricing strategy
  • SKILL.md covers Before You Begin, Tasks, Summary and Go Deeper
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Setting Pricing is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design. Phase 5 of 12: interactive guided workflow for competition-based pricing research, value metric identification, Van Westendorp / Gabor-Granger WTP research, business model creation, unit economics (CAC/LTV), offer crafting, pricing workshops, and pricing review schedules.

Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Pricing strategy, Product strategy and Financial modeling. The repository describes itself as: Your AI go-to-market co-pilot. The licence is MIT.

When your agent uses it

  • The user asks about pricing strategy
  • How to price their product
  • Willingness-to-pay research
  • Business model design

Example prompts

  • “/setting-pricing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read my-gtm-context.md — especially sections 5 (Business Model), 4 (Problem & Value), 3 (ICP), 6 (Competitive Landscape), and 2 (Target…
  2. Check outputs/ for prior phase deliverables. This phase builds on
  3. Determine product type context. Pricing approaches differ significantly

What it can do on your machine

Read from SKILL.md and the folder at commit a5ead26. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • gtmstrategist.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Setting Pricing loads about 5.4k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 2,586 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from GTM-Strategist/gtm-strategist-skills at commit a5ead26, republished under its MIT licence (© GTM-Strategist). 2,586 words, ~5,398 tokens.

Download SKILL.mdSave it as .claude/skills/setting-pricing/SKILL.md (or your agent's skills folder).
name
setting-pricing
description
Use this skill when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design. Phase 5 of 12: interactive guided workflow for competition-based pricing research, value metric identification, Van Westendorp / Gabor-Granger WTP research, business model creation, unit economics (CAC/LTV), offer crafting, pricing workshops, and pricing review schedules.

Setting Pricing — Phase 5 of 12

You are a GTM pricing strategist executing Phase 5 of the GTM Strategist methodology. This phase transforms market intelligence and validated customer insights into a defensible pricing strategy and business model.


Before You Begin

  1. Read my-gtm-context.md — especially sections 5 (Business Model), 4 (Problem & Value), 3 (ICP), 6 (Competitive Landscape), and 2 (Target Market). If the Business Model section is empty, that is expected — this phase will fill it. But if ICP (section 3) and Problem & Value (section 4) are empty, prompt the user to complete Phase 3 (validating-customers) first.

  2. Check outputs/ for prior phase deliverables. This phase builds on:

    • outputs/03-* (Phase 3: Validated persona, ICP/ECP) — who you are pricing for
    • outputs/04-* (Phase 4: JTBD, product definition, MVP) — what you are pricing
    • outputs/02-* (Phase 2: Competitor analysis) — competitive pricing context
    • If key prior outputs are missing, tell the user which phase to complete first and why it matters for pricing decisions. Let them proceed if they choose, but flag the assumptions they are making.
  3. Determine product type context. Pricing approaches differ significantly:

    • SaaS/Software: Value metrics, tiered plans, freemium considerations
    • Services: Packaging, productized offers, retainers vs. project-based
    • Physical products: Cost-plus baseline, perceived value premium
    • Marketplace: Take rate, two-sided pricing
    • Read the Product type field from my-gtm-context.md and tailor all tasks accordingly.

Tasks

Work through these tasks one at a time. Present each deliverable, get feedback, then move to the next. Each task builds on the previous — the sequence is intentional.


Task 1: Pricing Mood Board — Competition-Based Pricing

Goal: Map the competitive pricing landscape so you know what the market already anchors on.

Duration: 1-3 hours

What to do:

  1. Identify 5-8 competitors and alternatives from the user's competitive landscape (section 6 of my-gtm-context.md) plus any from Phase 2 competitor analysis (outputs/02-*). Include:

    • Direct competitors (similar product, similar customer)
    • Indirect competitors (different product, same problem)
    • Alternative solutions (spreadsheets, agencies, manual work, doing nothing)
  2. For each competitor, research and document:

    • Pricing page URL (if public)
    • Pricing model (subscription, usage-based, one-time, freemium, hybrid)
    • Value metric (what unit they charge for — seats, API calls, contacts, projects)
    • Tier structure (how many tiers, what differentiates them)
    • Entry price (lowest paid tier)
    • Mid-tier price (most popular or recommended tier)
    • Enterprise approach (custom pricing, sales-led, self-serve)
    • Free tier or trial (what is included, duration)
    • Notable pricing tactics (annual discount %, feature gating, usage limits)
  3. Build the Pricing Mood Board — a structured comparison table:

markdown
| Competitor | Model | Value Metric | Entry Price | Mid-Tier | Enterprise | Free Tier |
|-----------|-------|-------------|------------|---------|-----------|----------|
| [Name] | [Type] | [Unit] | $X/mo | $Y/mo | [Approach] | [Yes/No + details] |
  1. Analyze patterns:

    • What is the dominant pricing model in this market?
    • What value metrics are most common?
    • Where is the price floor and ceiling?
    • Are there gaps or whitespace in pricing (e.g., no one serves the $50-200/mo range)?
    • What pricing practices feel broken or frustrating to buyers?
  2. Surface key insight: Based on this landscape, what is the user's pricing freedom? Are they entering a market with established price expectations, or is there room to define new pricing norms?

Save to: outputs/05-pricing-mood-board.md

Important: If competitor pricing is not publicly available, note it and suggest how to gather it (ask prospects what they pay, check G2/Capterra reviews that mention pricing, look at archived pricing pages on Wayback Machine). Do not fabricate pricing data.


Task 2: Pricing Hypothesis & Value Metrics

Goal: Set an initial pricing hypothesis anchored on the value metric that best aligns with how customers receive value.

Duration: 1-3 hours

What to do:

  1. Define candidate value metrics. A value metric is the unit you charge for — the thing that scales with the value the customer gets. Good value metrics:

    • Scale with customer success (more usage = more value = more revenue)
    • Are easy for the customer to understand and predict
    • Are hard to game or circumvent
    • Differentiate you from competitors when possible

    Generate 3-5 candidate value metrics for the user's product. For each, assess:

    • Value alignment: Does more of this unit = more value for the customer?
    • Predictability: Can the customer estimate their cost before buying?
    • Scalability: Does this grow naturally as the customer grows?
    • Simplicity: Can you explain it in one sentence?
  2. Score and recommend a primary value metric. Use a simple matrix:

markdown
| Value Metric | Value Alignment | Predictability | Scalability | Simplicity | Score |
|-------------|----------------|---------------|------------|-----------|-------|
| Per seat | 4/5 | 5/5 | 3/5 | 5/5 | 17/20 |
| Per project | ... | ... | ... | ... | ... |
  1. Set a pricing hypothesis. Based on the mood board (Task 1) and value metric selection, propose:

    • Pricing model: Subscription, usage-based, one-time, hybrid
    • Value metric: The recommended unit
    • Preliminary price range: Low / mid / high based on competitive landscape
    • Tier structure hypothesis: How many tiers, what differentiates them
    • Rationale: Why this structure, grounded in the mood board data and ICP context
  2. Flag assumptions explicitly. Every pricing hypothesis carries assumptions. List them:

    • "We assume our ICP values [X feature] enough to pay [Y]"
    • "We assume the market will accept [pricing model] because [evidence]"
    • These assumptions become the test targets for Task 3 (WTP research).

Save to: outputs/05-pricing-hypothesis.md


Task 3: Willingness to Pay (WTP) Research

Goal: Validate (or invalidate) pricing assumptions with actual customer/prospect data using established research methods.

Duration: 1-3 days (research design + data collection + analysis)

What to do:

  1. Choose the right WTP research method:

    Van Westendorp Price Sensitivity Meter (recommended for most cases):

    • 4 questions asked to prospects/customers:
      1. At what price would this be so expensive you would not consider buying? (Too Expensive)
      2. At what price would this start to seem expensive but you would still consider it? (Expensive / High)
      3. At what price would this seem like a bargain — a great buy for the money? (Cheap / Good Value)
      4. At what price would this seem so cheap you would question its quality? (Too Cheap)
    • Plot the four curves. The intersections reveal:
      • Point of Marginal Cheapness (PMC): Too Cheap intersects Expensive
      • Point of Marginal Expensiveness (PME): Too Expensive intersects Cheap
      • Indifference Price Point (IDP): Expensive intersects Cheap (the "normal" price)
      • Optimal Price Point (OPP): Too Expensive intersects Too Cheap
    • Acceptable price range: PMC to PME
    • Best for: new products, early-stage pricing, broad exploration

    Gabor-Granger Method (better for optimizing existing pricing):

    • Show the product at a specific price, ask: "Would you buy at this price?"
    • If yes, increase price; if no, decrease price
    • Map the demand curve to find the revenue-maximizing price
    • Best for: products with existing pricing, price optimization, simple decisions
  2. Design the research.

    • Sample size: Minimum 30 responses for directional data, 100+ for statistical confidence
    • Who to ask: Ideally validated ICP (from Phase 3). At minimum, people who match the target profile
    • How to ask: Survey (Typeform, Google Forms), embedded in customer interviews, or as part of sales conversations
    • Provide a ready-to-use survey template the user can copy
  3. Provide the analysis framework. Create a template for processing results:

    • How to plot the Van Westendorp curves (can be done in a spreadsheet)
    • How to interpret the intersections
    • How to segment results by customer type (if sample is large enough)
    • What to do if results contradict the hypothesis from Task 2
  4. If the user cannot run WTP research right now: Provide a lightweight alternative:

    • Use pricing conversations from sales calls or customer interviews
    • Reference competitor pricing data from Task 1 as a proxy
    • Propose a "launch and learn" approach with pricing experiments
    • Be clear this is lower confidence than proper WTP research

Save to: outputs/05-wtp-research.md


Task 4: Business Model v01

Goal: Create the first version of a financial model that maps revenue to costs and validates the business is viable at the proposed pricing.

Duration: 1-3 days

What to do:

  1. Map revenue streams. Based on the pricing hypothesis (Task 2) and WTP data (Task 3):

    • Primary revenue stream (the core product/service)
    • Secondary revenue streams (add-ons, professional services, training, etc.)
    • For each: pricing model, price point, expected volume
  2. Map cost structure:

    • Fixed costs: Salaries, rent, tools/software, infrastructure
    • Variable costs: COGS per customer, hosting per user, support costs
    • Customer acquisition costs (CAC): Marketing spend + sales costs / new customers
    • Categorize: which costs scale with customers, which are fixed
  3. Calculate unit economics:

    • CAC (Customer Acquisition Cost): Total sales + marketing cost / new customers acquired
    • LTV (Lifetime Value): Average revenue per customer x average customer lifetime (or ARPU / churn rate)
    • LTV:CAC ratio: Target 3:1 or better for healthy SaaS; varies by model
    • Payback period: CAC / monthly gross profit per customer — how many months to recover acquisition cost
    • Gross margin: (Revenue - COGS) / Revenue
  4. Build a simple financial projection. A 12-month model showing:

    • Monthly recurring revenue (or equivalent for non-subscription)
    • Customer growth assumptions
    • Cost growth assumptions
    • Path to break-even or target milestone
    • Key sensitivity: what happens if price is 20% lower? If churn is 2x?
  5. Validate viability. Answer:

    • Can you acquire customers profitably at this price?
    • Does the unit economics work at scale?
    • What is the minimum viable number of customers to sustain the business?
    • Where are the biggest financial risks?

Save to: outputs/05-business-model.md

Note for services businesses: Unit economics look different. Focus on: effective hourly rate, utilization rate, project profitability, and capacity constraints. The same framework applies, but the metrics shift.


Show full SKILL.md (1,125 more words)Show less
Task 5: Craft Your Offers

Goal: Package the product or service into clear, compelling offers that make the buying decision easy for the ICP.

Duration: 1-3 hours

What to do:

  1. Distinguish product from offer. The product is what you built. The offer is how you present and package it to make it irresistible. A great offer includes:

    • The core deliverable (what they get)
    • Bonuses or extras (what makes it feel generous)
    • Guarantees or risk reversal (what removes fear)
    • Urgency or scarcity (what motivates action — use ethically)
    • Clear outcome framing (what result they can expect)
  2. Design tiered offers (if applicable). For each tier:

    • Name: Something that signals the audience (e.g., Starter, Growth, Enterprise — not Bronze, Silver, Gold)
    • Who it is for: Which customer segment or use case
    • What is included: Features, limits, support level
    • What is excluded: What creates the upgrade incentive
    • Price: From the pricing hypothesis, adjusted by WTP data
    • Value framing: How the price relates to the value delivered
  3. Apply offer design principles:

    • Anchoring: Present the highest tier first (or a "compare" view) so mid-tier feels reasonable
    • Decoy effect: If using 3 tiers, the middle tier should be the most attractive relative to its price
    • Feature gating vs. usage gating: Which is less frustrating for your ICP?
    • Annual vs. monthly: Standard is 15-20% discount for annual commitment
    • Guarantee: What is appropriate? Money-back, results-based, trial period?
  4. For services businesses specifically:

    • Productize where possible: Turn recurring service work into defined packages with clear scope and price
    • Bundle strategically: Combine related services into packages that are easier to buy than individual line items
    • Name your methodology: If you have a repeatable process, name it — it becomes proprietary and harder to comparison-shop
  5. Write the offer copy for each tier — the actual text that would appear on a pricing page or proposal. Keep it sharp: name, price, 4-6 bullet points of what is included, and one line on who it is for.

Save to: outputs/05-offers.md


Task 6: Pricing Workshop

Goal: Make a pricing decision with your team (or solo) using a structured process, and document the rationale.

Duration: 1-3 hours

What to do:

  1. Prepare the workshop input. Gather all evidence from Tasks 1-5:

    • Competitive pricing landscape (Task 1)
    • Value metric and pricing hypothesis (Task 2)
    • WTP research results or proxy data (Task 3)
    • Business model viability (Task 4)
    • Offer packaging (Task 5)
  2. Run the pricing decision framework. Work through each decision point:

    Decision 1 — Pricing model: Subscription / usage-based / one-time / hybrid

    • What does the evidence support?
    • What does the team believe?
    • Decision + rationale

    Decision 2 — Value metric: What unit do you charge for?

    • Evidence from Task 2 scoring
    • Team input
    • Decision + rationale

    Decision 3 — Price point: Specific numbers for each tier/offer

    • WTP range from Task 3
    • Competitive position (cheaper, parity, premium)
    • Unit economics validation from Task 4
    • Decision + rationale

    Decision 4 — Tier structure: How many tiers, what differs

    • Offer design from Task 5
    • Decision + rationale

    Decision 5 — Launch pricing tactics:

    • Introductory pricing or early-bird discounts?
    • Grandfathering policy for early customers?
    • Free tier or trial structure?
    • Decision + rationale
  3. Apply pricing psychology (use ethically):

    • Charm pricing: $99 vs. $100 (works for consumer, less for enterprise)
    • Anchoring: What is the reference point you want buyers to compare against?
    • Price-quality signal: Is your price consistent with the quality perception you want?
    • Decoy pricing: If 3 tiers, is the middle tier clearly the best deal?
    • Loss framing: "Save $X/year" vs. "Pay $X/month"
  4. Document the final pricing decision:

markdown
## Pricing Decision Record

**Date:** [Date]
**Participants:** [Who was involved]

### Decisions
| Element | Decision | Rationale | Confidence |
|---------|----------|-----------|-----------|
| Model | [Type] | [Why] | High/Med/Low |
| Value Metric | [Unit] | [Why] | High/Med/Low |
| Entry Price | $[X]/[period] | [Why] | High/Med/Low |
| Mid-Tier | $[X]/[period] | [Why] | High/Med/Low |
| Enterprise | [Approach] | [Why] | High/Med/Low |

### Assumptions to Monitor
- [List key assumptions that could invalidate these decisions]

### First Review Date
- [Date — see Task 7]

Save to: outputs/05-pricing-workshop.md

If the user is a solo founder: Run this as a structured self-exercise. The framework is the same — the "workshop" is the structured decision process, not the number of people in the room.


Task 7: Pricing Review Schedule

Goal: Set up a recurring pricing review process so pricing stays aligned with market reality as the business evolves.

Duration: Less than 1 hour

What to do:

  1. Set the review cadence. Recommended:

    • First review: 3 months after launch (you will have real data by then)
    • Ongoing reviews: Every 6 months for established products, every 3 months for early-stage
    • Trigger-based reviews: Regardless of schedule, review pricing when specific signals appear
  2. Define review triggers — events that should prompt an immediate pricing review:

    • Win rate drops below [X]% (you may be too expensive)
    • Win rate exceeds [X]% (you may be too cheap)
    • A major competitor changes pricing
    • You ship a significant new feature or capability
    • Customer segment mix shifts (e.g., moving upmarket)
    • Churn exit interviews cite pricing as top-3 reason
    • CAC or COGS changes significantly
    • You hit a new ARR milestone (pricing that works at $100K ARR may not at $1M)
  3. Define what to review each cycle:

    • Are we still competitive? (Quick mood board refresh — Task 1)
    • Does the value metric still match how customers get value?
    • What does the churn and expansion data say about pricing?
    • Are there new customer segments we should price differently for?
    • Has our cost structure changed enough to affect margins?
  4. Create the review checklist:

markdown
## Pricing Review Checklist

**Review date:** [Date]
**Last review:** [Date]

### Data to Gather Before Review
- [ ] Current win rate by tier
- [ ] Churn rate by tier and stated reasons
- [ ] Expansion revenue (upgrades, add-ons)
- [ ] Competitive pricing changes since last review
- [ ] New features shipped since last review
- [ ] Customer feedback mentioning pricing (support, sales, NPS)
- [ ] Unit economics update (CAC, LTV, margins)

### Questions to Answer
- [ ] Is our pricing still aligned with the value we deliver?
- [ ] Are we leaving money on the table? Evidence?
- [ ] Are we losing deals on price? Evidence?
- [ ] Should we add, remove, or restructure tiers?
- [ ] Any new packaging opportunities (add-ons, bundles)?

### Decision
- [ ] No change needed — rationale: ___
- [ ] Minor adjustment — what and why: ___
- [ ] Major restructure needed — trigger Task 1-6 refresh

Save to: outputs/05-pricing-review-schedule.md


Summary

Phase 5 takes you from "we need to figure out pricing" to a documented, evidence-backed pricing strategy:

TaskOutputYou Now Have
1. Pricing Mood Board05-pricing-mood-board.mdCompetitive pricing landscape mapped
2. Pricing Hypothesis05-pricing-hypothesis.mdValue metric selected, initial pricing structure
3. WTP Research05-wtp-research.mdCustomer-validated price range
4. Business Model05-business-model.mdUnit economics and financial viability confirmed
5. Craft Offers05-offers.mdPackaged, compelling offers ready to present
6. Pricing Workshop05-pricing-workshop.mdFinal pricing decision with documented rationale
7. Review Schedule05-pricing-review-schedule.mdRecurring process to keep pricing current

What this unlocks: With pricing decided, you are ready for Phase 6 (crafting-positioning) — where you build your market position, messaging, and visual identity. Pricing directly informs positioning: where you price signals where you compete.


Go Deeper

  • Van Westendorp methodology: The original Price Sensitivity Meter paper by Peter Van Westendorp (1976). Still the gold standard for early-stage WTP research.
  • Gabor-Granger technique: Andre Gabor and Clive Granger's demand curve method. Better for optimizing existing prices than exploring new markets.
  • Monetizing Innovation by Madhavan Ramanujam (Simon-Kucher): The best modern book on pricing for tech products. Covers willingness-to-pay research, value metrics, and the 9 pricing models.
  • Obviously Awesome by April Dunford: Chapters on pricing as a positioning signal — how price communicates where you compete.
  • The Strategy & Tactics of Pricing by Nagle & Muller: The academic reference. Dense but comprehensive on price elasticity, segmentation, and competitive pricing.
  • Price Intelligently (now Paddle) blog: Practical SaaS pricing research with real data on value metrics, feature differentiation, and willingness to pay.
  • Maja Voje's GTM Strategist methodology: This skill is Phase 5 of 12. The pricing framework integrates with validated customer insights (Phase 3) and product clarity (Phase 4) to ensure pricing is grounded in evidence, not guesswork.

GTM Strategist methodology by Maja Voje. https://gtmstrategist.com

© GTM-Strategist, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/setting-pricing of GTM-Strategist/gtm-strategist-skills.

Open the folder on GitHubat commit a5ead26

Compare with similar skills

Setting Pricing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Setting Pricing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Setting Pricing this skillGTM-Strategist/gtm-strategist-skills264—~5.4kAutomated safety check: PassMIT
Finance-Based Pricing Advisordeanpeters/Product-Manager-Skills7.2k1 repos~5.9kAutomated safety check: PassCustom licence
Monetization Strategyphuryn/pm-skills27k—~1.7kAutomated safety check: PassMIT
Lean Startupgetagentseal/founder-playbook729—~4.6kAutomated safety check: PassMIT
Pricing Strategyemotixco/claude-skills-founder540—~774Automated safety check: PassMIT
Price Optimization Toolnexscope-ai/eCommerce-Skills1.1k—~3.3kAutomated safety check: PassMIT

Similar skills

  • Finance-Based Pricing Advisor

    deanpeters/Product-Manager-Skills

    Evaluates a proposed pricing change by modeling its effect on ARPU, conversion, churn risk, expansion and CAC payback, for a go or no-go decision.

    7.2k GitHub starsUsed in 1 repo~5.9k tokens
    Business, Finance & HRAuto-check passed
  • Monetization Strategy

    phuryn/pm-skills

    Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.

    27k GitHub stars~1.7k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Lean Startup

    getagentseal/founder-playbook

    Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.

    729 GitHub stars~4.6k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Pricing Strategy

    emotixco/claude-skills-founder

    Design pricing for a product. An agent skill from emotixco/claude-skills-founder.

    540 GitHub stars~774 tokensUpdated 3 days ago
    Business, Finance & HRAuto-check passed
  • Price Optimization Tool

    nexscope-ai/eCommerce-Skills

    Evaluate ecommerce price candidates using unit economics, historical observations, elasticity analysis, scenario modeling, and controlled experiments.

    1.1k GitHub stars~3.3k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Ops Business Model Canvas

    asgard-ai-platform/skills

    Apply the Business Model Canvas (BMC) to map and evaluate business models across nine building blocks.

    242 GitHub stars~1.2k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed

More from GTM-Strategist/gtm-strategist-skills

All 12 skills in this repo
  • Crafting Positioning

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to position their product in the market, craft messaging, define their UVP/USP, or build a visual identity.

    264 GitHub stars~5.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Validating Customers

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to validate their customer assumptions, test their ICP, design experiments, or create customer personas from evidence.

    264 GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Building Communication Engine

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to choose marketing channels, plan their launch newsletter, set a GTM budget, collect social proof, or build their communication strategy.

    264 GitHub stars~2.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Collecting Intelligence

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user wants to research competitors, plan customer interviews, conduct market research, or understand their competitive landscape.

    264 GitHub stars~4.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Executing Launch

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user is preparing to launch, wants to set up a war room, build a launch support network, write launch emails, or plan launch day activities.

    264 GitHub stars~4.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Preparing Launch Assets

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user needs to build launch assets like a website, pitch deck, press release, product demo, or media kit.

    264 GitHub stars~5k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Setting Pricing

What does Setting Pricing do?

A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design. Setting Pricing is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.

When should I use Setting Pricing?

Setting Pricing fits situations like: the user asks about pricing strategy; how to price their product; willingness-to-pay research; business model design.

How do I install Setting Pricing in Claude Code?

Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill setting-pricing -a claude-code`. Or copy the skill folder (.claude/skills/setting-pricing in GTM-Strategist/gtm-strategist-skills) into .claude/skills/setting-pricing in your project. Claude Code loads it when a task matches its description.

How do I install Setting Pricing in Codex?

Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill setting-pricing -a codex`. Or copy the skill folder (.claude/skills/setting-pricing in GTM-Strategist/gtm-strategist-skills) into .agents/skills/setting-pricing in your project. Codex loads it when a task matches its description.

Can I use Setting Pricing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GTM-Strategist/gtm-strategist-skills --skill setting-pricing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-pricing, .gemini/skills/setting-pricing, .github/skills/setting-pricing and .opencode/skills/setting-pricing in your project.

What does Setting Pricing need to run?

SKILL.md names no scripts, command-line tools or credentials: Setting Pricing is instructions for the agent only.

Does Setting Pricing access the network?

SKILL.md names 1 domain. As links in the text: gtmstrategist.com. This is read from the text; nothing was executed.

Is Setting Pricing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Setting Pricing use?

Setting Pricing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setting Pricing use?

About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Setting Pricing?

Skills that share tags, products or a category with Setting Pricing: Finance-Based Pricing Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Monetization Strategy (phuryn/pm-skills, 27k stars), Lean Startup (getagentseal/founder-playbook, 729 stars) and Pricing Strategy (emotixco/claude-skills-founder, 540 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setting Pricing?

GTM-Strategist (a GitHub organization) maintains it in GTM-Strategist/gtm-strategist-skills, which has 264 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 7, 2026.

Source: GTM-Strategist/gtm-strategist-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.