Why Fees Break Down (And How to Think About Pricing)

Most architects have a proposal they look back on and wince.

Not because the fee was wrong exactly.

Because something about the conversation that followed felt like a negotiation they weren’t prepared for.

The client pushed back. Or went quiet. Or compared the number to something that had nothing to do with the actual work.

The architect – confident in the calculation – found themselves unable to explain it in terms that landed.

The reason that happens is structural.

Architects price from what the work costs to deliver.

Clients evaluate fees against what the outcome is worth to them.

These are different questions.

When neither party names that gap, the fee conversation becomes a negotiation about a number with no shared frame of reference.

That’s where most pricing problems actually begin.

The Calculation That Makes Sense Internally

The standard approach to architectural pricing starts with a familiar exercise.

Estimate the hours each stage will require.

Multiply by the relevant rates.

Add contingency for the things you know you’ve missed.

Build in the brief, the complexity, the consultants, the programme.

The result feels defensible. It represents the actual cost of delivering the work.

The problem is that this calculation is entirely internal. The client has no visibility of it. They don’t see the coordination calls. They don’t see the redraws. They don’t see the hours spent managing risk before it became visible.

The proposal arrives as a number.

And a number without context is just a number.

Why Fee Conversations Break Down

The most common friction point isn’t scope or budget. It’s mismatched assumptions about what the fee is actually for.

Fee disputes rarely emerge because clients want more drawings for less money.

They emerge because clients and architects often have entirely different assumptions about what successful delivery requires – and what that’s worth.

The client is evaluating an outcome.

The architect is defending a process.

Neither is wrong.

But they’re answering different questions.

And that misalignment, left unnamed, turns a fee proposal into a negotiation neither side fully understands.

What Clients Are Actually Buying

Architecture firms sell time. That’s how the business model works – hours priced at rates, multiplied across a programme.

But clients, with very few exceptions, are not purchasing hours.

They are purchasing an outcome.

Planning approval on a site they’ve been trying to move forward for three years.

A home that finally works – a kitchen that connects to a garden, a bedroom that a growing child can actually use, a house that functions the way the family lives rather than the way it was built.

A development that stacks financially and gets through without the cost overruns and disputes they’ve heard about from others.

Confidence that someone competent is managing complexity they don’t have the expertise to manage themselves.

The fee, from the client’s perspective, attaches to that outcome – not to the labour required to produce it.

Which is why two clients can respond entirely differently to identical proposals.

One sees the fee as expensive. The other barely questions it.

The number hasn’t changed. The perceived value of the outcome has.

Consider a residential extension.

A client might describe it as “only a small project.”

But that extension might open the back of the house to a garden a family has barely used for ten years. It might add a room that finally gives a teenager somewhere to study. It might be the reason the family doesn’t move, doesn’t uproot schools, doesn’t take on a larger mortgage.

The scope is small.

The outcome isn’t.

A practice that prices only from cost will often leave money on the table with clients who understand exactly what they’re getting.

The Structural Disadvantage of Effort-Based Pricing

There is a subtler problem with effort-based pricing alone.

Practices become more efficient over time.

Experience shortens programmes. Established relationships reduce friction. Tested details resolve faster. Mistakes that cost days on the fifth project don’t happen on the fifteenth.

In theory, this should increase profitability.

In practice, many architects discover something unexpected: the more efficient they become, the harder it is to justify fees based purely on the hours that remain.

Consider what that looks like in practice.

A junior architect might take three days to resolve a complex planning constraint.

An experienced architect might resolve the same problem in three hours – because they’ve seen it before, know which approach fails, and know exactly what the planning officer needs to see.

The client benefits directly from that experience.

But an hours-based model suggests the more experienced solution should cost less.

That’s not a quirk of one project. It’s a structural feature of effort-based pricing.

The better the practice becomes at delivering outcomes, the more the pricing model works against it.

Because the client isn’t paying for the hours.

They’re paying for the years that reduced them.

That value doesn’t appear in a cost calculation. It has to be named differently.

How to Think About Pricing

The internal cost calculation still comes first.

A fee that doesn’t cover the work is a worse problem than a fee the client questions.

That number is the floor – the minimum the practice needs to deliver the project without losing money.

But it shouldn’t be the only thing determining the fee.

The second question is: what is this outcome worth to the client?

A planning application on a site worth £800,000 with clear development potential is a different conversation to the same application on a site worth £120,000.

The work may be nearly identical. The outcome value is not.

A client who has been planning a project for four years and has a precise sense of what it will change has a different relationship to the fee than a client who is still deciding whether to proceed.

This isn’t a licence to price arbitrarily.

It’s a framework for understanding where the fee can reasonably sit – and for having a conversation that makes sense to both parties.

The Floor and the Ceiling

THE FLOOR – Cost to deliver

What it costs the practice to complete the work

Covers time, resource, risk, and overhead

Protects margin. Protects the business.

This number comes first. Always.

THE CEILING – Value of the outcome

What the result is worth to this specific client

Reflects project value, client commitment, and outcome significance

Creates pricing flexibility above the floor

This number determines how the fee is positioned.

Every proposal sits between these two points.

Most fee problems emerge when architects focus entirely on one and ignore the other.

A practice that prices only from cost will often leave money on the table with clients who understand exactly what they’re getting.

A practice that prices only from perceived value – without anchoring to delivery cost – will take on work that quietly loses money.

The firms that price most effectively understand both numbers.

They build the cost calculation with rigour.

And they position the fee with an understanding of what the outcome means to the specific client in front of them.

That’s not a formula.

It’s a discipline.

And it changes the fee conversation before it begins.