agentleFS
patonkikhpatonkikh/APES/skills/growth/pricing-strategy-advisor/skill.md

pricing-strategy-advisor

Skill3 starsChanged 4 months agoMITView on GitHub

Recommend a pricing model and price points for AI/SaaS products: usage, seat, tier, and hybrid structures with unit economics. Use when pricing a new product, repricing, or designing AI consumption-based billing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If COGS unknown for AI product, estimate from ai/ai-cost-optimizer outputs or request model/token assumptions.

    line 34
  2. Distinctive:

    If margin negative at target price, recommend limit changes, model routing, or price increase — do not ignore COGS.

    line 82
  3. Distinctive:

    Use annual prepay to fund inference float.

    line 148

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Pricing Strategy Advisor

Purpose

Recommend a pricing model and structure: how customers pay, what drives the bill, tier boundaries, and unit economics sanity check for AI/SaaS products.

Input: Product type, ICP, cost structure (COGS per user/request), competitive pricing (optional), business goal (growth vs margin)
Output: Pricing Strategy Memo with model recommendation, tier table, unit economics worksheet, and rollout considerations
Examples: See examples.md for worked input/output.


Workflow

Step 1: Gather pricing inputs

InputWhy it matters
Value metricWhat customers pay for (seats, API calls, tokens, outcomes)
COGSInference cost, support, infra per unit
WTP signalsInterviews, competitor prices, pilot conversions
Sales motionSelf-serve vs enterprise affects packaging
Strategic goalLand grab vs profitability

If COGS unknown for AI product, estimate from ai/ai-cost-optimizer outputs or request model/token assumptions.

Step 2: Map pricing model options

ModelBest forRisk
Flat subscriptionPredictable SMB SaaSMisaligned if usage varies
Per seatCollaboration toolsSeat inflation, under-monetize power users
Usage / consumptionAI APIs, variable workloadBill shock, unpredictable revenue
Credits / packsHybrid AI productsComplexity in UX
Freemium + paid tiersPLGFree tier COGS bleed
Enterprise customHigh ACV, long cycleOpacity, slow deals

Score each option against ICP and COGS (1–5).

Step 3: Define value metric for AI products

Metric typeExampleWhen
Per request$/1k API callsDeveloper API
Per tokenInput/output pricedRaw LLM proxy
Per outcome$/resolved ticketAgent automation
Per seat + allowanceSeats + included AI creditsCopilot in SaaS
Per workspaceTeam bundleB2B collaboration

Pick one primary value metric; secondary metrics only for overage.

Step 4: Design tier structure

Typical 3-tier pattern:

TierAudienceLimitsPrice anchor
Free / StarterTrial, indieHard caps, watermark$0
ProCore ICPGenerous limitsMain revenue
Business / EnterpriseTeams, SSO, SLACustom / annualExpansion

Per tier define: limits, features gated, support level, contract terms.

Step 5: Unit economics check

LineCalculation
ARPUWeighted average revenue per paying user
Gross margin(ARPU - COGS) / ARPU
PaybackCAC / (ARPU * gross margin)
AI COGS %Inference cost / revenue — flag if >40% at scale

If margin negative at target price, recommend limit changes, model routing, or price increase — do not ignore COGS.

Step 6: Competitive and psychological pricing

  • Anchor against 2–3 comparables (not race to bottom)
  • Charm vs round pricing by segment (SMB vs enterprise)
  • Annual discount standard: 15–20% for cash flow
  • Grandfathering policy for existing users on change

Step 7: Rollout and experimentation plan

StepAction
Price testVan Westendorp or A/B on landing (see experiment-designer)
Packaging testFeature gates vs limit gates
MigrationCommunication for repricing
InstrumentationTrack conversion by tier in analytics

Step 8: Validate

Run Validation checklist.


Decision Rules

ConditionAction
COGS unknownStop; require cost model before usage-based pricing
Negative margin at proposed priceRevise tiers or limits before launch
Enterprise only, no self-serveSkip freemium; focus annual contracts
Commodity LLM wrapperWarn on compression risk; differentiate on outcome pricing
Heavy AI usage variancePrefer consumption + caps over pure seat
Regulatory billing rulesNote jurisdiction; do not invent legal advice

Validation

  • Value metric identified and justified for ICP
  • ≥2 pricing models compared with scores
  • Tier table with limits and feature gates
  • Unit economics worksheet with gross margin estimate
  • AI COGS line item explicit for AI products
  • Competitive reference points cited
  • Rollout / experiment plan for price validation
  • Grandfathering and migration notes if repricing

Anti-patterns

  • Cost-plus only — ignores willingness to pay and value.
  • Copy competitor price — no wedge or COGS fit.
  • Unlimited free AI tier — COGS death spiral.
  • Too many tiers — decision paralysis (max 4 public tiers).
  • Hidden overage — destroys trust; disclose limits clearly.

Best Practices

  • Price on outcome when you can measure it reliably.
  • Show ROI calculator for enterprise buyers.
  • Pair with ai/ai-cost-optimizer to keep margins as models change.
  • Revisit pricing when model costs drop 30%+ (AI market shifts).
  • Use annual prepay to fund inference float.

Output Structure

# Pricing Strategy: [Product Name]

## Context
[ICP, motion, strategic goal]

## Model recommendation
[Primary model + rationale]

## Value metric
[What drives the bill]

## Tier table
| Tier | Price | Limits | Features |
|------|-------|--------|----------|

## Unit economics
| Metric | Value |
|--------|-------|

## Competitive context
[Comparables]

## Rollout plan
[Tests, migration, instrumentation]

## Risks
[Margin, competition, bill shock]

Next Skills

OutcomeRecommended Skill
Launch with GTMgrowth/go-to-market-planner
A/B test price pointsgrowth/experiment-designer
Reduce inference COGSai/ai-cost-optimizer
Competitive price contextproduct/competitive-analysis
Track conversion eventsproduct/analytics-instrumentation-planner

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.