Launch Time Budget Template: Plan the Hours Before You Post Anything
A launch time budget is a sheet that lists every launch task, an hour estimate for each and the total you can spare. List tasks by phase, estimate in hours, add the time for replying to comments, and compare the total with the hours you actually have. If it does not fit, cut places to launch, not preparation. Log actual hours so your next estimate comes from your own history.
Why budget hours instead of just a to-do list?
A checklist tells you what to do. It does not tell you whether it fits in the time you have, and a side project rarely has much. Makers who plan a launch from a task list tend to meet the early items in full and rush the late ones, which are usually the replies, the follow-ups and the measuring. A budget fixes that by putting a price on every line before you start, so the cuts happen on paper instead of at midnight on launch day.
The unit is hours, because the constraint is your time, not money. Everything on the sheet below can be done for free; the free launch route is the premise of this whole site. If you have a day job, count only the hours you will really have. A launch plan that assumes eight clear days is not a plan for a person with evenings.
What goes on the sheet?
Five phases cover most launches. Under each, write the tasks that apply to your product and leave blank the ones that do not. A browser extension has store assets that a web app does not; a web app has a pricing page that a free open-source tool skips.
Hours I really have before launch: ____ Hours I can give in launch week: ____ Hours for the two weeks after: ____ PHASE 1: PREPARE THE PRODUCT Task | Estimate (h) | Actual (h) | Cut if short? (y/n) Fix the first-run path so a stranger reaches the main action | | | n Write the three-line explanation of what it does | | | n Test on a clean browser or device | | | n PHASE 2: PREPARE THE PAGE AND ASSETS Task | Estimate (h) | Actual (h) | Cut if short? Landing page or README | | | n Screenshots and a short clip | | | partly Icon and share image | | | partly Tagline and description variants | | | n PHASE 3: MEASURE Task | Estimate (h) | Actual (h) | Cut if short? Tagged links for each place | | | n A sheet for results | | | n PHASE 4: LAUNCH WEEK Task | Estimate (h) | Actual (h) | Cut if short? Submit to each place on the list (one row per place) | | | y, from the bottom Reply to every comment within a day | | | n Two follow-up messages to people who showed interest | | | partly PHASE 5: AFTER Task | Estimate (h) | Actual (h) | Cut if short? Read and sort feedback | | | n Fix the top confusion | | | n Write down what worked | | | n TOTAL ESTIMATE: ____ TOTAL ACTUAL: ____ DIFFERENCE: ____
How should the budget change for a weekend, two-week or month launch?
The phases stay; the scope of each changes. These are shapes to adapt, not hour counts, because nobody else’s numbers fit your product.
| Shape | Spend the most on | Cut first | Skip entirely |
|---|---|---|---|
| A weekend launch | The first-run path and one clear page | Extra directories, a video, a second share image | Newsletters and any outreach that needs replies over days |
| A two-week launch | Page, screenshots, tagged links and two or three places | Long-form posts, a pricing experiment | A press list |
| A month-long launch | A waitlist or beta, a post series and follow-ups | Nothing early; cut late-month places instead | Paid tools you would need to buy to try |
If you are working to a weekend limit, the weekend launch playbook lays out a day-by-day order, and the thirty-day launch plan is the same idea stretched across a month. The launch day checklist lists what must happen on the day itself.
How do you estimate without fooling yourself?
- Estimate in a small range, then use the high end. Write a low and a high figure for every task, and budget the high one. Writing, assets and replies tend to run long.
- Compare against a past project. If you have shipped anything, pull out how long the page, the screenshots and the announcement took last time. Your own record beats any advice.
- Estimate the work, not the wish. Ask what you will really produce in one sitting. A polished demo video is a different task from a thirty-second screen capture.
- Keep a buffer line. An empty row labelled “things I did not think of” with a fixed number of hours stops one surprise from deleting your replies.
- Log actuals as you go. The Actual column is the point of the sheet. After the launch, the difference between estimate and actual per phase is the correction to apply next time.
Do not invent a ratio you have not measured. If your page took twice as long as you thought, write down “my page estimates run about twice short” and use that on your next product, but only after you have seen it more than once.
What do you cut when the total is too big?
Work from the bottom of the value list. The order that usually loses least: second and third directories first, then optional assets such as a video, then long-form posts, then secondary languages. Do not cut the first-run fix, the tagged links or the reply time. The first stops the launch from wasting visitors, the second lets you learn anything, and the third is what turns a visitor into a conversation.
Pick launch places by cost to you, not only by size. Launch your product free here takes a form and one email click, which is among the cheapest steps on any sheet, while a place with a queue or a review step costs hours of preparation and waiting. The free launch platforms comparison says what each asks. Read how to launch without an audience if you have no list to post to, and browse the home and family ideas if you need something simple to practise on.
Frequently asked questions
How many hours does a product launch take?
It depends on the product and how much is already built, and no honest average exists. A small web tool with a page and one listing may take a weekend of focused work; a store submission with assets and review notes takes longer. Estimate each task, add reply time, and log your actuals.
What is the most underestimated launch task?
Replying. Comments and questions arrive on launch day and for a few days after, and each deserves a considered answer. Makers budget for building the page and forget the hours of conversation that follow. Reserve a fixed block each day of launch week.
Should I budget for paid promotion?
Not for a first free launch. This sheet counts hours only, and everything on it can be done at no cost. If you later consider paying to skip a queue, measure what the free route delivered first, using the sheet’s actual hours and your tagged results.
How do I stick to the budget?
Mark every task as cut-if-short before launch week starts, then protect the tasks marked no. When a task overruns, take the missing hours from the cut-if-short list, not from reply time or the first-run fix. Log actuals daily so the overrun shows early.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.