Pricing your very first template, guide, or mini-course can feel like throwing darts in the dark. Too high and nobody clicks; too low and you can’t fund the next release. The goal of this guide is to get you to a confident starting price using simple research, a tiny willingness-to-pay test, and a clear pricing ladder you can grow into. No spreadsheets from Mars—just a few moves that work in real life.
Start with value, not with rivals’ prices
“What problem does this remove and how fast?” is a better pricing question than “What do others charge?” The Elements of Value framework from Bain shows that products priced around concrete outcomes (save time, reduce risk, make money) justify higher willingness to pay—overview here. Start by writing a one-sentence promise that’s specific enough to measure. If you struggle with scope, use our One-Page Plan to cut it down until it fits a week.
A quick willingness-to-pay check (15 minutes)
You don’t need a giant survey to get a signal. Run the classic Van Westendorp four-question probe with 10–30 people from your true audience (not friends). Ask them, about this product:
- At what price would it feel too expensive to consider?
- At what price would it start to feel expensive but still worth it?
- At what price would it feel like a bargain?
- At what price would it feel too cheap to trust?
The intersection of “too cheap” vs. “too expensive” gives you a sensible range for a first test. If you want a primer on this method, see a plain-English walkthrough from Pragmatic Institute or a practical guide by Paddle/ProfitWell here.
Choose a model: one-time, tiered, or “lite → full”
For a first product, keep it simple. One-time pricing is easiest to explain and deliver. If your offer naturally splits by scope (features, rights, or support), use two or three tiers. Avoid confusing matrices—remember, people skim. Nielsen Norman Group has long shown that simpler comparison tables improve decisions; a good refresher on table clarity lives here.
Your starter ladder (edit to fit)
| Tier | Who it’s for | What’s included | Price idea* |
|---|---|---|---|
| Lite | First-time buyers | Core file(s) + quickstart PDF | Inside your “acceptable” range |
| Standard | Primary use-case | Everything in Lite + examples, bonus presets | Anchor price (middle of WTP range) |
| Pro | Power users/teams | Standard + extended rights/support | Top of WTP range |
“Lite → Standard → Pro” is less about squeezing every dollar and more about fitting different situations. If you’re productizing services later, this ladder becomes your menu. For a primer on tiered pricing psychology, Nick Kolenda’s research-backed breakdown is helpful here.
Set the first price—then test on live buyers
Pick one price (often the middle of your WTP range) and go live. In our weekend validation playbook we push for 10 paid units or preorders; do the same here. Real purchases beat survey intent. If you see clicks but few checkouts, revisit the promise and the first screen before you move the number.
Charm pricing and endings—when (and when not) to use
$29 often outperforms $30 (so-called “charm pricing”), but it’s not magic. It works best for consumerized, low-risk buys and loses power as stakes rise. A solid roundup of the underlying effects and limits is here. If your audience is B2B or you want a premium feel, consider round numbers.
Regional pricing for US & English-speaking Europe
If your traffic mixes the US and the UK/EU, mind currency and VAT. For EU buyers, many platforms can calculate/display VAT at checkout; confirm how your provider handles this. Stripe and its docs on tax settings are a useful starting point—see Stripe Tax. Keep your public price clear (e.g., “VAT calculated at checkout”).
Fees, refunds, and guarantees
Payment processors and marketplaces take a cut—factor that into your floor price. Check your current provider’s fee page before launching. If you offer a guarantee, write it in one sentence and put it near the button. Counter-intuitively, clear refund terms can increase conversions by reducing risk; HBR has covered this effect across categories here.
Raise with evidence (not vibes)
Plan two checkpoints: after your first 25 buyers and after your first 100. Raise the price only when you add clear value (better outcomes, new modules, rights/support) or when demand stays strong at current conversion. Keep notes from buyer interviews—“What nearly stopped you from buying?”—and ship improvements that address those frictions first. If you need a weekly system to make steady progress, anchor your build work in a protected A-block using our 3-Block Day.
Example: tiny pricing test for a template
- Run the 4 WTP questions with 15 target users → range clusters around $12–$35.
- Launch at $19 (Lite) and $29 (Standard). Pro at $59 with extended rights.
- Sell 10 units in a weekend using the validation playbook.
- Ship one meaningful upgrade, then raise Standard to $39 at buyer #50; announce the change in advance to reward early adopters.
Pricing isn’t a one-time decision. It’s a series of honest tests. Start with value, sanity-check with a tiny WTP probe, pick a simple ladder, and let real purchases guide the next move.
