How to Price an Engineering Project: A Fee Guide for Consultancy Offices

When an engineering office loses money on a project, the ready explanation is that the price was too low. In most cases it isn't. The real reason is that the office didn't know its true cost when it priced the work, so it accepted fees that looked healthy on paper while consuming several times the effort estimated for them.

Pricing consultancy work isn't a number you write at the end of a proposal. It is a decision that defines the scope of work, how many revisions you will give away for free, when you get paid, and what happens when the client changes their mind. This guide walks through those decisions one by one.

Four Ways to Price Engineering Fees

Lump Sum

A fixed amount for a defined scope. The clearest for the client and the easiest to collect — and the riskiest for you: every extra hour comes straight out of your margin.

It only works when the scope is defined precisely enough for you to estimate hours with confidence. With a vague scope, a lump sum becomes an open ceiling on your losses.

Percentage of Project Value

The most common model in design and supervision work, calculated as a percentage of the estimated construction cost. It is fair on larger projects because it ties your fee to the scale of your responsibility.

Watch two points, though: exactly what is the percentage calculated on — estimated or actual cost? And what happens to your fee if the actual cost comes in lower? A written agreement on these two clauses saves you the longest argument at the end of the project.

Time and Materials

Hourly or daily pricing for work of undefined duration: preliminary studies, consultations, post-handover support. It protects you from open-ended scope, but it demands disciplined time recording — otherwise every invoice turns into a negotiation.

Always set an estimated ceiling to be reviewed when reached. A client looking at an open-ended invoice with no cap gets nervous even when every hour is justified.

Monthly Retainer

A recurring amount for keeping your office available to an ongoing client: reviews, consultations, periodic supervision. It gives you stable income that covers your fixed costs, which turns the rest of your projects into margin rather than survival.

Its only condition is a clear boundary: how many hours or visits it covers per month, and what gets billed outside it.

Model	Best for	Main risk
Lump sum	Clearly defined scope	Every extra hour hits your margin
Percentage of project	Design and supervision of large projects	Dispute over the calculation base
Time and materials	Open-ended studies and consultations	Collapses without precise time records
Monthly retainer	Ongoing client relationships	Scope creep inside the same retainer

Why Lump Sum Fees Collapse

Because the office prices what it understood from the client, and the client buys what they imagined. The gap between the two never shows at signing — it shows at the third revision.

Three clauses in your proposal prevent that collapse:

Exactly what the scope includes — drawings, disciplines, and deliverables, counted rather than described.
What the scope excludes — the clause that saves the longest arguments, and the one most often forgotten.
The number of free revisions — with anything beyond billed hourly. Without that cap, "small tweaks" never end.

How to Calculate Your Real Hourly Cost

You can't price a project without knowing what one hour of work actually costs you. The calculation is simpler than it looks.

Add up your annual fixed costs — salaries, rent, licences, software, vehicles, administration. Then divide by the number of hours actually chargeable to projects, not by total working hours.

The difference between those two numbers is what breaks most estimates. An engineer on an eight-hour day does not charge eight hours to projects. Meetings, coordination, proposals, training, and waiting consume a real share of the day. Realistic utilisation in most offices is far lower than what gets assumed at pricing time.

When you calculate hourly cost on chargeable hours alone, the true cost rises — and that is precisely the number to price from, because it is the only honest one.

Clauses No Proposal Should Be Missing

Scope of work in detail, with exclusions stated explicitly.
Proposal validity period — an offer with no expiry date comes back a year later at prices you no longer charge.
Payment schedule tied to completed stages rather than calendar dates, so you don't finance someone else's delay.
Advance payment — it measures the client's seriousness before you fund the start of the work.
Retention percentage if applicable, and when it is released.
The effect of client delay in providing information or approvals on both duration and fees.
The change mechanism — that any scope change is documented in an approved change order before it is executed.

That last clause is what protects the whole project later, and it is the one most often left out.

What Changes When Pricing Lives Inside a System

The difference isn't in writing the proposal — it's in everything after it. When proposals are built inside one integrated engineering office system:

An accepted proposal converts into a contract with its items and value, with no re-entry and no clauses lost between two files
Sent proposals stay visible with their status — draft, sent, accepted, rejected — instead of sitting in somebody's inbox
Quoted fees are compared against actual cost after delivery, so you learn which kind of project actually pays
Your next quote is built on the numbers from your last ten projects rather than on a guess

That last point is the real impact: an office that knows its actual cost across ten past projects prices the eleventh with confidence, and walks away from unprofitable work early instead of discovering it at the end.

Frequently Asked Questions

What is the best way to price an engineering project?

There is no single model for every case. A precisely defined scope suits a lump sum, large design and supervision projects suit a percentage of project value, open-ended studies suit time-based pricing, and ongoing clients suit a monthly retainer. The common mistake is using a lump sum with a vague scope.

What is the usual engineering fee percentage?

It varies by project type, disciplines, size, and service scope — design only versus design and supervision — and it also varies by market and by the regulating authority or engineering body in each country. More important than finding a prevailing percentage is verifying that the percentage covers your estimated hours and still leaves a margin.

How do I calculate the hourly cost in my office?

Divide your annual fixed costs by the hours actually chargeable to projects, not by total working hours. The gap between those two figures is wide, and using total hours is the single biggest reason pricing looks profitable when it isn't.

Should I ask for an advance payment?

Yes, for two reasons: it funds the start of the work before your first payment certificate, and it measures the client's seriousness. A client who stalls on the advance will usually stall on everything after it.

What do I do when a client asks for endless revisions?

Go back to the number of revisions agreed in the proposal. If it was specified, the extra revision is priced as a change order. If it wasn't, the problem started in the proposal rather than with the client — fix it in the next one.

How long should a proposal stay valid?

State it explicitly — one month or three, depending on the work. An open-ended offer may be accepted long after your costs and prices have changed, leaving you bound to a number that is no longer correct.

Conclusion

Pricing is less a negotiation skill than a knowledge skill. The office that knows its hourly cost, writes its scope precisely, and documents every change quotes with less hesitation and earns more.

Open the last proposal you sent and ask one question: is there anything in it that stops the client from requesting a tenth revision for free? If not, that is the first thing to fix.