Swapna
Nair

There's a particular kind of silence that happens right after a client says yes. For a moment, everyone in the room is relieved — the deal is signed, the deck is approved. Then someone checks the calendar, and the silence breaks: we're live in seven days.

That's usually when people assume the panic starts. It doesn't, if the first day is spent correctly. The first day isn't for building anything. It's for asking questions most people are tempted to skip in the excitement of a signed deal. What does the client actually need this microsite to prove? Who signs off on copy, and how fast do they usually respond? Which internal team is the bottleneck, and can we get ahead of them today instead of on day four?

A launch that feels effortless on day seven is almost never the result of speed. It's the result of sequencing. Technology needs a locked scope before they can build anything real, so that conversation happens first, even if it means a slightly uncomfortable call with a client who wants to keep adding pages. Design needs the technology constraints before they can hand over anything usable, so that follows immediately after. Editorial needs both, plus a style guide, before a single word gets written. Get the order wrong, and everyone ends up building against a moving target — which is where most week-long timelines quietly become three-week timelines.

The part nobody sees is the coordination sitting underneath all of it. A single microsite touches sales, who sold the deliverable; design, who has to make it look like it belongs on the network; technology, who has to make it actually work; editorial, who has to make sure it reads like the brand and not like an ad; and outreach, who has already promised a client a specific number of guests attending launch. Every one of those teams has other priorities that week. Managing a launch like this is less about pushing people to move faster and more about making sure nobody is ever waiting on someone else without knowing it.

By day five, the shape of the thing is usually there, and this is the point where it's tempting to call it done. It isn't. This is when I go through it the way a guest would — not a colleague checking whether the sections exist, but someone landing on the page for the first time with no context. Does the first screen explain what this is, in one sentence? Does anything look like a placeholder that was supposed to be replaced three days ago? Is there a broken link hiding in a menu nobody clicked during testing? These are small things individually. Collectively, they're the difference between a client who trusts you with the next campaign and one who quietly starts asking for someone else on the account.

On launch day, my job has almost nothing left to do with building. It's making sure the client sees it before their stakeholders do, making sure the social team has what they need to post on time, and making sure that if something breaks in the last hour, it gets fixed before anyone outside the room notices. If it goes well, nobody remembers the seven days. They just remember that the microsite was live, on time, and looked exactly like it was supposed to.

That's the part I find genuinely satisfying about this work. Not the finished page — pages are just pages. It's the fact that twenty-five people across five teams, most of whom never spoke to each other directly, moved in the same direction long enough to make something that looks like it took one person a month, in a week that felt, from the outside, completely calm.