Why Your Project Quotes Are Always Wrong (And the Log That Fixes It)

Every freelancer I know has a number in their head for how long things take. "A landing page? Two days." "A logo revision round? An afternoon." We quote from that number. And that number is almost always wrong.

The problem: you quote from memory, not measurement

Here's the trap. You finish a project, feel good, and move on. Six weeks later a similar project comes in and you pull a quote out of the same fuzzy memory that has quietly forgotten the two evenings you spent untangling the client's brand assets, the three rounds of "small" revisions, and the hour you lost every morning just reloading context.

So you quote for the happy path — the version of the project where nothing goes sideways. Then reality shows up, the hours balloon, and you eat the difference. Not because you're slow. Because you estimated against a memory that was edited to make you feel competent.

Underquoting doesn't feel like a crisis. It feels like a slightly disappointing month, over and over.

The fix: keep an actuals log

You don't need a methodology. You need one habit: after every project, write down what you estimated and what it actually took. Two numbers and a one-line note.

A minimal version looks like this:

| Project type      | Quoted (hrs) | Actual (hrs) | Note                          |
|-------------------|--------------|--------------|-------------------------------|
| Landing page      | 16           | 27           | Client assets were a mess     |
| Logo, 3 concepts  | 8            | 14           | Revision rounds ran long      |
| Blog, 1500 words  | 4            | 5.5          | Research heavier than assumed |

Do this five times and something uncomfortable but useful happens: you get a personal multiplier. Mine hovered around 1.6x for design work — meaning my gut estimate needed to be multiplied by 1.6 to land near reality. That single number changed my quoting more than any pricing course.

Why the actuals are the hard part

The estimate is easy — you write it when you send the quote. The actual is where everyone falls off, because reconstructing real hours at the end of a project means fighting the same faulty memory that caused the problem in the first place.

The only reliable way to know your actual hours is to have captured them as they happened, in small pieces, without ceremony. That's the whole reason time tracking exists — not for surveillance, but so future-you can quote honestly.

This is where a low-friction tracker earns its place. I use FillTheTimesheet so the "actual hours" column fills itself from what I logged during the work, instead of me guessing on a Friday. The point isn't the tool — it's that your actuals need to be a byproduct of working, not a separate chore you'll skip.

Key takeaways

• Your mental estimate is edited to make you look good; it's not data.
• Underquoting rarely feels dramatic — it just quietly caps your income.
• Log estimated vs. actual hours after every project. Two numbers, one note.
• After ~5 projects you'll have a personal multiplier worth more than any template.
• The actuals only exist if you captured time as you worked — that's the part to automate.

Quote from a spreadsheet of what actually happened, not from the story you tell yourself about how it went.