Effective Hourly Rate for Freelancers: Fixed-Price Project Examples

Your effective hourly rate shows how much a fixed-price project returns for each hour you put into it. Start with the project fee divided by all project hours, including meetings, revisions, and administration. If you also subtract direct project expenses, label that result separately so you compare like with like.

This guide uses a fictional website project to show both calculations, how to get the hours from a calendar, and how to use the result in the next estimate. The examples are illustrative, not customer results or suggested market rates.

Two useful hourly-rate calculations

Revenue per project hour = Project fee ÷ Total project hours

Return per hour after direct costs = (Project fee − Direct project costs) ÷ Total project hours

“Effective hourly rate” is used with different cost assumptions. In this article, we show both and name the version being used. Neither is your personal take-home hourly pay: business overhead, taxes, and time outside this project may still need to be considered separately.

A quoted hourly rate is what you charge for a unit of billable work. An effective rate is the result of the fee and the actual effort. They can differ substantially on fixed-price work.

Count the hours the project actually required

Include project-specific production, calls, research, revisions, testing, and administration. Include proposal work for this project if you want to measure the full effort of winning and delivering it. Choose one rule and use it consistently across projects.

Do not add general sales or bookkeeping to every project independently: that would count the same overhead hours several times. Track those separately for a business-wide review.

Worked example: a $3,000 fixed-price project

Suppose a fictional website project pays $3,000 and uses $300 of subcontracting and project-specific assets. The completed work adds up as follows.

Project work	Actual hours
Design and development	30
Client meetings	4
Revisions	8
Proposal and administration	3
Total	45

Counting only the 30 production hours gives $3,000 ÷ 30 = $100 per hour. Including all 45 hours gives $3,000 ÷ 45 = $66.67 per hour before direct costs. After the $300 of direct costs, the result is $2,700 ÷ 45 = $60 per hour.

The fee did not change. The apparent return changed because the first calculation left out 15 hours. That missing effort is the reason to review the time record before changing your price.

Get the total hours from Google Calendar and Kotomil

Give all events for the engagement a consistent project code, such as [ACME-WEB].
Update timed events to reflect actual work, including calls and revision sessions.
In Kotomil, select the calendar and date range covering the complete engagement.
Filter using the project code and inspect the matching events.
Use the total duration in a separate worksheet with the fee and direct costs.

For the full setup and a worked weekly reconciliation, see Google Calendar time tracking for freelancers. Kotomil aggregates calendar events; the fee, cost, and rate calculations below are performed in your worksheet, not automatically by the app.

Check three things before using the total: canceled plans have been removed, overlapping events are not counting the same work twice, and unrelated projects do not share the same code. If parts of the record are estimated, make that uncertainty explicit.

A small worksheet you can recreate

Cell	Input or result	Value or formula
B2	Project fee	3000
B3	Direct project costs	300
B4	Total actual hours	45
B5	Revenue per hour	=B2/B4
B6	Return per hour after direct costs	=(B2-B3)/B4

Use decimal hours: 6 hours 30 minutes is 6.5 hours, not 6.30. Convert minutes by dividing them by 60. Enter a positive hours value before calculating; zero hours does not produce a meaningful rate.

For consistency, use the same currency and fee basis for each project. Record whether you are comparing agreed fees or payments received. A cash-collection review answers a different question from a completed project's pricing review.

Use the result to review the next quote

Suppose your chosen target is $75 per hour after direct project costs. With the same $300 direct costs and a $3,000 fee, the project can use at most ($3,000 − $300) ÷ $75 = 36 hours to meet that target. The completed example took 45 hours, nine more than that allowance.

If a similar project is expected to require 45 hours again, the fee needed for the same target is 45 × $75 + $300 = $3,675. That is a planning calculation, not a prediction that a client will accept the price.

Revisions caused the overrun: make the included revision scope clearer in your next proposal.
Meetings expanded: review their cadence and include the expected time in your estimate.
The work was unfamiliar: separate one-time learning from effort likely to recur.
The estimate missed routine tasks: include setup, handover, and project administration next time.

Actual hours can also support a decision to keep a lower-rate project because it is reliable or strategically useful. The purpose is to make that tradeoff visible.

Retainers: repeat the same calculation each month

A fictional $2,000 monthly retainer with no direct project costs returns $80 per hour at 25 hours, $50 at 40 hours, and $40 at 50 hours. A growing request load changes the result even when the fee stays the same.

Use the same monthly boundaries and labels each time. Review several comparable months before treating a one-off launch or support incident as the normal workload. If a longer date range or comparison feature is needed in Kotomil, check the current plan limits.

For an unfinished fixed-price project, dividing the full fee by hours so far can overstate the eventual return. Keep completed hours and estimated remaining hours separate; use their sum only as a clearly labeled forecast.

Project return is only part of the picture

Good project rates do not reveal how much time goes into finding clients and running the business. For a separate monthly review, compare a consistently defined revenue-and-cost figure with all business hours, including general sales and administration. Do not label the result net profit unless you have included the costs required for that definition.

For a client-facing update, use the freelance monthly report template. Keep your internal pricing targets separate from the deliverables and hours you choose to report.

Common questions

Should I divide by billable hours only?

Use all project hours to assess the return on your effort. A billable-hours-only calculation answers a narrower question and can hide included revisions or administration.

What is a good effective hourly rate?

There is no single target in this guide. Set yours using your costs, available working time, and income goals, then compare similar projects under the same assumptions. The $75 target above is only an example.

How do I start?

Choose one completed project with a known fee. Review its recorded time in Kotomil, reconcile the events, and put the hours into the worksheet above. Identify one change to the next estimate, scope, or workflow.