Blog · Board and management reporting · Sales teams
Choose sales support measures for quote turnaround, order accuracy and unfinished work. Follow a worked distributor example, a change in one quote's turnaround and the checks that keep the figures honest.
A useful KPI for sales support staff shows whether quotes and orders move quickly, accurately and without an accumulating queue. Pair service speed with a quality measure and a backlog check so faster completion does not hide rework or abandoned requests.
These measures describe the support workflow. Quota attainment and pipeline creation belong in the separate B2B sales KPI review, where the sales rep's job and denominator are different.
Define the unit before choosing a target. A request, a quote version and an order line are different units; counting all of them as completed work rewards extra processing rather than useful output.
| Measure | Formula | File needed | Decision it supports |
|---|---|---|---|
| Mean quote turnaround | Total counted hours / Quotes issued | Request and first-issued timestamps | Identify broad delays |
| Median quote turnaround | Middle counted duration, or average of the middle pair | Same completed quote rows | Describe the typical completed request |
| Quote service compliance | Quotes issued within the agreed window / Quotes issued | Duration and applicable service window | Check customer commitments |
| First-pass quote accuracy | Quotes needing no correction / Quotes checked | Quote ID and correction flag | Find avoidable rework |
| Order error rate | Orders with at least one error / Orders checked | Order ID and quality result | Direct order-entry coaching |
| Closing backlog | Opening requests + New requests - Completed requests - Canceled requests | Queue movements and dated open-request list | Allocate remaining work |
The first-pass definition adapts a standard quality concept: ASQ defines first-pass yield around work meeting requirements without rework or repeat processing in its quality handbook glossary. For support work, write down which corrections count before collecting the measure.
Keep required fields small: request ID, request type, received timestamp, ready-to-work timestamp, first-issued timestamp, owner, status and correction reason. Add an order identifier where a reliable link exists. Anonymized request and order identifiers are enough for this review; customer contact details are unnecessary.
Prairie Components, an illustrative US distributor, reviews quotes issued during a completed reporting week. The duration starts when a request is complete enough to work and ends when the first quote is issued. Counted hours follow the company's published working calendar, with waiting time recorded separately.
The agreed service window is eight counted hours. The linked order amounts show orders accepted by the review cutoff; they are associated outcomes, rather than sales credited to support staff.
| Quote ID | Counted turnaround hours | Correct on first issue? | Linked accepted order value (USD) |
|---|---|---|---|
| Q001 | 2 | Yes | 10,000 |
| Q002 | 4 | Yes | 15,000 |
| Q003 | 6 | No | 0 |
| Q004 | 8 | Yes | 20,000 |
| Q005 | 10 | Yes | 0 |
| Q006 | 18 | No | 0 |
| Total | 48 | 4 correct; 2 corrected | 45,000 |
The calculation steps are small enough to inspect directly:
| KPI | Calculation | Result |
|---|---|---|
| Mean quote turnaround | 48 / 6 | 8.0 hours |
| Median quote turnaround | (6 + 8) / 2 | 7.0 hours |
| Within the service window | 4 / 6 | 66.7% |
| First-pass quote accuracy | 4 / 6 | 66.7% |
| Quotes linked to accepted orders | 3 / 6 | 50.0% |
Percentages are rounded to one decimal; durations to one decimal. The mean and median answer different questions. NIST's explanation of location measures defines the mean as the sum divided by the count and the median from the ordered middle values; it also explains how skew affects the mean.
Here the slowest quote pulls the mean above the median. The manager should inspect Q006's delay and the correction reasons on Q003 and Q006. The numbers identify the requests to investigate; they do not establish whether the cause was staffing, missing information or an approval delay.
The order-entry review covers orders checked during the same week. This is a separate cohort, including orders from quotes issued earlier; it is not limited to the accepted orders linked above.
| Order-check outcome | Orders |
|---|---|
| No correction required | 5 |
| At least one correction required | 1 |
| Total checked | 6 |
Order error rate is 1 / 6 = 16.7%; first-pass order accuracy is 5 / 6 = 83.3%. The categories are exhaustive and mutually exclusive, so their counts add back to all orders checked. Record individual error types in a separate reason list without counting an order again in the denominator.
This separates order-entry accuracy from quote accuracy. A quote can be correct while the later order has an address error, and a corrected quote can still lead to an accurate order. Combining both stages obscures which process needs attention.
The quote queue starts with four open requests. Use movement counts for the entire queue, including requests carried forward from the prior week.
| Queue movement | Requests |
|---|---|
| Open at the start | 4 |
| Received during the week | 8 |
| Completed during the week | 6 |
| Canceled during the week | 1 |
| Open at the end | 5 |
The identity is 4 + 8 - 6 - 1 = 5 requests. Compare that result with the closing open-request list. Completed work is the six issued quotes in the example; cancellation is a separate exit, not a successful completion.
Attach each remaining request's age, request type and next owner to the closing list. A backlog total can stay steady while older work becomes increasingly overdue. That is why the count and the actionable list belong together.
Suppose Q006's counted turnaround falls from 18 hours to six hours. All other inputs stay fixed, including quote quality, received requests, completed requests and cancellations.
| Measure | Original | Revised | Calculation for revised result |
|---|---|---|---|
| Total turnaround | 48 hours | 36 hours | 48 - 18 + 6 |
| Mean turnaround | 8.0 hours | 6.0 hours | 36 / 6 |
| Median turnaround | 7.0 hours | 6.0 hours | Middle pair in 2, 4, 6, 6, 8, 10 |
| Service compliance | 66.7% | 83.3% | 5 / 6 |
| First-pass quote accuracy | 66.7% | 66.7% | 4 / 6 |
| Closing backlog | 5 requests | 5 requests | 4 + 8 - 6 - 1 |
The service improvement is 16.7 percentage points, calculated before rounding. Mean turnaround falls by 2.0 hours, or 25.0%. Quality and backlog remain unchanged because neither their counts nor their classifications changed. This is a speed improvement with a separate quality problem still to resolve.
Use the broader KPI examples for other business functions. For the related finance workflow, finance department staff KPIs uses a different completion and quality population.
Bring a request export, order-quality file and dated backlog lists to Covirage. Covirage maps the columns; its tools compute and check turnaround, quality and queue movements, and the external AI model explains the results with every figure traced to its rows.
Create a free Covirage account and bring a sample of your own data. Account creation takes about a minute; then you set up your business and bring your files.
See sales insights for the supporting team-review context.
Set the target from customer commitments and the complexity of the request. Standard replenishment quotes and engineered proposals need separate expectations. Publish when the clock starts, which working hours count and how incomplete requests are treated before comparing people or periods.
Revenue can provide context when requests link to orders, but the support team rarely controls pricing, customer decisions or account assignment. Review service speed, accuracy and backlog as direct workflow measures, then investigate how those measures relate to sales outcomes.
Divide orders that passed the agreed accuracy check without correction by all orders checked in the same cohort. Count an order once even if it has several errors. Keep error categories separately so the team can identify recurring pricing, quantity or address problems.