Claude for pricing strategy, done properly.
The tested prompt, the codes that help, and the setup product strategy pros run. Copy, adapt, ship.
Most founders guess at pricing. Too low and you leave money on the table. Too high and you kill conversion. Without a framework, pricing decisions are pure anxiety.
Three reasons this actually lands.
The prompt, the codes, the fit. Each one on its own is a nice-to-have. Together, they change the workflow.
One tested prompt, copy-paste ready. Rules baked in, placeholders marked, tone locked down. No prompt-engineering trial runs, no back-and-forth.
Prefix with REASON, V=2, REFINE for compound effects. Each code is a documented technique, not a magic word.
Tuned for product strategy workflows. Not a generic template, and not another "you are a helpful assistant" hack.
Without the pattern vs with it.
What the day looks like when you keep winging the prompt, and what it looks like when you stop.
Generic prompt. Claude writes something that could be about anyone, in any industry, from anywhere. Sounds like a template because it is one.
The CLSkills prompt with placeholders for your context. Claude writes it like a specialist who actually knows the work. Publishable after one edit pass.
You paste, Claude answers, you rewrite, you paste again. Ten minutes of back-and-forth per output. Three hours across a batch of five.
Prompt loaded once. You feed the specifics, Claude returns the finished output. Two minutes per, twenty across five. Same tone, same structure, every time.
Middle-of-the-road copy that reads AI-flavoured. Recipients notice. Response rates stay low. You end up rewriting most of it anyway.
A data-informed pricing strategy with specific tier recommendations, psychological anchoring, and a test you can run immediately. Not academic theory — actionable pricing.
Copy this, replace the placeholders, ship.
Help me develop a pricing strategy for [PRODUCT]. Product: [WHAT IT DOES] Target customer: [WHO BUYS IT + THEIR BUDGET CONTEXT] Current pricing (if any): [WHAT YOU CHARGE NOW] Competitors' pricing: [WHAT THEY CHARGE] Cost to serve: [YOUR COSTS PER USER/UNIT] Analyze: 1. **Value metric**: What should I charge based on? (per user, per usage, flat, tiered?) 2. **Price anchoring**: How should tiers be structured? (Good/Better/Best) 3. **Willingness to pay**: Based on the value delivered, what's the ceiling? 4. **Competitor positioning**: Where should I sit relative to competitors and why? 5. **Psychological pricing**: $X.99 vs round numbers — what fits this market? Recommend: - 3 pricing tiers with names, prices, and feature allocation - Which tier is the "intended" choice (and how the others anchor it) - Free tier strategy (if applicable) - Annual vs monthly discount strategy - One pricing experiment to run in the first month
Replace the [BRACKETED] placeholders with your context.
Stack these prefixes for compound gains.
Prepend one or more of these to the prompt above. Each code is documented on its own page with before and after examples.
Every prompt, once.
The Cheat Sheet is every tested code, with a before and an after.