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.