Why launches leak
A launch is not one project. It is four projects with dependencies: identity, website, campaign, and event. Each is usually owned by a different party, and each assumes the others will be ready.
The result is a launch that dribbles out over ten weeks — brand first, website a month later, campaign after that, event when the venue was free. Impact requires simultaneity, and simultaneity requires backwards planning.
Step 1: Fix the date and work backwards
Choose the launch date against real constraints: seasonality, festivals, competitor activity, production lead times, and readiness of the thing being launched.
Then map backwards. The critical path usually runs: positioning → identity → website content → website build → campaign creative → media booking → event production.
Identify what cannot start until something else finishes. Those dependencies, not the total work, determine your timeline.
Step 2: Lock the message before anything is designed
One message, expressed consistently everywhere. Write it as:
- One sentence describing what is launching and for whom.
- Three supporting points.
- The single action you want each audience to take.
Every asset traces back to this. Without it, the website, the campaign, and the event will each say something slightly different, and the market will hear noise.
Step 3: Sequence the build
Identity first, because everything else applies it. Core system plus the specific applications the launch requires.
Website next, with content written before design where possible. Content is the usual bottleneck, and design waiting for copy is the most common cause of slippage.
Campaign creative after the site, so ad promises match landing destinations exactly.
Event production in parallel, since it has independent lead times, but with creative drawn from the same system.
Step 4: Build the measurement layer early
Before any spend:
- Analytics and conversion tracking live and verified.
- CRM ready with campaign and source fields.
- Lead routing rules defined, including who handles launch-week volume.
- Reporting view built, so week one is measured rather than guessed.
Launch weeks produce the most concentrated data you will ever get. Losing it to untested tracking is an expensive, common mistake.
Step 5: Rehearse the week
Two weeks before, run a rehearsal:
- Submit a test enquiry through every channel and follow it to a human.
- Load every page on a mid-range phone over mobile data.
- Check every link in every asset.
- Confirm inventory, staffing, and capacity for expected demand.
- Brief everyone customer-facing on the message and the offer.
Most launch-week failures are not creative failures. They are a broken form, an untested payment path, or a team that had not been told what was being launched.
Step 6: Launch week choreography
- Website live and stable a few days early, indexed and tested.
- Announcement across owned channels on day one, all within the same window.
- Paid campaign activated with budget concentrated in the first days when attention is highest.
- Event mid-week, with content captured and published within hours.
- Daily standup: what is working, what is broken, what needs budget shifted.
Step 7: The follow-through nobody plans
Prepare these before launch:
- Follow-up sequence for enquiries generated during the week.
- Content plan for weeks two to six, so momentum does not vanish.
- Retargeting for everyone who engaged but did not convert.
- Sales briefing on objections encountered during the week.
- A retrospective, scheduled, with the data pulled in advance.
Launch weeks generate more attention than any other period. Businesses that plan only up to the launch date convert a fraction of what they generated.
The dependency map that saves projects
Before starting, list every deliverable with three columns: what it needs from someone else, who owns it, and the date it must be complete for the next item to start.
Circulate it. Most launch slippage comes from someone waiting on an input nobody realised was blocking, and a shared dependency map surfaces that in week one instead of week eight.
What success looks like
Every channel says the same thing in the same week, every enquiry reaches a prepared human, every asset points at a destination that works, and the follow-up was written before the launch rather than improvised after it.
That is the entire difference between a launch and an announcement.
