What a Project Really Paid You Per Hour

Picture two projects. A designer agrees to build a brand kit for a small bakery for a fixed fee. A month later she agrees to a similar-sized job for a consultancy at the same fee. On paper they are twins. In her bank account they are, too.

But one of them swallowed forty hours and the other swallowed ninety. She only finds out if she wrote the hours down. Without that record, both jobs feel like "a good month", and she will happily say yes to the second kind again.

This post is about using a simple time log for one purpose: finding out what each piece of work really paid you per hour, and acting on it.

A fee is a price, not a rate

When you charge per project, the number on the invoice tells you what the client pays. It says nothing about what you earn. Your real rate is the fee divided by every hour the job took, including the ones nobody saw.

Those hidden hours add up fast:

• Email threads and quick calls that "only took a minute"
• Extra revision rounds past what you planned
• Waiting for files, then rebuilding your focus when they arrive
• Writing the proposal, sending the invoice, following up

Even hourly freelancers lose time this way. If you bill only the hours you remember, you under-bill. A log fixes both problems.

Start with a loose log, not a perfect one

Most people quit tracking because they aim for second-by-second accuracy. You do not need that. You need a log that is honest to the nearest ten or fifteen minutes.

Pick any tool you will actually open: a timer app, a spreadsheet, even a notebook next to the keyboard. Each entry needs only three things:

1. Which client or project
2. What kind of work it was
3. How long it took

Keep it up for four weeks. A single week can mislead you, because one unusual deadline will distort everything. Four weeks gives you enough of a pattern to trust.

Sort your hours into three buckets

At the end of the month, group every entry into one of three buckets.

Paid delivery

The work a client is paying for directly: designing, writing, coding, editing, consulting.

Project overhead

Time tied to a client but not part of the deliverable: messages, meetings, revisions, chasing feedback. This bucket is the one that surprises people most.

Running the business

Finding new clients, sending invoices, bookkeeping, learning a tool, tidying files. No single client pays for it, yet it keeps the business alive.

Now compare the buckets. Many freelancers expect delivery to dominate. Often it is closer to half of the working week. That is not a failure. It is a fact you can plan around.

Work out your real rate per client

For each client, add the delivery hours and the overhead hours. Then divide what they paid by that total.

Say a copywriter has three clients in a month:

• Client A pays a steady fee, sends clear briefs and approves quickly. The effective rate is high.
• Client B pays the same fee but rewrites the brief halfway through. The effective rate is about half.
• Client C pays less, yet the work is repeatable and takes little back-and-forth. The rate beats Client B.

These are invented numbers, but the shape is familiar. The biggest fee is rarely the best client. The best client is the one with the best fee per hour actually spent.

What to do with the answer

A log is only useful if it changes a decision. Here are the moves that usually follow.

Reprice the expensive kind of work

If a type of project always runs long, your price was based on a guess. Replace the guess with your tracked average, and add a margin for overhead. You now have a number you can defend.

Limit the revision rounds

If the log shows revision time eating your margin, write a fixed number of rounds into your next quote, and a clear hourly price for extras. Clients rarely mind a limit when it is stated before work starts.

Fire or fix the worst performer

One client at a very low effective rate can drag down a whole month. Raise their price, change how they send feedback, or let them go. You will usually find the hours you free up are easy to fill with better work.

Quote with confidence

The next time someone asks "how long will this take?", you will not be guessing. You will say, "Similar projects took me about this many hours", and price from that.

Bill the hours you can prove

If you charge by the hour, a log has a second job: it makes your invoice easy to defend. A client who sees a clear list of tasks and time per task is far less likely to dispute the total than one who sees a single line saying "consulting".

In TickPaid you can add each task as its own line on an invoice, using saved services with their prices, so the client reads exactly what they are paying for. Later, the reports show what you invoiced per client, which pairs well with your hours: divide one by the other and you have the rate from the section above without opening a spreadsheet.

Watch out for the common traps

• Only logging billable work. Then your numbers look great and tell you nothing. Log the overhead too.
• Logging at the end of the day. Memory rounds time down. Log as you go, or at least after each task.
• Judging yourself. The log is not a scorecard. A day with three hours of focused work is normal for many people. Use it to understand your rhythm, not to feel guilty.
• Stopping after the first insight. Run the log again after you reprice. Check that the change worked.

A small habit with a large payoff

You do not have to track forever. Many freelancers run a log for a month, learn what they needed, then repeat it every six months or whenever their work changes. Think of it as a health check for your pricing.

The reward is simple. You stop guessing which work is worth your time, and start knowing. Your price list, your quotes and your calendar all get better from that single piece of knowledge.

Start with one client you suspect is costing you more than they pay. Log the next two weeks of their work, divide, and look at the result. It might be good news. If it is not, you have just found your next price change.