DIGITAL PRODUCT LAUNCH SALE PLANNER FICTIONAL WORKED EXAMPLE Product Client Project Planning PDF, a PDF checklist and example for freelance designers. Regular price $29 USD Launch code LAUNCH20 Discount 20% of $29 = $5.80 Discounted product price $29 - $5.80 = $23.20 USD before applicable tax and fees Revenue comparison At $29 each, 8 paid orders produce $232 before fees. At $23.20 each, 10 paid orders produce the same $232 before fees. That is 25% more paid orders after a 20% price cut. This comparison measures product revenue before fees, rather than profit. It does not predict that a discount will produce more orders. Worked fee example checked November 19, 2026 Starter direct-sale fee: 6.45% of 23.20 USD rounds to 1.50 USD. 23.20 - 1.50 = 21.70 USD before Stripe processing, tax-related obligations and other costs. This is not profit. Other plans and Marketplace routes have different fees. 1. DECIDE WHAT THE OFFER IS FOR Product and included files [ ] Buyer and problem the product helps with [ ] Reason for this sale [ ] Where your own audience will see the offer [ ] Success measure and observation period [ ] Choose a measurable goal. Keep the product's usefulness clear after the sale ends. 2. WORK THROUGH YOUR OWN NUMBERS Currency [ ] Reference price and when it was actually offered [ ] Discount percentage or fixed amount [ ] Discount amount [ ] Price after discount [ ] Genesize fee applicable to this plan and sales route [ ] Payment processing charge or estimate [ ] Expected support cost per order [ ] Refund allowance, if used [ ] Estimated amount after those fees and costs [ ] Discount amount = reference price multiplied by the percentage divided by 100. Discounted price = reference price less the discount amount. For equal revenue before fees, divide reference price by discounted price. Here, 29 / 23.20 = 1.25. Compare the same product and currency. Account for tax, fees, support and refunds separately. Use a reference price you can substantiate. Keep a record of when it was offered. 3. WRITE THE RULES Public code or automatically applied offer [ ] Exact public code, if used [ ] Eligible product or products [ ] Eligible currency [ ] Intended audience (a public code is not buyer access control) [ ] Start date, time and time zone [ ] End date, time and time zone [ ] Where the saving and final price will be explained [ ] How other offers will be handled [ ] What buyers see after the deadline [ ] A public code gives buyers a code to enter. An automatic offer applies the saving where supported. Check the available route in your selling tool. State an honest deadline and time zone. 4. DRAFT A SHORT OFFER Fictional copy for a creator's own audience Client Project Planning PDF includes a PDF checklist and example for your next client kickoff. Use LAUNCH20 for 20% off $29 USD. Your product price is $23.20 USD before applicable tax. Ends [date] at [time and time zone]. Check the product page for contents and offer terms. Your offer copy [ ] Your product link [ ] Place you are authorized to share it [ ] Match the actual offer. Share through channels you are entitled to use. 5. CHECK THE BUYER'S ROUTE Use an isolated test store with discount support for code and payment cases. Genesize's private buyer-experience simulation checks delivery; it does not validate a promotion in paid checkout. Inspecting a published page's quoted price without paying is a separate check. Do not activate a live campaign merely to manufacture failure cases. Valid eligible code [ ] The intended product price changes to the expected amount. Invalid code [ ] An incorrect code is rejected with a useful message. Expired code [ ] An offer past its deadline is rejected. Ineligible currency or product [ ] The offer is refused when its rules do not apply. Multiple offers [ ] A second offer does not create an unintended combined discount. Final review [ ] The currency, product, price, tax treatment and delivery terms are clear. [ ] A phone user can find the code field and understand the resulting price. [ ] The test result says whether the actual checkout accepted the code. Simulation covers the behavior simulated. If checkout never accepted the code, the test cannot prove it works in a paid checkout. Stop before payment. Keep email sending and live activation outside these checks. Test environment [ ] Test case and expected price [ ] Observed result [ ] Issue to resolve [ ] Retest date and result [ ] 6. REVIEW RESULTS AFTER THE OFFER Observation window and time zone [ ] Page views or tracked visits [ ] Reported code uses [ ] Confirmed real paid orders [ ] Confirmed paid orders using the offer [ ] Gross product revenue before fees [ ] Fees, processing and refunds [ ] Support time or cost [ ] Test orders and simulations excluded [ ] One change to consider next [ ] Keep code uses, views and test orders separate from confirmed paid orders. Match time windows and mark missing figures unknown. Traffic and timing also affect sales. These figures alone cannot prove the discount caused extra sales.