Home / Fields / Digital products
Digital Products: Build the File Once, Sell It Many Times
You package knowledge or assets into a file — template, ebook, checklist, preset pack, mini-course — and a store sells it while you sleep. The product is built once; the real ongoing work is traffic.
How the money flows
| Step in the chain | What actually happens |
|---|---|
| You build a file someone wants | The best first products are extracted from work you already do: the template you reuse, the checklist you follow, the spreadsheet you built for yourself. |
| A store handles checkout and delivery | Gumroad or Payhip takes payment, delivers the file, and handles the receipt. Fees are known and published — the store comparison with worked fee math is on our digital stores page. |
| Traffic arrives from your engines | Content, community posts, an email list, affiliates. Stores have almost no natural traffic of their own — this is the fact beginners refuse to believe. |
| Each sale is near-zero marginal cost | After platform and processing fees, the rest is yours. A $29 sale on the free Gumroad plan keeps $24.46 by the worked math on the stores page. |
| The catalog compounds | Product two sells product one's buyers. Bundles and a small catalog raise average order value without new traffic. |
Who this fits — and who it doesn't
Good fit
You have reusable know-how, templates, checklists, or files from your work or hobbies, and access to (or willingness to build) one traffic channel. Pairs naturally with content as the traffic engine.
Bad fit
You expect the store itself to bring buyers (it won't), or your idea requires months of production before a first sellable version — first products should be finishable in days. Also a bad fit if you can't stand writing the sales page; in this field, the page is half the product.
Zero to first payment
- Mine your own work first: list 10 files/templates/checklists you already use. The one other people have asked you for is product #1.
- Validate before building the full thing: post the problem it solves in one community; if nobody asks 'where can I get it?', shrink or switch the topic.
- Build the minimum complete version: the file, a one-page README (what it is, how to use it, where to get help), and nothing else.
- Price by band: impulse items roughly $5–19, serious templates/tools $19–49, deep courses/bundles $49–199 — then verify with the fee math so you know what you actually keep per sale.
- Open the store (Gumroad for zero-config start, Payhip for lower fees — comparison on the stores page), write the listing with the six-part structure (title, pain, contents list, fit/not-fit, FAQ, price anchor), and buy it yourself once to test the full flow.
- Publish the launch post where your buyers already are, with a free sample (an excerpt or lite version) as the hook.
- Collect every question buyers ask into the FAQ and the product itself; version 1.1, informed by real buyers, is where this field starts compounding.
Platforms & tools
The store layer is covered end-to-end on our Gumroad vs Payhip page — fee tables, the $10/$29/$99 take-home comparison, the 7-step listing checklist. The traffic layer is the content field or the affiliate field run in reverse (your own links, your own product). Before launch day, walk your store as a customer with the launch checklist: open → cart → checkout → payment methods visible.
Worked example (illustrative math, not an earnings promise)
Assumptions, stated out loud: a $29 product on Gumroad's free plan keeps $24.46 per sale (the worked figure from our stores page: $29 − $2.90 platform − $0.50 fixed − $1.14 processing). Assume 20 sales in the first month from one launch post and a small back catalog of content.
24.46 × 20 = $489.20 before the PayPal wire home.
Result on these assumptions: $489.20 on these assumptions. Change the traffic assumption and the result moves linearly — which is the point: in this field you don't have a product problem, you have a distribution problem. Every input below is an assumption we state out loud, not a market average and not a promise. Change the inputs to your own quotes and fee pages before you rely on any of it.
Week one
- ☐ List 10 reusable files/templates from your own work; mark the one people ask for
- ☐ Post the problem in one community and count real 'where can I get it' replies
- ☐ Build the minimum version + README in a single focused day
- ☐ Choose the store and verify your keep-per-sale with the fee table
- ☐ Write the listing (six parts) and self-buy to test checkout and delivery
- ☐ Schedule the launch post and the free sample
How people fail at this
- Building for months in secret. A perfect product with no audience loses to a decent product launched in a week to people who asked for it.
- Pricing at $5 'to get volume'. After fixed per-sale fees, $5 products keep a pittance and attract the most support requests. Price for the outcome, not for courage.
- One product, no engine. Listing and waiting is not a strategy. Without a content/community/email engine feeding the store, the catalog is a warehouse nobody visits.
FAQ
What actually sells?
Things that save time or make money for a defined buyer: templates, checklists, swipe files, presets, niche databases, practical mini-courses. 'My notes, but as an ebook' sells only if the notes solve an expensive problem.
Gumroad or Payhip?
Start where setup is zero (Gumroad) to prove someone pays; move or dual-list when fees outweigh convenience — the crossover math is worked out on the stores page.
How do I stop piracy worries from stalling me?
Some copying is the cost of digital goods; watermarking PDFs and licensing clearly is enough for most small products. The bigger risk by far is obscurity, not piracy.