Why do clients often want design certainty before fee certainty?

 

One of the more difficult patterns in practice is this: the client wants increasing clarity about the design before they are willing to commit clearly on fees.

They want to know what is possible.
What can fit.
What the likely arrangement is.
How many units may work.
Whether the planning path is encouraging.
Whether council is likely to push back.
Sometimes even how value might be improved.

All of that can be understandable. Clients want confidence before they commit. But there is an uncomfortable asymmetry here. The certainty they seek is not free-floating. It is created through architectural judgment.

And yet the market often behaves as though that certainty should appear before formal appointment.

This is where architects can find themselves caught in a subtle trap. To win trust, they offer enough early direction to help the client feel reassured. But the more direction they provide, the more the client begins receiving the thing they were uncertain about paying for in the first place.

Design certainty starts arriving before fee certainty.

That should concern the profession, because it reverses the normal structure of service. Instead of the client engaging expertise to reduce uncertainty, the architect is encouraged to reduce uncertainty first in order to earn engagement.

The problem is not only commercial. It also affects behavior. Practices may begin oversupplying early clarity in the hope that it will secure the project. Clients may begin expecting more because the early flow of help creates a new baseline. The boundary between paid design work and unpaid pre-appointment reassurance becomes unstable.

To be fair, clients are not always acting strategically. Many simply want to feel that the project is sensible before they commit. But that does not change the fact that the work of creating that confidence is professional work.

The profession may need to ask whether it has become too comfortable with this sequence.

Should design confidence really arrive before fee commitment?
Or should fee commitment be what creates the conditions for design confidence to be responsibly developed?

A healthier practice culture might still allow for an introductory conversation and a broad sense of approach. But it would be more deliberate in protecting the stage at which architectural thinking begins creating real project clarity.

This is especially important in small practice. Every early-stage sketch, scenario, or directional comment carries opportunity cost. It uses time, attention, and judgment that could have gone into live work. If too much certainty is supplied before fee commitment, the architect carries both commercial risk and expectation risk at once.

Perhaps the more useful question is not whether clients want reassurance. Of course they do.

The better question is whether architects are giving away too much certainty in order to secure the work, and whether that habit is weakening both fees and boundaries.

The profession is unlikely to solve this through harder language alone. But it may solve part of it by clarifying where reassurance ends and paid design intelligence begins.

If certainty is valuable, it should not arrive by default.

How much unpaid feasibility work is too much?

Feasibility is one of the most interesting stages in practice.

It is also one of the most vulnerable to being undervalued.

At this stage, the architect may be reading the site, testing constraints, considering planning implications, sensing likely massing, identifying risks, commenting on access, parking, services, or levels, and helping the client understand what kind of project may or may not be possible. It may not look like “design” yet in the conventional sense. But it is often the point at which the project becomes commercially intelligible.

That is precisely why the stage matters.

It is not merely preliminary. It is often where the most consequential early judgment lives.

And yet feasibility is still frequently treated as something that can be partly given away.

Perhaps that happens because it appears light. No detailed drawings, no visible package, no polished output. Just advice, thoughts, options, professional reading. But this is exactly the problem. The less visible the output, the easier it becomes for the market to misread the value.

The architect sees risk, possibility, limitation, and sequence.
The client may experience that as “helpful early guidance.”

The difference between those two perceptions is where scope leakage begins.

Small amounts of unpaid feasibility can seem harmless in isolation. A short review, a quick comment, an early sense-check. But stacked together, they can amount to significant professional work performed before commitment. And because feasibility often reduces uncertainty for the client, it can become the very stage where the client derives major value while the architect carries major ambiguity.

That should prompt a serious question for the profession: should feasibility almost always be a paid first stage?

There will always be some variation by project type, client sophistication, and practice model. But if feasibility is the stage where risk is clarified and commercial direction begins to emerge, then treating it as optional-to-charge may be one of the profession’s quieter self-inflicted wounds.

The reluctance to charge is understandable. Some architects worry that asking for fees too early will scare off the enquiry. Some hope that flexibility at the front end will lead to trust and later appointment. Some feel that feasibility is too “light” to justify formal engagement.

But if the work changes the client’s understanding of the project, reduces uncertainty, or provides a basis for decision-making, it is already professional value.

The profession may need stronger language here.

Not defensive language.
Not legalistic language.
Just clearer language.

What is included in an introductory conversation.
What sits inside a paid feasibility review.
What the client receives from that review.
And why that early step deserves recognition as service rather than goodwill.

Feasibility is not a prelude to value. It is value.

The real question is not whether architects should be generous. It is whether generosity has been allowed to displace structure at exactly the stage where structure matters most.