The riskiest moment in a website project is the design reveal. I try to move that moment to the very start, before any code is written.
A lot of bad experiences with developers follow the same pattern: the client doesn't see the design until the site is basically done, and by then it's expensive to change. I try to avoid that by deciding on the design first.
Why the late reveal hurts
- The client is reacting to a finished-looking thing, so any adjustment feels like a re-build.
- It's hard to separate 'the direction doesn't work' from 'I just don't like this colour'.
- Rework happens at the most expensive stage, after everything is wired up.
Show the design before writing code
For most projects I put a homepage direction together first — in your brand, before any code, before any invoice. If you don't like where it's going, we change it there, when it's cheap to change.
This is a genuine part of how I like to work. I'd rather spend a few days making sure the direction is right than a few weeks building in the wrong one.
What it means for the rest of the build
- The structure is settled, so the code gets written once.
- Colours, spacing and copy tone are agreed early.
- You're judging a plan early, not a surprise reveal at the end.
It's a preference, not a promise
Showing the direction early removes most of the risk, but it's not a guarantee everything goes smoothly. What I can say honestly is that most disagreements on websites are about direction, not execution — and direction is what we settle first.
If you're comparing developers, asking 'when do I see the design?' is a fair question. The answer tells you a lot about how they'll run the project.