Sell a $29 Digital Product With an Owned Stack

You are deciding where one digital template will live: on a marketplace, or on a small stack you control. Use the one-bad-day test. If the marketplace disappears, the sale should still work, the file should still arrive, the refund should still be possible, and the customer email should still be yours.

Easlo, also known as Tomas Garcia, runs a Notion template business that has been publicly documented at over $100,000 per month. You do not need that scale. You need a durable trick: keep the customer relationship, the payment path, and the refund path under your own control. Count the hours, not just the dollars.

Design for the day the marketplace disappears

The design question is simple: what survives when the channel that brought the buyer is gone. The owned stack is small enough to build before launch: email, checkout, delivery, refunds, and a price that covers your time. It is small because it follows the buyer, not a growth dashboard.

Do not build a pile of growth hacks. Build the path a buyer follows. The usual mistake is building checkout before the email list, so the early sale leaves without a way to follow up. Each step depends on the previous one, so the order matters.

Build the stack in the order money moves

• Collect email before checkout. A welcome message should arrive from your own list, not from a marketplace inbox. The customer should be able to reach you without a platform intermediary. Keep the list separate from any marketplace customer panel. If the marketplace closes, your list should still open in your own inbox.
• Connect checkout to delivery. A payment should produce a delivery link, a licence key if needed, and a record you can find later. Gumroad takes care of licence keys, file delivery, and customer account storage after a payment is completed. The delivery link should work even if the buyer never creates an account on a third-party site. Keep a copy of the file in a place you control.
• Write the refund path before launch. The note should say where to send a refund request, what proof you need, and how long the response takes. The refund path should be as easy to find as the buy button. Put the policy on the checkout page, not only in a separate help page. A refund request should not require the customer to guess.
• Set pricing with margin. The price should cover your time, your payment costs, and a small buffer for support. A single digital template typically sells for $10 to $79, while a template bundle or system typically sells for $19 to $299. Count the hours you spend on support, updates, and delivery. If the price leaves no room for that time, the product will feel like extra work.
• Run the one-bad-day test. A sale, delivery, refund, and customer email should all work without the marketplace. Turn off the marketplace link for a test day. Buy the product, check the email, request a refund, and confirm the file arrives.

Use the marketplace as a comparison, not the business

A marketplace can help you find buyers, but it can also charge fees and hold the customer relationship. Etsy's pricing includes a $0.20 listing fee, a 6.5% transaction fee, and extra payment-processing fees. Gumroad has no monthly base fee and takes a 10% flat platform fee, plus gateway fees. For a solo creator, the fee is only part of the cost; the channel also takes time. Compare those fees against the hours you spend managing the channel.

More than 30% of ecommerce websites worldwide run on WooCommerce, which gives creators ownership of their business assets. That ownership matters when you are building a small owned stack. The marketplace can be a place to compare prices, test copy, or find an early buyer. It should not be the place where the customer lives. Keep the marketplace link as a test, not a dependency.