How Much Pipeline Does a Solo Consultant Actually Need?

How much pipeline does a solo consultant actually need?

Less than a sales team needs, and for a different reason. A sales team sizes pipeline against a quota it wants to beat. You size pipeline against a delivery calendar you cannot exceed. Once you understand that, most of the coverage advice written for sales organisations becomes actively misleading for a practice of one.

I price on a fixed fee, with most projects landing between $1,000 and $10,000, and I have done 70 or so projects for 25 or more clients across six years. That works out to roughly a dozen projects a year, give or take, which is a small enough number that ordinary sales arithmetic breaks down on it.

Small numbers behave differently. That is the whole subject of this article.

What is pipeline coverage, and why does the standard version mislead you?

Pipeline coverage is the total value of your open opportunities divided by the revenue you are trying to book in a period. A sales team carrying several times its target is holding a buffer against a known loss rate. The logic is sound when you have enough deals for a loss rate to mean anything.

With a dozen projects a year, it does not. A rate calculated over twelve events is barely a rate at all, and building a forecast on it gives you false precision dressed as rigour. Two unusual months in a row will move your apparent win rate by an amount that has nothing to do with how you are actually selling.

The second problem is more important. A sales team wants more pipeline without limit, because more closed deals is always better. You do not. You have a ceiling, and pipeline beyond that ceiling is not a buffer, it is a queue of people you are going to disappoint.

What numbers do you actually need to know?

Four. How many projects you can deliver well at once. How long a typical project occupies you. What a typical project is worth. And how long it takes from first conversation to signed agreement. Everything else is decoration until you have those.

Notice that three of the four are about delivery rather than sales. That is not an accident. For a solo practice the binding constraint is almost always capacity, and a pipeline calculation that ignores capacity is answering a question you do not have.

Write them down somewhere durable. Airtable, Notion, a HubSpot record, or a plain spreadsheet, it genuinely does not matter which. What matters is that the numbers come from what actually happened rather than from what you remember, because memory systematically over weights the last conversation you had.

Why does capacity change the math more than win rate does?

Because capacity is a hard limit and win rate is a soft one. If you can run three projects at once and each takes two months, your year has a shape regardless of how good your sales conversations are. Improving your win rate against a full calendar changes nothing except which clients you take.

This is why I decided some time ago to cap how many active engagements I carry, and I have written separately about why I cap my active client count. The cap is not modesty. It is the number that makes every other number in this calculation meaningful.

Once the cap exists, the pipeline question inverts in a useful way. You are no longer asking how much pipeline do I need to hit a target. You are asking how much pipeline do I need so that the next slot on my calendar is filled by someone I want to work with. That is a smaller number and a better question.

What does a realistic month look like when you work backwards?

Start from the slot, not the revenue. Say a slot opens in six weeks, a typical engagement is worth a certain amount, and it takes you a month from first conversation to signature. Then the conversations that fill that slot have to be happening now, and the useful question is whether you have enough live ones.

For a practice at my scale, enough is usually a very small integer. Two or three genuinely qualified conversations for one slot, not thirty leads. I would much rather have three people who have described a real problem and asked what it would cost than a list of forty who downloaded something.

Notice what that does to your marketing. If you need three real conversations to fill a slot and you have a handful of slots a year, you do not need volume, you need the right few. That realisation is why referrals have outperformed paid acquisition for me by a wide margin, and why writing has done more than advertising ever did.

Why is the lag between conversation and cash the number that kills you?

Because it is the one you cannot compress when you need to. If a month passes between a first call and a signature, and another month before the first payment lands, then a gap you notice today was created by something you did or did not do two months ago. By the time the problem is visible, the fix is already late.

This is the single most common failure I see in solo practices, and it has nothing to do with skill at the work. Someone gets busy delivering, stops having conversations for six weeks, delivers beautifully, and then discovers an empty calendar and a two month lag before anything can fill it. The gap is structural, not moral.

The defence is boring and it works. Keep some small, fixed amount of business development happening during delivery, even when you do not need it, precisely because the cost of restarting from zero is measured in months. A little every week beats a scramble every quarter.

What should you do when coverage is thin?

Go to the warmest source first, and be specific about what you are asking for. Past clients who were happy, people who referred you before, and anyone you had a good conversation with who was not ready at the time. A direct note to six people you already know beats a campaign to six hundred you do not.

Then shorten the distance to a decision on what you already have. Someone who has been thinking about it for two months does not need more nurturing, they need a smaller first step. A scoped, paid discovery piece is often the honest answer, and I have written about how I price a standalone audit for exactly this situation.

What I would not do is drop price to fill a slot. A discounted project occupies the same capacity as a full price one and sets an anchor you will negotiate against for as long as that client stays. An empty week is cheaper than a bad rate.

What should you do when coverage is too high?

Treat it as a pricing signal before you treat it as a scheduling problem. If more qualified people want to work with you than you can serve, and that persists across a few months rather than one lucky spell, you are priced below what the market will pay. That is useful information and most people sit on it for a year.

The other lever is selection rather than price. With more demand than capacity you can choose the work that compounds, meaning projects that teach you something, produce a case study, or come from a segment you want more of. That choice is the actual privilege of a full pipeline, and it is worth more than the extra revenue.

What you should not do is take the overflow and deliver it badly. A solo practice runs on reputation, and one rushed project costs more in referrals lost than it earned. Saying not right now, with a real date, keeps the relationship intact.

What should you do next?

Write down your four numbers this week, from records rather than memory: how many projects you can run at once, how long one takes, what one is worth, and how long from first conversation to signature. Then count how many genuinely qualified conversations you have live right now and compare it to how many slots open in the next quarter.

If the comparison makes you uncomfortable, that discomfort arrived roughly two months early, which is exactly when it is useful. If it looks fine, put a recurring reminder in your calendar to do this again, because the number that matters most is the one you check when nothing is wrong.

And if you are sitting on thin pipeline and want to talk through where the next few conversations should realistically come from, reach out. It is usually a shorter conversation than people expect.