The landing page that took six weeks

You needed a landing page by Thursday. Campaign budget was signed off. Brief was written. The team was ready to drive traffic to it. You briefed the agency.

Then the waiting started.

First, the brief document the account manager needed before they could open a project. Then an internal kickoff call. Then a creative concepts presentation, three directions, none quite right, all needing "a round of feedback." Then a design file. Then a revision. Then a development handoff. Then a review link that didn't work in Safari. Then another revision.

Six weeks later, the page was live. The campaign window you planned around had half-closed. The team driving traffic had moved on to other things. The moment passed.

Agencies are slow even when they're trying not to be

Agency slowness isn't usually laziness. It's structure. Every layer of the process exists for a reason, usually to protect the agency from scope creep, miscommunication, or client dissatisfaction. The briefing document, the concepts stage, the sign-off cycle: these are process controls, not value generators.

They protect the agency. They cost you time.

By the time your brief has moved from account manager to project manager to designer to developer and back again, two weeks have gone. Not because anyone is bad at their job. Because that's how many handoffs the process requires.

If you've sat in a status meeting watching a junior account manager paraphrase your own decisions back to you, you've experienced this in its purest form. The meeting isn't creating value. It's creating a record that the meeting happened.

Every handoff is a delay. The agency needs them. You don't.

The CMS problem is separate but equally annoying

Sometimes there's no agency. The bottleneck is a developer ticket.

You have a brief, a design, copy written and approved. But to get the page built in your CMS, you need a developer. And the development queue is six weeks long, because the development team is building the product, not serving marketing.

Some CMSs let marketers ship independently. Most, especially the enterprise ones bought by a committee, don't. The trade-off made five years ago (this platform scales, it's secure, it integrates with Salesforce) now means you can't move a text block without raising a ticket.

The cost isn't visible on any dashboard. It shows up as campaigns that don't ship on time, tests that never get run, ideas that die in a queue. Nobody writes up the leads they didn't generate. Which is why the pattern repeats. And it's not just the queue: a page that finally ships but loads slowly quietly repeats the same problem in a different disguise.

The revenue number nobody runs

Say the campaign was supposed to generate 200 leads over four weeks. At a 3% conversion rate, that's roughly 7,000 visitors needed. You shipped two weeks late. You ran for two weeks instead of four. You generated half the leads.

The budget was the same. The opportunity cost was real. It just doesn't appear in the post-mortem, because nobody writes up the leads they didn't get.

Take the expected lead volume for your campaign period. Divide by the number of weeks. Multiply by however many weeks you lost. Multiply by your average lead value. Look at the number. It's usually uncomfortable.

The invisible cost is the one that never gets fixed.

Fewer handoffs, faster shipping

The brief goes directly to the person doing the work. No handoff. Questions get answered on Slack, same day. A first draft is up within 48 hours. You review it, mark it up, it's revised the same afternoon. It goes live when you say it goes live.

This isn't a fantasy. It's what happens when the person scoping the work is the person building it, and the process is designed around shipping rather than around protecting margins.

I've been on the other side of this. At Dropbox and Joblogic, I built content programmes that involved agencies, developers, CMSs, the whole infrastructure. I know which parts of that process add value and which parts are ceremonial. When I work with a team now through Zenlio Studio, we skip the ceremony.

When this model doesn't work

Worth being direct about the limits. One person working fast is not the same as a large agency working slowly. If you need five languages, a global rollout, and a team of ten specialists on simultaneous tracks, a studio model won't cover it.

But for most in-house marketing teams, the ones running campaigns, testing messaging, launching features, building landing pages, the bottleneck isn't headcount. It's process. And the fix for a process problem is not more people. It's fewer handoffs.

Got a page that needs to be live by Thursday?

Tell me what you're building. I'll tell you whether I can help and when it can ship. No briefing document required.