The Project You Priced as Simple and Worked Complex

The brief was clean. Two pages. The deliverable was clear. The timeline was reasonable. I quoted it fast because I had done similar work before and it went fine.

It did not go fine.

The client had three internal stakeholders with conflicting opinions. Every revision reset something a different person had already approved. There were seven rounds of feedback on a project I quoted for two. By the end I had worked more than twice the hours I planned and invoiced for exactly what I originally said I would.

I smiled through the final call and never quoted that type of project the same way again.

Simple-Looking Projects Have a Pattern

There are specific project types that consistently expand. Small website redesigns. Single-deliverable decks. Short-form copy. One-page anything. They feel quick at the pitch stage because the output is small. But the output being small doesn't mean the process is simple.

Complexity doesn't come from the size of the file you hand over. It comes from how many people touch decisions, how clear the client is internally, and how much the brief was really understood before you started.

You can't always know this upfront. But you can track it after, and use that data the next time.

What Tracking Hours Actually Catches

When I started logging time seriously, the first thing I noticed wasn't how long my tasks took. It was how often I worked on projects I had already closed in my head.

Revision rounds that came after I thought we were done. Calls I didn't count as part of the project. Small edits that each took fifteen minutes but added up to four hours across a week. None of that was on my invoice because I hadn't tracked it clearly enough to defend it.

Time-Trak's floating timer made it easier to stay honest with myself. I started the timer when I opened the client's file. I stopped it when I closed it. That was it. No estimating at the end of the day. No trying to reconstruct my afternoon from memory.

The logs started showing me exactly where the extra hours were going.

The Quote You Build From Gut vs. the Quote You Build From Data

Gut quoting is fast. It's also how you end up working complex projects at simple rates.

When you have clean time logs from previous projects, you can find comparable work and look at what it actually took. Not what you thought it would take. Not what the brief suggested. What it took.

That comparison is usually sobering. Projects that felt quick often logged at 40 or 50 percent more hours than the quote assumed. When you see that pattern repeat across multiple clients, you stop calling things simple.

How to Build In a Complexity Buffer

For any project with multiple decision-makers, add time. Not a vague amount. A specific number based on your logs showing how much extra revision rounds typically cost you.

For any project where the brief came to you verbally, add time for clarification work. Discovery calls, follow-up questions, summary documents. That's all real work.

For any project type you've done before and found harder than expected, look at your historical logs before you quote. Time-Trak lets you pull reports by project type so you can see patterns instead of relying on selective memory.

The Habit That Protects Your Rate

Before every quote, run a quick check. Have I done this type of project before? What did my logs say about it? Where did the time actually go?

If you don't have logs yet, start now. Your next quote will be better. The one after that will be better still.

The project I got burned on became the most useful data point in my pricing. I just wish I had captured it sooner.

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