Proposals go quiet. Your pipeline should not.

Where does a services pipeline actually live?

Not in the CRM. In a services firm it is spread across partner inboxes, meeting notes, a proposal folder and the heads of four people who are all billable this week. The CRM record is a summary written after the fact, by someone who was feeling optimistic — which is why the number you report on Monday and the number that lands in the quarter are two different numbers.

You should not have to reconstruct the pipeline from four people's memories every Monday. And the cost of not knowing is sharper here than almost anywhere: the proposal that was going to fill Q3 is still open, still quiet, and two consultants roll off in three weeks with nothing to roll onto. By the time that is obvious, the fix is a discount.

• Your pipeline lives in inboxes

  A partner has four live conversations, two of which never became opportunities because opening a CRM record felt like admin. The firm-wide number gets assembled on Monday morning from memory and optimism.

• Proposals go quiet without dying

  Nobody says no to a consultancy. They say "let us come back to this after the board meeting", and then the board meeting moves. Six weeks later the proposal is still open and nobody can say what changed.

• Delivery knows things sales does not

  The team already staffed on the account has heard the client mention a hiring freeze. That is the most decision-relevant fact in your pipeline, and it lives nowhere your forecast can reach it.

• The CRM is whatever someone set up

  HubSpot with three custom fields, or a spreadsheet, or the timesheet system doing double duty. Any tool that needs a clean CRM before it says anything useful is a tool your firm will never adopt.

What does it take to see the real pipeline?

Three steps, and one of them is optional if your CRM is already HubSpot. No CRM clean-up project, no new fields for partners to fill in, nothing that depends on people logging things they have never logged.

1. 1

   Hand over one export

   A CRM report, the business development spreadsheet, or a timesheet export — whichever is the most complete record of client activity you actually have. If you run HubSpot, connect it read-only instead. Nothing in your systems changes either way.

2. 2

   Read the report on your own data

   Before a single score appears: which fields came through, which were ambiguous, which were missing, and what that means for what can be scored. That report is worth having even if you stop there.

3. 3

   Work the conversations that changed

   The proposals where the evidence has thinned, and the accounts where the relationship you thought you had has only ever involved one person. Each one comes with the specific next move.

Then Monday changes. The partner call opens with a number nobody has to defend from memory, a short list of client conversations worth a call this week, and an honest note where the data does not support a view. SalesSynq spots at-risk deals early and tells your team exactly what to do next. That is the whole promise, and for a firm your size it is usually worth one proposal a quarter.

What if our CRM is a spreadsheet?

Then start with the spreadsheet. Uploads accept .csv, .xlsx and .zip exports, and what comes back first is a report on your own data: which fields were usable, which were ambiguous, which were missing, and what that means for what can be scored. Keep that report even if you go no further — it is the clearest picture most firms have ever had of what their business development data actually contains.

A proposal has gone quiet. What does the evidence say?

First, whether it is the client who went quiet or your data. Those look identical on a dashboard and they call for opposite responses — one is a relationship problem, the other is a connection that expired and nobody noticed. SalesSynq reports what it could actually observe on the account, so a partner sees the difference before deciding whether to chase, re-scope or let it go. It also shows which relationships have real engagement behind them, and which were named on the account but never appeared.

Which is what turns "chase everything" into three calls that are worth making this week.

Can I put this number in front of the partners?

You can, because you can take it apart in front of them. Scores are computed by rules rather than by a chatbot, the same evidence always gives the same answer, and you can open any score and see exactly what it looked at — which client activity, which people, how recent each piece was. Where the export was thin, it tells you it does not know instead of producing a confident-looking number.

And here is what it will not do for a services firm — the five things worth establishing before the second meeting:

• It does not forecast utilisation, bench time or staffing. It scores revenue evidence, not delivery capacity.
• It never scores individual consultants or partners. Aggregate reporting suppresses groups below five by default and can be configured no lower than two.
• It does not change your CRM records or your timesheet system. Connections are read-only, an import is a file you hand over, and routing a task into a work tool is a separate permission you grant per tool.
• It does not invent a pipeline out of thin data. Where the evidence is not there it says so, and the report names the field that was missing.
• Model-derived judgements about a client’s mood, sentiment, tone or personality are discarded, rejected at the storage boundary and excluded from scores and actions.

Everything else is the part you came for: knowing which client conversations are cooling while there is still time to do something about them.