Skip to content
Back to skills

Raise Prices

ASecurity

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.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 19, 2026
ai-agentsgoexpressgit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 19, 2026

npx -y skills add checkout-page/ecommerce-skills --skill raise-prices --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Raise Prices?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Raise Prices
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/checkout-page-raise-prices/badge)](https://www.skillsdirectory.com/skills/checkout-page-raise-prices)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: raise-prices
description: 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.
---

# 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**

6. **Concrete units** (applications, washes, days), smaller unit for precision. Depth: `product-copy`.
7. **Branded ingredient in the headline.** † Depth: `product-copy`.
8. **Register by product type.** Science/effectiveness language only if utilitarian. † Depth: `product-copy`.
9. **Three best claims, plain words.** Depth: `product-copy`.

**What the buyer sees**

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

**Quality signals**

14. **Cost breakdown; say you're small** (low-tech); **extraordinary guarantee** if unknown; **real sustainability** stated if true. Depth: `store-audit`.
15. **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

| # | Finding | Change | Measured effect (study context) | Depth |
|---|---|---|---|---|
| 1 | $9.99, quality-led product | $14 list; just-below for promos only | 99-ending signals low price | `pricing` |
| … | | | | |

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

| Lever | Depth |
|---|---|
| Rounded list; simple add-ons; flat rate | `pricing` |
| Units, branded ingredient, three claims, register | `product-copy` |
| Video / hand / shine / multiples | `product-visuals` |
| Price below image; sold-out share | `product-page` |
| Cost breakdown, size, guarantee, sustainability | `store-audit` |
| Validate the level | `price-research` |

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

Evidence and effect sizes: see [reference.md](reference.md).

Files in this skill

  • SKILL.md4.9 KB
  • reference.md651 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.