Time Tracking That Tells You Your Real Hourly Rate
How many people can answer "what's my hourly rate?" on the spot?
The first time I faced that question was while reviewing an engagement's invoice. When I worked out how much time the project had taken, the per-hour figure was a small shock. The rate I'd pitched and the hours I'd actually spent didn't line up.
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.
In most cases, the cause isn't "the rate is low" — it's "the effort estimate was optimistic."
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.
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.
Keeping the records going
Building rate evidence requires a recording system that survives.
Build the habit of starting the timer when a task starts: begin recording every time you begin working. The simplest and most effective method.
Switch the record every time you switch tasks: 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. The review itself sharpens the next week's recording accuracy.
High-friction recording doesn't last. Choosing a tool you can run at the lightness of "pick a task, hit the timer" is essential.
Summary
- Noticing the quoted-vs-effective rate gap requires accurate time records
- Effective rate = contract amount ÷ total actual hours
- Time records power estimate accuracy, rate justification, and profitability judgments
- Recording "invisible work" — meetings, revisions — reveals the real picture
- A system that keeps recording going is the precondition for accumulating data
Your rate isn't something you quote; it's something you calculate from actuals. Producing the source data for that calculation is what time tracking is for. The longer you record, the more evidence-backed numbers you own.
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 — and pull per-engagement actuals via CSV export. From estimate-accuracy improvement to profitability analysis, free to try.