01Services
Design and engineering under one roof, from the first sketch to the hundredth page your team publishes.
All services→02Studio
Nine people, six projects a year. Here is who we are and how we like to work.
About the studio→ProcessFive phases, one team
Every Zuzo project follows the same five phases, in the same order, with the same people. You always know what is happening this week, what comes next and what you will have at the end of it.
The order of work matters more than the speed of it.
We research before we design, design the system before the pages, and build while we design so nothing gets lost in a hand-off. It sounds slower. In practice it is faster, because nothing needs redoing in week nine.
01The five phases
Phases overlap on purpose. Engineers join while the design system is still taking shape, so the build starts with fewer surprises and launch comes sooner.
01 / 05 · Weeks 1 to 2
We interview your team and a few customers, dig through your analytics and audit every page you have. It ends with a short brief, a sitemap and a fixed price for the rest of the project.
From youTwo workshops and a few short calls
02 / 05 · Weeks 2 to 5
We design the parts before the pages: type, colour, spacing and components. Key pages are then assembled from those parts, so the whole site feels like one brand from day one.
From youA weekly review and quick feedback
03 / 05 · Weeks 4 to 6
We decide how the site moves: easing, timing, scroll behaviour and any 3D moments. Prototypes run in the browser, so you judge the real feel on your own devices.
From youTry the prototypes on your own phone
04 / 05 · Weeks 4 to 10
Components are built as they are designed, tested for accessibility and speed, and connected to your CMS. Your editors start working in it before launch, not after.
From youContent and an hour of editor training
05 / 05 · After launch
Launch is the start. A settling period catches anything real traffic reveals, then a retainer keeps the site improving with new pages, experiments and quarterly audits.
From youA monthly planning call, if you choose a retainer
02Before we start
We listen, ask questions and tell you honestly whether we are the right fit.
A short document with our understanding, the approach and a realistic budget range.
A fixed fee. You keep the brief, sitemap and audit even if you build elsewhere.
A fixed price and timeline for design and build, broken into clear phases.
03Working together
No surprises
A few habits that keep projects calm, decisions quick and everyone looking at the same thing.
01
Every week you see working pages in the browser, not slides about progress.
02
We join your Slack or Teams. Questions get answered in hours, not at the next meeting.
03
The people on the first call do the work. No account managers passing messages along.
04
Figma files, code and the project board are yours to see at any time.
04FAQ
Something else on your mind? Email the studio and a designer, not a salesperson, replies within a day.
Most brand websites take six to twelve weeks from the start of discovery to launch. Large headless builds, several languages or big content migrations can take longer. You get a firm timeline at the end of discovery, before you commit to the build.
Because guessing is expensive. Two weeks of research and planning lets us give you a fixed price instead of a padded estimate. It has a fixed fee, and you keep the brief, sitemap and audit even if you decide to build with someone else.
Usually two to three hours a week from one decision maker, plus two workshops during discovery. Your editors need about an hour of training before launch, and some time to add content.
We demo working pages every week and collect comments in one place, usually Figma or the project board. One named person on your side makes the final call, which keeps decisions quick and avoids feedback loops.
Every project includes a two-week settling period where we fix anything real traffic reveals. After that, many clients move to a monthly retainer for new pages, experiments and audits, which can be paused any month.
Loosely. We plan in one or two week cycles that each end with a demo, but we do not bury you in sprint ceremonies. You see progress in the browser every week and always know what comes next.
05Start a project