What is a launch retrospective?
- A post-launch review of a book's release.
- Covers sales, reviews, ad spend, and what to repeat or drop.
- Done within a few weeks while the data and memory are fresh.
- Turns one launch into reusable knowledge for the next book.
- Written down, not just thought through, so it compounds.
A launch retrospective is a structured review of how a book release went, done while it is still fresh. You look at the numbers — sales, reviews, ad spend, email and social results — and the qualitative side: what worked, what flopped, what you would repeat or drop. The point is to turn a single launch into reusable lessons for the next book.
Chapter i·Why it matters
Most authors finish a launch exhausted and move on, so every release starts from scratch. A retrospective captures what actually moved sales and what wasted money while you still remember the details. Written down, those lessons compound: by the third or fourth book, the launch is built on evidence instead of guesswork.
Chapter ii·What to include
- Sales by channel and format over the launch window.
- Review count and where reviews came from.
- Ad spend against measurable return.
- Email and social results — what drove clicks.
- A "repeat / drop / try next time" list.
- A date — file it where the next launch plan will find it.
Chapter iii·Example
Three weeks after launch, an author writes a one-page retrospective: the newsletter swap drove the most preorders, two podcasts converted well, and $300 of Facebook ads returned almost nothing. Next launch she doubles down on swaps and podcasts and skips the ads.
In WriteLoom
A launch plan, not a launch day
WriteLoom keeps your launch plan and results together, so each retrospective feeds the next book.
Not ready for a workspace yet? Get the free six-part series on winning the writing game: finishing drafts, editing in the right order, querying with real math, and launching on a runway.