How to Price Digital Products: Ebooks, Courses and Templates (2026)

Start with the buyer’s outcome, not your file size

A buyer is deciding whether your resource helps with a task they care about. “An 8,000-word ebook” describes the container. “A guide to preparing a first freelance client handover” explains its purpose. Make the outcome concrete without promising results you cannot control.

Identify who needs it, when they need it and what they would use instead. Alternatives may include a free article, a competitor’s toolkit, their own spreadsheet or paid professional help. Compare products serving the same buyer and task; a supported training program is not equivalent to a downloadable PDF.

List the useful differences you can demonstrate: a completed example, editable files, clear instructions or a narrower focus. Then show those differences in the product preview. If the offer feels interchangeable, improve its specificity before simply raising the price. Shopify’s pricing framework is a useful reference for considering costs, competitors and customer value together.

How to price ebooks, written courses and templates

These three offers target freelance designers preparing client handovers. Their prices are deliberately chosen examples to show the reasoning. None is a claimed market average or a price that every creator should copy.

Ebooks: charge for useful guidance

A short, specific guide can be more useful than a long general manuscript. Show a sample section and explain the reader’s starting point. Review factual claims and examples before selling; AI-generated volume does not make the content valuable. Our ebook creation guide covers the draft-to-delivery workflow.

Written courses: price the learning experience

A course needs a sensible sequence, teaching before practice and instructions that agree across lessons. Explain how students use it and what they will produce. Do not imply video, coaching, personal feedback or certification if you only provide written lessons and exercises. Those expectations affect the buying decision.

Templates: make the practical details visible

Name the compatible tools, included files, customization needed and license permissions. Demonstrate a filled-in example rather than only an attractive cover. A template pack should help someone complete a task; adding more blank files does not automatically support a higher price.

Calculate what each sale leaves after fees

Separate variable costs from fixed costs. Variable costs may include processing, a platform sales percentage and per-order delivery or support. Fixed costs can include software and your product development time. A digital file is inexpensive to copy, but maintaining and selling it still costs money.

For the next table only, assume a hypothetical processing charge of 2.9% plus $0.30 per successful sale, rounded to the nearest cent. This is not a universal Stripe rate. Actual rates depend on the provider, account country, payment method, currency and other factors. Check Stripe’s current pricing and your own account terms.

Revenue after fees is not profit. This example excludes platform fees, taxes, refunds, disputes, currency conversion, payouts, advertising, support and other expenses.

At the example $19 price, a sale leaves $18.15 after that fee. Genesize Starter is $34 per month on monthly billing. Allocating that whole subscription to this one product would require 2 such sales to cover the subscription alone: round $34 ÷ $18.15 up to a whole sale. This does not recover your creation time or other costs and does not predict demand. If several products share the software, choose a sensible allocation rather than charging each for the full bill.

For your own offer, use: contribution per sale = price − payment fees − platform sales fees − other variable costs. Then divide the fixed costs you want to recover by that contribution. If contribution is zero or negative, more sales will not solve the underlying economics.

Choose one price you can explain

1. Write the offer in one sentence. Name the buyer, task, format and included resources.
2. Inspect a few relevant alternatives. Note price, support, access and licensing differences. A listed price does not prove how well an offer sells.
3. Check your cost floor. Include plausible support and refund costs; do not depend on optimistic sales volume to make every order viable.
4. Choose a test price. Treat $19, $49 or $99 as examples to reason about, not magic conversion numbers.
5. Show evidence of the product. A real sample, contents list and compatible-file details let buyers judge fit.

Ask potential buyers what they currently use and where that approach falls short. “Would you buy this?” is weaker evidence than an actual purchase, but concrete objections can reveal a missing instruction or unclear promise. If you have no audience, start with our guide to finding customers without a following.

Use introductory prices, discounts and bundles carefully

An introductory price should have an honest reason: an early version with a defined scope, a stated launch period or a limited cohort you can actually support. Describe what is available now. Avoid invented “usual” prices, fake scarcity and a countdown that repeatedly resets. Keep your promise when the offer ends.

Recalculate the economics before discounting. A 20% reduction takes the example $49 template pack to $39.20. Under the same hypothetical fee, that sale leaves $37.76 rather than $47.28: $9.52 less to cover the rest of your costs. A discount needs a reason beyond making the button more tempting.

Bundle complementary resources around one task. The $19 ebook and $49 template pack total $68 separately; an illustrative $59 bundle saves the buyer $9. Explain every included file and avoid charging for duplicates. You can prepare a combined resource package as a product; check what your selling platform supports before promising automatic cross-product access or subscriptions.

When uncertainty is the problem, offer a useful preview or lead magnet instead of cutting the price. A sample can demonstrate the quality while preserving the economics of the complete product.

Test prices without confusing traffic changes with demand

Keep the product and sales message stable while testing one meaningful change. Record the date, price, audience, traffic source and period. Compare periods with similar visitor intent and campaign conditions; a holiday promotion and a quiet week are not a clean price comparison.

Track conversion alongside revenue per qualified visit. In a hypothetical example, four $19 purchases from 100 comparable visits leave $72.60 after the example fees, or about $0.73 per visit. Three $29 purchases leave $83.58, or about $0.84 per visit. The higher price has lower conversion and higher revenue per visit in this arithmetic example. Neither figure includes other costs.

Seven purchases are too little evidence to declare a winning strategy. Continue observing enough comparable traffic and allow time for refunds and support requests. There is no universal number of visits that makes every pricing test reliable. Review buyer feedback, fulfilled promises and refund patterns alongside the numbers; a price that increases revenue while disappointing customers is not a sustainable improvement.

Low conversion may come from the wrong audience, an unclear outcome, weak previews or a checkout problem. Inspect those before assuming the price is wrong. Once a product is working, revisit pricing when its scope, support or relevant alternatives change.

Copy this digital product pricing worksheet

Paste these fields into a document and complete them for one offer. Use your actual processing terms and conservative assumptions. Save the worksheet before each test so you can explain what changed.

Product and format: [name, files or lessons]
Specific buyer and task: [who needs this, and when]
Useful outcome: [what the resource helps them do]
Included / excluded: [access, support, updates, license]
Relevant alternatives: [prices and meaningful differences]
Initial price: [currency and one-time or recurring terms]
Fees and variable costs per sale: [actual assumptions]
Contribution per sale: [price minus variable costs]
Fixed costs allocated: [software, creation and other costs]
Sales to cover those costs: [round fixed costs / contribution up]
Preview and proof of contents: [what the buyer can inspect]
Test period and traffic source: [dates and comparable audience]
Review: [conversion, revenue per visit, refunds, feedback]
Next decision: [keep, improve the offer or test a new price]

Put your price into a complete selling workflow

In Genesize, create or refine the product, check its exported files and prepare an editable sales page connected to the offer. State the format, contents, price and delivery clearly. Preview the page on a phone, connect an eligible Stripe account and check buyer access before inviting customers.

Choose a one-time payment or free offer in the Store editor. Save your changes, use Preview buyer experience and check Review & publish before updating the live offer. Saving a different price alone does not change future checkout: publish the revision. Existing buyers retain their purchased edition.

Genesize does not take a platform percentage of Store sales; payment processing and your subscription are separate. It does not automatically validate demand or replace your responsibilities for product quality, licensing, taxes and customer promises. Compare complete selling costs in our Gumroad alternatives guide and check current Genesize plans.

After launch, use Storefront and Funnels analytics to review purchases, measured traffic and conversion. Genesize’s net revenue subtracts known refunds and excludes payments currently marked disputed; it is not profit or a bank payout. Track fees and other expenses separately. Keep notes for traffic quality, objections and test dates. Your next improvement might be a clearer example or simpler instructions, rather than a new price. The goal is an offer buyers understand and a product you can confidently maintain.

Digital product pricing: frequently asked questions