The launch discount that does not undermine your normal price

You have finished your product, opened the checkout and told people it is available. Then someone asks the question you were hoping to avoid: “Will the price go up later?” If you answer with a permanent discount, your launch price can quietly become the price customers expect. A better opening offer gives buyers a clear reason to act now without suggesting that your normal price is arbitrary.

Set the normal price before the launch price

Start with the price you expect to charge once the opening period is over. This is the reference point for every message that follows. If the normal price is £80 and the launch price is £64, the saving is £16, or 20%. That is easier for a buyer to understand than a vague claim such as “special founder pricing”.

The normal price should reflect the product as you intend to sell it, not only the first version. Include the time spent creating and supporting it, the result it is designed to help with, and the alternatives your buyer might otherwise consider. For a course, that might include the structure, lessons, exercises and access to your support. For a digital download, it might be the time it saves the buyer.

The arithmetic is simple: subtract the launch price from the normal price for the cash saving, then divide that saving by the normal price for the percentage. Showing both can help. The cash amount makes the saving tangible; the percentage makes it comparable.

Give the discount a credible reason

A discount feels less like a warning sign when it pays for a real difference between buying now and buying later. You might be asking early buyers to join before the first cohort begins, give feedback on the initial materials, or accept that some supporting resources will be added after launch. Say exactly which of these applies.

1. 1Name the early action: buy during the opening window, join the first live group or provide feedback after using the product.
2. 2Name what the buyer receives: the complete current product, a place in the first cohort, or the stated founding version.
3. 3Name what happens later: the price changes on a particular date, or the offer closes when the launch window ends.
4. 4Use the same explanation on the sales page, checkout and launch emails so the offer does not look improvised.

Avoid reasons you cannot verify. “We are celebrating” may be true, but it does not explain why the buyer should exchange money now. A credible reason connects the timing to the product or to your work: the first group starts on a date, the opening version needs a small group of users, or launch buyers are receiving an agreed early-buyer condition.

Make the end point difficult to misunderstand

A time limit only works if a buyer can tell when it ends. Use a date, time and time zone. “Available until 30 September at 23:59 BST” is clearer than “for a limited time”. If the launch price changes when the first live session starts, state that instead. Do not use a countdown that resets or an invented scarcity limit.

You also need an operational plan. Schedule the price change before you announce the offer, check the checkout after the change and remove old launch copy from places where people may still find it. If you use store.fan, its [discount tools](/features/discounts) can help you create a code or campaign, but the customer-facing promise still needs to be written and checked by you.

Choose a saving that protects the reference price

The right saving depends on what early buyers are being asked to do and how much certainty they have. A product that is already complete may need a smaller opening reduction than a first live cohort whose lessons will be refined with participant feedback. The discount should compensate for a defined difference, not for your discomfort about selling.

A useful test is to imagine the second sale. If someone buys at the normal price next month, can you explain in one sentence why they are receiving a different deal? “The opening price ended when the first cohort began” is a durable explanation. “I was nervous and reduced it by half” is not a pricing policy.

Present the offer without making the normal price look fictional

Keep the sales page orderly. Lead with the product and its result, then show the opening condition near the price. A compact section might read: “Opening price: £64 until 30 September at 23:59 BST. Standard price afterwards: £80. Early buyers receive the complete first version and will be invited to share feedback.”

Put the normal price beside the launch price rather than hiding it. Explain whether the offer applies automatically or requires a code. If buyers are joining a course, membership or community, include the start date and any access terms. You can use [store.fan](/features/store-designer) to present the offer in your own storefront, and paid plans start with a 14-day trial. Store.fan takes 0% of sales; Stripe's own processing fee still applies, and the money goes straight to your Stripe account.

After launch, keep the promise

When the deadline arrives, change the price. If a technical problem prevented people from buying, record the issue and communicate a specific correction rather than extending the offer silently. Then update your email links, pinned posts and sales page so the normal price is the one people see.

Review the launch by separating interest from sales. Count how many people reached the page, how many used the offer and how much revenue the launch produced after refunds and payment fees. You do not need a large audience to learn something useful; you need a clearly defined price, period and message. Store.fan's own Stripe connection keeps the payment path direct, while the iOS app can send instant sale alerts when a purchase arrives.