Why I Price Projects, Not Hours
Early in my consulting career, everything was billed by the hour. It is the default model in the industry, and I never questioned it until I started working with small businesses and realized how poorly it serves them. For small businesses, the incentive structure is backwards, the client experience is anxious, and the entire arrangement rewards slowness over skill. I switched to fixed-price project billing and have not looked back.
The incentive problem
Hourly billing has a structural flaw that is difficult to talk around: the provider earns more by working slower. If I bill $75 an hour and a project takes 10 hours, I earn $750. If I find a more efficient approach and finish in six hours, I earn $450. The better I get at my job, the less I make per project. That is a misalignment that works against both parties.
The client feels this too, even if they cannot articulate it precisely. Every question they ask carries an implicit cost. "Can I see a draft before you finish?" is a reasonable request, but if the client knows they are on the clock, they hesitate to ask it. The hourly meter creates a friction in communication that makes the working relationship worse, and it incentivizes the client to minimize interaction, which leads to worse outcomes.
Fixed pricing eliminates both problems. I scope the work, name a price, and deliver. If I find a faster method, I benefit from my own efficiency and the client still gets the same deliverable at the same cost. If the client wants to ask a question or request a draft review, there is no meter running.
How I scope a fixed price
The price is based on what the build requires, not on how valuable the result is to the client. I assess four variables: the number of data sources involved, the complexity of the calculations or logic, the amount of data cleanup or restructuring needed, and the likely number of revision cycles. Each of those variables maps to a rough effort estimate, and the estimate produces the price.
This means the client knows the cost before any work begins. They are not approving a rate and hoping the hours stay reasonable. They are approving a specific deliverable at a specific price with a specific timeline. If the scope changes after the project starts, we discuss it explicitly and agree on the adjustment before any additional work happens. No surprise invoices.
What this changes for the client
The most immediate change is the removal of cost anxiety. In an hourly arrangement, the client is always aware that the clock is running. They batch their questions, delay feedback, and sometimes skip review cycles entirely to keep the bill down. All of those behaviors make the project worse.
With fixed pricing, the client engages freely. They send feedback when they have it, ask questions when they arise, and participate in the build process without worrying about what each interaction costs. The result is better communication, faster iteration, and a final deliverable that more accurately reflects what the client actually needs.
The second change is predictability. A small business owner managing cash flow needs to know what a project costs before committing to it. "Somewhere between $400 and $800 depending on hours" is not a budget number. "$500, delivered in seven business days" is a budget number. The certainty matters, especially for a business that has never hired outside help for data work before and does not know what to expect.
What this changes for me
Fixed pricing forces me to be a better scoper. If I estimate poorly, I absorb the cost of the extra time, which means I am strongly incentivized to understand the project fully before quoting it. That makes the scoping conversation more thorough, the deliverable definition more precise, and the overall project more likely to succeed.
It also rewards efficiency and expertise. The faster and better I get at building workbooks, dashboards, and reports, the more I earn per hour of effort. That is the correct incentive for a professional service: skill and speed should increase earnings, not decrease them.
And it eliminates billing administration. I do not track hours, generate timesheets, or justify line items. The client pays for the deliverable. The invoice is one line. The relationship stays focused on the work.
When hourly makes sense
I do not think hourly billing is inherently wrong. For ongoing advisory work, where the scope is intentionally open-ended and the client wants access to expertise on an as-needed basis, hourly or retainer billing makes sense. For consulting engagements where the deliverable is ambiguous and the work is exploratory, hourly billing distributes risk fairly.
But for defined deliverables, which is most of the work I do, fixed pricing is the better model. The client gets cost certainty, the incentives align correctly, and the working relationship is more collaborative because nobody is watching the clock.
