Every project begins with a blank file.
We do not carry components forward from one client to the next. We do not maintain a template library that gets reskinned. What we carry forward is judgment.
The things we actively refuse.
The easiest way to build a web design studio in 2026 is to build six or eight template skeletons — one for each industry — and reskin them per client. Change the colors. Swap the hero photo. Replace the copy. Charge $3,000 for four hours of work.
We don't do that. We don't do it for three reasons, in order of importance:
We don't use templates.
Every site starts from an empty project. The Google Business Profile for a solo lawyer, the new-patient intake funnel for a dental practice, and the portfolio architecture for a custom woodworker are not the same problem. Templates pretend they are.
We don't maintain a cross-client component library.
Components within a single site are obviously reused — a button is a button. What we don't do is carry a “dental hero section” or a “legal services grid” from last month’s project into next month’s. Every structural decision is made for the specific practice.
We don't start from another client's site.
Looking at a previous client's work for inspiration is fair. Opening a previous client's project file and saving a copy is not.
Two weeks from signed brief to live site. Five of those are production days.
The engagement runs two calendar weeks. Week one is preparation and intake. Week two is the five-day production sprint. Splitting the calendar this way is deliberate — the intake and content work can't be rushed without costing the quality of the build, and the build itself runs best as a concentrated five-day push with your attention on it.
Week one — intake and preparation.
Day one of week one is a forty-five-minute intake call. We look at what you have, what your best clients look like, and what the site needs to do. No deck, no prep required from you — come as you are and we'll drive. Most prospects are surprised at how short the intake is.
The remainder of week one is asynchronous. You send content — any existing copy, photographs, testimonials, practice details. We respond with a short brief document outlining structure, voice direction, and imagery plan. You approve the brief by end of week one, or we iterate until you do.
Week two — the five-day production sprint.
Day 1 — Monday. Structure and direction.
We make the real decisions: information architecture, which pages, which voice, which imagery direction, which standard patterns we're deliberately ignoring. This is the day the site stops being a brief and starts being yours.
Day 2 — Tuesday. First-pass build.
By end of Tuesday, there is a working draft of every page. Not final, but working — every section has real copy, real structure, and real layout.
Day 3 — Wednesday. Refinement.
We tighten copy, swap imagery, refine typography, check mobile behavior on every page.
Day 4 — Thursday. Revisions.
You react. We revise. If something is genuinely wrong — not a matter of taste, but structurally wrong for the practice — we rebuild the section without a change order.
Day 5 — Friday. Ship.
The site goes live on your domain by end of business Friday. We handle DNS, SSL, analytics setup, and the handoff call. Starting Monday, you're live, and the monthly retainer begins its first full month.
A five-day production sprint is not a corner-cutting promise. It's what becomes possible when you stop treating production speed and quality as a tradeoff. The AI tools that have made design and copy production faster do not replace craft — they free craft from the busywork that used to consume it. What used to be thirty hours of HTML and CSS is now four hours of judgment and two hours of revision.
The parts that can't be accelerated — the intake conversation, the structural decisions, the voice calibration, the revision judgment — get more of our attention, not less. Separating week one from week two protects the parts of the process that actually need time.
The month and year that follow.
The week after launch, we monitor the site for anything that breaks under real traffic. Rare, but it happens.
Month two is when the monthly retainer starts earning. Small edits — new staff bios, updated photos, a changed service list — are handled within forty-eight hours of request. Larger changes — a new service page, a significant structural change — are scoped and billed separately, but at a clients-get-the-better-rate discount to what outside agencies charge.
Month twelve is the buyout window. Clients who want full ownership of hosting can exercise a one-time buyout (twelve months of hosting, paid at once) and take the site fully independent. Most clients don't — the ongoing retainer is designed to be genuinely useful — but the option is always there.