If you work on fixed-fee projects, you know the price before you start. What you probably don't know is what you actually earned per hour when the project was done.
That number is your effective hourly rate. On fixed-fee work, it's almost always lower than freelancers expect. Understanding it, measuring it, and acting on it is the difference between a freelance practice that's profitable and one that just feels busy.
This guide shows you how to calculate your effective hourly rate, why tracking time on flat-rate projects matters even when you never bill by the hour, and how to use that data to price future work with confidence.
Table of Contents
- What is the effective hourly rate?
- Why does fixed-fee pricing hide your real earnings?
- How does scope creep cut your rate in half?
- Why should you track time on fixed-fee projects?
- How to calculate your effective hourly rate
- What target rate should you aim for?
- Common mistakes fixed-fee freelancers make
- Expert tips for protecting your rate
- Setting up a simple tracking system
- Case study: Six months of data from a UI designer
- Checklist
- Frequently asked questions
What is the effective hourly rate?
Your effective hourly rate is the total payment you received for a project divided by the total hours you actually worked on it.
Formula: Fee received ÷ Actual hours worked = Effective hourly rate
If you charge €2,400 for a website redesign and it takes 30 hours, your effective rate is €80/hour. If the project stretches to 50 hours because of scope changes and revision rounds, your effective rate drops to €48/hour. Same client. Same invoice. Very different outcome.
This number matters because it tells you the truth about what your time is worth inside each engagement. Without it, you're estimating your income based on headline fees that may not reflect where your hours actually went.
Why does fixed-fee pricing hide your real earnings?
Hourly billing creates a direct, visible link between time and income. Every hour you log appears on the invoice. Fixed-fee billing breaks that link.
On a fixed-fee project, the client pays a set amount regardless of how long the work takes. That's part of what makes it attractive: the client values the outcome, not the clock. The upside for you is that working efficiently earns a higher effective rate. The downside is that going over your estimated time earns you nothing extra, and you may not notice until it's too late to act.
Many freelancers who switch from hourly to fixed-fee billing feel like they're earning more. The numbers on the invoices get larger. But without tracking hours, the actual rate per hour often drops. The headline figure grows while the denominator (hours) goes uncounted.
Fixed-fee pricing is not the problem. Not measuring your time is.
How does scope creep cut your rate in half?
Scope creep is the slow expansion of a project beyond its original boundaries, without a corresponding increase in the fee. It's the most common reason effective rates on fixed-fee projects decline, and research consistently shows that scope overruns of 25% to 50% above original estimates are common across freelance and agency projects.
Here's what scope creep does to the numbers:
| Project Fee | Estimated Hours | Actual Hours | Effective Rate |
|---|---|---|---|
| €3,000 | 30 | 30 | €100/hr |
| €3,000 | 30 | 38 | €79/hr |
| €3,000 | 30 | 45 | €67/hr |
| €3,000 | 30 | 60 | €50/hr |
A 100% scope overrun (30 hours becomes 60) cuts your effective rate in half. The invoice stays the same. You did twice as much work.
What makes scope creep particularly damaging on fixed-fee projects is that it's invisible without a time log. The extra revision round, the extra call, the expanded requirements: none of these generate a line item on the invoice. They just add hours that reduce your effective rate, silently.
Where does scope creep actually come from?
Most scope creep on fixed-fee projects falls into three categories:
Client-driven additions. New requests that fall just outside the original scope but feel awkward to refuse without a clear contract clause.
Estimation errors. You underestimated how long a phase would take. Revision rounds are the most common culprit. Most freelancers budget one round and experience two or three.
Communication overhead. Calls, emails, status updates. On some projects, the communication time itself exceeds the original time estimate for delivery.
The only way to distinguish between these causes and take targeted action is to track time by phase, not just in total.
Why should you track time on fixed-fee projects?
There are four strong reasons, each independent of whether you ever share the log with a client.
Know your real rate. You can't optimize what you don't measure. Tracking time on fixed-fee work surfaces your actual effective rate on every project, making it a concrete business metric rather than a guess.
Price future work accurately. Each completed, time-tracked project is a calibration point. After ten similar projects, you see patterns: how long discovery actually takes, how many revision rounds happen in practice, where unplanned time consistently appears. Estimates shift from guesses to comparisons.
Spot scope creep in progress. If you track during a project, you can see when you're crossing the threshold where the project stops being profitable at the agreed fee. That gives you the option to raise a change order, flag the issue early, or consciously accept the trade-off. Without tracking, you have no choice, because you don't have the information.
Support change order requests. When a client pushes back on additional fees, a time log showing exactly where the hours went is neutral, concrete evidence. It's not a complaint. It's a record.
How to calculate your effective hourly rate
Follow these steps on every project, regardless of pricing model.
Step 1: Track all hours, not just delivery hours. Include discovery, client calls, internal review, revisions, handover, and project-specific admin. Non-delivery hours are real costs.
Step 2: Record total payment received. Use the amount actually paid, not the amount quoted. If there was a discount or renegotiation, use the final figure.
Step 3: Divide payment by total hours. This is your effective rate. Note it alongside the project details.
Step 4: Compare to your target rate. If your target is €75/hour and your effective rate was €48/hour, you have a 36% gap. That gap has a cause, and the time log helps you find it.
Step 5: Break down hours by phase. Total hours tell you your rate. Phase hours tell you where the rate went. If revisions consumed 40% of your total time and you allocated 15% in your estimate, that's the story.
This five-step review takes about 15 minutes per project. Over time, it's among the most valuable 15 minutes you'll spend on your business.
What target rate should you aim for?
Start with your annual income goal. Add your annual business costs: software, professional development, insurance, taxes, and any other overheads you carry as a freelancer.
Total revenue needed = Target income + Business costs
Divide that number by your realistically billable hours per year. Most freelancers work 1,200 to 1,600 truly billable hours per year after accounting for marketing, admin, learning, sales, and time off. (The higher figure applies to high-utilization freelancers with steady clients. The lower figure is more realistic for most.)
The result is your minimum effective rate floor. Your fixed-fee projects should average at or above it. If your average effective rate across recent projects is consistently below your floor, something in your pricing, scope management, or project selection needs to change.
Common mistakes fixed-fee freelancers make
Pricing from the client's budget, not your hours. Starting from "what will they pay?" produces under-pricing almost every time. Quote from your hours estimate multiplied by your target rate, then consider competitive context afterward, not the other way around.
Excluding non-delivery hours from the estimate. Briefing calls, project management, status updates, and revision management all cost time. A common failure is pricing only the creative or technical work while absorbing surrounding hours for free.
No revision cap in the contract. The difference between one and three revision rounds can double the time on a design-heavy project. Naming the number of included rounds, and specifying a process for additional ones, is the single most effective scope protection you can add to a fixed-fee contract.
Not counting time for past project types. When you quote a "similar project," you're often comparing it to a memory of how the last one felt. Memory compresses time. Tracked data doesn't. Freelancers who track consistently quote more accurately because they compare against a record, not a feeling.
Closing the project without looking back. Even freelancers who track time during projects often don't review the data after closing. The review is where the value lives. Before you archive a project, spend fifteen minutes on the numbers.
Expert tips for protecting your rate
Cap revisions in writing before the project starts. "Two rounds of revisions included; additional rounds at [hourly rate]" is clear, professional, and protects both parties. This single clause prevents the most common driver of scope overruns.
Use phase-level tracking. Tracking total hours is better than nothing. Tracking by phase is dramatically more useful. It tells you not just whether you went over, but where, so you can fix the right thing in your next estimate.
Send a short project summary to yourself at close. Before you archive: fee, hours, effective rate, top time driver. A sentence per point. Six months of these summaries is a data set that changes how you price work permanently.
Track from the start of each session, not at the end of the day. Time reconstructed from memory is systematically underestimated. People forget calls, small back-and-forth exchanges, and the time between sessions. Logging at the moment of work, even imperfectly, is more accurate than reconstruction.
Include a change order clause by default. A written change order process normalizes out-of-scope requests rather than making them feel like confrontations. "Here's how we handle additions" is far easier to say at the start of a project than after a client has already made three new requests.
Setting up a simple tracking system for fixed-fee projects {#setting-up-a-simple-tracking-system-for-fixed-fee-projects}
The goal is a system low-friction enough to use consistently. Tracking that stops after the first difficult week isn't useful.
Step 1: Define phases before the project starts
Decide which phases you'll track separately. A practical starting point:
- Discovery and Scoping
- Core Delivery (design, build, writing, etc.)
- Client Review and Revisions
- Handover and Admin
Four to five phases is enough to get useful data. More granularity helps, but basic phase tracking is far better than total-only tracking.
Step 2: Use a browser-based tracker with automatic capture
If you do most of your work in the browser, an extension that captures which websites you're visiting while the timer runs removes the need to manually log every tab switch. You start the timer when you begin a session, and the tool records both the elapsed time and the root domains you visited. This creates a session log you can review, not a reconstruction from memory.
TimeRecord works this way: install the Chrome extension, set up your Client, Project, and Task hierarchy, start the timer, and it handles the rest. Idle detection (default 8 minutes) pauses tracking automatically if you step away, then asks whether to keep or discard the idle time when you return, so you're not billing for time you weren't working. For freelancers managing multiple clients and fixed-fee projects at the same time, the Quick Switch feature lets you change tasks without stopping the timer entirely.
The extension is tracker-free (it doesn't capture keystrokes, full URLs, or page content, only root domains while the timer runs), and data is stored in the EU. For fixed-fee project tracking, this gives you everything you need: a timestamped log, organized by the Client and Project you're working on, with the website context to understand what each session involved.
Step 3: Review before closing each invoice
Before sending the final invoice on a fixed-fee project, pull the time report. Even if the client sees only the fixed fee, you see the total hours. Calculate your effective rate. Note it. Compare it to your last project of the same type.
Step 4: Log the data and look for patterns
Keep a simple record for each completed project:
- Project type
- Fee received
- Total hours
- Effective rate
- Primary time driver if you went over estimate
After a dozen projects, patterns become visible. The type of project that looks profitable on paper but consistently isn't. The client communication style that doubles revision time. The phase you always underestimate. These patterns are only visible in tracked data.
Case study: Six months of data from a freelance UI designer {#case-study}
A UI designer working on fixed-fee branding and interface projects started tracking time after three consecutive projects that left her feeling underpaid but unable to explain why.
She set up tracking by phase (Discovery, Design, Client Review and Revisions, Handover) and logged every project for six months.
What she found:
- Discovery and core design phases were consistently close to her estimates (within 10-15%).
- The Client Review and Revisions phase ran at 180 to 250% of her estimate on every project.
- Her contracts used the phrase "revisions as needed." Clients treated that as unlimited.
The data gave her three clear actions:
- Update every contract with a hard revision cap: two rounds included, additional rounds billed at her standard hourly rate.
- Add 25% to every revision phase estimate to reflect actual patterns rather than optimistic ones.
- Raise quotes on projects where the revision phase is likely to be complex (multiple stakeholders, unclear decision-making structure).
After six months of applying those changes, her effective rate improved substantially across similar project types. The work was the same. The clients were comparable. The only difference was that she now had the data to price and protect her time accurately.
Checklist: Protect your effective rate on fixed-fee projects {#checklist}
- Set up Client, Project, and Task structure before work begins
- Define phases to track separately (Discovery, Delivery, Revisions, Admin)
- Start the timer at the beginning of every work session, not the end of the day
- Include a revision cap and change-order clause in your contract
- Pull a time report before closing each invoice
- Calculate and record effective hourly rate for every project
- Log the primary time driver if the project ran over estimate
- Review patterns across projects every quarter
- Adjust future estimates based on tracked actuals, not memory
Frequently asked questions {#faq}
Do I need to track time if I always bill a fixed fee? Yes, but not to invoice accurately. You track time to measure your effective rate, improve future estimates, spot scope creep before it becomes costly, and build a data set that makes your pricing more accurate over time. The tracking is for you, not the invoice.
What is a good effective hourly rate for freelancers? It depends on your income target, costs, and location. The practical approach: add your annual income target and business costs, then divide by your billable hours per year (1,200 to 1,600 for most freelancers). The result is your floor. Your fixed-fee projects should average at or above it. If they don't, your prices or scope controls need adjustment.
How do I handle scope creep without damaging the client relationship? The best protection is a contract that names deliverables, caps revision rounds, and includes a change-order process. "This is outside our original scope; here's how we handle additions" is a professional response. The harder version is raising scope creep mid-project with no contract clause to reference. That's why addressing it before the project starts is so much easier.
Is automatic time tracking accurate enough for fixed-fee analysis? Yes, for this purpose. You're not billing to the minute. You're analyzing patterns across projects to improve future pricing. Automatic tracking that captures root domains and elapsed time while the timer runs gives you enough context to understand where sessions went and make good decisions from that data.
Should I share the time log with fixed-fee clients? You're not obligated to. But having it means you can, if needed. A time log becomes useful evidence if a client questions whether the project was fairly scoped or challenges a change-order request. Some freelancers include a time breakdown alongside fixed-fee invoices as a transparency gesture. Most don't. Having the data is what matters, regardless of whether you share it.
What if I keep forgetting to start the timer? This is the most common tracking failure. The fix is reducing friction: a browser extension that's always visible, a single click to start, and idle detection that handles pauses automatically. Manual time entry requires a habit you have to maintain consciously. Automatic capture that runs from the moment you start the timer requires far less discipline to sustain.
The bottom line
Fixed-fee pricing is a legitimate and often profitable billing model. It rewards efficiency, simplifies client budgets, and lets you earn more per hour as you get faster at your craft. But it only rewards efficiency if you're measuring it.
Without tracking time, you're flying blind on your most important business metric. With it, you have a feedback loop: quote, execute, review, adjust, repeat.
Your effective hourly rate is the clearest signal of whether a fixed-fee practice is working. Start measuring it on every project. The data compounds, and what you learn from project ten will make project twenty significantly more profitable.