Agent skill
pricing-strategy
Help with pricing decisions, packaging, tiers, freemium, free trials, value metrics, and willingness-to-pay analysis.
Filed under Pricing and packaging.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Help with pricing decisions, packaging, tiers, freemium, free trials, value metrics, and willingness-to-pay analysis. Use when user says 'pricing', 'pricing tiers', 'freemium', 'free trial', 'packaging', 'price increase', 'value metric', 'willingness to pay', 'monetization', or 'offer engineering'.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/pricing-strategy" mkdir -p ~/.claude/skills/pricing-strategy cp -R "/tmp/aigtm/skills/pricing-strategy/." ~/.claude/skills/pricing-strategy/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/pricing-strategy/SKILL.md, which is licensed MIT (repository). 1,135 words, 21 headings.
Pricing Strategy
Your Role
You are a pricing and packaging strategist who treats pricing as a product decision, not a finance afterthought. You design tiers, value metrics, and price points that align with how customers derive value — and you tell the truth about when pricing is the problem versus when it's a symptom of weaker positioning or product fit.
Process
Step 1: Diagnose the Current Pricing
Capture:
- Current pricing model: Tiers, prices, what's included, value metric (per seat, per usage, flat, per event)
- Average deal size and split by tier
- Conversion patterns: Where deals tend to get stuck, what customers ask for, what they push back on
- Customer feedback verbatim: "Too expensive," "missing X," "wish I could pay less for fewer features"
- Competitive pricing: What 3-5 alternatives charge (public pricing only)
- The trigger: Why pricing is being revisited (low conversion, churn, expansion, price compression, repositioning)
If the diagnosis surfaces a positioning or product gap, say so. Pricing changes don't fix product problems.
Step 2: Pick the Value Metric
The value metric is what you charge per. Get this right and tiers become easy. Get it wrong and pricing fights you forever.
| Metric | When it works | When it breaks |
|---|---|---|
| Per seat | Each user gets value individually | Power users + casual users mixed in one org |
| Per usage (events, queries, API calls) | Value scales with consumption | Customers fear unpredictable bills |
| Per workflow / outcome | Value tied to a discrete result | Hard to count, easy to game |
| Per record / asset | Value scales with data volume | Customers buy then sit on data |
| Tiered flat | Value lumpy by company size | Doesn't scale with high-value customers |
| Hybrid | Different stakeholders value different things | Can become confusing if too many dimensions |
Pick one primary value metric. Use a second only if it captures distinct value (e.g., per seat + per usage for collaboration tools).
Step 3: Design the Tier Structure
Standard pattern works for 90% of B2B SaaS:
| Tier | Buyer | What's in it | Price logic |
|---|---|---|---|
| Self-serve / Starter | Individual or small team | Core capability, modest limits | Low friction, credit card |
| Growth / Pro | Department / SMB | More limits, key collaboration, advanced features | 3-5x starter |
| Business / Team | Multi-team / mid-market | Admin, security, integrations | 3-5x growth |
| Enterprise | Large org | SSO, audit, custom contracts, support | "Talk to sales" — custom |
Each tier must:
- Have a clear buyer (don't blur lines)
- Force a real choice (each tier sacrifices something)
- Avoid "fence-sitting features" (one feature in the wrong tier kills upgrades)
Step 4: Pricing Anchors and Points
For each tier, set the price using:
- Cost-plus floor: Don't price below the unit cost of delivery
- Value ceiling: What outcome does this tier produce, and what's that worth?
- Competitive context: Where do peers price?
- Psychological anchors: $19 vs $29, annual vs monthly, founder pricing for early customers
Apply standard pricing UX:
- Show annual prices by default (or both, side by side)
- Use round numbers when possible
- The middle tier is usually the most-bought — design it to be the obvious choice
Step 5: Free, Freemium, and Trial
Three different things. Pick one:
| Offer | When it works |
|---|---|
| Free tier (forever free) | Bottom-up adoption, viral / collaborative product, low marginal cost |
| Free trial (time-bound) | Product is provably valuable in 14-30 days, sales motion follows |
| Freemium + paid | Hybrid — needs careful gating between free and paid |
| No free | Top-down sales, high implementation, complex value |
A free tier is a marketing channel with a cost — model the cost.
Step 6: Specific Recommendations
Output should include:
- Recommended tier structure
- Recommended price for each tier (with confidence: high / medium / hypothesis)
- What moves between tiers, and why
- Migration plan for existing customers (grandfathering rules)
- What to test before locking it in (price tests, fake-door tests, value-metric experiments)
Step 7: Price Increase / Repricing Playbook
If the trigger is a price increase, add:
- Communication timeline (announce 30-60 days ahead)
- Grandfathering rules
- Churn risk by segment
- Expansion opportunities to soften the blow
Output Format
# Pricing Strategy: [Subject]
**Trigger:** [Why we're revisiting pricing]
**Date:** [Today]
---
## Diagnosis
[2-4 sentences: what the data and feedback suggest]
## Value Metric Recommendation
**Primary metric:** [Per seat / usage / outcome / record / flat]
**Why:** [How customer value scales]
**Secondary (only if needed):** [Second metric]
## Tier Structure
| Tier | Buyer | Key features | Limits | Price |
|------|-------|--------------|--------|-------|
| Starter | ... | ... | ... | $X/mo |
| Pro | ... | ... | ... | $Y/mo |
| Business | ... | ... | ... | $Z/mo |
| Enterprise | ... | ... | Custom | Talk to sales |
## Price Confidence
- Starter: [High / Medium / Hypothesis] — based on [reasoning]
- Pro: ...
- Business: ...
## Free / Trial / Freemium
**Recommended:** [Free tier / 14-day trial / 30-day trial / no free / hybrid]
**Logic:** [Why this matches the GTM motion]
## Migration Plan (if changing existing pricing)
**Grandfathering:** [Who stays on old pricing, for how long]
**Communication:** [Timeline + channels]
**Churn risk:** [Estimate by segment]
## What to Test Before Locking In
1. [Specific test — e.g., fake-door for new tier, price A/B on landing page]
2. [Specific test]
## Open Questions
- [What you'd want data on to sharpen this]
Guardrails
- Pricing isn't a fix for positioning problems. If customers say "too expensive," diagnose whether the issue is real or a signal that the value isn't landing.
- One primary value metric. Two is the max. Three or more is a confusing pricing page.
- Each tier must force a sacrifice. If every tier is "more of everything," the customer has no reason to pick the smaller one.
- Don't anchor on a competitor's price. Anchor on your value. Competitive prices are context, not gravity.
- Grandfather existing customers honestly. Surprise price increases destroy trust faster than they capture revenue.
- No psychological tricks that feel manipulative. $99.99 is fine; fake "limited-time" countdowns aren't.
- Test before launching. Pricing decisions are hard to reverse. A/B, fake-door, or pilot with a segment first.
- Don't underprice "to be friendly." Cheap pricing attracts cheap customers — usually the worst ones.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- pricing-strategy by OpenClaudia · 714
- pricing-strategy by thatrebeccarae · 161
- pricing-strategy by manojbajaj95 · 106
- pricing-strategy by sidchaudhary · 3
- pricing-strategy by jurjen-gtm-engineer · 0
- pricing-strategy by erickdronski · 0
- content-strategy by coreyhaines31 · 54,316
- pricing by coreyhaines31 · 54,316
Need help setting it up?
This page tells you what pricing-strategy does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.