“Our funnel isn’t fully set up.”

A little later, it usually turns out that salespeople do not fill in the CRM system, you cannot make a decision based on the conversion rates, and the forecast has to be pieced together from what the team says.

The first thought is understandable: add mandatory fields and be stricter about keeping things in order.

First, check something else. What does the head of sales do when the CRM already shows a gap?

The problem was spotted on Monday. On Thursday, it just has a new date

Take a typical week in a sales team.

At Monday’s sales meeting, the head of sales opens a deal. The record says “The client is thinking it over”, and the next task is to call on Thursday. It is unclear what exactly the client is choosing, who is involved in the decision and why the conversation has been put off.

The head of sales asks the salesperson to add more detail to the comment and make the task more specific.

By Thursday, the record looks better: “Getting their partner’s approval; follow up on Monday.” The task is complete. Nothing is overdue. But the client has not confirmed who is involved in the decision, the timing or the next conversation. The deal remains in the forecast on the same basis as before.

The salesperson has filled in the CRM.

And what has the head of sales done?

They could have distinguished between two different reasons. The client really is going through an internal approval process — in that case, you need to find out who decides, what they need in order to choose and when the next contact will take place. Or the salesperson is using the word “approval” to hide the fact that contact has been lost — in that case, the deal cannot stay in the forecast just because it has a future task.

If the head of sales has not chosen which reason to check, has not set the required outcome of the conversation and has not returned to it on Thursday, the problem is no longer an empty record. The data is there. It has not changed how the sales team works.

CRM should show more than just salespeople’s work

Usually, CRM is used to check on salespeople: whether they called on time, filled in the field, completed the task or moved the deal to another stage.

That is not enough.

The same deal should also show the work of the head of sales:

  • which risk they spotted;
  • which two reasons they distinguished between;
  • what decision they made;
  • who they assigned an action to and what result they expected;
  • when they checked back;
  • what they changed if the first decision did not work.

This is where RENTROP checks something different. We look at more than the salesperson’s discipline. We look at whether the head of sales turns a problem into a new action for the team.

An entry saying “task overdue” is a fact about a salesperson. If the head of sales responds only by demanding that the red items be cleared, the report will turn red again a few days later. There can be different reasons: the task served no purpose, the employee does not know how to conduct the conversation, the client was lost long ago, the salesperson has too much work or the deadline was set without agreement with the buyer.

One colour: red. Five different decisions.

The head of sales’ work begins when they stop trying to fix the report’s colour and choose a reason to check.

“Perhaps the CRM is just poorly set up?”

The question is fair. Two different kinds of work are mixed together here.

The first is technical. The CRM may lack a suitable stage, a place for the next step, a clear field or a report that is easy to use. If the salesperson has nowhere to record a fact or the head of sales cannot physically see it, the system really does need setting up.

The second is about management. The fact is already visible, but the head of sales makes no decision about it, does not check that the action has been carried out and does not change the action after the same mistake happens again.

It is easy to tell the difference.

Open a stalled deal. Can you tell from the record what the client last did and what next step was agreed? If you cannot, fix the way information is recorded. If you can, look at what the head of sales did after that fact appeared.

If the head of sales has made no decision, a new field will not help. It will only describe the standstill in more detail.

Mandatory fields quickly teach the team the right words

When the business owner does not trust the CRM, they ask for more detail to be recorded. Fields appear for “reason for rejection”, “probability”, “risk”, “next step” and “head of sales’ comment”.

Sometimes this is useful. But every field needs someone inside the company who will use the answer to change how work is done.

If a salesperson sets the probability at 70%, what does the head of sales do when it drops to 50%? Check a new fact? Change the forecast? Join the conversation? Or does the number simply go into the report?

If the decision does not change, the team quickly understands the field’s real function: it must be filled in so the record is not sent back.

Missing data is then replaced by plausible data. “The client is thinking it over” becomes “the client is getting their partner’s approval”. “Call” becomes “check the status of the decision”.

The wording sounds more grown-up. There is still no management.

Check whether behaviour changes, not whether there is a comment

Do not overhaul the whole CRM at once. Take five important active deals with no confirmed progress, and run a short check over one week.

On Monday, record the following for each deal:

  1. What is known as fact and what the salesperson is still only assuming.
  2. Which two reasons could look the same in the record.
  3. Which reason the head of sales is checking first.
  4. What action has been assigned and what it should produce.
  5. When the head of sales will check the result.

This is not one more report from the salesperson. The deal record must contain the head of sales’ position.

At the end of the week, do not look for a promised rise in revenue. A week proves nothing that would justify that conclusion.

Look for four observable changes:

  • the deal has a confirmed next step, or it has been removed from the forecast;
  • the salesperson has applied the new requirement to the next similar deal without a separate reminder;
  • the head of sales was the first to spot the repeated mistake, rather than the owner;
  • if the first action did not work, the head of sales changed the decision, rather than just the task date.

If this has happened, the CRM has started to support management.

If all you have are new comments, the team has learnt to report better.

What if the salesperson gets it wrong again?

Do not rush to label them a weak salesperson.

First, open the conversation, the task and the head of sales’ feedback. Was the requirement specific? Did the salesperson know how to meet it? Did the head of sales check the result on time? After the review, did the employee repeat the same mistake in a new situation?

Only this sequence lets you distinguish between three reasons: the person lacks the skill, the head of sales is not managing, or the rule itself does not help the deal.

Without it, the decision to dismiss someone will be as subjective as the 70% probability in the record.

The owner does not need to become a CRM inspector

The business owner does not have to review every deal for the head of sales. Otherwise, keeping the CRM in order will once again depend on their personal involvement.

They only need to see the quality of the head of sales’ work: which recurring risks the head of sales has found, what decisions they have made, what has changed in the team’s actions and where the owner’s decision is needed.

Price, discount limits, the marketing budget, the product, production capacity and the employer’s staffing decisions remain with the owner. The next contact, reviewing a stalled deal, feedback to a salesperson and checking that actions have been carried out are the head of sales’ job.

The role can be handed over. The way decisions are made may still remain with the owner.

Why RENTROP comes into this

RENTROP’s “turnkey sales management” is built on this distinction.

The head of sales is responsible for the team’s daily work. The business development director reviews the quality of their decisions: whether the risk was spotted in time, what was assigned to the team and whether behaviour changed after the check. AI picks up signals about deals with no progress, missed actions and repeated mistakes from the CRM, calls and messages.

When the head of sales changes, the new head of sales takes over a project with recorded figures, decisions, agreements and the results of past actions, rather than an empty one.

The business owner continues to make decisions about strategy, price, budget and other matters affecting the whole business. RENTROP is responsible for the sales team’s daily work within boundaries agreed in advance.

Salespeople fill in the CRM. Management is visible in what the head of sales did after the signal.

Check five stalled deals over one week: not how many new words appeared in the records, but which decisions by the head of sales changed the forecast, the next step or the team’s behaviour.