Pricing

Keep the first price simple

Early pricing is not about perfect packaging. It is about learning whether the problem is valuable enough for someone to pay to solve.

Pick one simple model:

• One-time template/license — good for starter kits, codebases, and playbooks.
• Monthly subscription — good for hosted software with ongoing value.
• Setup fee + monthly — good when customers need help getting live.
• Founding access — good when the product is early but useful enough for first buyers.

Do not hide from the money question

Ask directly once someone understands the problem and outcome:

If this solved [problem] and saved you [time/cost/risk], what would feel like a fair price?

Or:

Would this be a £50 problem, a £500 problem, or not really a paid problem for you?

Ranges are easier to answer than an open-ended price.

Early pricing rules

• Charge earlier than feels comfortable.
• Start with one clear package.
• Avoid complicated tiers until customers ask for them.
• Increase price when conversations are easy.
• Lower friction before lowering price.

Useful signals

Strong signal:

• They ask how to buy.
• They ask if they can use it this week.
• They compare the price to time saved.
• They ask for an invoice, team access, or implementation help.

Weak signal:

• They say it is cool but avoid price.
• They ask for many extra features before paying.
• They want free lifetime access for feedback.