What your hourly rate doesn't include

The ledger

Round numbers, so the arithmetic is easy to check against your own last project.

Quoted: 60 hours at $75, which is $4,500.

Hours that never made it into the quote:

• Two calls before the proposal, and the proposal with one round of revisions: 6
• Kickoff, access, onboarding docs: 3
• The library you had to learn because the client's stack was new: 5
• Four rounds of “small tweaks” after the first review: 9
• The invoice, plus two chases: 3
• Handover call and the walkthrough recording: 2
• The thing they asked for three weeks later, since you were already familiar: 6

Thirty-four hours. The job was ninety-four.

$4,500 ÷ 94 = $47.90 an hour.

You quoted $75. You were paid $48.

The quote was not dishonest. You estimated the making: the part with a shape, the part you can picture at 11pm the night before you send it. The other thirty-four hours were the job's paperwork, and paperwork has no shape until it is on your calendar.

The hours nobody bills

Seven entries, and none of them is the one that eats the most: finding the next client.

Nobody bills it. It happens in the gaps, on the Tuesday you rewrite your own site, in the three proposals that go nowhere, at the thing you went to because someone might be there.

Count it once. Take last month: every hour you worked, including the ones you would not put on a timesheet. Then take the hours you invoiced. Divide the second by the first.

If you bill 25 hours in a 40-hour week, that share is 62%. At 20 hours it is 50%. Those two numbers decide whether a rate is survivable.

What the rate has to cover

Say you want $80,000 before tax, and you bill 20 hours a week for 46 weeks. That is 920 billable hours.

$80,000 ÷ 920 = $87 an hour.

$87 is the number to quote. $75 is the number that felt fair next to your last salary, and it was calculated on a calendar that does not exist.

Look at it from the other side: 920 billable hours sit inside roughly 1,840 worked hours. The other 920 go to the business, and none of them can be invoiced.

The other direction

Raising the rate is the first thing people try. Take $95 instead of $75 and the same job pays $8,930, which fixes the arithmetic in one line.

It also lifts the price of the thirty-four hours the client never agreed to pay for. You now have to sell 94 hours at $95 to a client holding a budget line and a salary benchmark. The rate moved. The number of hours you can sell did not.

The lever that requires nobody's approval is the hours: one round of feedback written into the contract, an onboarding doc instead of a kickoff call, a change request that gets priced before it gets built. Each of those buys back four to six hours on a job this size, and they cost a paragraph.

Why fixed pricing is not a raise

Move the same job to a fixed price and nothing changes on day one. Price the 94 hours at $48 and you land on $4,500 again.

What changes is who owns the hours you save. Under hourly billing, finishing in 70 hours cuts your invoice by $1,150. Under a fixed price, those 24 hours belong to you: sell them to someone else, or stop working at four.

That is the argument for project pricing, and it has nothing to do with charging more.

The number to write down

One line at the top of your rate card:

Target income ÷ billable hours = rate

Two lines under it: hours you bill per week, hours you work per week. When the second is more than twice the first, the rate is the wrong lever; the calendar is the one that moves.

Today

Open last year's statements. Add up what came in. Then write down, honestly, the hours you worked to get it. Divide.

The number you get is what you were paid. Run the same sum on the quote you are about to send, before you send it.

Next week: the tool that didn't survive a real week.