A sales audit shows where the purchase process stalls and which actions the sales team should change: it does this by comparing deals, calls, messages and the decisions made by the head of sales. The review produces confirmed reasons for the hold-ups, questions that still need answers, and an action plan setting out the next steps. For a business owner, this review helps decide what the team should spend time on this week.
You want certainty from an audit. Where we are losing buyers, who is falling short, what to fix first. But a list of thirty issues on its own makes that choice harder: every item is marked “urgent”, and the same people who are working with customers now will have to deal with them.
I believe the auditor must explain why they propose starting with this particular change. A link to a poor call explains a criticism of that conversation. Deciding to train the whole department, replace the head of sales or rework the CRM system requires further grounds. Otherwise, the company will pay for the review, and the owner will once again be left to choose the remedy.
Sales department audit
A sales department audit covers the customer's path from enquiry to purchase and the work of the people who guide them along it. It should show exactly where things stall, who can influence this and what is stopping them from doing so now.
It is worth reviewing four connected areas:
- Enquiries. What the buyer wants, whether the offer suits them, and what they already know about the price and terms. Being turned down by someone who needs a different product is different from losing a suitable buyer.
- Deals. What was offered, what response was received, and what the parties agreed to do next. The stage in CRM is compared with the events that brought the deal there.
- Conversations and messages. How the salesperson finds out what the customer needs, responds to doubts and agrees what happens next. The sequence of contacts matters: an answer to a question asked during a call is often sent by email.
- Leadership. Which problems the head of sales notices, what they change in the work, and what happens as a result of their intervention. This shows whether an error recurs after a review and whether the salesperson can get the decisions they need.
These areas share one common unit: a specific sale. Separate reports on calls and CRM leave a gap between them: one shows how a person spoke, the other where they moved the deal record. The person conducting the audit must connect the two. The owner only needs to see the basis for the conclusion and the proposed choice; there is no need for them to listen to everyone's calls themselves.
What data do you need for a sales review?
The review needs deal histories, the related conversations and messages, actual orders and the working rules in force at the time. All sources are taken from an agreed period, so that current results are not explained by conditions introduced later.
The starting set includes:
- an export of deals showing the source, person responsible, dates of stage changes, amount and reason for closing;
- call recordings and messages linked to these deals;
- information about paid orders, cancellations and returns;
- salespeople's tasks, deadlines and completion history;
- sales terms and staff authority: who approves the price, deferred payment, product configuration and delivery date.
The period must let you see a completed purchase process. If your customers take longer than a month to decide, a selection of only recent enquiries will show the start of the work. To review completed sales, you will need an earlier group of enquiries. New deals will be useful separately — for assessing current delays and promises that should have been fulfilled by now.
The sample needs three groups: those who bought, those who declined and those still deciding. Looking only at lost deals encourages you to find fault in everything the salesperson does. Comparing them with deals that led to a purchase helps you notice that the same approach appears with different outcomes. So the approach alone is not enough to explain a refusal.
Record gaps straight away: which channels have no message history, which staff have no recorded calls, and where dates are missing. A conclusion that a salesperson stayed silent only makes sense once the channels they used have been taken into account. If some of the work is unavailable, the immediate task is to recover its record; otherwise, the person's assessment will depend on which messaging app they used.
Price changes are also separated from the team's work. There is a separate review of this: How to assess the work of a head of sales after price increases. For the audit, it is enough to record the date when the terms changed, so that the comparison between periods does not start from a false basis.
How do you compare deals, calls and messages?
You need to compare the events in a single deal in the order they happened: the buyer's request, the salesperson's response, the agreement and its fulfilment. This shows which commitment was the last to be fulfilled and whose next action was needed when progress stopped.
Reviewing one poor call without the messages before and after it can easily lead you astray. The terms were discussed earlier, the answer was sent later after approval, and the recording shows only the middle. So a comment on an individual remark must remain connected to what the buyer knew before the conversation and received afterwards.
Here is a guide to reading the findings. You can attach it to the audit brief or use it alongside the finished report.
| What CRM shows | What to look for alongside it | How to tell the causes apart | What action follows |
|---|---|---|---|
| A deal has been waiting for approval for a long time | The promised response deadline and the buyer's most recent request | Whether the customer is waiting for a decision from our company or seeking approval for the purchase themselves | Get an internal decision or agree a date to contact the customer |
| No response after the proposal | What was sent and what was agreed before sending it | Whether the proposal answers the request or needs missing information | Clarify the specific unresolved question, then decide the next step |
| The next task is overdue | The history of all available contacts | Whether a promise to the customer was broken or a completed action was not entered in CRM | Fulfil the commitment or correct the records |
| The reason for refusal is price | The terms the buyer compared and the content of the salesperson's response | Whether the decision stalled because of the budget, what the proposal includes or an unresolved doubt | Prepare an option you are authorised to offer or get the missing answer |
The second row of the table is particularly awkward for those who like to push every buyer towards a purchase in the same way. An extra call makes sense when you know which issue it will move forward. If a salesperson sent an estimate without the configuration the buyer needs, a reminder about that estimate will repeat the original mistake.
Once the events have been reconstructed, another question arises: why did the head of sales miss the hold-up? The task may have disappeared from their list, the wait for approval may have had no deadline, or missed deadlines may have kept recurring without consequences. Different causes call for different changes. Training someone in conversation skills will not speed up a decision they are not authorised to make.
Which audit findings give you grounds to act?
You can act on a confirmed failure to keep an agreement; changing the whole way you sell should follow a review of a recurring cause. An unfulfilled promise and an explanation of why a buyer left require different levels of evidence.
If the agreed estimate has not been sent and the communication history confirms this, it needs to be prepared. To make that decision, you do not need to prove that the buyer would definitely have paid after receiving it. But you cannot record the amount of this deal as lost revenue: the customer was still deciding, and the outcome of the purchase is unknown.
The same principle applies to the overall scale of the problems. To assess the scale, use your own numbers: divide the number of deals with a confirmed failure to keep an agreement by the number of deals reviewed and multiply by 100%. Keep both original figures and the selection method alongside it. The proportion in a set of specifically selected complaints describes those complaints; you cannot apply it to the whole department.
Explaining the cause requires another step. If the auditor links refusals to a failure to ask when the buyer plans to buy, ask them to show where that failure prevented progress. They should also compare this with conversations in which the timing was established. There needs to be a link between the missing action and the customer's decision; otherwise, the team will start saying a required phrase just to tick a box.
A working explanation of the cause can be disproved. Internal approval was made faster, the salesperson replied by the promised date, but the buyer still declined because the delivery date did not suit them — so another constraint emerged in this deal. The corrected response will remain useful, but it makes no sense to credit it with the ability to solve the delivery problem.
What should be recorded for each finding?
Each finding needs supporting evidence, the limits of the conclusion, the next action and a sign that it has been completed. Then the owner can see what work is being proposed and can stop a recommendation that does not follow from the facts.
Below is a form you can use. Fill it in with company data; the wording in the right column explains what belongs in each row.
| Field | What to record |
|---|---|
| Where it was found | Links to deals, message dates or the relevant minute in a recording |
| What has been established | Which commitment was broken or which necessary answer is missing |
| What is still unknown | Which fact is missing to explain the cause |
| Where it recurs | The number of cases out of the number reviewed, the product and the source of enquiries |
| Next action | What the employee will do with specific deals and by what deadline |
| What prevents completion | Which approval, authority, information or time is needed |
| How to see the result | Which event will appear in the deal history; who will check completion |
The field about obstacles guards against the convenient but useless conclusion “tighten control”. If an estimate depends on a technical specialist, reminding the salesperson every day will not produce an answer. You need to say who gets the estimate from the specialist, what deadline has been agreed and who to contact if there is a delay.
This record shows the salesperson's work and the work of the head of sales separately. The salesperson handles the conversation and fulfils the agreement. The head of sales secures a decision within their authority, removes a recurring delay or takes a specific constraint to a higher level. The owner is given a clear choice with supporting reasons, instead of being asked to personally push another deal forward.
How do you choose actions for the coming week?
Start with confirmed failures to keep agreements where the deadline promised to the customer is nearest, and actions without which the other recommendations cannot be carried out. Investigate unclear causes in parallel, limiting the work to a specific question.
On the first working day after the audit, the head of sales divides the list on this basis. A response promised to a customer must not be delayed until the review of the entire department is complete. There are already enough facts to prepare it. But the decision to rewrite everyone's sales conversation script can wait until conversations have been compared and the cause established.
For the next two or three days, choose one recurring obstacle that the team can remove on its own. Link it to the affected deals, a person responsible and a deadline. If the owner's permission is needed, it should concern a specific condition — for example, how much time approval can take — so that the team can carry on independently once they have an answer.
The rest of the week is for carrying out the actions and recording the response. The answer was delivered, the buyer clarified their requirements, agreed on the next steps or declined with a clear reason — these are different outcomes, and each changes the work that follows. A “contacted” note does not preserve these distinctions. Revenue growth over these days should not be treated as proof: a purchase follows its own timetable.
The action plan will contain fewer items than the report. That is normal. If there is no spare time for the actions, the head of sales names the work they will postpone. The owner should see the cost of that choice before agreeing to the full list of improvements.
When do you need a review beyond individual deals?
The review needs to be widened when the state of deals depends on the mix of customers, traffic, competitors' offers and the team's workload. Salespeople's conversations alone will not answer all these questions.
If the issue has already been narrowed down to deals and communication, RENTROP has AI ROP for it: the sales audit links deals, calls and messages to the next step. AI ROP reads the data; people remain responsible for decisions and carrying them out.
For a broader question, there is a separate review of sales across six areas — “Sales Audit 360°”. Over 10 working days, a RENTROP expert reviews sales, customers, deals, traffic, competitors and the team, and provides an action plan with prioritised actions.
Wanting to find every weak point is understandable: you have paid for the audit and want the full list. But a complete description does not make every change necessary. I am willing to accept a short action plan in which one costly overhaul has been ruled out on sound grounds. For the owner, that is a result too: the team will work on a confirmed problem, and the part of sales that works will be left alone.