Time Tracking That Tells You Your Real Hourly Rate
How many people can answer "what's my hourly rate?" on the spot?
It started with a quick bit of math. I took one engagement's invoice and just divided it by the hours it had taken. Looking at the hourly figure that popped out, I caught myself going "wait — that's it?" The rate I'd pictured when I pitched and the time I'd actually put in didn't line up at all.
Setting your rate "roughly from market feel" has hard limits. Owning numbers grounded in your own actuals changes both your estimate accuracy and the evidence behind your rate.
Quoted rate vs. effective rate
"Rate" means two different things.
One is the quoted rate — the per-hour amount you present when taking on work. The other is the effective rate — the real per-hour figure computed from the contract amount and the time actually spent.
Work without noticing the gap between the two and you get the situation where revenue grows but take-home never feels like it does. It's not rare for an engagement's effective rate to land 40–50% below the quoted rate.
The tricky thing is that this gap is normally invisible. Money comes in as "X per engagement," so as long as you're watching the deposits, everything looks fine. But the figure that actually bites is the effective rate — that amount divided by time. The quoted rate is the number you put on a business card; the effective rate is the number that pays your life. They can diverge and you'd never know, unless you bother to do the division.
And in most cases, this isn't "the rate is low" — it's just "the effort estimate was optimistic." Which, flipped around, means it's fixable once you measure it.
What you need to compute your effective rate
Computing an effective rate requires an accurate record of how many hours the engagement took.
The formula is simple:
Effective rate = contract amount ÷ total actual hours
Say the contract was ¥400,000 and the work actually took 160 hours: the effective rate is ¥2,500/hour. If the quoted rate was ¥3,000/hour, that's roughly a 17% gap.
Analyze where the gap comes from and you'll find the underestimated phases and the unplanned recovery work.
One caution: don't average across engagements. Compute the effective rate per engagement — ideally per type of work — because averaging everything lets the well-paying jobs hide the poorly-paying ones. "It's fine on average" while a few heavy engagements run near a loss is a common story. And running the same calculation periodically, to watch the trend, makes the effect of rate negotiations and skill growth show up in the numbers. A one-off calculation tells you far less than the arc over six months or a year.
Three situations where time records become your evidence
Keep accurate records and they serve as evidence in three situations.
1. Feeding actuals into the next estimate
A record of "how many hours API design took last time" gives your next estimate of similar work a foundation. Instead of "20 hours, roughly," you get "18 last time, so 22 this time given the wider scope."
2. Justifying your rate
With actuals like "this type of engagement averages XX hours for me," rate proposals and rate changes can be argued from data. Speaking from records rather than impressions raises the quality of the conversation.
3. Spotting low-profitability engagements early
If you run several engagements and can compare effective rates, "this one pays poorly for its hours" becomes a data-driven judgment — useful at contract renewals and when deciding what work to take.
Making "invisible work" visible
An engagement's total hours include more than direct production time: meetings, email, spec confirmations, revision handling. Leave these unrecorded and your effective rate gets overestimated.
Once the reality is visible — "50 hours of implementation plus 20 hours of coordination, 70 total" — you learn lessons like "meeting-heavy engagements need those hours in the estimate." Record hours by type of work (implementation, design, communication) and your time-usage patterns come into view.
In particular, when you're "somehow busy but the hours look small," unrecorded communication work is usually the culprit.
And what quietly erodes the effective rate most is the work that never makes it onto an invoice: writing proposals, preparing estimates, contract back-and-forth, and the unpaid revisions that pile up from "while you're at it, could you also fix this." Every one of them is necessary to the engagement, yet none is reflected in the contract amount. Record them and you see "this engagement ate time around the edges more than in the work itself." Out-of-scope additions in particular — hard to refuse, so they drag the effective rate down fast — are worth holding as numbers: knowing how much you did for free gives you something to draw a line with at the next contract.
Draw a "floor line" under your effective rate
An effective rate only means something when you use it to decide, not just compute it. The simplest move is to draw one floor line for yourself — "below this, I reconsider."
Decide, say, "any engagement whose effective rate dips under ¥2,500 gets a rate renegotiation at renewal, or I change how I take it on." With a line, you notice the poorly-paying jobs you'd been continuing out of inertia, and for new inquiries you can judge early that "these terms would likely break the floor."
The hard part is that the engagements that don't pay off are usually the ones where you've built a relationship and find it hard to say no. Which is exactly why you hold it as a number, not a feeling. Being able to say "the effective rate is 20% under my floor," instead of "this feels heavy," makes the conversation easier to move — both with yourself and with the other side.
Keeping the records going
Building rate evidence requires a recording system that survives.
Start recording in the moment you begin: leave the record as you start, rather than recalling it later. Hitting a timer is the easiest, but manual entry is plenty too — one line "when you start, when you finish."
Switch the record when you switch work: when "stop the previous, start the next" happens naturally, missed tracking drops. A system that auto-stops the previous timer on switch makes it even easier.
Review your records weekly: look over the accumulated logs and check per-engagement summaries — including the effective rate, if you can. Doing this weekly lets you notice "this engagement is eating more than I thought" early, so you're not scrambling before month-end or a renewal.
High-friction recording doesn't last. Timer or manual, choosing a tool light enough to "leave a record in one step" is what works best in the end.
In the end, a rate is "measured," not "set"
Boiled down, it comes to one thing: noticing the gap between your quoted rate and your effective rate takes accurate time records. The effective rate is just contract amount ÷ total actual hours — a single division — but unless that denominator includes the invisible work like meetings and revisions, the number flatters you. Which is why the system that keeps recording going comes first; the fancy analysis is for afterward.
Your rate becomes a figure with real weight only when you measure it from actuals, rather than setting it from market feel — that's what I took away from the slightly jarring experience of looking back at my billing. That said, do I compute the effective rate cleanly on every engagement? Honestly, I'm not that disciplined. Even so, just running the number now and then and holding it against the floor line makes the call — "don't underprice this type of work next time" — come a lot faster. The habit of dividing once in a while beats perfect analysis over the long run.
Related articles
- Building a Time-Tracking System That Eliminates Month-End Gaps
- Time Tracking That Lets You Say, in Numbers, Where the Time Went
- Forecasting Remaining Effort: How EAC (Estimate at Completion) Works
The "recording actuals and understanding your rate" covered in this article is exactly what LayerClock supports. Record hours across a four-level structure — project, phase, deliverable, task. Per-engagement CSV export and profitability analysis are on the Business plan; start with recording and estimate-accuracy improvement, free to try.