CRM for consulting firms: what to look for, and what a sales CRM misses

Most CRMs on the market were designed around a sales team. A rep works a lead, moves a deal through stages, wins it, and hands it to someone else. The CRM’s job ends at “closed won”, and every report it produces is about getting there faster.

Consulting does not work like that. A firm sells an engagement, not a product. The scope is written for one client, the price depends on who does the work, and the moment the client signs is not the end of the sale but the start of the thing that was sold. The next engagement, which is where most consultancies make their money, comes out of how the current one is delivered.

So a consulting firm that buys a well-reviewed sales CRM often ends up with a very good record of everything before the signature and almost nothing after it. This post covers what a CRM for consulting firms should do differently, how to test it, and the questions worth asking.

Engagements, not transactions

Five differences explain most of the friction between consultancies and generic CRMs.

The relationship outlasts any deal. A client may buy one diagnostic this year, a transformation programme next year and an advisory retainer after that. The account, not the deal, is the unit that matters, and it has to carry years of history.

One account has many buyers. The finance director who bought the cost review is not the operations director who might buy the follow-on. Each contact has their own relationship with your partners, and the CRM should show who knows whom.

The deal is a scope, not a line item. A product deal has a SKU and a quantity. An engagement has phases, a team, assumptions and a fee basis: fixed price, time and materials, or a retainer. That detail usually lives in a proposal document the CRM cannot see.

Winning is the midpoint. Closed won is where the delivery team needs everything the partner learned during the sale. In a sales CRM that knowledge sits in notes and email threads, and the kickoff meeting exists mainly to say it aloud.

The next sale comes from delivery. Whether a client buys again depends on how the engagement went, whether it ran over budget, and whether invoices were paid on time. A CRM that cannot see delivery or billing cannot tell a partner which accounts are healthy.

What to look for in a CRM for consulting firms

Group the requirements by the life of an engagement rather than by feature list.

Relationships

• Accounts first, with many contacts per account and the history of every engagement.
• Email and calendar activity threaded against the account, not only against one contact.
• A summary of an account that includes delivery and billing, not just the last sales email.

Pipeline

• Stages you can rename, add and remove to match how you actually sell: discovery, proposal, negotiation, engagement letter, or whatever your firm calls them.
• A way to flag the transition that most often stalls, usually a proposal that has gone quiet.
• A forecast you can read honestly. Weighted pipeline is useful; it is not the same as capacity to deliver it.

Proposal and engagement letter

• The proposal written or stored against the deal, not attached as a loose file.
• An internal approval step before a proposal or engagement letter goes out.
• A clear record of which version the client signed.

The handover

• A won deal that opens the project, carrying scope, team, budget and deadline, and stays linked to it.
• Tasks and time that roll up to the account, so a partner can see delivery without asking.

Billing

• Invoices that read the client, terms and lines from the engagement rather than from a retyped copy.
• Payment status visible from the account, so “what do they owe us” has one answer.

The handover test

Feature lists flatter every vendor. Use one demo to walk a single engagement from end to end, and watch for the moment the presenter switches product, opens an export or says “integration”.

1. Create an account with two contacts at different levels.
2. Create a deal with a scope, a proposed team, a fee and a target start date.
3. Move it through your stages, including an internal approval before the proposal goes out.
4. Mark it won. Ask to see the project that was created, and where it shows the deal it came from.
5. Log a few hours against the project. Ask where those hours count against the budget that was sold.
6. Ask for a draft invoice for the first phase. Check that the client, terms and lines came from the engagement.
7. Go back to the account and ask: what is happening with this client right now?

A strong answer to step 7 includes the open opportunity, the running project, the budget position and the invoice. A weak answer shows you the last email.

We set out the same lifecycle in more detail, with a broader checklist, in how to run a consultancy on one system.

Where consulting CRMs fail in practice

It becomes the partners’ address book. Contacts go in, deals rarely do, and nothing after the signature ever appears. Within a year the CRM is a directory with a pipeline view nobody trusts.

The pipeline forecasts fees nobody can deliver. A sales CRM will happily show a strong quarter that the team has no capacity to staff. Pipeline and capacity are separate questions, and a firm should know which tool, if any, answers the second one. We look at that side in utilisation, budget and margin.

Custom fields sprawl. Without a model for phases, fee basis and team, firms add a field for each one, then a second field when the first was used inconsistently.

Notes become the system of record. The real scope is in a paragraph of free text on the deal, which nobody downstream reads.

The handover is a meeting. If the only way for delivery to learn what was sold is a kickoff call, the CRM is not doing the job.

Questions to put to any CRM vendor

• Can I redraw the pipeline stages myself, after go-live, without a consultant?
• Where does the proposal live, and how is it linked to the deal?
• What happens, in the system, when a deal is won?
• Can time and invoices be seen from the account, or only in another product?
• Is the client record in your CRM the same record your invoicing uses, or a synced copy?
• What does your CRM not do well for professional services? Name one thing.
• What does a full export of our data cost, and what format is it in?

How Cyril approaches it

Cyril treats the sale and the delivery as one relationship at two stages. Sales in B2B mode is account-first, with contacts and deals under each account, email and calendar activity threaded against it, and an AI summary on every record written from your own data.

For consultancies there is a researched starting point proposed at onboarding: five engagement stages, an approval rule before a proposal or engagement letter goes out, a follow-up task once discovery completes, and a notification to the owner when a proposal goes quiet. Each is a proposal you accept, edit or drop, and the stages are the default firms change most.

When a deal is won, the project can open from it on the same graph, so time logged counts against the engagement budget, and invoicing reads the client and lines from the deal itself. The detail is on CRM with projects and CRM with invoicing, and delivery itself is in Projects.

What it does not do: territory management and quota planning at the depth a large sales organisation expects, and firm-wide utilisation and bench planning across a large consultant pool. Treat both as absent today. Cyril is also pre-launch, with no customers yet.