The thirty-second question
The email always looks the same. “Hey, do you have capacity for a project starting in a couple of weeks?”
The cursor blinks in the reply box. And here is the thing I am not proud of: I can feel the answer I want to give before I have checked a single thing. The work looks fun. The money is real. So I type “Yeah, I can fit that in,” and I hit send, because actually checking is annoying and the optimistic version of me is always already typing.
That is a zero-second answer to a thirty-second question. And a wrong yes does not bounce back at you right away. It is patient. It waits about six weeks, and then it shows up as a weekend you did not plan to work, and a Sunday-night feeling in your chest that you have started to recognize.
For years, “Can I take this?” was the single most expensive question in my business, and I kept answering it the worst possible way.
Stage one: I kept it all in my head
My first system was no system. I had a vibe. A rough sense of “I’m busyish right now” or “I’ve got a bit of room.” Most weeks that vibe was approximately true, which is exactly why it was so dangerous.
Memory has two failure modes, and freelancing finds both.
First, memory is recency-biased. I could feel this week’s load in my body. The three commitments that quietly kicked in next month were invisible, because they were not happening to me yet.
Second, memory is optimistic. When I tried to picture my availability, I counted the hours I wished I had, not the hours I had already promised to other people. The promised hours do not feel like spending. They feel like nothing, until they arrive all at once.
Like this one time where a regular client asked me whether I could pick up a greenfield software development project over the coming 12 weeks. I said yes but didn’t take into account the one commitment I had already made that would start 4 weeks in the future.
The real cost was never visible as a number. It was visible as mood. Saying yes felt free in the moment and got billed back to me later, in evenings and weekends, with interest. “Am I going to be working weekends again?” is not a scheduling question. It is the sound of a capacity decision you made eight weeks ago and cannot take back.
Stage two: the spreadsheet
Eventually I got tired of being surprised by my own calendar, so I did what freelancers do when they get serious about a problem. I built a spreadsheet.
I lined up the calendar weeks as rows and projects as columns. I tried to project which project would swallow how many hours in the future. I could see at a glance how I was doing on a week-per-week basis.
For the first time, the answer to “Can I take this?” stopped being a feeling and became a subtraction. Capacity, minus what I had already committed, equals the room I actually have. That is it. That is the whole formula, and it changed how the question felt to answer.
I want to flag something I only learned later, when I started talking to other freelancers about this. I was not special. Several people I interviewed had independently invented the same coping strategy: think in hours per week, treat your capacity like a budget. One put it about as cleanly as it can be put. He knew his total capacity was thirty billable hours a week, full stop, so any new request was just arithmetic against that ceiling. The budget framing is not a niche trick. It is what careful freelancers reach for on their own.
So the spreadsheet was a real upgrade. And then it failed me too, just more slowly.
The spreadsheet only told the truth on the day I updated it. By Wednesday it was already drifting into fiction. Worse, it never reconciled with what I had actually logged in Harvest, so the two slowly disagreed, and they disagreed most at the exact moment I leaned on the spreadsheet to make a decision.
And manual upkeep is a tax you pay forever. The people who most need a current capacity number are the busiest ones, and the busiest ones are precisely the people who will not keep a side-spreadsheet up to date. One freelancer I spoke to hated manual tracking so much that he wrote a little automation script to log his hours for him. That is the energy here. Nobody wants to maintain the map. They just want the answer.
Stage three: the app, and the thing I finally understood
Here is the realization that took me embarrassingly long to reach: I already had the data.
Every billable hour I had worked was already sitting in my time tracker. I was not missing information, I was missing a direction. My tracker is a rear-view mirror: It is very good at telling me where my hours went last week, and completely silent on the only question I actually care about, which is whether I can take on more next month.
The spreadsheet had taught me the formula: capacity minus commitments. The tracker already held the inputs. The single missing piece was something that pointed the data I was already collecting forward instead of backward.
So I built it. (It is called Crow’s Nest, and turning logged hours into a forward-looking “do I have room” answer is the entire point of it. That is the only sentence of sales pitch in this article, and now we are done with it.)
What you can steal from this today
You do not need my app to get most of the way here. You need about twenty minutes and the willingness to write down a number you might not like. Here is the method, stripped down:
- Write your real weekly capacity in billable hours. Not the hours in a workday. The hours you can actually bill in a week before the quality of your life starts to drop. For a lot of people that honest number is somewhere around 25 to 30, not 40.
- List your current commitments as hours per week, per client. Be pessimistic. The retainer that is “about five hours” is six.
- Subtract. Capacity minus commitments. Whatever is left is your room. That is the number.
- Stop answering capacity emails from your inbox. When the next “do you have capacity?” lands, do not reply from your gut. Reply from the number.
Two honest caveats. A stale spreadsheet still beats memory, so build the spreadsheet even if you know you will not maintain it perfectly. And the only durable way to keep that number from rotting is to base it on the time you are already logging, instead of on a second set of figures you have to keep alive by hand. That is the wall I hit, and it is the wall that turned a spreadsheet into an app.
The close
The thirty-second question deserves a thirty-second answer you can actually trust. I spent years giving it a zero-second answer from memory, and then a high-maintenance answer from a spreadsheet, before I built the one I genuinely wanted. You can start with the spreadsheet this afternoon. It will be better than your memory by Friday.