A week, not a moment
Release day is one day in a short run of them. Most of what makes it go well happens in the week before: the proof approved, the final files uploaded, the shop page filled in and checked, the announcements written, the early readers sent their copies. If all of that is done, the day itself is small. You check that everything works, then you tell people.
Three parts of a launch
- The week beforeFiles, proof, shop page, words drafted
- Release dayCheck it works, then tell people
- The days afterThanks, fixes, notes, rest
The days after matter too. Thank the people who helped, fix anything that went wrong, write down what you would change next time, and rest. Launching a book is tiring, and the next book needs you.
Plan what you control
You cannot control how many people buy your book, and no plan can promise sales, rankings or reviews. You can control whether everything works on the day, whether the people who would want to know are told, and whether you are rested enough to enjoy it.
In your hands, or not
So build the plan from tasks you can finish. A plan full of goals you do not control, such as a place in a chart or a number of reviews, can make a good week feel like a failure. A plan of tasks you can tick off gets done, and leaves you free to notice what happened.
Check as a buyer, then tell
When the book goes live, open its page as a stranger would, on a phone and on a computer. Is the cover right? Is the blurb there, with its paragraph breaks? Is the price right in each country you set? Are the categories the ones you chose? Does the sample start at the story? Are the ebook and paperback linked? Only then send the news.
On the day
- Open the pageOn a phone and a computer
- Check every partCover, blurb, price, sample, links
- Fix what is wrongBefore anyone sees it
- Tell people, oncePlainly, with the link
Tell the people who would want to know: your newsletter, if you have one, your writing friends, readers who asked to hear. Say it plainly and once, with the link. BlurbBio’s Launch Kit keeps your blurb, taglines, author bio and keywords in one place for this, and Cover mockups will make a picture of the finished book for your posts.
If you set the book up for pre-order, the platform will have its own deadlines for final files. Read its current rules before you pick a date you have to meet.
Example
A launch week on one page
A horror writer plans the week around her release. Notice where the work falls, and what is not in the plan.
Release: Thursday 30 October. Ebook and paperback.
By Friday 24th: paperback proof read and approved. Final files uploaded.1 Blurb, categories, keywords and price entered and checked against my notes. Newsletter and three short posts drafted, with an image of the finished book.
The day before: send the ebook to the six early readers who asked, with a note that an honest review would be welcome and is not expected2.
Thursday morning: open the shop page on my phone and laptop. Check cover, blurb, price in my three countries, the sample, and that the paperback and ebook are linked. Fix anything wrong before telling anyone.3
Thursday afternoon: send the newsletter. One post. Reply to whoever writes back.4
Friday to Sunday: thank the early readers who post anything. Write down what went wrong and what I would change. Two evenings off.5
- “By Friday 24th: paperback proof read and approved. Final files upl…”The heavy work is finished almost a week early, which leaves time to fix a problem.
- “an honest review would be welcome and is not expected”Early readers are asked for honesty, with no pressure.
- “Fix anything wrong before telling anyone.”Check, then tell, in that order.
- “send the newsletter. One post. Reply to whoever writes back.”Told once, plainly, and then she listens.
- “Write down what went wrong and what I would change. Two evenings off.”The days after are part of the plan, including rest. There is no sales target anywhere in it.
Before and after
All on the day, or spread out
The one faultEverything is left to release day, so there is no time to fix what goes wrong.
Release: Tuesday 3 June. Ebook and paperback.
On release day: upload the final files, order a proof of the paperback, write the blurb for the shop page, choose the categories and keywords, write the newsletter and posts, send copies to early readers, check the shop page, and tell everyone.
The two plans contain exactly the same tasks. The first puts all of them on release day. A paperback proof takes days to arrive, so the paperback will go on sale unseen. If a file is rejected, or the blurb loses its paragraph breaks, the writer finds out at the moment she wanted to be celebrating, and early readers get their copies too late to read them.
The second spreads the same tasks over the fortnight before. Each one has room to go wrong and be put right. On the day, only two things are left: check, and tell.
The exception
When to break it
A short story or a novella released quietly, to learn the process, can have a much smaller plan: check the page, tell a few friends, done. A writer whose readers are waiting for book four may need little more than an email. And some writers prefer a soft launch, letting the book go live, fixing what needs fixing, and announcing it a week later.
The parts that do not change are the order, check and then tell, and building the plan from things you can do rather than results you hope for.
Check yourself
Quick checkabout 2 min
It has gone live
A writer’s novel has just gone live, and her newsletter is written and ready. What should she do first?
Key takeaway
Do the work of a launch in the week before it, so release day is for checking and telling. Build the plan from tasks you control, never from sales or rankings. On the day, check the live shop page as a buyer would, fix what is wrong, then tell the people who would want to know, plainly and once. Leave time afterwards to thank people, take notes and rest.
