A 7-day digital product launch, day by day: the calendar, the day that slips, and the Gumroad wall

Day four, ten past eleven at night, the top tier half-written and the landing page still a blank file. That is where a seven-day launch usually stands on Thursday, in my experience, and it is the point where the calendar either holds or quietly turns into a fourteen-day launch that nobody announces. I built the studio's sprint kit after running that week enough times to know which day breaks. This post is the calendar, not the pep talk.

Seven days is 168 hours. For someone doing this beside a day job, as I do beside mine at the trading company where I work, it is nearer twenty working hours, most of them at night. The calendar below assumes that budget, not a free week.

What does each of the seven days actually contain?

The sprint is a sequence, and the order is the whole point. Making before deciding is how a week produces three PDFs and no buyer.

1. Day one: decide, then stop. Run the niche through the four filters and pick one. The output of the day is a single sentence: who pays, what for, and why they cannot get it free. If the sentence is not written by bedtime, the week has not started.
2. Day two: design the ladder. Three tiers, priced, with a written list of what each one contains and what it does not. The top tier is the one sold by hand, so its price and its buyer decide the outreach list. Day two ends with the tracker filled in and still no product built.
3. Day three: build the bottom two tiers. The generation prompts do the bulk of this. The quality bar matters more than the volume: every file gets opened and read as a buyer would, because a refund on a $9 product costs the same trust as one on a $199 product.
4. Day four: build the top tier and the copy. The top tier is the part the prompts cannot fake. That is why it is the day that slips.
5. Day five: open the storefront. Upload, descriptions, the FAQ, the delivery emails, then a real test purchase from a second account. Everything on the launch checklist has to be true before day six, not "nearly".
6. Day six: wave one. The opener goes to the outreach list. Not the whole list. Enough to learn which objection comes back first.
7. Day seven: follow-ups and fixes. The first follow-up goes out, the questions from wave one get answered, and whatever wave one exposed in the product gets patched before wave two.

Two days of deciding, three of making, two of selling. When the making eats the selling, the week ends with a finished product and an empty inbox, which is the most common outcome and the one the calendar exists to prevent.

What do I cut when day four slips?

It slips because the top tier needs the one thing no prompt supplies, which is the maker sitting down and doing the hard part. The temptation at eleven at night is to thin the top tier and push on. That is the one cut I do not make. The order I cut in, from first to last:

• The third delivery email and any FAQ question past the seventh. I have not seen a refund because the thank-you sequence was two emails long.
• The entry tier's polish. It keeps its content and loses its formatting pass.
• The size of wave one. Ten messages on day six instead of thirty is still a launch.
• The date. If the top tier is not honest by the end of day five, day six moves to day seven and the follow-ups move to the following week. One day of slip is invisible to a buyer. A hollow top tier is not.

A launch that slips by a day is still a launch. A launch that goes out with a hollow top tier is a refund queue with a start date.

What never gets cut: the test purchase and the checklist. Both take under an hour and both catch the mistake that turns a launch into an apology.

Why does Gumroad stop at ten products a day, and which day does it bite?

Gumroad publishes its source code, so this one does not need guessing. The validation lives in a file called creation_limit.rb, and the error it returns is exactly: "Sorry, you can only create 10 products per day." The code counts products created in the last 24 hours that have not been deleted, and refuses the next one once that count reaches the limit. The default limit is 10; accounts Gumroad has marked compliant get 100. A comment in the same file, dated 8 August 2026, records that deleting a product now frees up quota, a deliberate trade-off so a seller who deletes a "test" listing does not lose the day.

The script I use to push the studio's catalogue up to Gumroad stops at ten creates and queues the rest for the next day. That line is there because of this validation, not out of caution.

For a sprint it bites on day five, and only for one kind of seller: the one who treats launch day as catalogue day. A three-tier ladder is three listings. Add a free lead magnet and it is four. The wall arrives when a backlog of old products gets uploaded in the same session because "the storefront is open anyway", and then it is the ladder's third listing that fails, with the launch checklist still open.

Two practical consequences follow from the code rather than from folklore. The window is rolling, not calendar: it is 24 hours from each create, so a batch made at 11 pm does not reset at midnight. And the count is of live products, so a deleted test listing gives the slot back. The ladder goes up first; the archive waits a day.

The manual inside The 7-Day Digital Product Sprint says plainly which part of the week only the maker can do. That part is day four, and the rest of the calendar is arranged so that day four gets its full share of the twenty hours.

The week is not seven days of making. It is a short argument with the calendar about which two days are for deciding, which three for building, and which two for selling, and the product only sells when the building loses that argument on time.

Sources

• app/modules/product/creation_limit.rb (Product::CreationLimit) · Gumroad source code, antiwork/gumroad on GitHub