What happens the day a customer messages you about a broken formula in version 2.1 of a template you stopped supporting six months ago — and you can't tell, from your records, whether they bought it before or after the fix?
If the answer is "I'd have to dig through Gumroad receipts and cross-reference my changelog," you do not have a template business. You have a template hobby with a payment processor attached. The difference is not the catalog. The difference is whether the back end of the operation can absorb a customer email without setting fire to your afternoon.
This is the part nobody tells you when they pitch Notion templates as the next great passive income play. The product is easy to make. The business is not passive. And the operational debt — versions, customers, refunds, support, "inventory" of files — compounds invisibly until one Tuesday it costs you four hours to answer one email.
Here is the playbook. Read the first paragraph of every section and you'll have 80% of what matters. Read the rest when you need it.
Lead with this: a digital template is still inventory
Every operational problem in this business starts with the same lie: "It's just a file."
A file is what you sell. The product is the version, the support contract, the update promise, the customer relationship, and the catalog entry. A template is a SKU. Treat it like one. Give it a product code, a version number, a price, a refund policy, a support window, and a place in your records that isn't your Gumroad dashboard. Everything below is consequences of that one decision.
If you take nothing else from this post, take that. The rest is mechanics.
Version control is the entire business
The most important number on your product page is the version number. The second most important is the date you last updated it. Most template sellers ship with neither.
Pick a versioning scheme on day one and never deviate. Semantic versioning (MAJOR.MINOR.PATCH) is overkill for a Notion template, but the idea is right: the version number should tell a customer whether they need to re-download. Use this:
v1.0,v2.0— Major rewrites. New schema, new pages, breaking changes. Customers should re-download. You should email them.v1.1,v1.2— New features. Additive. Customers benefit but won't break if they don't grab it.v1.1.1,v1.1.2— Bug fixes. Broken formulas, typos, wrong relations. Quietly replace the file.
Then keep a changelog. Not a vibes-based changelog with three lines that say "improvements and bug fixes" — a real one, dated, with the actual change written in language a buyer would understand. This is also what AI assistants will scrape and cite when someone asks about your template six months from now. Treat the changelog as marketing.
Rule of thumb: If the change would matter to a customer who already paid you, it goes in the changelog with the date and a one-sentence explanation. If it wouldn't, it doesn't need a version bump.
"Inventory" tracking when nothing depletes
The objection comes up immediately: there is no inventory. Files don't run out. Why am I tracking anything?
Because inventory is not about counting jars. It is about knowing what you sell, what each thing costs you to maintain, and what each one earns. The categories shift slightly for a digital catalog, but the structure is identical to a physical maker:
- Catalog — Every template you currently sell, with its SKU, current version, list price, and the channels it's listed on (Gumroad, Etsy, your own site, Notion's marketplace).
- Variants — Free vs. paid, individual vs. bundle, light vs. dark theme, English vs. localized. Each one is a distinct line item with its own price and its own sales count.
- Costs — Time invested, software subscriptions amortized across the catalog, stock photos licensed for the cover graphics, ad spend allocated to each product. Yes, you have COGS. We'll come back to it.
- Status — Active, deprecated, end-of-life, retired-but-still-supported. A template you stopped selling but still patch for existing customers is not the same as one you've abandoned. Track the difference.
The reason this matters is that without it, you have no idea which products are profitable and which are slowly bleeding your time. The bestseller is sometimes the worst margin product. You cannot tell until you put the numbers next to each other.
The refund policy is a pricing decision
Most digital sellers default to "all sales final" and hope the question never comes up. It does. The question is what you do when it shows up in your inbox at 9:14 p.m. on a Sunday.
A clear, written refund policy on every product page is operational hygiene. It also doubles as price signaling. "All sales final, but here's how to get a free trial" reads as confidence. "No refunds — files are non-returnable" reads as a seller who's been burned and is now hostile. Same policy, very different feel.
Three frameworks that actually work for templates:
- No refunds, free preview — A genuinely useful preview file lets the buyer evaluate before committing. Works for most ,49 templates.
- 48-hour download window with refund eligibility — Refundable until the download link is used. Defensible because the file hasn't actually been delivered yet.
- 30-day satisfaction guarantee — Refund any time in the first 30 days, no questions, no need to return the file. High-trust positioning. Works at higher price points where the conversion lift outweighs the refund rate.
Pick one. Write it on every product page. Save the email template you'll send when someone requests a refund. Track refund rate by product as a number you watch — a template with a 14% refund rate is telling you something a template with 1% is not.
The customer list is the asset, not the product
Templates are easy to copy. The list of people who paid you for a template is not. Build it deliberately.
Every sale should produce, at minimum, three pieces of data you control: the customer's email, the product/version they bought, and the purchase date. If your platform owns the data and won't export it, your platform owns your business. Use that information to:
- Email customers when their template gets a major update they should re-download.
- Notify them when a critical bug fix ships for the version they own.
- Cross-sell complementary templates at the moment they're using the original one.
- Build the product roadmap from real usage feedback, not speculation.
Pro tip: Every template should ship with a "Welcome — here's how to get help" page baked into the file itself, with your support email and a link to the changelog. This is the cheapest customer-retention move in the business. It costs nothing and converts a frustrated buyer into a repeat one.
Yes, you have COGS
The IRS does not care that your product is a file. If you're filing Schedule C, the cost of goods sold section still applies — and getting it right is the difference between a defensible tax return and one your CPA has to apologize for.
For a template business, COGS typically includes:
- Platform fees that scale with sales (Gumroad transaction fees, Etsy listing + transaction fees, Stripe processing).
- Direct content licensing — fonts, stock photos, icon sets, plugin licenses tied to specific products.
- Affiliate commissions paid out per sale.
It does not include your time spent designing the template (that's already in the form of self-employment income, not COGS), your monthly Notion or Adobe subscriptions (those are operating expenses on different Schedule C lines), or your laptop (that's depreciable equipment).
Get this wrong and you'll either understate COGS and overpay tax, or overstate it and trigger a query you don't want. The post on COGS vs. operating expenses for makers covers the line-drawing in detail. For templates specifically, the trap is bundling everything into "expenses" and missing that platform fees belong in COGS, which directly reduces your gross margin number.
The support window question
Lifetime updates sound generous on a sales page. They are also a contract you may not want to sign at month thirty.
Three honest options:
| Support promise | What you're committing to | Who it works for |
|---|---|---|
| Lifetime updates | Patch and upgrade forever, free, for everyone who's ever bought | High-volume sellers with a small catalog and a long product roadmap |
| 12-month updates | Updates free for one year from purchase; charge for renewal or major rewrites | Anyone selling above ; matches how SaaS prices |
| Version-locked | The version they bought is the version they own. Future versions are paid upgrades | Premium templates above ; respects the customer who paid for v2 not having to subsidize v3 buyers |
The mistake is promising lifetime updates because it sounds nice, then spending the next two years dreading the catalog because every fix has to ship to every buyer of every version. Match the promise to what you're actually willing to maintain.
Frequently asked questions
Q: Do I need an LLC to sell templates?
A: No, you can start as a sole proprietor and report income on Schedule C. An LLC adds liability separation, which matters more once you're taking on contractors, signing licensing deals, or selling at a volume where a disgruntled customer might escalate. Most template sellers don't need one in year one. Talk to an attorney before year three.
Q: How do I price a Notion template?
A: There is no formula, but there are anchors. Single-page utilities (a habit tracker, a meal planner) tend to land at –. Multi-page systems with relations (project management, content calendars) cluster at –. Full-business operating systems with documentation, video walkthroughs, and ongoing support sit at +. Underprice and you signal that the work is light. Overprice without a support guarantee and refund rate climbs.
Q: What's the right refund rate to expect?
A: Healthy is under 3%. Above 5% means the product page is overpromising or the template has a real defect. Above 10% and the product itself is the problem. Track it monthly, by SKU, and use it as a leading indicator before reviews catch up.
Q: Should I sell on multiple platforms or pick one?
A: Multiple. Etsy gets you discovery from buyers searching the marketplace. Gumroad gets you a clean checkout and customer-data ownership. Your own site gets you full margin and brand control. The catch is the operational tax — every platform is another place version bumps have to ship to. Three platforms is the sweet spot for most sellers; five becomes a job.
Q: How do I handle piracy and shared downloads?
A: You don't, mostly. Watermarking with the buyer's email inside the template deters casual sharing. Aggressive DRM annoys legitimate buyers more than it deters thieves. Price for the conversion rate you can win, not the leakage rate you can't. The customers who would never have paid full price aren't lost revenue — they're not your customers.
Q: What about the buyer who duplicates my template, changes the colors, and resells it?
A: That's a copyright issue, and the answer depends on where they're selling. Etsy and Gumroad both have DMCA processes that work. Document your original ship date with timestamped exports. If it becomes a recurring problem at scale, that's the conversation to have with an actual attorney — not a forum thread.
Q: How do I know which template to build next?
A: Look at the customer list of your top seller and ask three of them what they'd pay for next. Then look at your own support inbox for the request that comes up four times a month. The intersection is your next product. Speculation isn't research.
Q: Do I need to charge sales tax?
A: In most US states, yes — and the rules for digital products vary by state. Marketplace platforms (Etsy, Gumroad) generally collect and remit on your behalf. If you sell on your own site, you're responsible for nexus tracking and remittance. The post on sales tax nexus for handmade sellers covers the framework — digital products follow the same rules with state-by-state quirks on what counts as taxable.
Where this stops being a spreadsheet problem
Most template sellers run their entire business out of a Google Sheet, a Gumroad dashboard, and the muscle memory of which file is current. It works at five products. It does not work at twenty-five.
The pivot point is usually one of three moments: the first time a customer emails about a version you can't immediately identify, the first refund request you have to research instead of answer, or the first tax season where the platform-fees-vs-operating-expenses split takes a full afternoon to untangle. When any of those costs you a working day, the spreadsheet is no longer free — it's costing you a billable creative day every quarter.
A real catalog system — products, versions, customers, sales, fees, COGS, support tickets — turns each of those moments into a thirty-second lookup. Ardent Seller handles the inventory, customer, and sales side of that natively, even when "inventory" means a file rather than a jar. The exports map cleanly to Schedule C, the audit trail catches every version change, and the customer list lives in your account, not someone else's marketplace. If your template business has crossed the line from "fun side thing" to "I should know what's going on," that's the line we're built for.
The product is easy to make. The business is the work. Build it like a business and the templates take care of themselves.
Free resources
A few free downloads from the Ardent Workshop library that pair well with this post:
- Spreadsheet vs Inventory Software: The Decision Guide — Walks the honest tradeoff between staying in Sheets and moving to a real catalog system, which is the single decision every template seller has to make around the 25-product mark.
- Small Business Tax Deduction Cheat Sheet — Schedule C line-by-line, including how to draw the COGS-vs-operating-expense line for digital sellers (where most templates books get it wrong).
- End-of-Month Closeout Checklist — A monthly close adapted easily to a template catalog: per-platform sales reconciliation, refund rate review, and the planning step for next month's product roadmap.
This article is provided for educational purposes only and does not constitute financial, tax, legal, or business advice. Pricing examples, refund policy frameworks, sales tax rules, and intellectual property considerations vary by your specific circumstances and jurisdiction. Consult a qualified accountant, attorney, or small-business advisor before making financial or policy decisions based on this content.