InsightsSales Department Transformation

Sales department audit checklist: a working document

A ready self-check for your sales department: questions on process, CRM, calls, chats, reports and control, and what to prepare for a review

Angelina Vasylenko7 min

This is a working document for a self-check. Go through it with your head of sales and mark every question with one of three answers: yes, no, do not know. "Do not know" is a result too: it shows exactly which data you are missing. If you would rather understand how the review itself works first, read what to check in a sales department audit; the service, with its scope, price and timeline, is on the sales department audit page.

How to use the checklist

The six sections below mirror what AKORDO diagnostics cover: processes, CRM, calls and chats, plus the reporting and control without which the first four cannot be checked. The order matters: the process is described first, because every other section checks whether what was described actually happens.

Start with a list of questions your current reports do not answer. With that list you will frame the task of the review and will not collect data without a purpose.

No question here assesses people. If the answer is no, first check whether there is a rule for the action and data on whether people follow it, and only then talk about who carried it out.

1. Process: the customer journey and who owns it

  • Are the actual steps from first contact to payment written down, rather than the intended ones?
  • Does every step name the person responsible for the next action?
  • Does every step state which data is needed to carry it out?
  • Is the condition for moving to the next step written down?
  • Are the places where the journey stops marked: no reply to the client, no next contact agreed, no reason for refusal recorded?
  • Does every manager know what to do with an enquiry outside their own area?
  • Is there a separate description for a repeat enquiry from a client who has already bought?

2. CRM: the data you manage by

  • Does every enquiry reach the system, whichever channel it came through?
  • Is it clear from the record why a deal has the status it has?
  • Does the team understand enquiry statuses in the same way?
  • Is there a rule for filling the mandatory fields, and is it followed?
  • Does the record show the date of the next agreed contact?
  • Is the reason for refusal recorded, and can a conclusion be drawn from it?
  • Are there duplicate records, and is it known what creates them?

If there is no single system yet, that is an answer too: write down where enquiries, agreements and reports are stored now. The review works with spreadsheets as well.

3. Calls: what happens in the conversation

  • Are conversations recorded, and is there access to them for review?
  • Does the manager clarify the client’s need rather than moving straight to an offer?
  • Does the manager agree the next step at the end of the conversation?
  • Are there agreed criteria for what counts as a good conversation?
  • Does the manager know what is actually assessed in their conversations?
  • Are there example conversations the team considers exemplary?

4. Chats and email: the asynchronous channels

  • Is context preserved between messages if the client comes back a week later?
  • Is it visible from the thread who owns the client right now?
  • Is there a scenario for when the client stops replying?
  • Does a messenger thread land in the same record as the calls?
  • Is it agreed how quickly the team has to answer a first enquiry?

5. Reports: what decisions rest on

  • Is it known which decision each metric in the report is meant to support?
  • Does every metric have a written definition?
  • Do all the reports count the same things under the same names?
  • Do the reports show the stage at which clients are lost?
  • Does the data update without manual consolidation?
  • Does the head of sales compare managers while allowing for different incoming enquiries?
  • Is there a report the head of sales actually opens every week?

One example makes this visible more often than any other. A head of sales compares two managers: one receives more complex enquiries, the other fills in the CRM faster, and the total number of deals does not explain the difference. So describe the process first and agree what each metric counts.

6. Control: what happens after a problem is found

  • Is there a procedure for feedback to the manager after a conversation is reviewed?
  • Does a problem that was found turn into a task with an owner and a date?
  • Does anyone check that the task was done?
  • Is there a regular meeting that looks at the same metrics?
  • Does the team know which changes to its own work came out of the previous review?

What to prepare for the review

The table below is the same working list AKORDO asks you to go through before a consultation.

AreaQuestionWhat to prepare
ProcessWho is responsible for the next action after an enquiry?A description of the actual steps and roles
CRMIs it clear why a deal has a particular status?Sample records and data entry rules
CallsDoes the manager clarify the need and the next step?Sample conversations available for review
ChatsIs context preserved between messages?Sample chat threads and working scenarios
ReportsWhat decisions should each metric support?Current reports and explanations of definitions
ControlHow does the team fix a problem once it is found?The feedback and task procedure

Adapt the list to your own process. Agree the volume of material and the criteria before the work begins.

How to read your own result

The checklist gives no score, and that is deliberate: how much a question weighs depends on how you sell. Look not at how many answers are no, but at where they cluster.

  • Mostly no in sections 1 and 2: there is no documented process and no data about it. Start with the description, because otherwise the reports have nothing to count.
  • Mostly no in sections 3 and 4: the process exists, but conversations carry it out differently each time. That is a job for standards and training, not for reporting.
  • Mostly no in sections 5 and 6: the team is working, and the head of sales cannot see the result or has nothing to decide on.
  • Many "do not know" anywhere: the first task is not a change, it is access to the data.

What a paid review adds to this checklist

The checklist shows which answers you are missing. Diagnostics give you those answers, on your own data. In the AKORDO catalogue the output is a map of how a client moves from first contact to payment, with the points where clients are lost, an analysis of business processes, CRM, calls and chats, a prioritised list of risks and proposals, and an action plan for the next 30 to 90 days. The indicative timeline is 7 working days.

The catalogue gives no numeric guarantee of sales growth. The output of a review is a map, an analysis and a plan; the commercial effect depends on the changes the team puts in place next and on the conditions of the business.

Questions about the checklist itself

How long does it take?

You can go through it with your head of sales in one meeting. What takes time is not the ticking, it is finding the data behind the questions you answered "do not know".

Do we have to stop the team?

No. The review works from recordings, CRM data and short conversations with the managers. The team keeps selling.

Can it be used without a CRM?

Yes. Section 2 then describes whatever you have instead of a single system, and that becomes part of the result.

What should we do with the completed checklist?

Keep it as a starting point: a few months later the same questions will show what changed. If you would like to go through the result together, send an enquiry and bring the completed checklist to a free AKORDO consultation. If CRM comes next, the following document is the CRM technical specification template.