What Does A Website Actually Need To Do?
We’ve recently been through the process of rebranding. Not just how we look, but how we talk about ourselves — what we say, what we don’t say and what really matters.
As part of that, we’ve been building a new website. And somewhere along the way, what felt like a relatively simple task turned into a much bigger question.
What does a website actually need to do?
It’s easy to assume the answer is everything. To tell your story, show your work, explain your services, prove your credibility, optimise for search, tick procurement boxes, look beautiful, work seamlessly on mobile, load quickly and convert.
But when you try to do all of that, you risk building something that does everything… and nothing particularly well.
We found ourselves asking whether we were giving people too much, or not enough. Whether visitors are really reading every word, or simply scanning for signals. Whether they want to explore in detail, or just understand quickly whether we’re right for them.
And perhaps more importantly, where are people actually going when they’re looking for their next partner?
Is it through a website?
A recommendation?
A conversation?
Or, more likely, a combination of all three?
We’ve always believed in being people-first, in real conversations and in taking the time to understand properly before proposing anything. So it’s been interesting to sit in front of a screen and question whether a website can ever really do that job.
Can it genuinely reassure someone that you’re worth investing in? Can it communicate how you think, how you work and how you show up when it matters? Or is it simply a starting point, a signal of credibility, clarity and intent?
Even the smaller decisions became bigger debates. Whether navigation should always be visible or intentionally stripped back. Whether to guide people through a journey or let them choose their own path. Whether to explain everything, or trust that less says more.
And then there’s mobile, film, structure and tone, each decision quietly shaping how someone experiences you before you’ve even spoken.
At times, it felt like we were designing for everyone. At others, we wondered if we should focus on the people we actually want to work with.
We used to talk about the idea of the “user chooser”, the understanding that people don’t just use something, they choose it. And we still believe that’s true.
So perhaps the role of a website isn’t to do everything. Perhaps it’s to do a few things well. To be clear, to be easy to navigate and to feel like you. To give just enough for someone to decide they want to know more.
Because ultimately, the best work doesn’t come from a perfectly structured website. It comes from a conversation that starts with a simple feeling:
“This feels right.”
We’re still shaping ours, and we’re genuinely curious.
What do you actually want from a website when you’re looking for a new partner? And what is it that makes you choose one?
If this resonates or challenges your thinking, we’d love to hear from you.