How Many Tools Does a Solo Business Actually Need?

Somewhere in most solo consultants' first two years there's a month where the tool count quietly hits double figures. A CRM, an email platform, a scheduling link, an invoicing app, a proposal tool, a document signer, a project tracker, a form builder, a landing page, a payment processor. Nothing on that list was a bad decision on its own. Each one solved a real problem, on the day it was added, for a genuine reason.

The problem isn't any single tool. It's that nobody ever asked how many tools a solo business actually needs, because the question never came up in a way that forced an answer. Tools get added one at a time, under mild pressure, and removed almost never.

The Real Cost Isn't the Subscription

It's tempting to answer this with a monthly total — add up the subscriptions, see if the number looks reasonable. That's the wrong measurement, because the subscription cost is rarely where the damage happens. The real cost is what happens between the tools. A client's details live in the CRM. Their invoice history lives somewhere else. Their project notes live in a third place. None of that is a problem until you need all three at once — replying to a query, preparing for a call, working out whether someone's actually a repeat client — and the answer is scattered across systems that don't talk to each other.

That's not a productivity inconvenience. It's a specific, repeated tax on your attention, paid every single time you need a complete picture of one client and have to go looking for it in three places instead of one.

Why the Tool Count Grows Faster Than the Business Does

Every new tool gets added to solve a problem that exists right now, in front of you, usually with some urgency behind it — a client needs a proposal today, so you sign up for a proposal tool this afternoon. Nobody sits down first and asks what the whole stack should look like in a year. That question doesn't have any urgency attached to it, so it never gets asked, and the stack just accumulates one urgent decision at a time. The result is a set of tools that each made sense individually and makes no sense as a system. You end up maintaining integrations, remembering which tool does what, and re-entering the same client information three or four times, because nothing was ever designed to work together — it was assembled, one deadline at a time.

The Question Worth Asking Before the Next One

Before adding tool number nine or ten, it's worth asking a more specific question than "do I need this." A more useful one: does this tool need to know anything the others already know? If a new tool needs to know who your clients are, what they've bought, or what they owe — and it can't see any of that without you typing it in again — you're not solving the original problem. You're creating a fourth place client information can go missing from.

The tools that are actually worth adding on top of an existing stack are the ones that plug into what's already there — not the ones that quietly start a second, competing record of the same information.

What "Enough" Actually Looks Like

There isn't a single right number, and anyone who gives you one is guessing. But there's a useful test: could you explain your whole client-facing setup to another consultant in under two minutes, without needing a diagram? If yes, it's probably still a system. If it takes longer than that, or if the explanation involves the phrase "and then I copy that over to," it's stopped being one. For most solo consultants, that ends up meaning somewhere between one and three pieces of core infrastructure — not one tool per task, but one connected record that most tasks run through, plus maybe a couple of genuinely separate specialist tools for the things that don't fit into it.

The Honest Trade-Off

Consolidating a scattered stack down to something smaller isn't free. It usually costs a weekend of migration and a few weeks of finding your feet in something new — real cost, worth being upfront about rather than pretending it's nothing.

But it's a cost you pay once. The tax on a fragmented stack gets paid every week, indefinitely, in the form of the same small frictions repeating — until something changes. A weekend now is usually a better trade than years of paying the smaller cost forever.

I went deeper on one specific piece of this recently — comparing what a genuinely connected free plan gets you against a well-known course platform's paid tiers, in this piece on whether Kajabi has a free plan and what the alternative actually looks like in practice.

The number of tools was never really the question. The question is always whether they know about each other — and most stacks answer that one badly, one urgent decision at a time.