The Project I Lost Money on and Then Quoted the Same Way Again

I finished a project in October. It ran long, the scope shifted twice, and by the end I was working for somewhere below minimum wage. I knew it. I felt it in my chest every morning I opened my laptop.

In January, a similar project came in. Same type of work, similar client size, comparable deliverables. I sat down to write the quote.

And I quoted almost the same number I had in October.

Why does this happen

Because memory is optimistic. When you think back on a project, you remember the big blocks of work. The design phase. The writing. The main deliverables. You do not remember the three rounds of revisions, the two "quick calls" that ran ninety minutes, the admin time at the start and end, or the week you lost because the client went quiet and then came back with everything changed.

You compress it. The hard parts fade. The hours blur. And so the quote you write for the next project is based on a version of the last one that never quite existed.

I have done this more than once. Probably more than I realize.

What I found when I actually looked

After the January project also ran over, I finally did something I had been avoiding. I opened my time logs and compared both projects side by side.

Time-Trak keeps everything by project, so I could pull up each one and see exactly where the hours went. What I found was not surprising once I saw it. But I had genuinely not known before I looked.

In both projects, the work itself was close to what I had estimated. The design hours, the writing hours, all roughly on target. But there was a category of time I had never quoted for at all. Client communication. Revision cycles. Setup and handoff. That time was not zero. In both projects, it accounted for nearly 30 percent of the total hours.

I had been quoting for 70 percent of the job, every single time.

The uncomfortable part

The uncomfortable part is that I had the data after the first project. I just didn't look at it. I closed it out, moved on, told myself I'd do better next time, and then wrote the next quote from my gut.

The data was sitting there. The reports were available. I just didn't run them.

This is the part nobody talks about. Having a time tracker is not enough. You have to actually use the historical data when it matters, which is before you quote, not after you've already agreed to a number.

What I do now

Before I quote anything, I find the closest comparable project in my logs and I look at the full hour breakdown. Not the total, the breakdown. I look at every category. Communication, admin, revisions, everything.

Then I build the new quote from that. Not from memory.

The totals are usually higher than what my gut would have said. Sometimes significantly higher. But they're also accurate. And accurate quotes mean I don't end that sick, resentful feeling at the end of a project where I worked hard and got paid badly.

One more thing I started doing: I added a standing project entry in Time-Trak called "client communication" for every new project. Separate from the billable work. Just so I always have a clean record of what coordination actually costs me, per client, per project type.

Over six months, those entries told me something concrete. Some clients cost twice as much to manage as others, even when the work itself is identical.

That's not a feeling anymore. It's a number. And numbers are much easier to act on.

The quote you write from memory is always wrong

Not always too low. Sometimes it's fine. But you don't know which, and that uncertainty is exactly what good data removes.

Look at the last project before you price the next one. It takes ten minutes. It is the cheapest insurance you have.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots