Pricing model
Hourly vs. project pricing: a simple decision framework
Neither model is always better. The right choice depends on who controls the work, how clearly the outcome can be defined, and where the risk belongs.
The short answer
Use hourly pricing when the work is exploratory, ongoing, or largely controlled by the client. Use fixed project pricing when the outcome, deliverables, boundaries, and approval process can be described clearly enough to estimate the risk.
When hourly pricing works well
Hourly pricing is useful for advisory work, troubleshooting, open-ended revisions, embedded team support, and projects where priorities may change weekly. The client pays for the capacity used, so you carry less estimation risk.
The weakness is that the client cannot know the final cost, and you earn less when expertise helps you finish faster. Hourly billing also turns time tracking into part of the client relationship.
Use hourly when:
- The scope is expected to change.
- The client directs the daily work.
- You are joining an existing team or backlog.
- The problem must be investigated before a solution can be scoped.
- The engagement is support or maintenance rather than a defined project.
When project pricing works well
A fixed project fee gives the client cost certainty and lets you benefit from an efficient process. It works best when the deliverables, decision-makers, revision limits, dependencies, and completion criteria are written down.
The risk is hidden scope. If the project expands while the price stays fixed, your effective hourly rate falls. A fixed fee therefore needs a clear scope-of-work and a written change-request process.
Use a project fee when:
- The client is purchasing a defined outcome.
- You control the method and schedule.
- You have completed similar work before.
- Inputs and approvals have named owners.
- Out-of-scope requests can be identified and priced separately.
Build a project price from an hourly floor
Project pricing does not mean ignoring time. Use your sustainable hourly rate as an internal floor, estimate delivery and administrative hours, add direct costs, then include contingency for uncertainty and profit for taking responsibility for the outcome.
For example, a project requiring 40 delivery hours and 6 administrative hours at a $100 internal rate begins with $4,600 in labor. Add expenses, a risk buffer, and a profit allowance before rounding to a clear client-facing fee. Do not show the internal hour calculation unless hourly billing is part of the agreement.
A hybrid option
Many engagements work best as a paid discovery phase followed by a fixed implementation fee. Discovery is billed hourly or at a small fixed price because uncertainty is high. The resulting plan creates enough clarity to quote the larger project responsibly.
Protect either model
Hourly projects still need a budget, reporting rhythm, and approval threshold. Fixed projects still need assumptions, exclusions, revision limits, and change requests. Pricing models do not replace scope; they decide how the remaining uncertainty is paid for.