How to price a first digital product without copying everyone else

You have finished a small guide, workshop or template, and now the cursor is blinking in the price field. Someone else sells something similar for £9. Another creator charges £79. You could copy either number, but neither tells you what your product is worth to the person buying it. A first price should come from the outcome you help create, the effort involved and the evidence you have collected so far.

Price the change, not the file

A digital product may be delivered as a PDF, video, spreadsheet or set of prompts. That format is not the whole offer. The buyer is usually paying for a change: a decision made faster, a task completed with fewer mistakes, or a result they could not yet produce alone.

Write the change as one sentence: “After using this, you can…” Then describe the starting point and the finished point. “You get 40 pages” is a description of contents. “You can plan your first four weeks of content without opening a blank document” describes an outcome.

This does not mean you can charge any amount attached to a large promise. The outcome must be plausible, specific and within the product’s control. A checklist can reduce decisions; it cannot guarantee a customer’s revenue. A course can teach a process; it cannot make someone practise.

Build a price from three inputs

1. 1Outcome: What becomes easier, quicker or less uncertain for the buyer?
2. 2Effort: How much work will you do before and after the sale, including support, updates and administration?
3. 3Evidence: What do you know about the buyer’s problem, your method and their willingness to pay?

Outcome gives you the ceiling you can reasonably discuss. Effort gives you a floor below which the offer becomes unsustainable. Evidence tells you how much risk the buyer is being asked to take. A new product with limited proof may need a clearer scope and a lower first price than an established product with repeated results, even when the underlying method is similar.

Calculate your minimum sensible price

Begin with the work you are actually committing to. Add the hours for making the product, preparing the sales page, answering expected questions and making the first round of fixes. Multiply that total by the hourly amount you need the project to justify. Then add any direct costs and divide by the number of sales you can reasonably reach in the first release.

For example, suppose creation takes 12 hours, setup takes 3 hours and early support takes 5 hours. That is 20 hours. If you want the project to return £30 per hour, the target return is £600. If you expect 20 sales, the work-based price is £30 per sale before payment processing and tax. If you expect 10 sales, it is £60.

This is not a prediction of sales. It is a check against pricing so low that a modest amount of support makes the project a poor use of your time. If your product is designed to sell repeatedly with little support, you can spread the creation work across more expected sales. If every buyer needs a call, review or custom answer, price it as a service or create a separate higher-touch option.

Use evidence without waiting for perfect proof

Evidence is not limited to testimonials. It includes repeated questions in your messages, people asking for the same resource, previous sales of a related service, completed conversations and the objections that keep appearing. Write down what you have rather than treating every signal as equal.

• Strong evidence: people have paid for a related result or asked for this specific solution.
• Useful evidence: you have delivered the process manually and can name the common sticking points.
• Weak evidence: people say the idea sounds useful but have not taken a buying action.
• No evidence yet: the product is based mainly on your assumption about what people need.

When evidence is weak, reduce the buyer’s risk through a narrower promise, a clear contents list and an honest explanation of who the product is for. Do not compensate for uncertainty by piling on bonuses. More material can make the decision harder and increases the amount you must maintain.

Choose a first price you can learn from

Pick a price that gives you a useful signal. If you make a large discount, state why: an early release, a limited version or a launch window. A discount with no reason teaches you little, because you do not know whether buyers wanted the product or simply wanted the reduction.

You can also offer one product in two levels. The lower level might contain the download or lessons. The higher level could include a review, group session or coaching call. The difference should be a real difference in access or support, not a decorative bundle of files. If you use store.fan for the checkout, its paid plans can support products such as downloads, courses and coaching, while Pro adds discount codes and email marketing.

Keep the first version small enough to finish and observe. A storefront on store.fan gives you a place at store.fan/yourname to explain the offer and send people to checkout. On paid plans, money goes directly to your Stripe account and store.fan takes 0% of sales; Stripe’s own processing fee still applies. That makes the arithmetic easier to inspect, but it does not remove the need to account for tax, refunds or your own time.

Review the price after real behaviour

Set a review point before you launch. Look at actions rather than compliments: how many people reached the sales page, how many bought, which questions arrived before purchase, whether buyers finished the product and whether refunds revealed a mismatch.

• If people click but do not buy, check the promise, audience and checkout clarity before cutting the price.
• If people buy but ask for the same missing piece, improve the product or narrow the sales-page promise.
• If buyers finish and request the next step, consider a more supported version rather than adding more to the original.
• If support takes too long, raise the price, reduce access or separate support into a different offer.

Change one important variable at a time where possible. If you change the price, promise, format and audience together, you will not know what caused the result. Keep a short note of the date, price, version and what you learned. That record is more useful than comparing yourself with a creator whose audience, experience and offer are different.