Five things, five stages, zero revenue

A few weeks ago I sat down and listed everything I was working on. One project was about 75 percent done. One was maybe 25 percent done. One had just been started. One was still an idea I had been brainstorming. And one was a side project I kept tinkering with whenever I needed a break.

None of them were generating revenue. Not one.

I had spread myself across five different things and made meaningful progress on none of them. Each one felt important. Each one had a reason to exist. But the result was the same. A bunch of half-built stuff and an empty bank account.

This is the trap. And if you are a solo operator, freelancer, or anyone running a one-person business, you have probably been in it.

Why it happens

The solo operator trap is not about laziness or lack of discipline. It is about optionality feeling productive.

When you have multiple projects in flight, switching between them feels like progress. You spent an hour on the client site, then pivoted to tweak your portfolio, then opened up the cold email script you have been meaning to finish, then got distracted by a new domain idea that could be really cool if you just spent 15 minutes mocking it up.

Every switch feels like a decision. And decisions feel like work. But at the end of the night you have advanced nothing to the point where it can actually pay you.

I catch myself doing this constantly. I will have a client site that needs three more pages to launch and instead I will spend an hour buying old domains I used to own for nostalgia reasons, or playing with a crypto directory design because it is more interesting than writing copy for a services page.

The interesting thing always wins over the necessary thing if you do not have a system.

The one rule

The rule I use now is simple. Work on whatever is closest to getting paid.

That is it. No priority matrix. No time blocking spreadsheet. No Eisenhower quadrant. Just one question: which of these projects will put money in my account the soonest?

Once there is an answer, that project gets 100 percent of tonight’s work session. Everything else waits.

When I have a client site with a deadline and an invoice attached, the answer is obvious. That goes to the top. Nothing else matters until it ships.

The harder scenario is when nothing has a deadline. No client is waiting. No invoice is pending. You are in what I call the limbo period, where everything feels equally important and nothing feels urgent.

In limbo, the rule still applies. You just have to be honest about the answer. Which of these half-finished things, if I finished it tonight, would lead to revenue the fastest?

For me right now that means building a site for a new consulting client who came through a warm introduction. It is not the most exciting project on my list. But it is the clearest path to an invoice. So it goes first.

What goes on the back burner

Everything that is not the closest-to-paid project becomes a break activity. This is important because you need breaks. Working four hours straight without pausing is not sustainable and the quality drops.

But the break activity matters. Doom scrolling Twitter or browsing Facebook Marketplace for 15 minutes is a net negative. It drains energy and gives nothing back.

Playing with a side project for 15 minutes, like mocking up a crypto exchange directory or sketching out a family photo site, is a net positive. You are still building. You are still learning. You are just doing it in small doses instead of letting it consume your main work session.

I bought two old domains recently that I used to run years ago. A news site and a local Milwaukee blog. Both have basically zero domain authority at this point. The backlinks are spammy. The old content is gone. There is no strategic reason to own them.

But they cost $20 total and working on them for 10 minutes between build sessions is more productive than staring at my phone. So they stay on the back burner as break projects. They just never get promoted to the main session unless something changes.

The deadline and money triggers

Two things reliably move a project to the top of the list.

Deadlines. When a client sets a launch date or a deliverable is due, that project automatically becomes priority one. This is not complicated. Miss a deadline and you lose trust, referrals, and possibly the client.

Money. When a project has a clear invoice attached to a clear deliverable, it jumps the queue. This is why client work always beats spec work, even when the spec work is more interesting or more fun.

The absence of both is what creates limbo. And limbo is where solo operators lose weeks and months without realizing it.

What I do in limbo now

When I do not have an active client deadline, I force a synthetic trigger. I pick the project closest to done and set my own deadline. Not a vague “I should finish this soon” deadline. A specific “this ships by Thursday night” deadline.

Then I tell someone about it. A friend, a partner, anyone who will casually ask “did you finish that thing?” in three days. External accountability is a cheap substitute for a real deadline but it works better than nothing.

The other thing I do is keep a running list of tasks ranked by distance to revenue. Not priority. Not importance. Distance to revenue. How many steps between this task and money hitting my account?

A task like “finish the about page for the consulting client site” is maybe two steps from revenue. Finish the page, send the invoice. That ranks higher than “set up TikTok account for content engine” which is about fifteen steps from revenue even though it might be strategically important in the long run.

Fifteen-step tasks are real. They matter. But they do not get tonight’s work session.

The uncomfortable truth

The reason this trap exists is because starting new things feels better than finishing old things. The beginning of a project is pure potential. Everything is possible. Nothing has gone wrong yet. You have not hit the tedious parts where you are debugging a booking drawer integration at 2am or writing the seventh location page for a multi-location client.

Finishing requires grinding through the boring parts. And when you are the only one holding yourself accountable, it is very easy to convince yourself that switching to something new is a strategic decision rather than an avoidance behavior.

I still fall into this. Probably always will. But the rule helps. Work on whatever is closest to getting paid. Ask the question at the start of every session. Be honest about the answer. And save the fun stuff for breaks.