The best projects start with the right client
A studio confession, sparked by a podcast question we didn't expect to answer this
honestly.
On a recent podcast, someone asked what kind of projects Unbox says no to. I paused
— because in nine years of running this studio, we've rarely turned down a project.
Every brief has something worth solving: a site with an odd angle, a family that's
outgrown their home, a business that needs its space to work harder. Architecture is
rarely uninteresting once you're inside the problem.
What we've learned to say no to, almost always, is clients.
Not projects. Clients.
That's an uncomfortable thing for a design-build studio to admit out loud. But the
honest pattern, after fifty-plus projects, is this: the quality of a project has less to do
with the brief and more to do with who's holding it. A modest renovation with the right
client becomes some of our best work. A dream brief with the wrong client gets ground
down, meeting by meeting, into something safer than either side wanted.
So we've stopped screening projects and started screening clients. Here's what we
actually look for.
SIGNAL ONE
Do they push back with reasoning, or just override?
There's a real difference between “I don't love this — here's why” and “just make it look
like the picture.” The first is a collaborator sharpening the brief. The second usually
means the relationship is heading somewhere difficult.
We recently had to step away from a project where this signal showed up early, though
it didn't feel that way at the time. The client had studied design themselves, and we
were genuinely excited — a client who speaks the language usually makes for a sharper collaboration. But each meeting brought a new set of internet reference images,
presented as fresh ideas, with the ask to simply replicate them. There was no real
closure on anything. What we'd agreed on in one meeting would be reopened in the
next, and the drawings needed for a live site kept slipping further behind.
Eventually we made the difficult call to step away — after finishing every bit of technical
coordination, so the site wasn't left stranded. In hindsight, it was the right one. If a
project can be built entirely from a folder of screenshots, the role of the architect has
already been reduced to execution. That's not a collaboration we're able to do our best
work in.
FIELD NOTE — A RECENT PROJECT
New reference images every meeting, no real design closures, and drawings for a live site
falling behind. We stepped away only after every technical coordination was complete — so
the site was never left in disarray.
If a project can be built from a folder of screenshots, the architect's role has already been reduced to execution.
SIGNAL TWO
Do they want to understand the fee, or just reduce it?
Good clients ask what a fee covers — how scope changes are handled, what
construction administration actually involves, why a number is what it is. Those are
healthy questions, and we'd rather a client ask them than wonder quietly. What we
watch for instead is the push to extract more work for less money. That's usually the
warning sign that resurfaces once the project is running.
A fairly paid professional puts in every bit of effort a project deserves. A stressed one,
sooner or later, shows it in the work.
SIGNAL THREE
Do they check in like a person?
On another project, the client had a habit that seems small until you notice how rare it
is: they always came back with reasoning for why they preferred one option over another. It meant we had to think harder each time, to be doubly sure of what we were presenting — and the project was better for it. By the end, the outcome felt like a genuine co-creation, not a client approving a designer's homework.
That's the pattern across our best work. Clients who ask how the project — or the team
— is doing, not just for a status update, tend to stay reasonable when things inevitably
get hard. Because things do get hard. Every project has a difficult week. What decides
the outcome is who you're having it with.
The best projects aren't the ones where the client agrees with everything we say.
They're the ones where both sides care enough to question things, explain things, and keep pushing until the answer feels right. That's when architecture becomes genuinely collaborative — and those are usually the projects we're proudest of.
SIGNAL | WHAT IT LOOKS LIKE | WHAT IT PREDICTS |
Pushback | Reasoned disagreement, not override | A collaborative process |
The fee | Curiosity before negotiation | Respect for professional effort |
Check-ins | Asking how the team is doing | Trust when it gets difficult |
A Closing Thought
Your architect is human too. They're not just another vendor at the table — they're the
person responsible for carrying an idea from the first sketch through hundreds of
decisions, compromises, and difficult weeks.
Give them the same respect, clarity, and trust you'd want extended to your own work.
That's the real brief.
Comments