Blog · Territory, capacity and quota planning
Define the evidence, customer permission, receiving owner and next step for a cross-team expansion handoff. Separate accepted internal work from a customer-approved purchase.
An account manager identifies a possible new category and sends a brief message to a product specialist. The specialist receives no specification, customer permission or decision context, then the referral sits unanswered. A useful handoff is a transfer of a defined next task with enough evidence to act, not merely the transfer of a customer name.
The business-line referral guide measures referral flow and outcomes. This article owns the operational handoff that makes the receiving team's work reviewable.
Start with the question the specialist needs to resolve: compatibility, service scope, implementation requirements or a specific commercial option. A measured whitespace gap may motivate the conversation, but it does not establish customer demand.
Record what the customer has actually confirmed and what remains an account owner's hypothesis. Include product or category scope, relevant sites and the expected decision period. The buying-group map identifies the appropriate customer route.
Avoid an instruction such as “sell everything we do.” It provides no bounded decision and makes it difficult for the specialist to accept, reject or prioritize the work.
Use account and offer IDs, a concise statement of need, authorized contact route, relevant constraints, supporting records and the requested next step. Identify information the customer has agreed may be shared. Keep unrelated private notes out of a general handoff.
Link to reviewed evidence instead of copying inconsistent figures into a new message. If a candidate amount is estimated, carry its source and assumption with it. A specialist should not have to reverse-engineer a wallet number before answering a technical question.
Write down what is missing. A returned handoff with a specific evidence request is more useful than an accepted task whose recipient cannot proceed.
Use states such as submitted, accepted, returned for evidence, deferred and declined. An email delivered to a specialist is not acceptance. Record the receiving owner, decision date and reason so the account manager knows what happens next.
Agree a response expectation for this workflow. Different specialist teams may have different capacity and urgency; there is no universal referral service level. Escalate unresolved ownership rather than interpreting silence as customer disinterest.
The revenue-operations handoff measures can identify leakage after the process states are reliable. Establish the states before comparing their rates.
The DEMO-801 case is invented. A review contains 24 distinct submitted handoffs after removing duplicate submissions. Six are returned for missing evidence, and 18 are accepted for specialist work.
| Current state of accepted work | Handoffs |
|---|---|
| Customer meeting scheduled | 10 |
| Awaiting agreed customer information | 4 |
| Deferred to a confirmed later window | 3 |
| Declined after specialist review | 1 |
| Total accepted handoffs | 18 |
Internal acceptance is 18 / 24 = 75%. Of the accepted handoffs, 10 / 18 = 55.6% have a scheduled customer meeting. Neither is a win rate. The accepted states reconcile: 10 + 4 + 3 + 1 = 18.
The six returned submissions deserve an evidence-completion action. The four awaiting customer information need a different owner action. Combining both into “stalled referrals” would obscure where the work is blocked.
Agree who introduces the specialist, who confirms scope and who records the customer's decision. The account manager may provide context while the specialist evaluates the category. Avoid conflicting proposals or uncoordinated contact from several teams.
If two offers compete for one budget, use the competing-offer review before adding both to the account plan. If the opportunity closes, sales-crediting rules govern credit without duplicating company revenue.
Return the outcome to the account owner: customer need confirmed, mismatch found, new evidence required, deferred decision or next commercial step. A declined referral can improve future qualification if its reason is recorded accurately.
Review a small sample of accepted and returned handoffs with both teams. Do not reward acceptance volume alone; accepting unusable work can increase the queue without improving customer decisions. Keep observed outcomes separate from assumed benefits.
Read the handoff beside the completed customer-growth review. Bring an authorized handoff sample to Covirage contact to agree the analytical view and review scope.
No. It means the specialist accepts responsibility for the next internal task. Customer need, buying authority and the relevant pipeline exit criteria require separate evidence.
Record the agreed account owner and specialist responsibilities explicitly. Technical participation need not transfer overall account ownership.
Not as additional company revenue. Use the agreed crediting and attribution rules, with revenue counted once and any overlay or referral credit reported separately.