From design to deploy in 48 hours

Tight deadlines force you to strip away everything that doesn't matter. The trick is knowing what actually matters. Here is the 48-hour sprint I run with early-stage founders to ship a high-fidelity landing page without cutting corners on accessibility or performance.

The secret isn't working faster. It's ruthless sequencing, so no hour is wasted waiting on a decision that should have been made earlier.

Hours 0–6: content architecture

No design, no code. We decide what the page says and in what order: the one promise, the proof, the objections, the call to action. Most "design" problems are actually unresolved content problems. Settle the words first and the layout almost designs itself.

Hours 6–18: design on a locked token system

I design in Figma against a fixed set of tokens — type scale, spacing, color, radius — set on hour zero. Locked tokens mean every screen is consistent by construction and translates to code without a translation layer. This is the same modular discipline that keeps sites alive long after launch.

The component inventory I start with

I keep a standing kit: a hero, a logo bar, a feature grid, a testimonial block, a pricing table, an FAQ, and a footer CTA. Seven blocks cover 90% of landing pages. Starting from a proven inventory instead of a blank canvas is most of where the 48 hours comes from.

Hours 18–36: build with pre-wired components

Build happens in Next.js, or Webflow depending on who owns the site after launch, using components already wired to the tokens. Because the design used the same token system, build is assembly, not reinterpretation.

Hours 36–48: performance, accessibility, launch

The last block is non-negotiable quality: image optimization, semantic HTML, focus states, contrast, and a Lighthouse pass. I keep three budgets I never break — LCP under 2.5 seconds, CLS under 0.1, and a real accessibility pass. A deadline is not an excuse to ship something inaccessible.

Why it works

No all-nighters. The 48 hours work because the decisions are sequenced so each phase has everything it needs the moment it starts: content before design, tokens before screens, components before build, quality as a fixed final block.

That sequencing discipline is the same thing I bring to AI builds — prototype the riskiest piece first, measure, then expand. If you have a deadline that feels impossible, send me the brief. These are my favorite projects, and recent work shows how they turn out.