agentleFS
JakeschincariolJakeschincariol/whale-skill/pricing/SKILL.md

pricing

Skill15 starsChanged 6 days agoMITView on GitHub

Pricing. Sets the price from what they pay today. Takes the money already leaving their account for this problem, works out the year, and gives three prices with what each one leaves them, or checks a price you already have in mind, with the working shown so it can be argued with. Then puts the chosen price on the deal. Use when the user says "what should I charge", "pricing", "how much is this worth", "set the price", "founding price", "am I charging too little", or before writing an offer.

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grow-sustainably, processize 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.
  • slavingiaSkill

    grow-sustainably

    Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.

    Also in 7 projects that use this

  • slavingiaSkill

    processize

    Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.

    Also in 7 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 14 projects that use this

  • +6 more from Cesarjoquin
  • +1 more from slavingia

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 7

    Distinctive

    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. Distinctive:

    Don't price from your costs, and don't price from a competitor's page.

    line 14
  2. Distinctive:

    Full value, 50%: When you're certain of the problem and they've seen the demo.

    line 31
  3. Very specific:

    If the user has a price in mind, price.py check.

    line 38
  4. Distinctive:

    Your costs still matter: Before you commit, check it pays for the build and whatever it costs to run for those 12 months.

    line 49
  5. Distinctive:

    Never sets a price with no number behind it, and never invents what a company pays.

    line 59
  6. Distinctive:

    Never promises the saving.

    line 60
  7. Distinctive:

    Never changes a price after payment.

    line 61
  8. Distinctive:

    Never invent a number, a result, a client or a deadline.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 53 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

Don't price from your costs, and don't price from a competitor's page. Price from what the buyer already pays to have this problem. It's the only number they can't argue with, because it's theirs.

${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).

python3 "${CLAUDE_SKILL_DIR}/price.py" options --pay-month 6400
python3 "${CLAUDE_SKILL_DIR}/price.py" check --pay-month 6400 --price 24000
python3 "${CLAUDE_SKILL_DIR}/price.py" set --deal north-pier --price 24000

--months changes the term (default 12).

The three prices

  • Easy yes, 25% of what they pay now. Quick to say yes to. Good when you need the first customer more than the money.
  • Founding price, about 33%. The default: a real saving for them, real money for you, and a reason to be early.
  • Full value, 50%. When you're certain of the problem and they've seen the demo.

Steps

  1. Get the number. Use what they told you, then the board (spend_month), then the market research. No number, no price: go back to /market-researcher or ask them.
  2. price.py options. Read the three to the user with the working: what they pay, what they'd pay, what they keep.
  3. If the user has a price in mind, price.py check. It says what share that is, and warns when it's high for something unfinished, or so low it reads as a toy.
  4. Agree the number with the user. It's their call: the tool shows the working, the user decides.
  5. price.py set. /offer-builder and /pre-sale link read it from the deal. A price can't change after they've paid.

Things to think through

  • What "founding" means. Say what they get for being first: this price, and a say in what gets built. If the price really won't last, name the real date. If it will, don't pretend.
  • Size. A bigger company paying more for this problem pays a bigger founding price, from the same share of its own number.
  • Annual, up front. A year up front is the point of a pre-sale. If that's hard for them, a deposit beats a discount (/pre-sale record --deposit).
  • Your costs still matter. Before you commit, check it pays for the build and whatever it costs to run for those 12 months. Stripe also takes its fee.
  • Don't cut the price to win. Change what they get instead.

Example from the reel

North Pier pays $6,400 a month, $76,800 a year. Options: $19,000 (25%), $26,000 (34%), $38,000 (49%). The reel's price: check --price 24000 says 31% of what they pay today, and they keep $52,800. (Illustrative: North Pier and every figure are fictional.)

What it never does

  • Never sets a price with no number behind it, and never invents what a company pays.
  • Never promises the saving. "They keep $52,800" is arithmetic on their current bill, not a guarantee of what they'll save.
  • Never changes a price after payment.

Consent and truth

  • Nothing is sent or charged without the user's explicit yes. This skill only does the arithmetic and writes the price on the deal.
  • Never invent a number, a result, a client or a deadline. Fill in only what is true and ask when something is missing.
  • Pricing here is a starting point, not financial advice.

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.