A client receives two proposals. One quotes a day rate of eight hundred and estimates fifteen days. One quotes a fixed fee of fourteen thousand.
The day rate proposal appears to be twelve thousand and appears cheaper. It is an estimate rather than a commitment, and the days are the consultant's estimate of their own work.
The fixed fee is a commitment. If the work takes twenty days, that is the consultant's problem, and the client compared a certainty against an estimate as though they were the same thing.
What a consulting fee is actually made of
Four components. The time on the engagement, the time that cannot be billed, the direct costs and the overhead and margin the practice needs to operate.
Component 1: the engagement time
Days actually spent on the client's work. This is what a day rate prices and it is the only component clients ever see.
Component 2: the unbilled time
Scoping, proposals, travel, admin and business development. Real working time producing no invoice, which every billable day has to carry.
Component 3: the direct costs
Travel, any subcontracted specialist input, tools and anything specific to the engagement. Usually small and frequently invisible in a quoted rate.
Component 4: overhead and margin
Insurance, professional development, systems, accounting and the return the practice needs. This is why a day rate is not the same as a salary divided by working days.
A worked example, by day rate
Eight hundred a day, estimated fifteen days, giving twelve thousand. If it takes eighteen days, the client pays fourteen thousand four hundred and the estimate was not a commitment.
The same work as a fixed fee
Fourteen thousand, whatever it takes. The consultant carries the overrun risk and prices it in, which is why the fixed figure exceeds the day rate estimate.
What the comparison actually shows
That the client is choosing who carries the risk. Neither model is cheaper in principle, and comparing a rate against a fee without understanding that compares nothing.
When a day rate genuinely suits
Work whose extent cannot be predicted, ongoing advisory input, or where the client wants to control how much is spent by controlling how many days are used.
When a fixed fee genuinely suits
A defined deliverable with a clear scope, where certainty matters to the client and where the consultant can estimate the work reliably.
Why a fixed fee requires a defined scope
Which is why scoping matters so much before quoting, and why an unscoped fixed fee is a commitment with no boundary and no way to say when it has been met.
The retainer model and what it actually buys
Availability and continuity rather than a quantity of days, which should be defined carefully or it becomes an unbounded obligation.
The value pricing question honestly
Pricing against the outcome rather than the input, which works where the value is measurable and agreed, and produces arguments where it is not.
Publish the model and explain the trade off
An assistant that explains how each model works, which suits which kind of engagement and who carries the risk in each lets a client compare two proposals properly rather than on the smaller number. The commercial terms sit in rate and engagement questions consultants should answer, the scoping in consulting enquiries that need scoping before a call, the same basis problem in pricing by hour versus by job questions, and the openness in how much does an ai receptionist cost. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under consultants.