To choose a team structure, calculate the time spent on repeat orders and new needs raised by existing customers: sales organisation based on just one criterion, “the customer has bought before”, hides the negotiation workload. Suppose that, out of 80 enquiries, 60 repeat orders took 10 hours, while 20 enquiries involving new needs took 30 hours. By handing the whole customer base to an employee who only processes orders, you will hand them 30 hours of negotiation work.
When employees are busy all day and the owner has to sort out every difficult order, it is tempting to finally divide up the responsibilities. Give one person new customers, another existing customers, and a third the paperwork. Then at least it will be clear who is accountable.
But dividing customers into new and existing ones hides an uncomfortable fact. An existing customer also starts new deals: they choose a different product, change their requirements or involve colleagues in the decision. If all their enquiries go straight to quick order processing, nobody handles the complex sale. If every repeat of a previous order goes to an experienced negotiator, they will be busy doing work that did not require their experience.
I am against the habit of drawing up roles first and then fitting the work around them. If the duties of a customer support role end with sending an invoice, that employee has no reason to clarify the buyer’s new requirements. A salesperson responsible for new customers has no reason to get involved either: the company is already in the customer base. Someone is responsible for the order, but the work it needs has fallen into a gap between responsibilities.
Organising the sales team
Organising the sales team includes choosing a structure, assigning responsibilities, setting up the sales funnel, planning, training and rules for monitoring work. These need to be organised around types of deals: which orders can be processed under known terms, and which require clarifying a need and reaching a new agreement.
First, distinguish between purchases by the same customer
A repeat order can take a shorter route if what is being bought, the agreed terms and the decision process remain the same. The salesperson only needs to confirm the quantity, availability and current timeframe, then confirm the order. There is no reason to repeat the entire presentation to a familiar buyer.
A new need arises when the previous agreement is no longer enough. A different use, a new configuration, a different payment method or an additional person involved in approval: each of these signs requires finding out what has changed. The fact that the customer paid before does not provide the answers.
A small order value does not automatically make anything simpler, either. An order for a familiar product with a new requirement for its use may need technical approval. Meanwhile, a large repeat order under an already agreed supply arrangement may go through without new negotiations. The buyer’s size helps determine how much attention to give them, but does not describe the work on a particular enquiry well.
Here, it helps the owner to distinguish between two things: who maintains the relationship with the company and who handles the current purchase. The customer’s main contact stays the same. When a new need arises, an employee who knows how to work through it joins the sale; the familiar salesperson helps them join the conversation. This does not require handing over the whole customer relationship every time.
How to choose a team structure
A team of all-round salespeople and teams divided by stage, customer type or product suit different kinds of work. The choice is justified when the division removes a specific difficulty without creating unnecessary handovers for the buyer.
| Structure | When it is useful | Where mistakes happen |
|---|---|---|
| One salesperson handles the whole sale | There are few purchases, the nature of enquiries varies, and knowing the customer helps with negotiations | Leaving all the paperwork with the same person, even though it takes time away from conversations |
| By stage: finding customers, negotiating, processing orders | There are recurring actions with a clear result at each stage | Sending an order for processing before agreeing what the customer intends to buy |
| By customer group | Purchasing really differs between groups: for example, one person makes the decision, or several departments do | Dividing the customer base only by turnover and treating every purchase by a large company as equally complex |
| By product or territory | The sale requires specialist knowledge, a local presence or different terms for fulfilling orders | Making the buyer piece together answers from several salespeople about one order |
For a small sales team, it makes sense to start by combining roles. One person can handle both repeat orders and negotiations about new needs. But these activities need different requirements. Otherwise, there will be new job titles while the way of working stays the same.
Dividing the team by product does not resolve the question of the whole order either. If a customer needs several items, someone must put together the overall proposal, agree the terms and take responsibility for it with the buyer. Without this, the company sells its internal organisation chart along with the product: the customer has to work out which of your employees to call.
Two routes instead of one “existing customers” queue
For the existing customer base, establish a short route for repeat orders and a separate route for new needs. Switching between them depends on the content of the enquiry, even if the main salesperson stays the same.
Below is a sample set of rules you can give the head of sales to discuss with the team. It describes the work, so it suits both a department with a separate customer support role and a team of all-round salespeople.
| What the buyer has sent | What work is needed | How this part of the work ends |
|---|---|---|
| A repeat of a previous order with no new requirements | Confirm the items, quantity, availability, current terms and timeframe | The buyer has confirmed the order; payment and fulfilment can be arranged |
| An enquiry about a familiar product for a different need | Clarify the intended use, constraints and suitability of the solution | The requirements on which a proposal can be prepared have been agreed |
| An enquiry involving new people in the approval process | Clarify who chooses, who approves and what each person needs to make a decision | The approval process and the next action for both sides are clear |
| A change to the terms of an order already prepared | Assess what changes in the price, timeframe and the company’s obligations | An authorised employee has agreed the new terms, and the buyer has confirmed them |
The first route has a compulsory question: do the previous terms really fit? It protects against dangerously cutting conversation time. Order processing must not get faster because the salesperson has stopped noticing changes.
The second route needs a limit in the other direction. It should not become a compulsory long presentation. If clarification shows that the new requirement changes nothing, the order returns to normal processing. The head of sales reviews cases where the choice of route is disputed and clarifies the rule when the team repeatedly makes a mistake at the same point.
This is concrete work for the head of sales between sales meetings. If the recorded reason for an order stalling is “the buyer is thinking it over”, and the invoice was sent before the configuration was chosen, it is too early to demand another payment reminder. The head of sales returns the order to the requirements stage and discusses with the salesperson why they decided to process the purchase straight away. This corrects both the current order and the rule that puts the next one at risk of stalling in the same place.
What changes in the sales plan, CRM system and salespeople’s pay
The sales plan and performance targets must reflect the work assigned to each role. An employee who processes agreed orders and a salesperson who develops new purchases affect the result in different ways.
If the whole team is assessed only on total revenue, a large repeat order can hide stalled new negotiations. The head of sales therefore shows the owner the results of repeat purchases and new needs separately, including those from existing customers. The buyer remains in the customer base, but the source of the next sale becomes visible.
In CRM, it helps to record two separate details: the relationship with the customer and the type of current purchase. “Existing customer” describes the relationship. “Repeat with no changes” or “new need” describes the order. Renaming a stage “final push” is not enough: the record must show which decision the buyer has yet to make.
Employees’ pay should not make them hide new needs. If involving a colleague means losing all their pay for that customer, the main salesperson has a reason to keep a complex enquiry to themselves. The owner approves rules for recognising joint work in advance: what the person developing the relationship is paid for, and what the person handling the new sale is paid for. These rules cannot be applied retrospectively to work already done.
Training and recruitment follow the same division. Customer support requires the ability to notice a change and pass on accurate information. A complex sale requires clarifying requirements, putting together a proposal and completing the approval process. Assessing both roles only on the ability to issue an invoice quickly makes no sense.
The head of sales’ goals and tasks go beyond choosing a structure; they are covered in “Sales management: goals, functions and process”. Here, each tool serves one decision: what action this purchase needs now and who can carry it out.
An effective sales team
An effective sales team does the work a purchase needs without unnecessary actions and brings deals to the agreed outcome. It should be assessed by revenue and profit from sales, the progress of different types of deals and the team time they take.
Look at the line “work with existing customers”: it can hide the main negotiation workload. Calculate this separately: multiply the number of enquiries of each type by the time spent working on them, then divide the minutes by 60. Use the same period and actual working time, excluding days spent waiting for the buyer’s reply.
For example, 80 enquiries came from the existing customer base in a month. Of these, 60 were repeat orders, taking 10 minutes each: 60 × 10 = 600 minutes, or 10 hours. Another 20 involved new needs, each taking 90 minutes of conversations and preparation: 20 × 90 = 1800 minutes, or 30 hours. The total was 40 hours; a quarter of the enquiries took three quarters of the time.
All 80 enquiries will appear as “repeat” in a customer report. But you cannot hand all 40 hours to an employee who processes orders quickly without training them to handle new needs. The calculation shows that most of the work handed to them involves negotiation. The decision about the employee’s role must take this into account, even if they were hired “to handle the existing customer base”.
After making the split, judge it by what happens to new needs. If they have become visible, buyers receive suitable proposals and repeating a normal order has not gained unnecessary approval steps, the split is helping. The number of completed fields alone does not support that conclusion.
How to start without restructuring the whole team
You can try this approach in one area of the business, keeping the current salespeople and their buyers. First, change how purchases are identified; decide on new roles after observing the work.
For an initial trial, three steps in sequence are enough:
- Classify the upcoming orders. The head of sales works with the salespeople to separate repeat orders from new needs and record the criteria used. A change in the quantity of a familiar product and a change in its use should go into different categories if they require different preparation.
- Take current enquiries through both routes. For repeat orders, the team confirms the terms and processes the order. For new needs, it clarifies the requirements before sending the final proposal. The head of sales reviews mistaken switches as they arise.
- Compare the work and the result. After the first ten completed enquiries, the head of sales shows how many times the route changed and why, which actions were unnecessary and where another employee had to be involved. This provides material for correcting the rules; a conclusion about sales growth requires a longer period.
The owner does not need to read ten records personally. They need an answer to a different question: is separate customer support justified, or is it enough to organise the current salespeople’s work differently? If new needs cannot be separated without losing important information, an all-round salesperson with an assistant will be more sensible than strict handovers between roles.
General requirements for data, staff cover and employees’ actions are explained in “Sales team management: how to set up a system”. These should be kept whichever structure is chosen.
Who will change the process as new needs arise
When the owner has to distinguish between purchases and coordinate employees’ work every time, simply reassigning roles is not enough. You need a head of sales who maintains the rules every day: spots an incorrectly classified order, changes what the salesperson does and establishes a successful way of working.
At RENTROP, building a sales system is part of the “turnkey sales management” product: in three months, our head of sales puts the sales plan, sales funnel, scripts, procedures, recruitment and monitoring in place, then continues managing sales using them.
The requirement to keep the customer’s familiar salesperson is reasonable. It does not mean that this person must do all the work on every future purchase alone. The customer needs a company that remembers agreements and can address a new need; within that company, another person can be brought in without making the buyer build the relationship from scratch.