The Solo Consultant's Feast and Famine Problem

Every independent consultant knows the pattern and most describe it the same way: three months flat out with no time to think, then six weeks of refreshing an inbox and wondering whether it is over. The usual explanation is that the market went quiet. It rarely did. The quiet period was created three months earlier, during the busy one, and by the time it shows up there is nothing to be done about it except wait.

Line up the timing and the mechanism is obvious. A project starts. Business development stops, because client work has deadlines and nothing else does. Nothing appears to go wrong, which is the trap: the consequence is delayed by exactly the length of a sales cycle. The project ends, the pipeline is empty, and the empty pipeline is now six weeks from producing anything even if you start today.

The lag is the whole problem. If stopping business development caused an immediate drop in enquiries, nobody would ever stop. It does not. It causes a drop one sales cycle later, at which point the cause is invisible and the effect feels like the market.

Not laziness, and not bad planning. Three structural reasons, all of which are rational in the moment.

The client work has dates and a person attached. Somebody is waiting for it and will notice if it is late. Nobody notices an unwritten post or an unmade call. Given a full week, anybody rational drops the task with no consequence.

Delivery is the thing you are good at. Consultants are independent because they are excellent at a craft, and business development is usually not that craft. Given a choice between the thing you are best at and the thing you are worst at, on a week when both cannot fit, the outcome is not a mystery.

Being busy feels like being safe. A full calendar reads as evidence that the business is working, right up until the calendar empties. It is the least reliable signal available and the most emotionally convincing one.

The mistake is designing a business development routine for a normal week. There are no normal weeks. Design it for your worst week and it will still be running when you need it.

Ask a consultant with a steady pipeline where the last ten projects came from and the answer is almost never a channel. It is a person: a client from four years ago who moved companies, a colleague from a previous firm, someone who saw a talk once and got back in touch when a budget appeared.

This has an unglamorous implication. Your most valuable marketing asset is a list of people who already know you, and the only thing it needs is to not go cold. It cannot be bought, it does not scale with spend, and it takes almost no time to maintain. It just has to be maintained continuously, which is precisely the thing a feast-and-famine cycle prevents.

Two practical points. Keep it somewhere that is not your inbox, because an inbox has no memory of who you have not spoken to in a year. And record why each person matters, not just their email; a list of addresses is a mailing list, a list of relationships is a pipeline.

The uncomfortable skill. Most solo consultants only sell when they can see the gap, which guarantees the gap arrives, because the sales cycle is longer than the visibility.

The arithmetic is simple and worth doing once. Take your typical time from first conversation to signed work, add your typical project length, and that is how far ahead you should be talking. If it takes six weeks to close and projects run three months, the conversations you have this week are about work starting in four or five months.

Selling that far out feels dishonest to a lot of consultants, as though you are promising availability you cannot guarantee. You are not. You are having a conversation about a problem that will still exist in four months, and the timing question resolves itself later. The alternative is having the same conversation from a position of visible need, which is worse for both the rate and the fit.

A solo consultant has no team, so anything that can run without you is worth more than it would be to a company with staff. But the line matters, because getting it wrong damages exactly the relationships the business runs on.

Automate the remembering. Who to contact and when. The nudge that says you have not spoken to this person in five months. The reminder that a project ends in three weeks so the next conversation should already be happening. This is pure administration and you will not do it reliably by hand.

Automate the acknowledgement. An enquiry that arrives while you are in a workshop should get a reply within minutes saying a real one is coming. That single message is often the difference between being considered and being too late.

Never automate the message itself. Your entire advantage over a firm is that you are a specific person with a specific view. A generated check-in to someone who has known you for six years is worse than silence, because silence is neutral and a hollow note is evidence. Let a system tell you who to write to; write it yourself.

That line, machine handles the queue and the human handles the judgement, is the same one that shows up in every one-person business that runs marketing without a marketing department. For consultants the stakes are just more personal, because the list is not a database of leads. It is everyone you have worked with. The consultant overview covers how the rest of the workflow fits around it.