Blog · Territory, capacity and quota planning
A customer analytics strategy connects each business question to a decision, an owner and an export. Follow a practical sequence for choosing the first review, calculating account comparisons and checking whether the evidence supports action.
A customer analytics strategy starts with the decisions a company needs to make, then identifies the evidence and owner for each one. Build the first review from account, sales and service exports that already exist. A calculated comparison becomes useful when someone can explain what action it supports and what still needs investigation.
Write the decision before choosing the measure. Asking which accounts need a commercial review is more actionable than asking for every available customer metric. It identifies a meeting, a person and a possible next step.
For a US distributor, a short register might look like this:
| Business question | Decision | Source export | Decision owner | Evidence gap |
|---|---|---|---|---|
| Which established accounts lost revenue? | Assign account reviews | Posted sales and credit memos | Sales director | Order timing needs confirmation |
| Where does service effort absorb capacity? | Review service arrangements | Approved support hours and sales | Service director | Hours omit unlogged work |
| Which accounts might need another product category? | Ask account managers to investigate | Invoice categories and account roster | Category manager | Contract eligibility not confirmed |
These questions have different evidence requirements. Do not delay a usable revenue review while waiting for complete product eligibility information. Equally, do not interpret missing eligibility as permission to recommend a product.
The broader data analytics strategy covers program choices beyond customers. Keep this register focused on commercial relationships and decisions the named owners can actually make.
For the first review, select established accounts present in both reporting periods. Keep new accounts and confirmed closures in separate groups so their movements remain visible. Write down the treatment of credits, transfers between account IDs and customer mergers.
Use a stable account key rather than a company name. Prepare a sales export with account key in column A, posting month in B and net posted revenue in C. Store posting month as an actual date representing the month's first day. Keep invoice and credit identifiers in the underlying file for reconciliation.
Prepare a separate service export with account key in A, reporting month in B and approved support hours in C. Aggregate each export to account and month before comparing them. Joining invoice rows directly to service entries would repeat amounts when an account has several of each.
Keep the population definition beside the review. The method for defining the norm from your own customer base explains why a comparison depends on which relationships qualify for its denominator.
The following illustrative distributor review uses July and August 2026. The revenue and support-hour inputs are the prepared exports' account totals. Columns E through G are calculated from those inputs; money is USD. Percentages and hours per revenue unit are displayed to two decimal places, with calculations retaining full precision.
| Account (A) | July revenue (USD) (B) | August revenue (USD) (C) | August support hours (D) | Revenue change (USD) (E) | Revenue change (F) | Hours per 1,000 revenue (USD) (G) |
|---|---|---|---|---|---|---|
| North | 120,000 | 108,000 | 60 | -12,000 | -10.00% | 0.56 |
| East | 80,000 | 84,000 | 30 | 4,000 | 5.00% | 0.36 |
| West | 60,000 | 45,000 | 90 | -15,000 | -25.00% | 2.00 |
| South | 40,000 | 43,000 | 20 | 3,000 | 7.50% | 0.47 |
| Total | 300,000 | 280,000 | 200 | -20,000 | -6.67% | 0.71 |
On a Review sheet, put the accounts in A2:A5. These Excel formulas populate the first account's July revenue, August revenue and August support hours from sheets named Sales and Service:
B2 = SUMIFS(Sales!$C$2:$C$999,Sales!$A$2:$A$999,$A2,Sales!$B$2:$B$999,DATE(2026,7,1))
C2 = SUMIFS(Sales!$C$2:$C$999,Sales!$A$2:$A$999,$A2,Sales!$B$2:$B$999,DATE(2026,8,1))
D2 = SUMIFS(Service!$C$2:$C$999,Service!$A$2:$A$999,$A2,Service!$B$2:$B$999,DATE(2026,8,1))
Enter the expression after each cell label and fill down. Extend every range to cover the complete export. Microsoft's SUMIFS documentation explains summing values that meet multiple criteria; here the criteria are account and reporting month.
Calculate the comparison columns:
E2 = C2-B2
F2 = IF(B2=0,"",E2/B2)
G2 = IF(C2=0,"",D2/C2*1000)
A blank rate flags an undefined denominator for review. It does not erase the underlying revenue or hours. Format F as a percentage and G as a number.
Sum B through E for the total row. Calculate the total rates from the summed inputs:
F6 = SUM(E2:E5)/SUM(B2:B5)
G6 = SUM(D2:D5)/SUM(C2:C5)*1000
Revenue reconciles as 300,000 minus 20,000 equals 280,000. The declining accounts contribute a $27,000 decrease, while the growing accounts offset $7,000. Their net movement must equal the $20,000 decrease in the total row.
Check service intensity by weighting account rates by August revenue:
=SUMPRODUCT(C2:C5,G2:G5)/SUM(C2:C5)
This equals 200 / 280,000 × 1,000, displayed as 0.71 hours. Use the unrounded G cells. Microsoft's SUMPRODUCT documentation describes multiplying corresponding array entries and summing the products. Covirage is not affiliated with Microsoft.
Finally, tie revenue to the posted sales report and hours to the approved service summary for exactly these accounts. Record excluded rows separately. Matching arithmetic inside the review cannot prove that an export was complete.
West has both falling revenue and the highest recorded service intensity in the table. Assign its account manager and service owner a joint review. They should check order timing, credits and the work recorded before deciding whether a commercial change is appropriate.
North also needs a revenue explanation. East and South provide context, but their growth does not establish that their service practices caused a better result. The table supports investigation, not a promise that changing support effort will restore sales.
Write the decision, owner, due date and missing evidence next to each selected account. After the review, record the explanation and action separately from the original figures. Use customer care analytics for deeper service comparisons, rather than expanding this first review into every support measure.
Once the process works, rolling customer-growth analytics out to a second team is a separate implementation step. Reuse definitions before expanding the audience.
Bring a sample of your own account, sales and service export with consistent periods and account keys. Covirage maps the columns, and its tools compute and check the comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring the first question from your decision register.
See sales insights for the supporting business context.
Include a decision register, named owners, source files, account definitions, measures, reconciliation checks and a review schedule. State what action each comparison can support and what evidence is still missing. This makes the strategy usable in an operating meeting.
Choose a question with a decision due soon, a person authorized to act and source files that can be reconciled. Revenue movement by account is often a practical starting point when sales exports are complete. Missing evidence can make another question a better first choice.
Track whether reviews happen, decisions receive an owner and agreed actions are completed. Then compare the relevant account outcomes over a consistent period. Keep operational follow-through separate from claims that an analysis caused a revenue or retention change.
A commercial leader can own the program, while finance owns revenue definitions and service leaders own effort measures. Each individual decision needs a named owner with authority to act. An analyst prepares the evidence and checks without replacing that responsibility.