Launches go wrong when the product is finished and nobody is waiting, or when an audience is warmed up for something that slips. These are two projects with one date between them, which is the only arrangement that makes the dependency visible.
Free on any plan. You will see this list again in the app, and nothing is created until you press install.
Measured on what happens after the announcement, not on the day itself.
Finished enough to be used by somebody who was not told how.
Starts on day one, alongside the build.
A launch fails when the product is finished and nobody is waiting, or when an audience is warmed up for something that slips. They are separate projects sharing a single date so the dependency stays visible.\n\nIf the date has to move, move both. Holding a launch date the product will not meet is the expensive version of this.
A month planned in advance and a weekly slot that fills it, so publishing stops being a scramble.
The first ten issues written on a schedule, and somewhere for readers to come from.
Fix what is broken, then write the pages worth ranking — in that order, because the second is slow.
One audience, one message, a date, and a number decided before anything is made.
It takes one press. Everything it creates is tagged, so if it turns out not to suit you, it is easy to find and remove together.
Install this template