A sales plan sets out how much the team must sell over a chosen period and links that amount to buyers, actions and dates. To draw up a sales plan, first define the result — contracts, shipments or money received — then calculate sales to existing and new customers. Next, divide the amount between salespeople and establish when each required step must be completed so the result falls in the intended month.
It is not enough for me to hear from the head of sales that the team will catch up. If a purchase requires a sample to be tested, and the sample is still in the warehouse, I want to know the test date. Has the salesperson already agreed it with the buyer? Or is the end of the month only getting closer in our report?
I believe a sales plan starts helping the owner at an uncomfortable moment: when the head of sales shows which part of the amount no longer adds up, even though the month is still underway. Then there is time to choose a different action. If we only discuss the percentage achieved, that conversation will begin after some options have already disappeared.
Monthly sales plan: where the amount came from
The company expects to receive money, the head of sales brings contracts, and a salesperson talks about proposals sent. Everyone is busy selling. But a contract with payment due next month does not meet the company's needs today. So the first thing I establish is which event counts as achieving the sales plan here. From here on, the discussion concerns money received from sales; if your goal is shipments, count them by their shipment date.
The amount needed, on its own, says nothing about where it will come from. In my calculation, I separate three parts:
- Money from deals already underway: which payment we expect this month, what remains to be done before it arrives, and what confirms the date.
- Sales yet to be started: repeat orders and new buyers, each source counted separately.
- The gap between what the company needs and what the first two parts can justify.
That last line must not be hidden. If there are no buyers or time to make those sales, dividing the amount between employees adds nothing. The owner needs a choice: provide resources for a specific source of orders, change the terms of purchase, or acknowledge that the expected money falls short of what is needed. The head of sales presents a calculation of the consequences of each option.
For the first part, going through the deals is enough. The full order value and this month's payment are different amounts. Where there is an advance payment, that is what goes into the sales plan for money received; the balance is assigned to its own due date. One order must not appear in the total twice, once as a contract and once as a payment.
For the second part, you need a history of comparable sales. We take the same product, source of enquiries and purchase terms. We keep a one-off large order separate: you cannot demand a repeat of a record if you do not know who will buy that volume again. For similar small orders, the calculation looks like this:
- We divide the missing amount by the average payment from one order received in the required month. This gives us the number of orders needed, which we round up.
- We divide the number of orders by the proportion of enquiries that lead to payment. This gives us the number of enquiries needed, which we also round up.
- We compare this number with how many enquiries the chosen source brings in and when they can arrive.
Here it is easy to get an attractive answer from figures that do not belong together. Payments from old deals divided by this month's enquiries do not show what happens to those enquiries. You need a group of enquiries that has already been followed through to an outcome. We count repeat purchases separately from first purchases: they follow a different path to payment. We review large deals individually, without using an average order value.
Now for the calendar. Let us work through the calculation using an illustrative sale involving a sample test, without reference to a client case. The buyer pays after placing the order, places the order after making a decision on the test result, and starts the test after receiving the sample. We work backwards along this chain from the required payment date. This gives us the date by which the sample must reach the buyer.
Now that date gives us something to debate. The warehouse confirms readiness to dispatch, the carrier confirms delivery, and the buyer confirms the time for the test and the decision afterwards. The time needed for consecutive stages is added together; stages that happen at the same time are counted together. I will not accept a shorter test period just because the sales plan otherwise fails to add up. First, the buyer must confirm they can meet it.
If there is no sales history, the calculation remains an assumption. We record known timescales with a reference to the agreement, and unknown ones as separate questions with someone responsible for each answer. Work on the deal continues, but the amount tied to an unsupported date is shown separately from payments whose dates are confirmed.
Meeting the sales plan: what the percentage hides
To calculate sales plan achievement, divide the actual result by the sales plan and multiply by 100%. As long as the sales plan is not zero, the formula shows what proportion of the target has already been achieved. There is something else I want to know from this report: while we were counting payments already received, which future payments lost the grounds we had for expecting them?
The percentage will not pick that up.
If the sample did not arrive in time for the scheduled test, we have no less money today. Our chance of receiving it later has worsened. The payments report will stay the same until the day the payment was expected. So waiting until mid-month for the first serious conversation is too late: the deadline for action on this deal has already passed.
Comparing progress with the proportion of days that have passed also needs a basis. If sales are steady, it helps spot a shortfall. If payments follow an agreed schedule, a straight line will mislead: before a large payment the team looks weak, and afterwards it looks fine. The payment date says nothing about how ready the other deals are.
I need the head of sales to examine the missed step itself. In our example, we first establish what happened with the test. If the buyer has kept the time slot and is ready to accept the sample via another delivery method, the salesperson arranges dispatch. If the buyer has moved the test, the head of sales recalculates the expected payment date. If the salesperson never agreed the test at all, they first obtain a real date to replace their assumption.
These are different tasks. Telling everyone to make more calls leaves each of these causes in place. A call is needed if it secures a specific decision: agree receipt of the delivery, find out the test result, or get the order terms. A count of dialled numbers does not, by itself, change the buyer's calendar.
The owner can easily object here: if expectations can be revised, the team will simply lower its own sales plan. I am also against lowering the target after the fact. But banning people from reporting a new payment date will not bring the old one back. The report must keep the original sales plan, the amount already received, the revised estimate of payments and the gap to the target side by side. The head of sales proposes actions to address that gap and is held separately accountable for work left undone.
The sign of a timely response is visible on the day of the delay: either there is an agreed way to keep the payment within the month, or the owner has learnt which amount will fall outside it and why. That gap must not remain only in the salesperson's head until the next report.
Sales plan for the team: who gets the shared resource
Adding up individual sales plans is not enough. Let us suppose several deals need the same sample for testing. Each salesperson has agreed a date with the buyer and justified the expected payment. Separately, everything adds up. Together, it does not: the sample has been promised to different buyers at the same time.
Here I expect a decision from the head of sales. A salesperson is entitled to pursue their own order; the head of sales must choose which order gets the shared resource first. Otherwise, whoever gets through to the warehouse first will make the choice, and the consequences will show up in someone else's individual sales plan.
The sales plan for the team is put together on a single basis: for example, by adding up the sales assigned to each salesperson. Totals by channel or product show the same money from a different angle; they are not added to the overall amount. After adding up the figures, the head of sales reviews actions that depend on the same person or piece of equipment:
- Which deal needs the resource, and by what date.
- Who has confirmed it is available, and how long it will be occupied.
- Which payment will move if the resource goes to another deal.
- What the head of sales decides independently, and which steps to speed things up need the owner's agreement.
Removing the calendar clash is not enough. The deal that has been pushed back gets a new date for a required stage, and its expected payment changes as a result. While one employee's individual sales plan has been corrected but the overall total stays the same, the report keeps promising the same money.
I also look at what the team pays to save the month. If first meetings and sample shipments to new buyers are cancelled to secure urgent payments, next month has already lost some of its preparation. That cost must not be hidden behind the sales total achieved. I examined it separately in the article “We met the sales plan. Now do I have to carry everything myself again?”.
A salesperson's sales plan: what to hold them accountable for
The same amounts in individual sales plans are convenient for the head of sales. But I do not consider them justified until I see what each salesperson is working with. One has repeat orders, another has new enquiries, and a third must first re-establish contact with buyers. Requiring the same amount of money does not make the time needed to secure payment the same.
The debate needs to focus on deals. If an employee says they cannot make it in time, they show the required stage and the deadline that does not fit. The head of sales establishes where that deadline came from and what the employee has already done. This makes it clear where help is needed, where the calculation was wrong, and where the salesperson has not yet started the necessary work.
I link a salesperson's sales plan to a note opened alongside the deal record. Below is a template for the same sale involving a test; fill in the amounts and dates from your agreements:
- Result for the month: receive the payment specified in the order; only the amount expected this month goes into the calculation.
- Basis for the date: the test date set by the buyer and the agreed process for placing the order after the result.
- Next action: the salesperson agrees delivery of the sample in time for the test and obtains confirmation of receipt.
- What is needed from the head of sales: resolve the clash in sample use dates if it is already booked for another deal.
- Confirmation of completion: the buyer has received the sample and confirmed that the test will take place at the agreed time.
- Reason for revising the payment date: the test is postponed; the salesperson tells the head of sales on the day they find out.
Sending an email does not complete this item. I need a reply that confirms how the purchase will proceed. If there is no reply, the uncertainty remains in the note, and the head of sales decides how to resolve it. A record of a completed call says too little about the result here.
The number of calls is useful for calculating workload: whether the person has time to contact everyone they need an answer from. But making it the main target is dangerous — easy, short conversations will take time away from difficult ones. The article “Sales have fallen. There is a sales plan — but what should salespeople do differently?” explains how to turn a monthly amount into the work that needs to be done.
When a delay goes unnoticed
Even this kind of sales plan is useless if the new test date is in the correspondence but the deal record still shows the old payment date. The head of sales is calculating one thing, and the salesperson knows another. The owner learns about the mismatch when they are already asking about the money.
I see a specific task for daily oversight here: compare the agreements with what the calculation relies on. The head of sales needs the changed dates, unanswered messages and actions that did not happen. For each one, there must be a decision on who continues the work and what confirmation they obtain. If the head of sales has only read the message about the delay, nothing has changed for the deal yet.
RENTROP has AI ROP for this task — a service that increases sales by 20–30 % from the first day: it analyses calls and correspondence together with the deal record, shows who to reply to, which deals to take through to payment and which to bring back. More details: daily oversight of the sales team.
I expect the head of sales to have the uncomfortable conversation before the owner is left with no option but to demand the impossible. A sales plan is useful while it still lets you choose an action in time to affect the month's result.