The 48-hour build is the most compressed engagement I offer. A single deliverable, two days of focused work, one output. The protocol is not a hack, it is a sequence with documented checkpoints. Every step has an exit criterion. If the exit is not met, the build pauses. Most of the time the exit is met. The rest of the time, the client gets a clear answer about why the work needed more time, and the scope adjusts.
Hour 0, Diagnosis
The build starts with a 30-minute diagnosis call. The client explains the problem, I ask questions, we agree on the deliverable. The output of the call is a one-line scope: "A landing page for product X, target audience Y, conversion goal Z." The scope is written in the Notion brief, signed by both parties, and locked. No scope changes after this point.
Hour 1-2, Setup
The repository is initialized, the CMS is connected, the deploy pipeline is configured. The type system is loaded from the studio’s component library. The starter template is the studio’s default Next.js + Tailwind + Framer Motion stack. The setup is reproducible, every sprint starts from the same foundation.
Hour 3-12, Design system
The design system is built for the sprint, not for the long term. The system includes type, color, spacing, button, input, and card. It is the minimum set of components the deliverable needs. The system lives in Figma and in the code repo. The two are kept in sync manually, there is no auto-sync, because the sprint is too short for the tooling to be worth the setup cost.
Hour 13-32, Build
The deliverable is built. Pages, components, content, integrations. The work is focused, with no Slack, no email, no calls. The sprint is a single, unbroken sequence. The exit criterion is that the build is functional in the staging environment, with all routes resolving and the CMS returning real data.
The 32-hour build window assumes zero context-switching. If the client needs a synchronous check-in, the window expands by the length of the meeting. Async is faster.
Hour 33-40, Polish
Polish is the second pass. Spacing, type, motion, micro-interactions, edge cases. The polish is documented in a Notion list, with each item checked off as it ships. The exit criterion is that the build passes a Lighthouse 95+ in all four categories, and the design is reviewed by a fresh pair of eyes (usually a friend in the industry).
Hour 41-46, Handoff
The deliverable is deployed to production, the DNS resolves, the analytics is connected, and the client has admin access to the CMS. A 30-minute walkthrough is scheduled. The walkthrough covers how to edit the CMS, how to deploy changes, and how to extend the design system. The work is theirs. The handoff is signed off in writing.
Hour 47-48, Receipt
The receipt is filed. The engagement is closed. The next sprint is scheduled if the client wants it. The receipt is a single line in the Notion database. The studio has shipped. The work is done. The system moves on.
“The protocol is not a hack. It is a sequence with documented checkpoints.
The 48-hour protocol is not for every project. It is for the projects where the scope is clear, the design system is small, and the deliverable is single. For larger projects, the protocol extends to two weeks, four weeks, twelve weeks. The same checkpoints apply, just stretched over a longer window. The discipline of documented exits is the same.
Need a focused sprint? See the Brand-to-URL sprint or book a diagnosis call.
