Individual skill

pricing

Use this skill to decide what to charge: 'how much should I charge,' 'what should I charge my first customers,' 'pricing tiers,' 'freemium or free trial,' 'should I raise my prices,' or 'pricing page.' Before 10 paying customers it sets one simple price and works out how many customers the founder needs. After 10 it designs tiers from how real customers differ. Not for setting up Stripe or billing code (use payments) or for runway and the quit number (use finances).

skills/pricing/SKILL.md

Read pinned source

Source commit 01bd10f79a4b6a741be78e3184612a90ecbd54ef

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 262
Repository last updated: Oct 16, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,829 bytes

Read excerpt


# Pricing

Charge from the first customer. A free user tells you they like free things. A paying customer tells you the problem is worth money.

## Step 1: Find the stage

Ask how many people pay today. Before 10, use Step 2. From 10 on, use Step 3.

## Step 2: Before 10 paying customers

1. **Set one price.** No tiers, no free plan. Base it on what the customer spends on the problem today, in money or in hours multiplied by their hourly rate. Your costs set the floor, not the price.
2. **Check the anchor.** What do these customers already pay for tools? A \$49 add-on feels small to someone paying \$300 a month for software, and large to someone who pays nothing.
3. **Do the customer math with the founder:**
   ```