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

subscription-pricing

Skill5 starsChanged 36 days agoMITView on GitHub

Use when structuring or reviewing prices for a subscription, membership, recurring plan, or member dues — plan tiers, upgrade paths, pay-per-use vs flat rate, extra-seat or overage pricing, membership perks — e.g. "how should I price Basic vs Pro", "flat monthly or per video", "what should extra seats cost", "how do we get more upgrades", "is a paid membership worth it".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

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

    Only the rules that change for recurring plans.

    line 28
  2. Very specific:

    Put the upgrade path on the same left digit: No just-below on the lower tier if you want Basic → Pro ($40 → $48, not $39.99 → $48).

    line 31

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

Subscription pricing

Structure recurring prices so people choose a plan, pay the flat rate, and step up a tier. This skill is the delta versus pricing, discounts, and post-purchase. One-off digital products → digital-product-pricing.

When to use

  • Designing or reviewing plan tiers and their prices
  • Choosing flat-rate vs pay-per-use, or pricing seats, storage, minutes
  • Adding a paid membership perk, or rewards for members

When not to use

  • One-off digital products → digital-product-pricing
  • Shared digit and component rules in isolation → pricing
  • Wording a plan discount → discounts; measuring willingness to pay per month → price-research

Inputs

Collect, or state your assumption: tiers, prices, billing period; any per-unit component; whether members optimize for quality or lowest price; which tier you want people to move to; order/usage frequency.

Procedure

Only the rules that change for recurring plans. Shared catalogs live in the Depth skills.

  1. Lead with a flat rate that covers what most members want, priced above the pay-per-use equivalent. Keep pay-per-use only as a low-commitment entry. The source study is purchasing professionals buying usage-based services; applying it to consumer memberships is a transfer. Depth: pricing.
  2. Put the upgrade path on the same left digit. No just-below on the lower tier if you want Basic → Pro ($40 → $48, not $39.99 → $48). Depth: pricing.
  3. Simplify every component. Rounded per-seat / per-GB prices, the same ending, no admin fee. Depth: pricing.
  4. Paid perk needs a minimum. A membership that unlocks free shipping or member rates raises spend; without a minimum, members split into many small orders. Depth: post-purchase.
  5. Rewards: automatic, single tier, threshold. Optionally variable; combining variable rewards with auto-enrollment is untested. Depth: post-purchase.

Shared, unchanged: quality-led → rounded, price-led or post-trial → just-below (subject to step 2); "for $0" on free trials; abandoned-signup reminder at 24–72 h is an assumption transferred from carts. Depth: pricing, promotions, post-purchase.

Worked example

Membership site, plan: Basic $9.99, Pro $29.99, pay-per-video $2.49, extra seats $4.61 + $6 admin fee, opt-in 3-tier rewards, goal: more Basic→Pro upgrades.

  • $10 → $30 removes the just-below start that discourages the step up. Same-left-digit ($40.50 → $48.50) is the stronger version and needs closer tiers.
  • Pay-per-video stays as entry, priced so ~10 videos equals Pro.
  • Seats: $5, no admin fee.
  • Rewards: auto-enroll, one tier.

Output

ItemValue
TiersBasic $10/month · Pro $30/month
Upgrade pathNo .99 on Basic
Pay-per-useEntry only; heavy users cheaper on Pro
Components$5 per extra seat, no admin fee
Perk / rewardsMinimum order on the perk; auto-enrolled single tier
Whyone line per choice

Common mistakes

  • Adding a mid-tier to "shrink the jump" — the jump is the .99 boundary; fix the digits first.
  • Pricing the flat rate at the pay-per-use equivalent "to be fair" — people pay more for the cap.
  • A perk with no minimum — members fragment usage to exploit it.
  • Opt-in tiered rewards — automatic, single tier, threshold reward.

Quick reference

SituationDoDepth
Plan structureFlat rate above pay-per-use; pay-per-use as entrypricing
Want upgradesSame left digit; no .99 on the lower tierpricing
Seats / storageRounded, same endings, no feepricing
Membership perkMinimum order/usagepost-purchase
Member rewardsAuto-enroll, single tierpost-purchase

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.