Why billable hours are lower than working hours (and should be)

The month I worked 160 hours and invoiced 61

A couple of autumns ago I had a month that felt like the busiest of the year. I was at the desk early, I ate lunch in front of the screen more than I'd like to admit, and I went to bed tired every night. At the end of the month I sat down to send invoices and added up 61 billable hours. I had planned for 95.

My first reaction was that I must have been slacking without noticing. So I went back through my calendar, my time log, and my sent email, and rebuilt the month hour by hour. It took most of a Saturday morning. Nothing in it was laziness. The month had simply been eaten by work that no client was ever going to pay for.

That is 40 hours a week, every week, and only 38 percent of it billable. In a normal month my overhead runs at around 60 to 65 hours. That month it was 99. The accounting switch, the dead drive, and two proposals in the same four weeks were enough to wipe out about a third of the billable time I had counted on.

Two clocks, and only one of them sends invoices

Every freelancer runs two clocks at once. One measures the hours you work. The other measures the hours a client will pay for without an argument. They are never the same number, and treating them as the same causes most of the money trouble I've seen in solo practice: rates that are too low, unpaid evenings, and the occasional padded invoice that quietly damages trust.

The gap is not a moral failing. It is the cost of running a one-person business that has a pipeline, a set of books, equipment that breaks, and skills that need updating. An employer pays someone for all of that. When you work for yourself, nobody does, unless your rate does.

The gap is not a moral failing.

What usually happens is that people price as if the two clocks match and then try to close the gap with willpower.

That fails, because most of the non-billable work cannot be skipped. You can postpone the books, but not forever. You can skip the proposal, but then next month is empty.

Work that is real but rarely billable

Looking at my rebuilt month, the non-billable hours fell into a few groups, and most freelancers will recognise all of them.

• Selling: scoping calls, estimates, proposals, and follow-ups that may or may not turn into work.
• Running the business: invoicing, bookkeeping, contracts, chasing payment, renewing insurance.
• Keeping the tools working: backups, updates, security patches, and rebuilding a machine when it dies.
• Staying employable: learning the library or framework your next project will need.
• Quality costs: fixing your own bugs on work you already delivered.
• Your own projects: anything you build for yourself, which is fine as long as you know you are doing it.

Some of this can become billable with the right agreement. Learning a client's specific stack can be part of onboarding. Fixing your own mistake usually should not be. Rush support at short notice should be. The rule is that grey areas get written down before they happen, because a surprise on an invoice causes arguments faster than a surprise in the code.

Write the rule down where the client can see it

I now put a short definition in every statement of work. It takes two sentences and has saved me several awkward emails.

Billable: time spent directly moving the agreed deliverables forward for this client, including agreed meetings and revisions within scope.

Not billable: sales, general tooling, work for other clients, training unrelated to the project, and fixing errors I caused without a change request from the client.

Clients rarely argue with this. What they argue with is a line item they did not expect. Writing it down also forces me to decide in advance what happens with the "quick call" that turns into 45 minutes of new requirements. If it changes scope, it is billable, and I say so at the end of the call, not on the invoice.

Pick a ratio, then let it set the rate

The useful number is your utilization: billable hours divided by the hours you actually work. Mine sits somewhere between 55 and 70 percent in an ordinary month, lower when I am selling hard or learning something new. Yours will be different. Track a few months and use your own figure, not someone else's.

The ratio tells you how many hours you have to work to sell the hours you need. If you want 30 billable hours a week, at 70 percent utilization you need about 43 working hours. At 60 percent you need 50. That second number is a lot of week, and it is why the ratio belongs inside the rate calculation, not in hopeful scheduling. The whole method is in calculate a freelance hourly rate.

Here is an ordinary week with the arithmetic shown. You are at the desk for 40 hours. Six go on admin and sales, four on learning, three on client chat that is not in scope, and two on revisions you cannot bill yet. That leaves about 25 billable hours, if nothing else breaks. Planning 35 billable hours on that week means borrowing from evenings or delivering late. Better to find that out on a Monday than in resentment at the end of the month.

Inflating hours and undercharging are the same mistake

There are two ways to hide overhead, and both go wrong.

You can inflate billable hours: bill 40 when you did 25 hours of real client work, and let the extra cover the admin. That works until a client compares your output to the hours on the invoice. Once they suspect padding, every future invoice gets read line by line.

Or you can absorb it: bill the honest 25 hours at a rate that assumes 40. That keeps the client happy and slowly wrecks you. I did this for most of my first year, and the "subsidy" came out of my evenings and weekends.

The honest version is two ledgers. The client ledger has billable lines tied to deliverables. The private ledger has everything else. Your rate is the bridge between them, so the client sees a clean number and you still know what a sold hour actually costs you. Fixed-price work has the same ratio hidden inside the price, which is one reason fixed price versus hourly is a pricing decision and not just a contract format.

When a client asks why the hours are low

The month of 61 hours had a side effect I did not expect. One of my retainer clients saw 14 billable hours on their invoice and asked, politely, whether I was still fully on their project.

I did not explain freelance overhead to them. That is my problem, not theirs. I sent what I had done: "Fourteen billable hours this month. The checkout fix is live, the staging site has the new product filters ready for your review, and I've been waiting on the copy for the returns page since the 12th." They replied with the copy the next morning. When a client sees finished work and a named blocker, the hour count makes sense. When they only see a number, they fill the gap with worry.

The reverse question needs the same answer. If they ask why the hours are high, point at the agreed scope line and the change notes. Billable hours measure effort a client has agreed to pay for. Finished work measures value. A week of billable hours with nothing anyone can review is a warning sign of its own: busy versus finishing.

Watch the ratio move, not just the total

I check both clocks weekly now, and it takes about ten minutes on Friday. I compare billable hours invoiced, hours on client projects that I could not bill, hours on running the business, and hours on learning and sales.

The pattern matters more than any single week. If billable hours rise while total hours rise much faster, scope creep or bad estimates are winning. If billable hours flatten while total hours fall, I've probably stopped selling and next month will be thin. If one client keeps generating unbilled calls, the problem is that contract, not my week.

Waiting is its own leak. Time spent blocked on client feedback is still calendar time, and in a fixed bid it is time you are not paid for. Price review latency into the bid or keep the work hourly with visible caps, as covered in client feedback delays and pricing. And do not try to fix a low ratio by dropping your rate to fill the calendar. That usually adds hours and removes margin, which is the argument of cheap freelance rates shrink real income.

Plan for the month with the dead laptop

The month of 61 hours did not need a better time management system. It needed a plan that assumed bad months happen. Drives fail. Accounting software gets replaced. Two good leads turn up in the same fortnight and both want proposals. None of that is rare. It just never happens on schedule.

So I plan billable targets with room for it. I count my ordinary overhead, add a buffer on top, and treat a month that comes in above plan as a bonus rather than the baseline. How big that buffer should be is in how much buffer a freelancer needs.

Billable hours being lower than working hours is normal, and it should be. A business that bills every hour it works has stopped selling, stopped learning, and stopped looking after its own tools. The mistake is pretending the two clocks match when you set your rate, fill your calendar, and promise dates. Work out your ratio, put it in the price, and the month with the dead laptop becomes an annoyance instead of a crisis.