The Project I Quoted in Ten Minutes and Regretted for Three Months

The brief came in on a Friday afternoon. The client needed a response by Monday morning. I looked at the scope, thought about a similar project I had done the year before, picked a number that felt right, and sent the proposal.

They accepted within the hour.

That fast reply should have told me something.

The Similar Project Was Not Similar

I was doing brand work, copywriting, and some light creative direction. The project I was comparing to in my head had gone smoothly. About three weeks, clean feedback, one revision round. I had made decent money on it.

What I did not remember, because I had not tracked that project properly either, was that the smooth project was smooth because the client already had a style guide, clear brand voice documentation, and a team member who was dedicated to the handoff. The new client had none of that.

I found this out on day three.

What I thought was a three-week project became a nine-week project. Not because scope changed dramatically. Because every assumption I had made about what already existed was wrong. I was building the foundation and the house at the same price I had quoted for just the house.

The Hours Were Right There If I Had Looked

Here is the thing that still bothers me. The data to quote that project correctly existed. I had done similar work before. I just had not logged it in a way that let me read it back.

I had some rough notes in a Google Doc. A few invoice line items that said things like "Brand copywriting, week 2." No task breakdown. No hour count per phase. Nothing that would have told me how long the discovery work actually took, separate from the writing, separate from the revision cycles.

If I had been running a real time tracker on my previous projects, I could have opened my logs and seen exactly what foundation-building work costs in hours. I could have looked at a real number instead of a feeling.

Instead I quoted from a memory that was already fuzzy, for a project that only superficially resembled my reference point.

What Three Months Looks Like When You Are Losing

I kept working on the project because the contract was signed and I am not someone who walks away. But I tracked every hour once I realized how badly I had miscalculated.

By the end, I had logged roughly 140 hours on a project I had priced for 60. My effective hourly rate was less than half of what I charge. I was clearing less per hour than I had in my first year of freelancing.

The client was happy. They left a good review. From their side, they got tremendous value.

From my side, I worked most of a quarter at a loss.

The Rule I Set After That

No more quoting from memory. Every new project proposal now gets built from real logged data.

I run time-trak on everything. Discovery calls, proposal writing, project phases, revision rounds, final delivery. It all gets logged and labeled. When a new brief comes in, I search my history for projects with similar characteristics and read the actual hours. Not what I remember. What the timer recorded.

The discovery phase on a client without existing brand assets takes a specific number of hours. I now know what that number is because I have tracked it across multiple projects. I build that into every quote where it applies.

It also changed how I read new briefs. I look for the thing that is going to take longer than it seems. Usually it is the thing the client mentions casually in one line, like they assume it already exists.

Quoting in ten minutes might feel efficient. What it actually does is transfer the cost of your rushed thinking into weeks of undercompensated work. The ten minutes you spend reading your own data before you quote is the highest-value ten minutes in any project.

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