Twenty years ago, shipping software meant a fair amount of risk. A broken deploy could take down a product, and there wasn’t always a clean way to know what changed or undo it. The industry solved this. Version control gave every team a shared, authoritative history. Code review meant a second set of eyes before anything merged. Automated tests caught the obvious mistakes before a human had to. And rollback meant a bad deploy was a fast fix, not a crisis.
The same risk in marketing
Marketing runs a strikingly similar risk profile today, and never got the equivalent.
Twelve systems, no shared record
A modern marketing team touches a dozen systems to ship one campaign: analytics, ad platforms, a CMS, email, a CRM, commerce, design, docs. None of them talk to each other. There’s no shared repository of what’s currently live. There’s no review gate before a change ships: someone can update a price on the website without anyone in ad ops knowing the ad still references the old number. And if something goes wrong, there’s no rollback. Someone reconstructs what changed by hand across four dashboards. This usually happens under pressure, after a customer or an executive has already noticed.
Why the gap persists
The reason this gap has persisted isn’t a lack of care from marketing teams. It’s that the tooling was built for individual jobs, such as an ad platform for running ads or a CMS for managing pages. It was not built for the relationships between those jobs, which is exactly where things break. A price can be perfectly correct in the CMS and perfectly correct in the ad platform, and still be wrong, because they don’t agree with each other.
More volume, the same pipeline
What’s changed recently is the scale of the problem. AI-assisted tools have measurably increased how much content and how many campaigns a marketing team can produce. A meaningful share of CMO budgets now goes directly to AI. That is a lot more surface area, produced a lot faster, with the same fragmented, unreviewed pipeline it always shipped through. Volume without review is exactly the kind of problem that used to be someone’s job to catch by hand, and increasingly isn’t caught at all.
What release management is for
Software engineering’s answer to this, release management, wasn’t really about the code. It was about making the process of shipping trustworthy: a defined review before something goes live, an explicit approval decision, and a fast way to undo a mistake. That’s the layer marketing is still missing, and it’s the layer we built Launch to be.
Related reading
Two guides show the practices in detail. What release management means for marketing maps each software practice to a campaign, and why price parity breaks follows one common failure from cause to check. The marketing launch checklist lists the questions to ask before go live.
A two-time founder, David previously built and exited Voices.com, and currently also runs Lake.com. He's raised $27M and generated $200M in sales across his companies, and is a Harvard graduate.
All notes by this author