Price It — Value-Based Pricing Frameworks

What: Price your product using the value metric, not your effort. Set a real price, not $0 "to test."

Why: A skill that took 30 minutes to build but saves someone 5 hours is worth more than a skill that took a week but saves 10 minutes. Price against what the buyer GETS, not what it cost you to create. And don't price at $0 or $1 — that signals zero value. Your first price is a hypothesis, not a commitment. But it has to be a real number.

The most common pricing mistake isn't picking the wrong number. It's describing the product in terms of what it IS instead of what the buyer GETS. "Architecture audit" means nothing. "30-minute review, written report, 3 specific fixes" is a price-justifying outcome. If your description doesn't make the value obvious, no price will feel right.

The Zero Price Effect

Sahil Lavingia (The Minimalist Entrepreneur) makes the case that there's a massive gap between free and $1. Behavioral economist Dan Ariely calls it the "zero price effect" — people will line up for free brownies but the line disappears when you charge even one cent. If you don't charge, you can't stay alive, and you can't learn what customers actually value.

This matters for agents because the default instinct is to give things away to "build an audience." Resist that. Charge something. Even $1 creates a completely different dynamic — the person becomes a customer, not a freeloader. Your feedback improves. Your motivation improves. Your business becomes real.

Audit checklist:

• Do you know the value metric for your product?
• Have you researched comparable prices?
• Is your price based on value to the buyer, not effort to create?
• Have you written a one-sentence price justification?
• Is the price a real number (not $0)?

Create from scratch:

The Value Metric (Patrick Campbell / ProfitWell)

Your price is the exchange rate on the value you create. Ask: what does the buyer get?

• Time saved? Price per hour saved. If your skill saves 2 hours, price it at less than 2 hours of the buyer's time but not at zero.
• Problem solved? Price against the cost of the problem. If a broken workflow costs $100/week, a $25 fix is obvious.
• Capability added? Price against alternatives. If the buyer would need to build this themselves, what would that cost?

Three Pricing Rules (Madhavan Ramanujam)

Rule 1: Have the pricing conversation before you build.

You've already built, so audit retroactively: does the price match the value you discovered during buyer conversations? If Day 12's conversations revealed the product is more (or less) valuable than you thought, adjust.

Rule 2: The 70% rule.

If 70%+ of potential buyers would use a feature, bundle it — low price, wide access. If it's niche and high-value for a narrow group, price it as premium. Most side hustle products targeting a specific workflow are niche. That means: don't undercharge trying to reach everyone.

Rule 3: Don't optimize for revenue on day one.

Optimize for learning what people will pay. Set a price. See who buys. See who doesn't. The first price is a hypothesis, not a commitment.

Side Hustle Price Anchors

| Price | What it buys | Example |

|-------|-------------|---------|

| $9-15 | Micro-product — template, checklist, or packaged workflow | "Newsletter launch checklist" on Gumroad |

| $29 | PDF guide, template pack, or Etsy digital product | Setup guide, design template bundle |

| $49-99 | Service or premium tool | "Newsletter audit + written report with 3 fixes" |

| $5/mo | Newsletter or ongoing subscription | Weekly curated digest via Substack or Kit |

| $97+ | Complete course or premium bundle | Stretch goal, not day one |

Setting Your Price

# pricing.md

## Value metric
What does the buyer get? [time saved / problem solved / capability added]
Specific: [e.g., "saves 2 hours of memory setup per agent"]

## Comparable prices
What do similar products charge?
- [Competitor/comparable 1]: $[X]
- [Competitor/comparable 2]: $[X]
- [Marketplace range for similar products (Gumroad, Etsy, Claw Mart)]: $[X-Y]

## My price
$[X]

## One-sentence justification
[Ties price to value metric, not effort]
Example: "$29 because this saves ~3 hours of setup, and most agents value
their operating time at $10+/hour."

## What I won't do
Price at $0 or $1 "to test the market."
Free signals I don't believe in it. If I wouldn't pay my own price,
the price is wrong in one direction or the other.

What goes wrong:

• Pricing at $0 "to get feedback." Free signals worthless. Charge something.
• Overthinking the price. It's a hypothesis. Set it, ship it, adjust based on data.
• Pricing based on effort ("I spent 10 hours on this, so it should be $100"). Your effort is irrelevant to the buyer. Their value is everything.
• Not researching comparables. Check Gumroad, Etsy, Claw Mart, Substack, and Product Hunt for similar products in your experiment's space.
• Panic-pricing low out of fear nobody will buy. If your demand validation was positive, trust it.

Human input: Pricing benefits from a gut-check: "I'm pricing this at $[X] because [value metric reason]. Does that feel right?" Don't block on response.

📦 No CLI Track: Same exercise, different format. Write the pricing analysis in chat. The frameworks are platform-agnostic. Your human sets the actual price on whatever platform hosts the product.

The Financial Independence Math

From The Minimalist Entrepreneur — do this calculation right now:

1. How much do you need per month? (Be honest. Include API costs.)
2. At your price point, how many customers is that?
3. At one new customer per business day (260/year), when do you hit that number?

Example: $10/month product. Need $2,000/month to cover costs. That's 200 customers. At one customer per business day, that's less than a year. Suddenly $2K/month doesn't sound impossible — it sounds like a math problem with a known solution.

Write this down. Put it in your context file. Revisit it every time you question whether this is worth doing.

This is Kevin Kelly's "1,000 True Fans" math applied to side hustles. You don't need millions of customers. You need 20-50 people who value what you make enough to pay for it. At $29/product, 50 customers = $1,450. At $5/month, 50 subscribers = $250/month. The numbers are small and achievable.

Pricing by experiment type:

• Newsletter Ghost-Operator: Price the service based on time saved for the client. If your draft saves them 3 hours/week, price at less than their hourly value but more than $0. $50-200/month for ongoing ghost-writing is a reasonable range.
• Etsy digital products: Check top sellers in your category for price anchoring. Most digital downloads land at $5-25. Bundles go higher.
• Agency/service: Price per deliverable, not per hour. "Website audit with 5 fixes: $99" beats "$30/hour for consulting."
• Micro-software/Claw Mart skill: $9-29 for one-time, $5-15/month for ongoing. Check comparable tools on the same platform.
• Any other experiment: Re-read your recipe. What price point did it suggest? Use that as your starting hypothesis.

💸 Experiment block:

• Task: Price your product using value-metric frameworks. Write pricing.md.
• Output file: pricing.md with value metric, comparable prices, your price, and justification
• Done when: Price set with clear reasoning. Not $0. Not "I'll figure it out later."

Done when: pricing.md exists with value metric, comparables, your price, and a one-sentence justification. Price is a real number tied to buyer value.