Why launch speed is a growth metric

When we cut launch time for Pulse by 4.6×, the headline everyone wanted was efficiency — the team ships faster, saves hours, looks productive. That's true, and it's also the least interesting part. The real win was structural: a team that launches 4.6× faster runs 4.6× more experiments, and the number of experiments you run is one of the few inputs that genuinely compounds.

Most marketing orgs treat launch time as an operations problem to be tolerated. We treat it as a growth metric to be optimised, because the math is hard to argue with. Your win rate per experiment is roughly fixed by skill and luck. The total number of wins you bank in a year is your win rate multiplied by how many experiments you actually finish. You can't easily raise the first number — but you can raise the second by making launches cheap.

Speed multiplies your shots on goal

Say one in four experiments produces a real, durable lift. If launching is slow and a team manages eight a quarter, it banks two wins. Cut launch time enough to run thirty, and that same hit rate banks seven or eight. Nothing about the team's judgement changed — only the number of attempts. Over a year the gap between those two cadences isn't incremental; it's the difference between a channel that plateaus and one that keeps finding new ground.

This is why we're wary of teams that obsess over getting each campaign perfect before it ships. Perfectionism is expensive precisely because it lowers your shot count, and a lower shot count means fewer wins to learn from. Good enough, measured, and shipped beats flawless and delayed almost every time.

What actually makes launches slow

When we audit a slow launch process, the delay is rarely the creative work itself. It's the connective tissue around it:

• Re-building from scratch — every campaign assembled by hand instead of from templated, proven structures.
• Manual handoffs — assets emailed between tools, with someone waiting on someone else at each step.
• Bespoke tracking — UTMs and events wired up fresh each time, the most common source of broken reads.
• Approval queues — sign-offs with no clear owner, where a launch sits for days because nobody knows it's their turn.

We attack these with lifecycle pipelines, CRM triggers and templated launches — the same machinery behind the Pulse result. The goal isn't to remove human judgement; it's to remove the waiting, the re-keying and the silent failures, so the only thing standing between an idea and a live test is the decision to run it.

Tracking deserves a special mention, because it's the failure that hides. A campaign with broken UTMs still launches, still spends and still looks busy — it just produces a number you can't trust, which is worse than no number at all. By standardising the tracking layer once and reusing it on every launch, we don't only ship faster; we ship reads we can actually act on. Speed without clean measurement just lets you run bad experiments more often, so the two have to be solved together.

Cadence beats intensity

There's a quieter benefit that takes a quarter or two to show up. When launching is cheap, experimentation stops being an event the team braces for and becomes a habit it barely notices. A steady cadence of small, fast tests teaches an organisation more than a handful of large, carefully staged ones — partly because there are more results to learn from, and partly because the stakes of any single test are low enough that people are honest about what failed. Intensity burns teams out; cadence compounds, and it's cadence that automation is really buying you.

Automation didn't make Pulse's marketing cheaper. It made the team braver — when a test costs an afternoon instead of a fortnight, you stop rationing your ideas.

— David Hoffmann, Automation Lead

The takeaway

Launch speed isn't a vanity efficiency stat to bury in an ops report. It's an upstream lever on how much your marketing can learn, and learning is what compounds. If you want more wins, the most reliable move usually isn't a smarter strategy or a bigger budget — it's removing the friction that keeps you from running the experiments you've already thought of. Make launches cheap, and the rest of the system gets to do its job more often. That's why we count launch speed as a growth metric, and measure it like one.