CRM for Solo Consultants: You Probably Need a Database, Not a CRM
A sales pipeline tool is built for people who chase many small deals. A solo consultant chases three large ones. That mismatch is why most CRMs feel like overhead.
Marketing & SEO · Updated Oct 23, 2026
A CRM is a machine for moving many opportunities through a pipeline without dropping any. It assumes a sales team, a defined funnel, and enough volume that memory stops working.
A solo consultant has the opposite shape. Maybe fifteen conversations a year, of which three become projects. The information that matters is not "which stage is this deal at" but "what did we agree in the last call, who else is involved, and what did I promise to send."
That is a different problem, and most CRMs answer the wrong one.
The mismatch, stated plainly
| What a CRM optimises for | What a solo consultant needs |
|---|---|
| Many deals, small value each | Few deals, large value each |
| Pipeline stage progression | Conversation history and commitments |
| Team visibility and handoffs | A memory that survives six weeks |
| Automated sequences at volume | Judgement applied per client |
| Forecasting | Knowing who to follow up with this week |
Buying a CRM for a solo practice usually produces one of two outcomes: you pay for a system you do not maintain, or you spend a weekend configuring stages you will never move a deal through.
What actually goes wrong without a system
The failure is not lost deals. It is lost context.
Six weeks after a good conversation, you cannot remember whether you said you would send a proposal, whether they said budget was approved, or whether the person who introduced you is still there. So you write a vague follow-up, and the client reads it as disinterest.
That is the problem worth solving. It needs three things: a place to record what happened, a way to see who is waiting on you, and a reminder that survives your inbox.
The three workable setups
1. A database with a pipeline view
A general-purpose database with a table of people, a table of conversations, and a view grouped by status. This is the setup most solo consultants should start with, because it is exactly as complex as the problem.
What it gives you that a CRM does not: you define the fields. If "who introduced us" matters to your business, you add it in thirty seconds instead of discovering it is a custom field behind a paid tier.
What it costs you: nobody tells you how to use it, so you have to decide on a convention and keep it. The convention matters more than the tool — one row per conversation, always, with the date.
2. A document system with a person page
If you already write everything in a notes tool, one page per client with a reverse-chronological log at the top is genuinely sufficient for fifteen conversations a year. It is searchable, it is where you already are, and there is no new tool to maintain.
The weakness is the reminder layer. Documents do not tell you who is waiting. You need one separate place — a task list, a weekly review — where "follow up with X" actually appears on a day.
3. An actual CRM, for the right reasons
There are reasons to use a real one: you have a partner, you have a repeatable sales process with defined stages, you run outbound at volume, or you need to hand a deal to someone else.
If any of those are true, the CRM's overhead buys you something real. If none are, it is a subscription that makes you feel organised.
The fields that earn their place
Whether you use a database, a document, or a CRM, these are the fields that consistently matter for consulting:
- Name and organisation, plus how you met. The origin story determines how you open every later conversation.
- Status, but keep it to four values. Something like: talking, proposal out, won, dormant. Five or more stages will not be used honestly.
- Last contact date. The single most valuable column. Sort by it and you have your week.
- Next action and its date. If a row has no next action, the relationship is drifting, and you can see it at a glance.
- Who else is involved. The economic buyer, the person who will actually use the work, and the person who can veto it. Consultants lose deals to a stakeholder they never mapped.
- What they said the budget was. Write it down in their words, not your interpretation. It will be useful in three months.
The discipline that matters more than the tool
A CRM does not remember for you. Two habits do:
Log within an hour of the conversation. Not the whole call — three lines: what was decided, what you promised, what happens next. Written later, it becomes a summary of your impression rather than the facts.
Review weekly, sorted by last contact. Fifteen minutes. Anything with no next action gets one, or gets marked dormant. This single review is what keeps a practice from quietly losing its pipeline.
The most common consulting sales failure is not a bad pitch. It is a good conversation that nobody followed up on because it happened three weeks ago and the context is gone.
What about email marketing tools
They are a different category and worth keeping separate. A newsletter tool maintains a permission-based relationship with many people; a CRM-ish system tracks a small number of high-value relationships. Mixing them produces a list of five hundred people you email quarterly and three people you should be calling monthly.
If you have both, keep them in different tools and do not try to sync them. The overlap is smaller than it looks.
The honest recommendation
Start with one table in a database you already pay for, or one page per client in your notes tool. Add the six fields above. Log three lines after every call. Review weekly.
Do that for three months. If you find yourself wanting pipeline forecasting, team handoffs, or automated sequences, you have outgrown the simple setup and a CRM is now the right answer — and you will know which features you need, which is the part that no comparison article can tell you.
If you find yourself not maintaining it, the problem was never the tool. A CRM you do not update is more expensive than a notebook you do.