agentleFS
Sign inStart free
JakeschincariolJakeschincariol/founder-skill/skills/founder-pricing/SKILL.md

founder-pricing

Skill131 starsChanged 37 days agoMITView on GitHub

Finds the price buyers will actually pay. Reads the consumer panel's four price answers per buyer into a Van Westendorp price-sensitivity range (too cheap, a bargain, getting expensive, too expensive), sets it against what competitors really charge and against the CFO's margin, and recommends a price, a price ladder (good / better / best) and an opening offer to test. Use when the user says "how much should I charge", "price this", "is $X too expensive", "pricing strategy", "what price", or after the consumer panel.

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 /founder-consumer ran, every buyer answered four price questions.

    line 28
  2. Distinctive:

    Never price below variable cost to "buy" customers without saying so, and how long the CFO says the business can afford it.

    line 78
  3. Distinctive:

    No fake anchors: no "was $X" price that was never charged.

    line 80

≈ “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

founder-pricing

Price is the fastest lever on the margin and the one founders guess most. This skill sets it from three things you can check: what buyers said, what competitors charge, and what the business needs to earn.

Tool in this folder:

python3 "${CLAUDE_SKILL_DIR}/van_westendorp.py" founder/panel/answers --price 6.50 --out founder/pricing-curve.md

Step 1: what buyers said

If /founder-consumer ran, every buyer answered four price questions. Run the tool on founder/panel/answers (or a CSV with the columns too_cheap, cheap, expensive, too_expensive from real surveys, which beat simulated answers every time). It reports:

pointmeaning
PMCbelow this, too many think it is too cheap to be good
OPPthe price with the least resistance either way
IPPwhere as many call it a bargain as call it expensive
PMEabove this, too many will not buy at all

PMC to PME is the acceptable range. If the panel has not run, say so and offer to run /founder-consumer --quick first. Do not invent a range.

Step 2: what competitors charge

From founder/competitors.md (or look them up now, from their own public price pages, with links): the price of the nearest substitutes for the same job. Note what each price includes, so you compare like with like. A matcha latte is compared with other matcha lattes and with the coffee it replaces, not with a tea bag.

Step 3: what the business needs

From founder/numbers.json: the variable cost per unit and the break-even. Run the CFO's tool at two or three candidate prices to see the margin and break-even at each:

python3 "${CLAUDE_SKILL_DIR}/../founder-cfo/unit_economics.py" founder/numbers.json --price 7.00

Step 4: decide

Write founder/pricing.md:

  1. The price, and why: where it sits in the acceptable range, against the competitors, and the margin it gives (from the tool, not a guess).
  2. The ladder, if the business can have one: a good / better / best (size, bundle, subscription, membership) with a reason to step up each rung.
  3. The opening offer: an intro price or bonus for launch that does not train buyers to wait for discounts, with an end date.
  4. What to test with real buyers: two prices inside the range and how to test them (two landing pages, a pre-sale at each, A/B on the menu board).
  5. The panel's verbatim price objections (top three), so marketing can answer them.

Rules

  • Price answers from simulated buyers pick what to test. They are not proof.
  • Never price below variable cost to "buy" customers without saying so, and how long the CFO says the business can afford it.
  • No fake anchors: no "was $X" price that was never charged.

Output

founder/pricing-curve.md, founder/pricing.md. If the price changed, update founder/numbers.json and re-run /founder-cfo. Next: /founder-offer.

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.

Check your setup, free