The Project I Took On During a Slow Month

It Was Quiet and I Was Scared

February was dead. No new leads, two clients on pause, and a bank account that was starting to make my stomach tighten every time I looked at it.

Then an email came in. Someone needed a full content package. Fast turnaround. Budget was lower than I wanted but not zero. They were nice about it. Apologetic even. "We know it's tight but we really believe in what you do."

I said yes.

The Rationalizations Came Quickly

I told myself it was better than nothing. I told myself the work would be fast and the client seemed low-maintenance. I told myself slow months were a good time to take anything, just to keep the machine moving.

I did not check my actual capacity. I did not look at how long similar projects had taken me. I did not run any kind of estimate against real data.

I just said yes and started work the next morning.

What the Time Log Showed Later

By the time I invoiced, I had been tracking properly for about two months. Time-Trak had logs on everything. When I looked back at this project specifically, the numbers made me feel a little sick.

I had worked 41 hours on a project I had mentally budgeted for 20. The low rate I had accepted made sense for 20 hours of work. At 41 hours, I made less than I would have at a part-time minimum wage job.

The client had not been difficult. There was no dramatic scope creep, no blown deadlines, no chaos. The project just took longer than I had imagined, because I had imagined it without any real reference point.

Slow Months Mess With Your Judgment

When things are busy, you say no to low budgets almost automatically. You do not have the space and you know it.

When things are slow, the same budget looks different. It looks like rent. It looks like relief. So you agree without checking whether the math actually works, because fear is doing the math for you.

The only way to cut through that is data. If I had looked at my logs from similar projects before agreeing, I would have seen that this type of work consistently takes me between 35 and 45 hours. I could have either negotiated the rate up or walked away informed instead of walking away burned.

The Opportunity Cost Nobody Talks About

While I was buried in this underpaid project, two decent leads came through. I was too deep in delivery to respond properly. One of them found someone else.

That is the part slow months do not show you. Taking bad work does not just cost you in rate. It costs you in availability. You fill the slow time with low-value work and then you are not free when something better arrives.

My time log made this visible in a way that gut feeling never could. I could see exactly which weeks I was overbooked on the low-rate project and cross-reference that against when the other leads had come in.

What I Do Differently Now

Before I say yes to anything, I look at how long similar projects have actually taken. Not how long I think they should take. How long they have taken, logged in real time entries.

I build a rough hour estimate from that data and then apply the proposed rate. If the number does not work, I either push back on rate or pass.

Slow months still happen. But now I know that taking bad work because I am scared does not fix a slow month. It just makes the next month harder.

The Timer Is Not Just for Billing

I used to think of time tracking as something I did to build invoices. The log as receipt.

But the data does something else. It builds a reference library. Every project I track is a data point I can use to evaluate the next one. The more logs I have, the better my estimates get.

The slow month will come again. When it does, I want data telling me what to do, not fear.

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