agentleFS
checkout-pagecheckout-page/ecommerce-skills/skills/pricing/SKILL.md

pricing

Skill5 starsChanged 36 days agoMITView on GitHub

Use when setting or reviewing the full price of a product, plan, or add-on for an online store — e.g. "should this be $199, $200, or $197.50", "what should the add-on cost", "should we do a flat rate or pay per use", "where should the price go on the page", "how should I price this for a Japanese audience".

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 9 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

  • +5 more from Cesarjoquin
  • +1 more from slavingia

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 2

    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:

    Upgrades: if you want people to step up to a dearer option, keep both prices on the same left digit ($40.50 → $48.50, not $39.99 → $48.50).

    line 42
  2. Distinctive:

    Keep components simple: when you must price separately: rounded amounts ($0.10/min, not $0.07), the same ending across components, no …

    line 45

“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

Choose the digits, structure, and placement of a full price so it sends the signal you want. The last digits of a price tell people whether to think about quality or about cost, complex prices get read as expensive, and where the price sits on the page changes how big it feels.

When to use

  • Deciding whether a price should be rounded ($200), just-below ($199), or precise ($203)
  • Pricing add-ons, upgrades, and per-unit components
  • Choosing flat-rate vs pay-per-use
  • Placing and coloring prices on a product page
  • Setting an opening price for a negotiation or auction

When not to use

  • Working out how much people will pay → the price-research skill
  • Wording a sale or coupon → the discounts skill

Inputs

Collect, or state your assumption:

  • Product, candidate price, currency
  • What the buyer is optimizing for (quality/risk vs price); brand positioning (premium vs value)
  • Whether this is a promotion price or the everyday price
  • Whether the price will be negotiated, and whether the counterparty is an expert
  • Market (Japan/China change the lucky ending)
  • Audience gender mix, if known

Classify the product first. Hedonic = bought for enjoyment, pleasure, or the experience (chocolate, fashion, decor, travel, spa, perfume). Utilitarian = bought to do a job, judged on function and value (detergent, appliances, insect repellent, tools, accounting software). If it's mixed, decide by what the buyer is optimizing for at the moment of purchase.

Procedure

  1. Default to rounded ($80, $200, $35) when the decision runs on feeling or quality: premium or luxury goods, hedonic products, most services, a premium brand image, or when you want an effortless choice. Note the boundary: the roundedness study found non-rounded prices did better when buyers evaluate analytically (typical utilitarian purchases) — for those, rounded earns its place only as a low-price-image avoidance (a 99-ending signals bargain) or for simplicity, not from that study. The risky-purchase examples (medical, safety) are a practitioner extension. † Also when the price may be bid up (a hot auction, tight housing market). When in doubt, round.
  2. Use just-below ($199, $4.99) only when the left digit actually drops relative to the price you'd otherwise charge ($2.99 instead of $3.00 works; $3.49 instead of $3.50 doesn't) and one of these holds: it's a promotion price; buyers are price-focused; you want a low-price image; the item is cheap and low-risk. Lower left digits (1, 4) feel like bigger savings than high ones (7).
    • Four figures or more (common in ¥, ₹, ₺): repeat a low digit in the last three places instead — ¥2,111 beats ¥1,999. †
    • Japan and China: an 8 ending is the convention (prevalence evidence, not a measured lift), not 9.
    • Upgrades: if you want people to step up to a dearer option, keep both prices on the same left digit ($40.50 → $48.50, not $39.99 → $48.50).
  3. Use precise ($2,865; $53,832/month) when you need to signal expertise and calculation in a big decision (B2B quotes, renovations) or when the buyer will negotiate down: precise anchors pull counteroffers into smaller steps, so you get fewer but higher offers. With expert buyers, stay moderately precise ($23,750, not $23,721.85) or justify the number with a cost breakdown. Evidence for precise as a "slightly above rounded" everyday price is weaker than for just-below.
  4. Prefer a flat rate that covers what most customers want ($50/month, all-in; unlimited revisions), priced above the pay-per-use equivalent — a $6,000 fixed fee beat $50/h × 100 h. Keep pay-per-use only as a low-commitment entry tier.
  5. Keep components simple when you must price separately: rounded amounts ($0.10/min, not $0.07), the same ending across components, no service charge tacked on, options easy to compare side by side. Add-ons follow the same rule ($15, not $12.35).
  6. Place the price below the product image, not above; the same price reads lower.
  7. Color: mostly male audience and a routine, low-scrutiny purchase → every price in red; the effect disappears for expensive or important purchases. Mixed red and black backfires. Audience unknown or mixed → black.
  8. Hand off: sale prices → discounts; validating the level → price-research.

Output

ItemValue
Recommended price$200
Digit styleRounded — premium hedonic product, quality is the decision driver
Add-ons / componentsMonogramming $15 (rounded, same ending as core price)
StructureFlat rate / pay-per-use / n.a.
Placement & colorPrice below the product image; black (mixed audience)
Alternatives rejected$199 (just-below reads as price-led; save for promotions), $197.50 (precision signals nothing here)

Common mistakes

  • Picking $195 or $225 "for confidence" with no rule — the choice is rounded because quality is the driver; state the reason.
  • Using $9.99 everywhere by habit — just-below cues price-focus and undermines a premium image; use it for promotions and price-led categories.
  • $1,999 in a four-figure currency — the just-below effect is overridden; use ¥2,111-style low repeating digits.
  • Setting the upgrade tier across a left-digit boundary ($39.99 vs $48.50) when you want people to upgrade.
  • Underpricing the flat rate to match pay-per-use — people will pay a premium for the cap on spend.
  • Fiddly component prices ($4.61/GB plus a $6 fee) — people assume you're the expensive option without calculating.

Quick reference

SituationDigits
Premium, hedonic, risky, service, unsureRounded
Promotion, price-led, cheap and low-riskJust-below (left digit must drop)
Four-figure pricesLow repeating last digits (2,111)
Japan / China8 ending
Want upgradesSame left digit on both tiers
B2B quote, negotiated downPrecise; moderate with experts
Bid up (auction)Rounded
Usage-based serviceFlat rate, priced above pay-per-use
Components / add-onsRounded, same endings, no service fee
Page layoutPrice below the product
Mostly male audience, routine purchaseAll prices red

† No primary citation on file for this rule — a practitioner tip, not a measured finding.

Evidence and effect sizes: see reference.md.

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.