Six phases, in the same order, every time.
This is how a Four Eyes website project runs from first call to long after launch. Predictable on the inside so the launch can be quiet on the outside. Durations are typical for a mid-size site and are quoted per project.
Surprises in week eleven come from decisions skipped in week one.
We design against your longest headline and your worst photograph.
Most project overruns are not caused by hard engineering. They come from starting design before the content is understood, or launching before the redirects are mapped.
So the order is fixed. We find the real constraint before we draw. We model the content before we design around it. We design against your longest headline and your worst photograph, because templates that only work with ideal content are not templates. We measure while we build, not at the end. We launch with the redirects already in place. And we stay reachable afterwards.
What it asks of you. One decision-maker, timely feedback at each phase, and content on the schedule we agree. Content readiness is the most common cause of delay, so we plan it in discovery rather than hoping.
What stays flexible. The phases are fixed. The scope inside them is not. A five-page site and a membership platform run the same order at very different depths.
From first call to long after launch.
Find the real constraint.
Analytics, Search Console, the plugin stack, and the internal workflow nobody wrote down. We look before we draw.
Model the content first.
Post types, fields, taxonomies, URLs. Get this wrong and every template fights you for the next five years.
Draw against real content.
Your longest headline, your worst photograph, your densest table. Reusable patterns rather than one-off pages.
Engineer it, then measure it.
Weekly demos, performance budgets held as we go, and accessibility checked at AA before anyone sees a staging link.
Move without losing rankings.
Redirect map, content parity check, analytics wired, monitoring switched on before DNS. Most rank loss at launch is a redirect problem.
Stay the person who picks up.
Core and plugin updates, backups, uptime, and a direct line to the engineer who built it. No ticket queue.
A publishing workflow the marketing team stopped dreading.
Camp North End runs constantly shifting content. The content model came first, so the templates matched what the team publishes every week.
Read the Camp North End case study
Often paired with
Website Design
The full build this process describes, start to finish.
Website designWebsite Maintenance
Phase six as a standing service: updates, monitoring, backups, small changes.
Website maintenanceSecond Opinion Audit
Not sure what is wrong yet? Start with a written read of where the site stands.
Second opinion auditWhat people ask about how we work.
A typical mid-size build runs about eight weeks from kickoff to launch. Larger sites, heavy content, and integrations take longer. You get a written schedule with the scope.
The person on the first call is the person who builds the site. There is no account manager in between and no handoff after kickoff.
After a short call and a look at what you have, we give a written scope and a fixed figure for that scope. Changes to scope are agreed in writing before they are built.
One decision-maker, feedback at each phase within the agreed window, and content on the schedule we set together in discovery.
Training, written documentation, and a direct line. Ongoing maintenance is available as a plan, and most clients take one.
Tell us what you are planning.
The short form is enough to start. An expert reads it and replies within one business day with concrete next steps.
Brief reviewed by an expert within one business day. Thirty-minute call. Written scope within five days.
“I have built Web sites with a wide array of teams over the past 20+ years. It's been my pleasure to work with excellent designers, but none have come close to the level of ownership, intelligence and guidance Four Eyes Productions provided…”
"*" indicates required fields
Goes to Michael. No CRM, no autoresponder, no newsletter signup.