It started on a Thursday afternoon. Our client called to say they’d pushed back the launch by three weeks β which meant the homepage we’d built around their old positioning was no longer the right homepage. The new messaging was ready. The brief was clear. We had a weekend.
**Why 48 Hours**
We didn’t choose this timeline. It chose us. But what it forced was something we’ve been trying to engineer deliberately ever since: ruthless prioritisation, faster decision-making, and a build process stripped of everything that isn’t strictly necessary.
**Friday: Direction in a Day**
We started with two hours of structured decisions. No exploration, no mood boards β just answers to four questions: What is the single most important thing a visitor should understand in the first five seconds? What action do we want them to take? What do we have in terms of assets? What is non-negotiable from the old design?
By noon we had a skeleton. By 6 PM we had a working prototype in the browser β not a Figma file, not a wireframe, an actual clickable page built in WordPress with real content.
**Saturday: Build and Iterate**
We split the work. One person handled the hero section and navigation; the other built the features section and the footer. We reviewed each other’s work every two hours, made changes on the spot, and didn’t let anything sit in a feedback loop.
The hardest decision was the hero. We had three directions and needed to pick one by Saturday noon. We went with the option that felt most like the client β not the option that was most technically interesting.
**What We Shipped**
A completely new hero with updated messaging and a split-screen layout. Rebuilt features section using a bento grid. New social proof strip. Simplified navigation. Tightened footer. All in 48 hours.
**What We Learned**
Speed doesn’t require compromise β it requires clarity. The constraint removed our ability to second-guess. Every decision had to be made and made once. The result was one of the most focused pages we’ve built. We’ve since adopted a version of this process β compressed timelines, real-browser-first prototyping, decision checkpoints every two hours β as a standard option for clients who need to move fast without losing quality.