An hourly rate is a useful starting point, but a fixed project fee must also account for scope, revisions, non-billable work, expenses, payment fees, and uncertainty. This guide shows how to convert an hourly rate into a defensible project price, with formulas, assumptions, and worked examples you can reuse for proposals and scope changes.
Overview
The basic hourly-to-project calculation is simple:
Estimated project price = estimated project hours × hourly rate
That formula works only when the estimated hours include all of the work required to deliver the agreed result. In practice, a project may include discovery, planning, communication, research, production, quality checks, revisions, handoff, and administration. If those activities are left out, the fixed fee can look attractive to the client while creating an unprofitable workload for the person or team delivering it.
A more complete project pricing formula is:
Fixed project fee = labor cost + project expenses + contingency + payment costs
There are two common ways to use an hourly rate:
- Billable-rate approach: Your hourly rate already reflects your desired compensation and operating costs. Multiply the complete time estimate by that rate, then add project-specific costs and any agreed contingency.
- Cost-plus approach: You start with an internal labor cost, add overhead and project expenses, and then apply a target profit margin. This is useful when pricing work delivered by employees or several contributors.
Do not apply a profit adjustment twice. If the hourly rate is already your client-facing rate and includes profit, adding a second markup may produce a price higher than intended. Document what your rate includes before calculating the fixed fee.
How to estimate a project price
1. Break the scope into work packages
Start with deliverables rather than a single guess. List the major stages of the project, such as kickoff, research, first draft, implementation, testing, revisions, and final delivery. Smaller work packages are easier to estimate and make scope changes easier to identify.
For each stage, record an expected number of hours. Include work that is visible to the client and work that happens behind the scenes. A useful worksheet might look like this:
- Discovery and kickoff: 3 hours
- Planning or research: 5 hours
- Production or implementation: 18 hours
- Review and quality assurance: 4 hours
- Client meeting and communication: 3 hours
- Revisions and handoff: 7 hours
The total is the working-time estimate before contingency. If several people are involved, calculate each role separately and multiply its hours by the applicable rate.
2. Add a reasonable contingency
Contingency covers uncertainty that is related to the defined project, such as incomplete requirements, minor technical complications, or additional coordination. It is not a substitute for an unclear scope.
Calculate it as either additional hours or a percentage of estimated labor:
Contingency amount = estimated labor cost × contingency percentage
Use a smaller allowance when the requirements are clear and the work is familiar. Use a larger allowance when dependencies, approvals, integrations, or unknown inputs make the estimate less certain. State that the contingency is an estimating allowance, not an unlimited revision budget.
3. Add direct project expenses
Separate labor from costs incurred specifically for the project. Examples may include paid tools, materials, travel, specialist support, data, or transaction-related costs. Decide whether each expense is included in the fixed fee, billed separately, or subject to client approval before purchase.
4. Account for payment fees and taxes
If a payment processor or other collection method deducts a fee from the amount received, decide whether your price should absorb that cost. For a percentage-based fee, you can gross up the subtotal:
Price before tax = subtotal ÷ (1 − payment fee percentage)
For example, a subtotal of 2,000 with a 3% fee becomes approximately 2,061.86 before any applicable taxes. Treat taxes such as VAT or sales tax according to the rules and registration requirements that apply to your business and customer; they are not automatically profit.
5. Round and present the result clearly
A fixed fee does not need to display every internal calculation. Use the worksheet to understand the economics, then present a clear price, payment schedule, scope, assumptions, revision limit, and process for out-of-scope work. A fixed fee is easier to manage when the client can see exactly what is included.
Inputs and assumptions
A reliable hourly to project rate calculator depends on consistent inputs. Review these before sending a proposal:
- Hourly rate: Confirm whether it is a client-facing billable rate, an employee cost, or a blended team rate.
- Estimated hours: Include meetings, messages, planning, administration, testing, and handoff where they support the project.
- Revision allowance: Define how many review rounds are included and what counts as a new direction.
- Team mix: Use separate rates when work requires different roles or levels of experience.
- Direct expenses: Identify purchases, travel, software, contractors, and other costs tied to this engagement.
- Contingency: Match the allowance to uncertainty rather than using the same percentage for every project.
- Payment timing: Consider whether delayed payment, deposits, milestones, or staged billing affect cash flow and risk.
- Taxes and currency: State whether the quoted fee includes or excludes applicable taxes, and specify the currency.
- Scope boundaries: Record the assumptions behind the estimate, including client inputs, approval dates, formats, integrations, and dependencies.
Capacity is another important assumption. A project may require 40 hours of work but still take several calendar weeks if only part-time capacity is available. Use a workload capacity planning template to check whether the proposed deadline fits the team’s available hours.
For financial review, compare the expected return with the time and cost required. The ROI calculator for small business can help evaluate an investment, while the markup vs. margin calculator is useful when checking whether a proposed price produces the intended result.
Worked examples
Example 1: Converting a billable hourly rate into a fixed fee
Assume a consultant charges 80 per hour and estimates 30 hours for a defined project. The base labor value is:
30 hours × 80 = 2,400
The consultant adds a 10% contingency for modest uncertainty:
2,400 × 10% = 240
There are also 120 in project-specific expenses. The subtotal is:
2,400 + 240 + 120 = 2,760
If the consultant expects a 3% payment fee and chooses to absorb it in the quoted price, the grossed-up fee is:
2,760 ÷ 0.97 = approximately 2,845.36
The proposal could be rounded to an appropriate fixed fee, provided the rounded amount is documented as inclusive of the stated scope, contingency assumption, expenses, and payment cost.
Example 2: Pricing work from internal cost and target margin
Suppose a small team estimates 50 hours of labor at an internal cost of 45 per hour. Labor cost is 2,250. Add 250 in direct expenses and 10% contingency on labor and expenses:
Labor and expenses = 2,250 + 250 = 2,500
Contingency = 2,500 × 10% = 250
The cost base is therefore 2,750. If the target profit margin is 20% of the final selling price, use the margin formula rather than simply adding 20%:
Price = cost base ÷ (1 − target margin)
2,750 ÷ 0.80 = 3,437.50
This distinction matters because a 20% markup and a 20% margin are not the same. Check the result against your market positioning, capacity, risk, and scope before presenting it to a client.
Example 3: Handling a scope change
After approval, a client requests an additional deliverable expected to take 6 hours. At an hourly rate of 80, the change has a labor value of 480. If the new work also requires 40 in expenses and a 5% uncertainty allowance, the change estimate is:
(480 + 40) × 1.05 = 546
Record the change before doing the work. This preserves the original project economics and gives both parties a clear decision point.
When to recalculate
Recalculate the project price whenever an input changes, not only when a proposal is first prepared. Review it in these situations:
- The scope, deliverables, formats, or number of review rounds changes.
- The project deadline moves and creates rush work, idle time, or additional coordination.
- A key assumption, dependency, or client-provided input is delayed or unavailable.
- A team member or role is replaced with a different rate.
- Software, materials, travel, subcontractor, or payment costs change.
- Your standard hourly rate, target margin, or overhead allocation is updated.
- A renewal or repeat project reveals that the original estimate was consistently too high or too low.
- Actual hours differ materially from estimated hours during delivery.
After completion, compare estimated hours with actual time by work package. Do not rely only on the total. If production was accurate but communication took twice as long as expected, the next estimate should adjust the communication assumption rather than applying an arbitrary increase to every rate.
Keep a reusable worksheet with the formula, assumptions, approved scope, actual hours, and final outcome. Pair it with a small-business invoice template to keep billing details consistent, and use a simple task system to track approvals, revisions, and scope changes. The result is not just a faster calculation; it is a repeatable pricing process that becomes more accurate with every completed project.
