agentleFS
checkout-pagecheckout-page/ecommerce-skills/skills/raise-prices/SKILL.md

raise-prices

Skill5 starsChanged 36 days agoMITView on GitHub

Use when someone wants to charge more without losing sales — "raise prices", "charge more", "customers say we look cheap", "move upmarket", "will a higher price hold", "justify a higher price", "competitors charge more than us" — for any product or plan sold online.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Simple components, same ending: Add-ons and plans rounded like the main price.

    line 40
  2. Very specific:

    Announcing the increase: If you pre-announce it, compute the percentage against the old price so the honest number is the larger one.

    line 42

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

Raise prices

Turn "we're at $9.99 and want $14" into a ranked backlog of what must change on the product and the page for the higher price to hold. Willingness to pay is moved by how the price is written, the unit, what the buyer sees, and which quality signals are present — not by the number alone. Leave the how-to and the papers in the Depth skills. Do not forecast the user's sales at the new price.

When to use

  • The user wants a higher price and asks how to make it stick
  • Customers or the founder call the product "cheap-looking"
  • A price above the category norm needs justification

When not to use

  • Working out what the price should be → price-research
  • Wording a markdown → discounts; more buyers at the current price → increase-conversion

Inputs

Collect, or state your assumption:

  • Product, current price, target price, competitor range, currency
  • Company size; whether the product is high-tech
  • Branded ingredient or component; real sustainability practice
  • How quantity is expressed now, and what one "use" is
  • Current media, copy, price position, add-on and plan prices

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

Walk each check; include applicable levers the user didn't mention; list the rest as considered.

The number

  1. Rounded list price. Just-below only for a promotion price. One move vs stages isn't tested; a single move is the practitioner default. † Depth: pricing.
  2. Simple components, same ending. Add-ons and plans rounded like the main price. Depth: pricing.
  3. Flat rate above pay-per-use where usage varies. Depth: pricing, subscription-pricing.
  4. Announcing the increase. If you pre-announce it, compute the percentage against the old price so the honest number is the larger one. Existing subscribers usually need advance notice. Depth: discounts.
  5. Validate the level with price-research if the target is a guess.

The unit and the words

  1. Concrete units (applications, washes, days), smaller unit for precision. Depth: product-copy.
  2. Branded ingredient in the headline. † Depth: product-copy.
  3. Register by product type. Science/effectiveness language only if utilitarian. † Depth: product-copy.
  4. Three best claims, plain words. Depth: product-copy.

What the buyer sees

  1. Media by type. Hedonic → video; utilitarian → stills. Hand, shine, multiples of a single-function product. Depth: product-visuals.
  2. Price below the image. Depth: product-page.
  3. Horizontal layout among alternatives when quality should win. Depth: store-audit.
  4. Sold-out signal at 10–30% of variants. Depth: product-page.

Quality signals

  1. Cost breakdown; say you're small (low-tech); extraordinary guarantee if unknown; real sustainability stated if true. Depth: store-audit.
  2. Rank by measured effect and distance from the rule; free same-day changes (digits, units, copy, price position) ahead of a shoot or a guarantee program.

Output

#FindingChangeMeasured effect (study context)Depth
1$9.99, quality-led product$14 list; just-below for promos only99-ending signals low pricepricing
…

Then: what already complies. Each effect was measured on its own; don't add them up. Ship the top two or three, measure, then take the next.

Common mistakes

  • A 99-ending on the new price "to soften the jump" — that signals low price, the thing being fixed.
  • Keeping fiddly add-on prices as "the real margin numbers" — complex components read as expensive.
  • "More photos" — the measured levers are a hand, a shine, and multiples.
  • Hiding that the company is small — for a low-tech product it raises perceived quality.
  • Inventing a lift for the new price.

Quick reference

LeverDepth
Rounded list; simple add-ons; flat ratepricing
Units, branded ingredient, three claims, registerproduct-copy
Video / hand / shine / multiplesproduct-visuals
Price below image; sold-out shareproduct-page
Cost breakdown, size, guarantee, sustainabilitystore-audit
Validate the levelprice-research

† 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.