Blog · Territory, capacity and quota planning
Identify the people who use, evaluate, fund and approve an account-expansion proposal. Keep verified buying roles separate from legal-entity and reporting hierarchies.
A buying-group map describes how one proposed purchase can become an approved commitment. An account manager may know the customer well and still have no evidence about who evaluates a new category or releases its budget. The map makes those missing relationships visible before a proposal is mistaken for a purchase decision.
Use key account management for the broader relationship review. This guide owns the people and responsibilities behind a particular expansion decision, rather than another set of account KPIs.
Start with a proposed category, approximate scope, locations and decision period. Replacing a site consumable and adding a company-wide service may involve different people even at the same customer. Write the decision in one sentence that a customer can correct.
Distinguish the operating site, purchasing organization and contracting entity. Use the account hierarchy for those organizational relationships. The buying map attaches human responsibilities to that structure; it does not replace it.
Record only information needed for the business purpose. An initial analytical review can use role IDs rather than personal names. Private relationship notes need appropriate handling and should not be pasted into a broadly circulated report.
Useful questions are concrete: who describes the operational need, who checks the specification, who owns the budget, who manages sourcing, and who approves the final commitment? Add a security or technical reviewer only when the offer requires one. Avoid inventing a universal committee.
For each role, record a verified contact or an unresolved status, source, confirmation date and next question. A business card establishes a job title, not the responsibilities for this purchase. A statement from the customer about its approval sequence is stronger evidence than an internal guess.
The same person may use the product and own its budget. Conversely, two people with the same title may have authority over different locations. Preserve those distinctions instead of assigning roles from seniority alone.
The following DEMO-101 case is invented. A supplier is discussing an additional maintenance category with one existing customer.
| Decision role | Contact ID | Evidence | Next action |
|---|---|---|---|
| Operational user | DEMO-P1 | Confirmed the required application | Review trial specification |
| Technical evaluator | DEMO-P2 | Customer named this reviewer | Arrange specification discussion |
| Budget owner | DEMO-P2 | Same reviewer confirmed budget responsibility | Check available amount |
| Procurement coordinator | DEMO-P3 | Existing sourcing contact | Confirm qualification steps |
| Final approver | Unknown | No confirmation | Ask procurement to identify approval route |
Four of five role assignments are confirmed: 80% role coverage under this deliberately small definition. There are three known people, not four. Neither number is a probability of winning, and the unresolved approval role can matter more than the percentage suggests.
The next action is to establish the approval route. Sending a larger proposal to all three known contacts would not resolve that missing fact.
A contact agreeing to a meeting has not approved a specification or committed a budget. Use explicit states such as identified, contacted, requirement confirmed and approval pending. Explain what evidence moves a role between states.
Record objections alongside their owners. A technical concern, an unfunded budget and an incumbent obligation call for different actions. The customer buying-process guide connects those actions to decision timing; it should not turn the role map into a mechanically scored forecast.
Review roles after a scope increase, new site, customer reorganization or contact departure. Preserve the previous map and record why the new purchase needs a different route. The single-contact dependency guide helps assess whether access disappears with one person.
A useful review ends with a named unresolved role, an owner and a dated question. It may also end with a decision to stop because the proposal has no funded need. Both outcomes improve the quality of the expansion list.
Read the map beside the completed customer-growth review, keeping measured customer history separate from assumptions about demand and authority. Bring an authorized example to Covirage contact to agree the required analytical view and review scope.
No. The buying group describes people's roles in one decision. The contracting entity is the organization entering the agreement. Verify both without treating a senior contact as proof of signing authority.
Yes. Record the separate responsibilities and the evidence for each. Counting role assignments as distinct people would exaggerate relationship breadth.
Use common role questions, but confirm the actual decision process for the proposed category, location and amount. A previous purchase may have followed a different route.