Try before you buy
Here's a taste of what's inside the full system. Use these freely - no email required, no strings attached.
The Pricing Framework
Every product gets one of three tiers based on how badly the buyer needs it:
- Vitamin ($9) - Nice to have. Low commitment purchase. The buyer is curious but not desperate. Example: a calculator tool, a cheat sheet, a simple template.
- Aspirin ($29) - Solves a real headache. The buyer has tried free alternatives and they're not good enough. Example: a prompt kit, a starter template with real depth.
- Painkiller ($99) - Solves a serious, ongoing pain. The buyer would pay more but you're keeping it accessible. Example: a complete system, a production-ready toolkit.
The key insight: price reflects the buyer's pain level, not how long it took you to build. A $9 product might take a week. A $99 product might take a day - if it solves a big enough problem.
Simplified CLAUDE.md Template
This is the basic structure. The full system includes hooks, memory namespaces, model routing, and agent configs.
# Product Name
## What This Is
One-line description of the product.
## Tech Stack
- Framework (e.g. Astro, static site)
- Styling (e.g. Plain CSS with custom properties)
- Hosting (e.g. Cloudflare Pages)
## Pricing
- $X AUD one-time (Vitamin/Aspirin/Painkiller tier)
## AI Agent Notes
- Key context the AI needs to know
- Content guidelines
- What NOT to do
## Build & Test
npm run build
npm run dev
## File Structure
Brief overview of where things live. Evaluation Checklist
Before building anything, score it on these criteria (1-5 each):
- Pain severity - How badly does the buyer need this? (Weight: 3x)
- Market size - How many people have this problem? (Weight: 2x)
- Competition - Are free/cheap alternatives good enough? (Weight: 2x, inverted)
- Build effort - Can AI build this in under a week? (Weight: 1.5x)
- Ongoing cost - Does it need servers, APIs, or maintenance? (Weight: 1.5x, inverted)
- Cross-sell fit - Does it target the same audience as existing products? (Weight: 1x)
Score above 60: Build it. Score 40-60: Research more. Score below 40: Kill it.
The full system includes the spreadsheet template, real scoring examples, and decision logs showing what I built vs. killed.