Guide · Revenue growth
How manufacturers and distributors grow revenue from existing customers
Where the extra revenue sits in your existing accounts, what your ERP already knows, and how to put it in front of account managers.
For most established manufacturers and distributors, the easiest revenue to win next year sits with customers they already have: accounts buying fewer product lines than similar customers, reorders arriving later than usual, and spend that has quietly fallen. The evidence is usually in the ERP's order history already. The work is putting it in front of the account manager, inside the CRM they use every day, early enough to act on.
This guide is for managing directors and sales directors of UK manufacturers and distributors whose sales team works in HubSpot or Pipedrive while orders, invoices and products live in an ERP such as Sage 200, Sage 50 or Xero. It sets out where the extra revenue comes from, what the ERP already knows, how to find the accounts worth developing, and how to tell whether it is working.
Where does extra revenue from existing customers come from?
From five places, and most businesses are strong in one or two of them and blind to the rest:
- Range. Customers who buy one or two product families from you when similar customers buy four or five.
- Frequency. Customers whose reorders have drifted from their usual rhythm, so a monthly order has become a six-weekly one.
- Spend. Accounts whose value is down on the same period last year, which may be a change in their business or a sign that some of the work is going elsewhere.
- Quotes. Quotes and estimates that were never followed up, or were followed up once and left.
- Reach. Branches, sites or departments of a customer you already supply that have never ordered.
None of this replaces winning new customers. It means the revenue already within reach is not left to chance, or to whichever account manager happens to have the best memory.
What does the ERP already know about each customer?
More than most sales teams realise. A typical ERP holds, for every customer account:
- every order and invoice line, with date, product, quantity and value
- the product family or category of each line, where products are coded consistently
- the account structure, such as head office and branches
- price lists and agreed terms
- open quotes or estimates, where they are raised in the ERP rather than in the CRM
- credit status and payment history
The ERP is built to fulfil and invoice orders accurately. It is not built to tell a salesperson who to call this week. That information exists, but it sits in reports someone has to run, in a system most of the sales team never opens.
Two cautions before relying on it. First, the history is only as good as the data: the same customer set up twice, branches recorded as separate customers, or product codes that changed over the years will all distort the picture. Second, what the ERP can show depends on how it was set up. The answers below assume order lines carry a product family; where they do not, that is usually the first thing to fix.
How do you find underdeveloped accounts?
Compare each customer with customers like it, not with your best customer. Group accounts by something that predicts what they should buy, such as trade, size band or number of sites, then look for accounts whose spend or range sits well below the rest of their group.
An account is a candidate when:
- its annual spend is well below that of similar accounts of similar size
- it buys from noticeably fewer product families than its peers
- it orders from one of its sites when it has several
The comparison is a prompt for a conversation, not a verdict. Some customers genuinely need only one product line, some buy the rest from a supplier you cannot replace, and some groups are too small to compare fairly. An account manager who knows the customer will rule some out in seconds, which is exactly the point: the list should be short enough to read.
How do you find cross-selling opportunities?
Look at product families rather than individual products. For each group of similar customers, work out which families most of them buy. The accounts that buy most of those families but not one of them form a short, specific call list.
Take a distributor whose electrical contractors mostly buy both cable and accessories. The contractors who buy cable but never accessories are the obvious first conversation. The same logic works for a manufacturer selling machines and spares, or a packaging business whose customers usually take both cartons and labels.
Three rules keep this useful rather than noisy. Keep the list to a handful of accounts per account manager. Explain why each account is on it, so the conversation starts from the customer's buying pattern rather than a product push. And take accounts off the list when the conversation has happened, whatever the answer.
Which commercial signals should you watch?
Each signal suggests a question worth asking. None proves what the customer is doing or why.
| Signal | What it may suggest | Where the data sits | A sensible first action |
|---|---|---|---|
| Spend down on the same period last year | Lower demand, a change in the customer's business, or some work going elsewhere | ERP invoice history | A call from the account owner to understand what has changed |
| Gap since the last order longer than the usual cycle | A reorder missed, delayed or placed elsewhere | ERP order dates | Check the customer's stock and plans before it becomes a lost order |
| Fewer product families than similar accounts | Room to extend the range | ERP order lines by product family | Propose one relevant family, with a reason |
| A family most similar accounts buy, missing here | A specific cross-sell gap | ERP order lines, grouped by account type | A targeted conversation about that family |
| Quote with no reply after its chase date | A sale going cold | ERP or CRM quotes | Give it an owner and a date |
| A site or branch that has never ordered | Untapped reach inside an existing customer | ERP account structure | Ask for an introduction to that site |
| Spend rising quickly | A growing account | ERP invoice history | Protect it: check service, capacity and contacts |
What should account managers see in the CRM?
Only what changes the next conversation. On each company record in HubSpot or Pipedrive, that is usually:
- spend in the last twelve months against the twelve before
- the date of the last order against the customer's usual ordering rhythm
- the product families bought, and the ones similar accounts buy that this one does not
- open quotes, with a value, a date and an owner
- a short list of prompts, such as a reorder overdue or a quote unanswered
The ERP stays the system of record. The CRM shows the sales team what they need from it, and most of that information moves one way, from the ERP to the CRM. Resist the urge to copy every field across: a record crowded with data nobody reads is no better than a record with none. The wholesale and distribution page shows an illustration of what such an account view can look like.
A practical five-step process
- Agree the questions. Decide which accounts matter, which of the signals above you will act on, and who owns the follow-up. Starting from the questions keeps the work small.
- Check the data. Look for customers set up twice, branches recorded as separate customers, inconsistent product codes and missing product families. This is where most projects slow down, so it is cheaper to find it before anything is connected.
- Connect the ERP to the CRM. Bring across the records the questions need, on a schedule or as they change, using whichever tool suits the job: a native connector, Make, n8n, BPA Platform or custom code.
- Put the signals in front of their owners. Build the views, lists and tasks each account manager works from, so the prompts arrive without anyone running a report.
- Review monthly and adjust. Look at what was flagged, what was acted on and what came of it, and drop the signals that do not lead to useful conversations.
How do you measure whether it is working?
Set a baseline before anything changes, then compare like with like:
- revenue from existing accounts against the same period last year
- average number of product families bought per account
- share of accounts ordering within their usual cycle
- share of prompts followed up within an agreed time
- quote-to-order rate, and how long quotes wait for a reply
Be careful about credit. Prices, seasons and the wider market all move these numbers, so compare against the same period and treat a change as evidence to examine rather than proof. The follow-up measures are the most honest early signs, because they show whether the team is acting on the information at all.
When does this approach not fit?
It needs order history worth analysing and a sales team that owns accounts. It is a poor fit when:
- there is no ERP or order data to connect
- the customer base is small enough that the owner knows every account personally
- most of your product reaches end users through merchants or distributors whose sales you cannot see, so your own order history shows only part of the picture
What has Flowbird done in this area?
Flowbird connected an on-premises Sage 200 to HubSpot for a UK distribution business, bringing customer and company records into HubSpot through a secure tunnel. The result was less administration and better data, because each customer is written once, and the project won the Creative, Digital & Innovation Award at the Ashford Business Awards 2025. That project moved customer and company records, not order history: it is the foundation the account view above is built on, rather than the account view itself. You can read how it works or see all our case studies.
Flowbird has connected HubSpot and Pipedrive to Sage 200, Sage 50, Xero, the Linnworks order system and the Tharstern print MIS. Odoo and other ERPs can be connected where they offer an API. More on what this looks like by sector is on manufacturing and engineering and wholesale and distribution.
Where to start
The CRM & ERP Opportunity Audit is a fixed-price, two-week review. It checks what your CRM data can carry, maps one revenue-critical process end to end and tells you whether your systems could show which customers are buying less or are due to reorder, and what that would take. It does not need access to your ERP and does not analyse your order history; producing that analysis is the work that follows, if you go ahead. It ends in a written report and a plain go or no-go.
For further reading, our article on cross-selling from the CRM covers the CRM side in more depth, and more guides are on the Insights page.