How to pre-sell a digital product before the full build

When a pre-sale is useful

Pre-selling is especially useful when the major risk is whether buyers will pay for the promised outcome. It is less useful when the product has technical feasibility risk that must be proven first, or when regulations require the full service to exist before sale.

Define the pre-sale offer

State exactly what the buyer receives, the planned delivery date or window, the format, any live support, the price, and what happens if you cannot deliver. Do not make the product sound finished if it is not.

Build the smallest credible sales page

You need enough information for an informed decision: buyer, problem, outcome, approach, deliverables, timing, price, terms, and CTA. Avoid spending weeks on design before you know the promise works.

Send qualified people, not random traffic

Start with people who plausibly experience the problem: existing audience members, relevant communities where promotion is allowed, customer conversations, direct outreach where appropriate, or a small paid test.

Set an evidence threshold before launch

Example: “If 5 of 40 qualified visitors buy at $49, continue. If fewer than 2 buy, revisit the offer before building.” The exact numbers depend on context; what matters is deciding the rule before seeing results.

Deliver the minimum sellable version

Once buyers commit, build for the promised outcome. Early customers can become excellent research partners, but they are customers—not unpaid beta testers unless that was explicitly the offer.

Pre-sale guardrails

• Be clear that the product is pre-release.
• Give realistic delivery expectations.
• Have a refund/remedy plan if delivery fails.
• Do not fabricate scarcity, buyers, or results.
• Keep records of the offer buyers actually agreed to.