Sales fell. The sales team says: we need more leads.

Meanwhile, the CRM system contains customers who have bought before. Some were promised a follow-up after delivery. Others have reached the end of their usual interval between orders. A salesperson wrote to others, “I’ll get back in touch”, and set a task without a reason for the conversation.

There really may be too few new enquiries. But before buying more, I would check something else: which existing customers should have bought again, on what basis, and what the team did before the usual order failed to come in.

If there are no answers to these questions, the problem is not yet the number of leads. The company is not managing repeat sales — it is waiting for familiar customers to return on their own.

There are a hundred customers on the list. There may be no usable database

Open the list of customers who have bought before and choose one.

What do they buy? Why do they return? Is there a clear pattern to how often they order? What has changed since the last delivery? Who on the customer’s side influences the next decision? When should the salesperson have noticed that the usual pattern had not repeated itself?

If all you have instead of answers is a phone number, the date of the last payment and an “active” status, that is not yet a database for repeat sales. It is a history of transactions.

The difference shows in the salesperson’s work. With a transaction history, all they can do is call through the list: “Are you planning to order anything?” With a usable database, they understand why they are getting in touch now and what they need to check.

For example, not “we haven’t spoken for a while”, but: the usual interval between orders has passed; consumption volumes have changed; the customer has a new site; there was a promise to assess the last delivery after use; the person who used to make the decision has changed roles.

The reason may not prove valid. But it can be checked. The phrase “get back in touch” cannot be checked.

The customer does not have to tell you the usual order will not happen

Imagine a common situation. A customer has ordered similar quantities several times. After the last delivery, the salesperson decided the customer would return on their own: they were on friendly terms, the relationship was fine, and the product was familiar.

The usual interval passes. No new request comes in. There is no refusal recorded in CRM either, so nobody looks into what has changed. Some time later, the salesperson makes a general call while working through the database and finds out: the need has shrunk, the purchase has been postponed, another supplier has appeared, or the person handling the matter within the company has changed.

All these reasons call for different decisions. But the team learns about them equally late — when the money has already failed to come in.

From the outside, this looks like falling demand. The facts show something else: the company did not notice a change in a familiar customer’s behaviour while there was still time to ask a proper question.

This does not mean you can conclude that the customer has been lost. It is a missed change that no one checked in time.

“They already have our number” — a comforting truth that comes at a cost

A regular customer may indeed get in touch on their own. And not everyone needs a regular call.

But this confuses customer loyalty with the team’s work. Loyalty means the company is trusted and there is a familiar way to buy. It does not mean the salesperson knows what the customer now needs to do, their budget, internal changes and competitors’ offers.

So there is no need to call everyone every week. Customers need to be grouped by at least three facts:

  • who has a recurring need and how often it usually arises;
  • whose next contact depends on an event rather than a date;
  • who has no apparent repeat need yet and should only be contacted when there is a meaningful reason.

Sending the same message to the whole database will not replace this work. It will create activity, but it will not tell you where the company lost a usual order or why.

More leads may hide what is broken rather than fix it

Suppose marketing brought in new enquiries and total sales recovered. Does that mean a solution has been found?

Not necessarily.

If existing customers keep dropping away unnoticed, the team buys new enquiries every month to replace what it failed to retain and did not even investigate. The final figure may look better while the cost of maintaining it rises.

A new flow of enquiries is needed when checks confirm there really are not enough. But first it is worth separating two causes of the same result:

There are too few new opportunities. Existing customers are following their confirmed pattern, deviations have been examined, but there are still not enough enquiries to meet the sales plan. Then the question for marketing is justified.

Existing opportunities disappear without investigation. No one compares expected repeat orders with what actually happens, salespeople remember customers at random, and the reasons for the pause are not recorded. Then buying leads will add work to a team that is already failing to manage its existing customer base.

This is not a dispute between sales and marketing. It is the order of checks: first find exactly where less money is coming in, and only then pay for a way to close the gap.

What should replace “work through the customer database”

The phrase “work through the customer database” does not define a task. It names no chosen customer, reason, decision or sign of a result.

Proper work starts differently.

The head of sales chooses a group of customers with a clear reason for repeat purchases. For each customer, the salesperson pieces together the previous need, the usual interval or event that brings them back, the people involved in the decision and the last agreement. They then test a specific assumption, rather than checking “whether an enquiry is needed”: the need is still there, has changed, has been postponed or has disappeared.

After the conversation, there should be one of the following observable results:

  • the next order or an action before it has been confirmed;
  • a new need and a time for the customer to return have been identified;
  • the reason for the pause and a decision on what to do about it have been recorded;
  • it has been established that there is no active opportunity at present, and the customer is no longer expected to place an order.

Even the last result is useful. It removes false hope and shows how many opportunities there really are.

A one-week check

There is no need to start with the whole CRM. Take one group of customers who used to make repeat purchases and check five things:

  1. What pattern or event used to lead to a new order?
  2. For which customers has that point already arrived, with no new outcome?
  3. Who is responsible for checking the change?
  4. What specific question does the salesperson ask when they get in touch?
  5. What changed after the conversation: the next step, the reason for the pause, the timing or the status of the opportunity?

After a week, it is too early to judge revenue. But you can already see whether the customer base is being managed. Salespeople stop calling without a reason. There is an explanation for the missing order. The head of sales can distinguish a live opportunity from an old contact. And the question “do we have too few leads?” gets an answer based on facts.

Where RENTROP fits in

In RENTROP’s “turnkey sales management” service, work with the customer base is part of the head of sales’ daily work. They monitor which repeat opportunities were expected, where customer behaviour changed and what decision the salesperson made, rather than how many times customers were contacted. The business development director checks the quality of this work. AI helps compare data and communications and find deviations; the decision remains with a person.

The marketing budget, product, prices and decisions about development remain under the business owner’s control. Our job is not to label every drop a shortage of leads, but to show where it happened and what the team is already doing.

Sales did not fall when new leads became scarce. First, check whether you stopped noticing existing customers before they stopped buying.