← All posts
JourneyReflection

The month the work dried up

Wednesday 27 May 2026 · 4 min read · Rishi Gupta

Two deals slipped a month, a client paused a build, and an invoice I had counted on did not arrive.

None of these were disasters individually. Together, in the same three weeks, they were educational.

What I learned about my pipeline

I did not have one. I had a list of conversations I felt good about, which is a different thing.

A conversation is not pipeline unless it has a date attached and a defined next action. Everything else is optimism with a spreadsheet around it, and it will let you down at exactly the wrong moment.

What I actually changed

Every opportunity now has a next action with a date, or it is not in the pipeline. If I cannot name what happens next and when, it is a nice chat, and I stop counting it as revenue that has not arrived yet.

I also started tracking how many promises I had made and not yet kept — things I said I would send and had not. That number was much higher than I expected, and closing it turned out to be the cheapest source of new work available to me.

The uncomfortable realisation

A quiet month is usually created eight weeks earlier, during a busy one, when you stop doing the unglamorous work because delivery is loud and urgent.

The feast causes the famine. I know that now, and I still have to fight it.

Got a version of this problem? Twenty minutes minimum, seven questions, and a one-page Bottleneck Blueprint within 48 hours. If it's not a fit, we'll say so.

Book a call → Not ready to talk? Take the eight-question AI assessment →
Keep reading
The work I would not hand over to software
Friday 16 October 2026 · 4 min
The build was finished. Then nobody logged in for twenty days.
Sunday 11 October 2026 · 4 min
Sixty hours of paperwork is not a paperwork problem
Thursday 8 October 2026 · 4 min