agentleFS
SkillMedevSkillMedev/solo-founder-stack/skills/pricing-strategy/SKILL.md

pricing-strategy

Skill0 starsChanged 38 days agoMITView on GitHub

Set or revise pricing for any product by triangulating value, competition, and cost floor into a recommended structure, price points, and a test plan. Use when someone asks "what should I charge", "how do I price my product", "are we priced too low", "should we go usage-based or flat", or is preparing a repricing or a new-product launch. Do NOT use for designing SaaS tier ladders, value metrics, and expansion packaging in detail - use saas-pricing instead; for gym front-end offers and guarantees use gym-pricing-and-guarantees; for checking whether the resulting price produces healthy CAC payback use unit-economics.

110 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 102 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If already selling: current price, win rate, and how often price objections actually come up.

    line 25
  2. Distinctive:

    Keep the entry point low-friction and create one clear reason to move up.

    line 48
  3. Distinctive:

    Keep price gaps between adjacent tiers around 2-2.5x.

    line 55
  4. Distinctive:

    Test new prices on new customers only.

    line 59
  5. Distinctive:

    Do not price from cost - cost is a floor check, and anchoring there guarantees leaving value uncaptured.

    line 80
  6. Distinctive:

    Do not copy a competitor's price without their positioning.

    line 81
  7. Distinctive:

    Do not present three structures and let the user choose - recommend one, with reasoning, plus what to test next.

    line 82
  8. Distinctive:

    Do not charge by a metric the customer wants to minimize.

    line 83
  9. Distinctive:

    Do not run a price test judged on signup conversion alone.

    line 84
  10. Distinctive:

    Every number is sourced or labeled a guess.

    line 89

“Common” is measured: kept by at least 6 in 10 of the 102 edited versions of this file we could read. “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

Price is positioning: it tells the market what the product is worth before anyone uses it. The costly mistake this skill prevents is defaulting to cost-plus or copying a competitor's number - pricing is usually the least-tested lever in the business, and underpricing quietly donates margin the founder never gets back. Anchor on the value delivered, then sanity-check against competition and cost.

Operating procedure

Work the steps in order. Value must be quantified before a structure makes sense, and the structure must be chosen before individual price points mean anything.

Step 1: Gather inputs

Collect these before recommending anything. Where the user cannot answer, apply the default and label the number a guess.

  1. Buyer segments: who buys, split by size, use case, or urgency. Default: assume two segments - a self-serve smaller buyer and a larger buyer with real budget.
  2. The measurable outcome per segment: hours saved, revenue gained, cost avoided, risk removed - in the customer's units, not the product's.
  3. What the realistic alternatives cost: direct competitors, a spreadsheet, a hire, or doing nothing.
  4. Variable cost to deliver one unit (this is only the floor input, never the anchor).
  5. The growth vector: does a customer's value grow through more people using it, more volume flowing through it, or more capability unlocked?
  6. If already selling: current price, win rate, and how often price objections actually come up.

Step 2: Quantify willingness to pay by segment

Quantify value in the customer's terms (time saved, revenue gained). "Saves each account manager 10 hours a month" times a loaded hourly cost is a dollar figure; "makes reporting easier" is not. Do this per segment - a freelancer and a 50-person agency capture different value from the same feature, and that difference is what tiers monetize later.

When value cannot be computed directly, run a Van Westendorp price-sensitivity survey on 15 or more real prospects (the four questions: at what price is this too cheap to trust, a bargain, getting expensive, too expensive). The acceptable price range sits between the marginal-cheapness and marginal-expensiveness crossings. Label survey-derived numbers as directional, not exact.

Step 3: Apply the three lenses

  • Value-based: the ceiling and the story. Rule of thumb: charge about one-tenth of the quantified value (the 10x value-to-price rule) so the customer keeps an obvious surplus; 10-25% of value captured is defensible when the value is provable and switching costs are real.
  • Competitive: what alternatives charge, and how the product is differentiated. If the value lens supports a price far above competitors and there is no differentiation story to carry it, that is a positioning problem, not a pricing one.
  • Cost-plus: the floor only - never price below sustainable margin, and never anchor on cost. Pricing on cost alone leaves value on the table by construction.

Step 4: Choose the structure to match the growth vector

Per-seat, usage-based, tiered, or flat - match how the customer perceives and grows value:

  • Value grows with headcount → per-seat. Simple to budget, but revenue caps with the customer's team size.
  • Value grows with volume → usage-based, with a predictability guardrail (committed tiers or caps) so finance can budget it.
  • Distinct willingness-to-pay segments → tiered; gate the features that matter to larger buyers, not the features that cost the most to build.
  • Value is flat regardless of scale → flat price; compete on simplicity.

Keep the entry point low-friction and create one clear reason to move up. If the recommendation is a multi-tier SaaS ladder, hand the detailed tier design, value metric, and expansion packaging to saas-pricing.

Step 5: Set the price points

  • B2B: round, confident numbers ($50, $200, $1,500). Odd charm prices ($49.99) read as consumer.
  • Consumer or self-serve prosumer: charm endings and a visible anchor ("$29, normally $49") pull weight.
  • Show the highest tier first or alongside - it anchors everything below as reasonable.
  • Keep price gaps between adjacent tiers around 2-2.5x; smaller gaps make upgrades feel pointless, larger ones feel like a cliff.

Step 6: Write the testing plan

  • Test new prices on new customers only; never surprise existing ones.
  • Watch the objection rate: if fewer than roughly 20% of deals raise any price objection, the product is underpriced - raise until some deals push back.
  • Judge a price test on close rate and 90-day retention together, not signup conversion alone; a cheaper price that attracts churny customers is a loss.
  • Recommend exactly one structure with the reasoning, plus the single next test.

Worked example: SaaS reporting tool for marketing agencies

  • Value quantified: each account manager spends ~10 hours/month building client reports; loaded cost $55/hour → $550/month of value per AM.
  • 10x rule → ~$55/AM/month ceiling zone; capture 10-25% → $55-$135 per AM is the defensible band.
  • Competitive lens: incumbent dashboards run $99-$299/month flat; most agencies use spreadsheets (cost: the 10 hours).
  • Cost floor: ~$6/account/month in infrastructure - irrelevant to the anchor, confirms huge margin room.
  • Growth vector: value grows with number of client accounts managed, not seats → tiered on client accounts.
  • Recommendation: Starter $59/month (5 client accounts), Agency $149/month (20 accounts, white-label reports gated here because larger agencies need them), Scale $349/month (unlimited, API). Round numbers, ~2.4x gaps, entry under the value of two saved hours.
  • Next test: raise Agency to $179 for new signups and watch objection rate and 90-day retention.

Deliverable

Produce a pricing recommendation containing: the quantified value per segment (with guesses labeled), the three-lens readout (ceiling, competitive band, floor), one recommended structure with the growth-vector reasoning, specific price points, and the single next price test with its success metric.

Do NOT

  • Do not price from cost - cost is a floor check, and anchoring there guarantees leaving value uncaptured.
  • Do not copy a competitor's price without their positioning; the number only works attached to their story.
  • Do not present three structures and let the user choose - recommend one, with reasoning, plus what to test next.
  • Do not charge by a metric the customer wants to minimize; it makes success feel like punishment.
  • Do not run a price test judged on signup conversion alone; cheap prices convert churn.

Quality bar

  • Value is expressed in the customer's units with a dollar translation, or explicitly labeled as unquantifiable with Van Westendorp as the fallback.
  • Every number is sourced or labeled a guess.
  • The recommended price sits inside the 10-25%-of-value band or the deviation is justified in writing.
  • The structure maps to a named growth vector.
  • A testing plan with one concrete next test is included.

Escalation

This is strategy, not financial advice on the business's viability. For SaaS tier ladders, value metrics, and net-revenue-retention packaging, route to saas-pricing. For gym offers, route to gym-pricing-and-guarantees. To verify the chosen price yields healthy CAC payback and LTV:CAC, route to unit-economics.

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.