The Problem With Time-Based Fees

Time-based fees make sense on paper.

You estimate the hours a project will require. You apply a rate. You account for the stages. You arrive at a number that reflects the actual cost of doing the work.

This is not a bad place to start. Every practice needs to understand its costs. The calculation that produces that floor is not wrong.

But it is incomplete.

Time tells a practice what the work may cost to produce. It does not always tell the practice what the work is worth.

That gap – between cost and value – is where most small practices lose money. Not through carelessness. Not through difficult clients. Through a pricing logic that measures the visible work accurately while leaving much of the real value unpriced.

The Visible Work and the Work Behind It

Clients see outputs.

They see the drawings. The planning package. The specification. The tender information. The meeting notes. These are the tangible products of the engagement, and they are what most clients assume they are paying for.

But behind those outputs sits a different layer of work – one that rarely appears on a timesheet, and rarely gets priced explicitly.

Interpreting what a client actually wants, as opposed to what they have said. Identifying which approach is likely to hit planning problems before any drawings are produced. Knowing which options are worth testing and which will waste three weeks.

Keeping the project coherent across disciplines when consultants are pulling in different directions. Holding a client to a decision they are starting to reverse because reversing it now will cost them more than they understand.

These things are not separate from the service. They are often the most valuable part of it – accumulated judgement that prevents problems rather than resolves them after the fact.

But they do not show up clearly as hours.

A practice might spend ten minutes on a decision that prevents a planning objection, saves a contractor three weeks of confusion, or protects a client from a specification that would have caused problems for years. If that decision is measured by the time it took, it barely registers.

This is the structural weakness of time-based pricing. It makes visible labour easy to charge for. It makes invisible judgement almost impossible to price.

Time Does Not Measure a Practice

There is a subtler problem that becomes more acute as a practice matures.

Experience tends to make a practice faster. Established relationships reduce friction. Tested details resolve quickly. The mistakes that cost days on the fifth project do not happen on the fifteenth. The practice gets better at every part of delivery.

This pattern is explored in more detail in how small architecture practices make money – but the short version is that efficiency does not automatically produce better margins.

In a time-based pricing model, something different can happen.

The practice becomes more efficient, but the fee – still calculated from hours – starts to look smaller. Not because the work is worth less. Because the work takes less time.

The years of accumulated process, judgement and hard-won knowledge that allow the practice to deliver more reliably, more quickly, and with fewer problems than it could five years ago: none of that appears in a cost calculation. It has to be named differently, or it disappears into a faster turnaround that earns less than a slower one used to.

The practice improves. The pricing model does not keep up. That is not a quirk of one project. It is a structural feature of measuring value through time alone.

Why Projects Rarely Behave Like Estimates

Time-based pricing assumes a project will move in a predictable direction.

Most projects do not.

A straightforward residential extension becomes complicated when the planning officer raises an objection nobody anticipated. A client who seemed decisive reopens the brief three weeks into design.

A structural survey reveals something the desktop study missed. A contractor asks questions that pull the practice back into decisions that should have been resolved at Stage 3.

These are not unusual events. They are architecture. Projects loop. Decisions are revisited. Information changes. Briefs evolve past the point where the original estimate had any relationship to what the project has become.

The fee, however, was set before any of this was known – at the point of least information, before the site had revealed its complications, before the client had revealed their indecision, before the consultants had revealed their schedules.

The issue is not simply that projects change. The issue is that most fee structures have nowhere for that change to go.

When the project behaves differently from the estimate, someone absorbs the difference. In a small practice, that someone is almost always the practice.

What Happens When Uncertainty Is Absorbed Silently

Every project contains a level of uncertainty that the practice takes on at the point of proposal.

How cooperative will the planning authority be? How stable is the client’s brief? How reliable are the consultants? How many rounds of revision will the client need before they can commit?

The practice does not always know the answers when it prices the work. So it estimates – and the estimate implicitly absorbs the risk of being wrong.

In a larger practice, there is capacity to absorb overruns. One project can cross-subsidise another. The margin on a well-run job can offset losses on a difficult one.

In a small practice, that buffer rarely exists.

When a project overruns, it lands directly on the owner. They work later. They carry the client relationship. They become the buffer between the fee that was proposed and the work the project actually required. The practice absorbs the uncertainty that was never priced.

This is why fees break down so consistently – not simply because they are set too low, but because the structure they are built on is too narrow to account for the full nature of what the practice is taking on.

The specific mechanisms behind that breakdown are covered in why fees break down and how to think about pricing. The practice becomes better at delivering value, but not necessarily better at capturing it.

A More Complete Question

None of this means that time is irrelevant.

Understanding how long things take is fundamental to running a practice. Capacity planning, staffing, deadline management – all of it depends on knowing your hours. The cost calculation comes first. Always. A fee that does not cover delivery is a worse problem than any of the ones described here.

But time is the floor, not the ceiling.

Time asks how long the work will take. A better pricing model also asks what the work is carrying.

How much uncertainty does this project contain? How much decision-making support will this client need? How many consultants require coordinating? How likely is scope to move? How much accumulated practice knowledge is being applied to a problem the client could not resolve without it?

These questions do not replace the time estimate. They sit alongside it. They are the difference between pricing the hours required to produce a set of drawings and understanding what the project is actually worth to price.

A practice that only prices from cost will often leave money on the table with clients who fully understand the value of what they are buying. A practice that understands both – the cost and the nature of what it is taking on – is in a different position entirely.

That distinction is at the heart of what leverage actually means in an architectural practice context.

The Connection to How Practices Scale

For a small practice, fee structure is not a technical detail. It is a sustainability question. The broader economics of why this matters are laid out in why busy architecture practices still struggle to pay more – but the fee problem sits at the centre of it.

A practice that consistently underprices its work does not just lose money on individual projects. It creates a pattern. The owner works too many hours for too little return.

The margin is too thin to invest in the things that would allow the practice to operate differently – better systems, additional capacity, the time to develop client relationships where the work is priced appropriately.

The ceiling on what a small practice can achieve is not set by the quality of the architecture. It is set by how well the practice understands and prices what it actually does.

Time matters. But it is not the whole picture.

The practices that move past thin margins are the ones that stop treating hours as the complete measure of their value – and start thinking about what the work is carrying, alongside how long it will take.

Once that value is understood, the next challenge is to structure the work so it can be delivered, protected, and repeated without relying on the owner to absorb every overrun personally. That is where the question of scale begins.