A fee proposal is a business document, not just a price

Many architects treat the fee proposal as a necessary step on the way to the real work.

The client asks for a proposal. The practice prepares a scope, describes its services, sets out a fee and hopes the client accepts. Once the project begins, the proposal is often pushed into the background, while drawings, meetings, design decisions and delivery pressures take over.

That is a mistake.

A fee proposal is not just a price.

It is one of the most important business documents in the life of a project. If prepared well, it establishes value, clarifies assumptions, defines boundaries, sets expectations and reduces the likelihood of later dispute. If prepared poorly, it can create confusion that follows the practice all the way through the commission.

The proposal starts the relationship

By the time a client receives your fee proposal, they are already forming a view about how you work.

A clear proposal tells the client you are organised. A vague proposal tells them they may need to interpret too much. A confident proposal tells them you understand the value of your service. A defensive proposal can make the relationship feel strained before it begins.

This does not mean the proposal should be glossy, over-written or full of unnecessary legal language. It means it should be clear, thoughtful and useful.

The best fee proposals help the client understand not only what the architect will do, but why the service matters and how the project will be managed.

That distinction is important.

If a proposal only lists tasks and prices, the client may compare it with another proposal only on tasks and prices. If it explains the value of the service, the responsibilities being carried and the risks being managed, the conversation has a better chance of becoming a professional assessment rather than a simple price comparison.

What the fee really needs to explain

A fee proposal should do several jobs at once.

It should explain the project understanding. This tells the client you have listened and that your proposal responds to their situation, not merely to a generic service template.

It should define the scope of services. The client needs to know what is included, what is not included and where the limits sit.

It should identify assumptions. Many later disputes arise because assumptions were never made visible. Assumptions about programme, client decisions, consultant inputs, authority requirements, builder involvement, project budget, number of options or extent of documentation should not be left floating in the background.

It should set out exclusions. Exclusions are not negative if they are handled properly. They help prevent misunderstanding.

It should explain additional services. This is not just a contractual protection. It gives the client a fair understanding of what may happen if the project changes.

It should clarify the fee basis. Whether the fee is fixed, percentage-based, hourly, staged or a combination, the client should understand what drives the fee and what may cause it to change.

It should also explain the process for decision-making, approvals and change.

That may seem like a lot, but the purpose is simple: make the commercial relationship clear before the pressure of the project begins.

Value before numbers

One of the common weaknesses in architectural fee proposals is that the number appears before the value has been properly established.

The client sees the fee, but not always the thinking behind it. They see stages and deliverables, but not necessarily the judgement, coordination, risk management and guidance the architect will provide.

This is especially dangerous where clients are comparing multiple proposals.

If the value is unclear, the lower fee becomes more attractive.

The proposal should therefore help the client understand what they are buying. Not in exaggerated language, but in practical terms. What will the practice help them achieve? What uncertainty will it reduce? What decisions will it guide? What risks will it help manage? What experience does the team bring that matters to this project?

A good fee proposal makes the fee feel connected to value, not detached from it.

Scope clarity is commercial protection

Scope is one of the most important parts of the proposal because it becomes the reference point for the project.

If the scope is vague, both client and architect will fill the gaps with assumptions. Those assumptions may not match.

The client may assume additional meetings are included. The architect may assume they are not. The client may assume design options can continue until they are comfortable. The architect may assume a limited number of options. The client may assume authority changes are normal service. The architect may see them as additional.

None of these misunderstandings needs to involve bad faith. They can arise simply because the proposal did not make the boundary clear enough.

Good scope clarity protects the practice, but it also protects the client. It allows the client to make informed decisions about what they want, what they are paying for and what may change later.

Assumptions deserve more attention

Assumptions are often the most underdeveloped part of a fee proposal.

This is unfortunate because assumptions are where much of the commercial risk sits.

If you assume the client will provide timely decisions, say so. If you assume the project budget is sufficient for the brief, say so. If you assume the builder will not require substantial redesign during pricing, say so. If you assume authority requirements will be within a normal range, say so. If you assume consultant coordination will be limited to a defined level, say so.

Assumptions do not eliminate risk, but they make it visible.

That visibility matters when circumstances change. It is much easier to have a fair conversation about additional services if the original assumption was clear.

The proposal should still be readable

There is always a risk that, in trying to make fee proposals stronger, practices make them unreadable.

That should be avoided.

A good proposal should be clear enough for a client to understand and robust enough to manage the relationship. It should not feel like a legal trap. It should not bury the client in unnecessary complexity. It should not create anxiety where none is needed.

The tone matters.

The proposal should feel professional, confident and helpful. It should say, in effect: “Here is how we understand the project. Here is how we can help. Here is what is included. Here is what is not included. Here is how we will manage change fairly if the project shifts.”

That kind of clarity builds trust.

A document to return to

The fee proposal should not disappear once the project begins.

It should be returned to at key points. When the brief changes. When the programme shifts. When the client requests more options. When authority requirements expand. When builder input creates additional work. When assumptions no longer hold.

Used this way, the proposal becomes more than a record of the original agreement. It becomes a project management tool.

This is how mature practices treat it.

They do not rely on memory, goodwill or vague understandings. They use the proposal to keep the commercial relationship aligned with the actual work being performed.

A strong fee proposal will not solve every problem.

But a weak one can create many.

If architects want better fees, better client relationships and better scope control, the fee proposal is one of the best places to start.

---

Ross Clark has worked across the architecture industry in almost every capacity — the guidance that he brings from decades working in this industry has been tried, tested and refined working closely with practices just like yours.

If you’re thinking about the next stage of your practice, or want an experienced perspective on how things are currently set up, please reach out.

Get in touch