Process
How we actually work.
Process descriptions at most agencies are aspirational. This is what ours looks like in practice — week by week, with honest timeframes.
Seven steps
From first call to handoff.
Total timeline is typically six to eight weeks for a full brand site or redesign. Stewardship is ongoing. Ecommerce varies by catalog size.
Discovery
Week 1We start with a conversation, not a form. One call, no agenda, no pitch. We talk about the business, the audience, what success looks like, and whether we're actually the right fit. If we are, we scope the work together. If we're not, we'll say so — and suggest who might be better.
Most agencies spend the first call selling. We spend it listening. By the end, you should have a clearer picture of what you need, regardless of whether that picture includes us.
Architecture
Weeks 1–2Before Figma opens, we map structure. Information hierarchy, content decisions, key user flows. We decide what lives on each page, what the site needs to communicate in what order, and where the structure can break down under real use.
Getting architecture right means we never design ourselves into a corner. A page that looks beautiful but buries the most important information is a failure regardless of how good the visuals are.
Design
Weeks 2–4We work in the browser early and often. Static mockups don't predict how something moves, loads, or reads on a phone at midnight. We prototype in code alongside Figma, make decisions about type and spacing with real content, and iterate with you throughout — not at the end of a long silence.
You're in the process during design, not at a presentation at the end of it. This means fewer surprises and better decisions made faster.
Development
Weeks 3–6The people who designed it build it. There is no handoff between designers and developers on our team. That continuity matters — decisions made in the design phase get honored in the build, and problems that emerge in development get solved without a game of telephone.
Production code from day one. Not a prototype cleaned up later. Performance, accessibility, and semantic structure are built in throughout, not added at the end.
Review + Refinement
Weeks 5–7We don't present a final site and wait for notes. You've been in the process throughout. By final review, there shouldn't be surprises — just decisions about small details. We run a structured cross-browser, cross-device pass and fix everything before anything is called done.
This includes Lighthouse audits, Core Web Vitals verification, accessibility checks, and a full link and form test. If anything is below target, it gets fixed before launch.
Launch
Weeks 6–8Deployment, DNS, analytics, and performance verification. We run a Lighthouse audit on every page. We check Core Web Vitals. We don't launch a site with an LCP over 2.5 seconds or a Cumulative Layout Shift anyone would notice.
Launch is not the finish line. It's the moment the work starts being tested by real people. We stay close for the first two weeks.
Handoff
Post-launchYou own everything. Code, assets, accounts, documentation. We walk you through the CMS if there is one, answer questions, and make sure you can run the site without us. If you want ongoing support, stewardship is available. If you don't, you're genuinely ready to go.
A site that requires us to change the headline is a site we've failed to build correctly. The handoff is designed to make us unnecessary.
The process starts with one email.
Tell us what you're working on, where you are in the process, and roughly when you need to launch. We'll come back with an honest take on whether and how we can help.