What I Found When I Timed Everything for Seven Days Straight

The experiment

A freelancer friend dared me to time everything for a week. Not just client work. Everything. Every email. Every admin task. Every time I wandered off to do something that felt like work but probably was not.

I said sure, thinking I would confirm what I already believed: that I was a fairly efficient person who used time well.

I was wrong in a few specific and expensive ways.

Monday: the warm-up problem

I started my timer at 9am. By 11am I had logged forty minutes of actual client work. The rest was email, a Slack rabbit hole, reorganizing a folder I did not need to reorganize, and reading a tool comparison article that had nothing to do with anything due that week.

I knew I had a warm-up problem. I did not know it was consuming most of my productive morning.

Monday's billable total: two hours and twenty minutes. My mental estimate going in had been closer to five.

Tuesday through Thursday: the revision gap

This is where it got interesting. I had a client project that felt like it was in good shape. A design deliverable, mostly done, just needing polish.

When I looked at my tracked hours by end of Thursday, that project had consumed eleven hours that week. I had budgeted eight for the entire revision phase. The extra three hours were a mix of small changes that each felt minor, one rework that was technically my fault, and a long email thread that required reading the original brief again because the feedback was contradictory.

None of those three hours were on anyone's radar but mine.

The admin number

Here is the one that hurt the most: I tracked every non-billable admin task with its own category. Invoicing, scheduling, proposals, file organization, tool maintenance, reading industry stuff.

By Friday afternoon I had spent nine hours on admin across the week.

Nine hours. At my standard hourly rate that was over $1,100 in time that no client would ever see on an invoice.

Some of that is unavoidable. But I had never quantified it before. I had just absorbed it as part of the cost of freelancing without ever asking whether I was pricing my services to cover it.

The screenshot surprise

I was using Time-Trak during the experiment and had automatic screenshots running. I looked through them on Friday.

What I found was a pattern I could not have noticed in real time. Between 2pm and 4pm almost every day, my screenshots showed browser tabs that had nothing to do with the task I had running on my timer. I was technically clocked in. I was not technically working.

Seeing it in actual images was different from knowing it in theory. It was not accusatory. It was just accurate. And accurate was what I needed.

What the week cost me in real terms

Billable hours logged: twenty-two hours.

My estimate at the start of the week: thirty-five.

Hours spent on tasks that could have been batched or cut: roughly six.

Hours lost to slow starts and mid-afternoon drift: around five.

That gap, thirteen hours over a single week, represents money I was not earning and time I was not protecting. Across a month it becomes a real problem. Across a year it is the reason a lot of freelancers feel busy but not profitable.

What changed after

I restructured my mornings so the first task is something I can start immediately. No email until that first timer session closes.

I added a proper admin budget to every project quote. Not a guess. A number based on what the week showed me.

I started doing a quick time review every Friday before I closed out. Not to punish myself for slow days. Just to see what the week actually contained before I forgot.

One week of data did more for my freelance business than two years of gut instinct.

Time the whole week once. You will not need a second experiment to understand what you find.

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