Fichaloto

Blog CRM

Pipeline tracking when nobody sells full time

6 min read

In a services firm the person who sells is the person who delivers. That changes entirely which CRM can survive, and explains why the one you set up last year has been empty since March.

Why it dies

CRMs are built for full-time sales teams: seven stages, weighted forecasts, mandatory activities. All of that holds up when updating the CRM is somebody's job.

In a small practice, whoever sells has a day full of delivery. A system that asks for six fields per opportunity does not end up half filled. It ends up empty, and then it also lies, because the little that is in there is out of date and nobody dares rely on it.

What does survive: a list of next actions

The unit that works is not the pipeline stage. It is the next thing to do, with a date. "Call Mendoza on Tuesday." That gets updated because it is useful today, not because of a month-end report.

The pipeline then falls out of it for free: anything with a next action is alive, anything three weeks without one is dead even if it sits in "negotiation". That is more honest than any weighted forecast.

The three fields that matter

  • Where it came from. Referral, the website, a former client, somebody from the industry body. It is the only field that tells you where to spend effort, and the first one left blank.
  • When to come back. A date, not a status.
  • What was promised. The scope agreed verbally in the meeting, written down the same day. It is what prevents the month-three argument, and what turns a proposal into a properly defined project.

The link a generic CRM will not give you

This is the whole difference, and it is not about features: it is about what is connected to what. In a services firm the business question is not how many leads arrived. It is which kind of client works out well.

Answering that means following one chain end to end: the lead, the proposal and its scope, the project born from it, the hours actually spent and the margin left over. A separate CRM gives you the first stretch. The timesheet gives you the third. Nobody ever joins them, so the question goes unanswered year after year.

  • The referral that closes in two meetings, at the margin you planned.
  • The tender that costs six proposals and spends its budget by month four.
  • The small recurring client that looks like nothing and turns out to be the best hourly margin you have.
  • The prestige account that, converted into hours, is billing out at twenty-two euros.

The proposal as a living document

If the proposal is written where the project is going to live, the agreed scope is not lost on winning: it becomes the phases and tasks of the project, and the accepted budget becomes the budget it is consumed against. That is the exact moment half the overruns are avoided, and it is free. It only requires not typing it a second time.

Frequently asked questions

Do five people need a CRM?

Five people need a list of next actions with dates, which fits on one screen. What does not work even at five is keeping it in one person's head: the week they are on holiday, follow-up stops.

We already have a CRM. Now what?

Then the useful question is a different one: can you see the margin of the project that came out of an opportunity without exporting two files? If not, the problem is not the CRM. It is that it is disconnected from where the work happens.

What about leads from the website?

They have to land in the same list as everything else, with their source filled in automatically. A form that ends in an email to three people is a lead answered twice or not at all, and in both cases with no record of where it came from.

All of this is built into Fichaloto. See how it works.

Keep reading