How to Presell a Digital Product Before You Make It

There is a specific kind of pain that only builders know: you spend weeks making something, launch it, and hear nothing. The work was real, the effort was real, and the market's answer was silence. The frustrating part is that the market could have told you the same thing in a few days, for free, before you built anything. You just did not ask it in a way it could answer.

Preselling is asking in the way that gets a real answer. Instead of building first and hoping, you describe the product clearly, put a price on it, and try to get people to pay or firmly commit before it exists. A real payment is the only validation that fully counts, because it is the only signal where someone put money behind their interest. Done honestly, preselling does two things at once: it proves demand before you sink time into building, and it funds the build with your customers' money instead of your own. This guide is about doing it in a way that is both effective and completely fair to the people who buy.

Where does the money actually come from?#

Preselling flips the normal order of building and getting paid. Normally you spend your time and money first and find out about demand last. Preselling puts the demand test and the funding first, before your biggest cost. Trace it and the advantage is obvious.

You describe the product clearly (it does not exist yet)
        |
        v
You put a real price and a real delivery date on it
        |
        v
People decide: is this worth paying for, now?  <-- almost no one pays, stop here
        |
        v
Enough people pay or firmly commit
        |
        v
Their money funds the build   <-- customer capital, not yours
        |
        v
You deliver on the promised date
        |
        v
You keep the revenue and now have real customers

The money comes from customers deciding, before the product exists, that the promised result is worth paying for. That decision is the validation you actually needed, and the payment is capital you can use to build. Compare that to building first: there, all your cost comes before any signal, so a failed product costs you everything and teaches you late. Preselling moves the risk to the front, where it is cheap. A payment is a far stronger signal than a survey or a "yes I would totally buy that," because talk is free and money is not. This is validation in its most reliable form, and how to validate a digital product covers the weaker signals you should treat with more suspicion.

How it actually works#

The core move is simple to state and takes nerve to do: create the sales page for a product that does not exist yet, and ask for the sale. Everything else is making that fair and making it convert.

Start with a clear description of the transformation the product delivers. Preselling does not work if buyers cannot picture what they are getting, and it works even less if the promise is vague. You are asking people to pay on the strength of the promise alone, so the promise has to be specific and believable. This is where preselling and good product design meet: a sharp transformation is what makes both the presell and the eventual product succeed.

Then set a real price and a real delivery date. The date is not optional and it is not decoration. It is the commitment that keeps you honest and gives the buyer confidence. Pick a date you can actually hit, and if anything, pad it, because delivering early is a delight and delivering late erodes the trust the whole thing runs on.

Make refunds easy and say so plainly. This is the part that separates honest preselling from taking money under false pretenses. Tell buyers clearly that the product is not built yet, that it will arrive on the stated date, and that they can have their money back if you fail to deliver or if they change their mind before delivery. Easy refunds are not a weakness here. They are what makes it fair to ask for money on a promise, and they lower the fear that stops people from being your first buyers.

You do not always need to take full payment to validate. Sometimes a paid preorder at a discount is right. Sometimes a small deposit is enough of a commitment to prove intent while lowering the buyer's risk. A waitlist alone is weaker, because joining a list costs nothing and predicts little, but a waitlist you then convert into paid preorders can work well as a two-step. If you want the mechanics of building that list first, build a launch waitlist that converts covers it. Whatever the exact mechanism, the principle holds: the stronger the commitment you ask for, the more honest your signal.

Set a threshold before you start, so the result means something. Decide in advance how many sales or commitments would tell you the product is worth building. That way you are running a real test with a pass or fail line, not just fishing for encouragement and rationalizing whatever you get.

A clearly hypothetical example#

These numbers are invented to show the shape of the decision, not a promise of what you will see. Yours will depend entirely on your audience and offer.

Say you want to build a template pack for a specific niche and you expect it to take three weeks to make well. Rather than spending those three weeks first, you write a one-page sales page describing exactly what the pack includes and the result it delivers. You set the price at 40 dollars, a presell price of 25 for early buyers, and a delivery date four weeks out. You state plainly that it is being built, names the date, and promise a full refund to anyone who wants one before delivery.

You decide in advance that 20 preorders would prove it is worth building. You put the page in front of your audience or the communities where the niche gathers. Say 30 people buy at 25 dollars. That is 750 hypothetical dollars and, more importantly, a clear pass on your threshold. You now build the pack knowing 30 people already want it, and their money covers your tools and your time. Deliver on the date and you have 30 happy customers and proof to sell to the next batch at the full 40.

Now the other branch. Suppose only 3 people preorder. That is disappointing, and it is also the best possible outcome short of a yes, because you learned it in a week instead of after three weeks of building. You refund the 3 buyers, thank them, and either sharpen the offer or move on. Either way you spent days, not weeks, finding out.

What you need (required vs optional)#

Required:

• A clear, specific description of the product and the result it delivers, good enough that someone can decide to pay on the promise alone.
• A real price and a real, achievable delivery date.
• A simple sales page or offer and a way to take payment or preorders.
• A stated, easy refund policy and the genuine intention to honor it.
• A small audience or access to the communities where your buyers gather, so there is someone to make the offer to.

Optional but helpful:

• A preset threshold for how many sales mean "build it," decided before you launch so the result is honest.
• Some proof you can deliver, such as a sample, a mockup, or a track record, which raises how many people are willing to pay on a promise.
• A waitlist you have warmed up in advance, so the presell does not launch to silence.
• A discount for early buyers, since asking people to pay for something that does not exist yet fairly earns them a better price.

What it costs#

The out-of-pocket cost of preselling is low: a sales page and a payment method. The real cost is the discomfort. Asking people to pay for something that does not exist feels exposed, and a weak result stings because it is a clear, early no. That sting is the value. It is cheap information delivered before your expensive work, which is exactly when you want bad news.

There is one cost you must be willing to carry: refunds. If you presell and cannot deliver, or buyers change their minds before the date, you refund them without friction. Build that into your thinking from the start. It is the price of doing this honestly, and it is far cheaper than the reputation cost of taking money you do not return. Charging before you build is a legitimate and old practice when it is done cleanly. Charge from day one makes the broader case for not being shy about asking for money early.

How long it takes#

Setting up a presell is fast. Writing the offer, building a simple page, and putting it in front of people can happen in a few days. Running the test long enough to get a meaningful answer usually takes a week or two, depending on how much reach you have.

The part that takes real time is still the build, but now it happens with proof and funding behind it, which changes everything about how it feels. You are no longer building on hope. You are fulfilling orders. Give the presell enough exposure to be a fair test before you read the result, since a tiny audience can produce a misleadingly small number of sales that says more about your reach than about demand.

What beginners usually get wrong#

The biggest and most damaging mistake is preselling dishonestly: implying the product already exists, hiding that it is not built, or taking money with no real plan or intention to deliver. That is not validation, it is deception, and it destroys trust you cannot easily rebuild. Say plainly that it is being built, name the date, and mean it.

The second mistake is skipping the delivery date or setting one they cannot hit. A missing date makes buyers nervous and makes you unaccountable. An unrealistic date sets up a broken promise. Pick a date you can beat.

The third mistake is treating a free waitlist or a pile of "I'd definitely buy that" comments as validation. Interest is not intent. Money is intent. If you want a signal you can trust, ask for a payment or at least a deposit, because that is the only response that costs the person something.

The fourth mistake is having no threshold and reading whatever happens as success. Two sales can feel encouraging in the moment and still mean the product is not worth building. Decide your pass or fail line before you launch, so the test tells you something instead of just flattering you. And once a presell succeeds, do not stall on the build. The commitment you made is the whole basis of the trust, and this format leans on the same launch discipline covered in how to launch a digital product.

How I would start#

1. Define the product and the specific transformation it delivers, sharply enough that someone could decide to pay on the description alone.
2. Set a real price, a fair early-buyer discount, and a delivery date I am confident I can hit.
3. Write a simple sales page that is honest about the product not existing yet and clear about the delivery date and the refund policy.
4. Decide, before launching, how many sales or paid commitments would prove it is worth building.
5. Put the offer in front of my audience or the communities where the buyers gather, and ask for the sale or a deposit, not just interest.
6. If I hit the threshold, take the money, keep the refund promise available, and start building immediately with the delivery date as my deadline.
7. If I miss the threshold badly, refund everyone cheerfully, thank them, and either fix the offer or move on, glad I found out in a week.
8. Deliver on or before the date, collect proof from the first buyers, and use it to presell the next version with more confidence.

What I would not do#

I would not pretend the product already exists or hide that it is being built, because the entire honesty of preselling rests on that disclosure. I would not take money without a real, achievable delivery date and a genuine intention to deliver. I would not refuse or slow-walk refunds, since easy refunds are what make it fair to ask for money on a promise. I would not treat a free waitlist or verbal enthusiasm as proof and start building on the strength of talk. And I would not spend weeks building first and preselling never, because that is the exact mistake preselling exists to prevent. If a course is what you are considering building this way, how to create an online course that sells pairs directly with this approach.

The bottom line#

Preselling moves the risk of building a digital product to the front, where it is cheap. You describe the product, price it, name a real delivery date, offer easy refunds, and see whether people actually pay before you build. A real payment is the only validation that fully counts, and the money you collect funds the work with customer capital instead of your own. The one rule that cannot bend is honesty: be clear the product does not exist yet, deliver when you said, and refund without friction. Do it that way and preselling stops being risky or shady. It becomes the smartest possible order of operations. For the pricing side of the offer you put in front of buyers, how to price a digital product is the natural next read.