Territory plan from account data

Use this workflow to turn a target-account list into a ranked outreach plan with clear account owners. It is for BDRs preparing a patch and territory sales leads resolving overlap before activity begins.

The result is one working document: a territory plan that records the evidence behind each rank, the route into the account, the next action and the ownership decision.

1. Build one account input sheet

Create a spreadsheet or CRM report with one row per account. Remove duplicate parent companies before you assess fit. If separate subsidiaries buy independently, keep them as separate rows and state why in the Account notes field.

Include these fields:

• Account name and CRM account ID
• Parent company and buying entity, if known
• Territory: geography, segment, industry or named-account rule
• Fit evidence: firmographic details, use case, technology, headcount band or other approved qualification data
• Existing relationship: open opportunity, current customer relationship, partner contact, former prospect, event attendee or none
• Trigger event: a dated change or signal relevant to the account
• Known people: name, role, seniority, source and last contact date
• Current owner and any claimed owner
• Route in: direct contact, partner introduction, inbound follow-up, executive connection, event follow-up or research needed
• Data source and date checked

Keep facts separate from assumptions. Write Hiring in target function, source dated 12 May rather than Likely expanding. The first can be checked. The second may still be useful, but label it as an inference.

2. Set the scoring rules before ranking

Agree the rules with the territory lead before asking the model to sort anything. Use a simple score that your team can explain in a pipeline review. For example, score each category from 0 to 3:

Category	Score 0	Score 3
Fit	Outside the agreed profile	Clear match to the agreed profile
Relationship	No recorded connection	Active, relevant relationship with a named person
Trigger	No relevant recent signal	Dated event that creates a credible reason to contact now
Route in	No named route or role	Named person or introduction path with a clear first step

Add the four scores for a maximum of 12. Define the action bands in the sheet, for example:

• 10-12: priority outreach this week
• 7-9: research or warm-route development
• 0-6: retain in the territory list, but do not prioritise

These bands are working rules, not proof that an account will buy. If your territory uses other fields, such as account tier or strategic coverage, add them as a separate rule. Do not quietly change the score after seeing the ranked list.

3. Ask for a structured assessment

Export only the fields needed for the task. Remove personal contact details that are not needed to decide account ownership or the next work step. Check your organisation's handling rules before uploading CRM material. Available tools and their limits can vary, so check the relevant guidance in the xAI documentation overview.

Give the model the scoring rubric, the account rows and the required output format. Use this prompt, replacing the bracketed text:

You are assisting with territory planning. Use only the account data provided.

Score each account from 0 to 3 for fit, existing relationship, trigger event and route in. Give one short evidence statement for each score. Mark unsupported claims as "not evidenced".

Apply these ownership rules:
[PASTE TERRITORY RULES, NAMED-ACCOUNT RULES AND HANDOFF RULES]

For every account, return a table with:
Account name | total score | fit evidence | relationship evidence |
trigger evidence | route in | recommended owner | ownership rationale |
next action | missing information

Rank accounts by total score. Break ties by stronger relationship evidence, then by a clearer route in. Do not invent contacts, events, account ownership or product use.

Use the model's table as a draft, not as the territory record. Copy its recommendations into a review sheet where the lead can accept, amend or reject them.

4. Resolve ownership in a short review

Review the highest-ranked accounts first with the BDR, the territory lead and any existing account owner. For each account, make one of three decisions:

1. Assign: name one owner, set the next action and record the decision date.
2. Hold for evidence: assign a person to confirm a parent account, relationship or territory rule by a stated date.
3. Escalate: send genuine conflicts, such as competing named-account claims, to the person who owns territory policy.

Do not solve an ownership conflict by assigning two people to the same first outreach. One person owns the next action. Others can be listed as contributors.

If you see this	Do this	Record in the plan
A current opportunity under another owner	Keep that owner unless the territory rule says otherwise	Opportunity link and owner confirmation
A parent company spans two territories	Check the buying entity and account hierarchy	Parent, subsidiary and deciding rule
A partner has the best route in	Assign the internal owner, then name the partner as contributor	Introduction request and due date
No clear route or fit evidence	Hold or lower priority	Specific research gap

5. Turn rankings into an outreach plan

For every assigned priority account, write a next action that can be completed without another planning meeting. It should name the person, channel, reason and due date.

Use this format:

Owner: [name]. By: [date]. Action: ask [named connector] for an introduction to [role], citing [dated trigger]. If no reply, research [missing field] before direct outreach.

Group the final plan into three lists:

• Start now: assigned accounts with a reason to contact and a route in.
• Develop route: assigned accounts where fit is strong but the relationship or contact path needs work.
• Resolve ownership: accounts blocked by a documented territory or hierarchy question.

Keep lower-scoring accounts in the sheet. They are not discarded. They are deferred until new evidence changes their score.

6. Check the output before handover

The output is wrong if it sounds certain where the input is thin. Review every priority account against the original CRM row, relationship record and trigger source. Check that the named owner fits the written territory rule, not merely the model's rationale.

Look especially for these errors:

• An inferred trigger presented as a dated fact.
• A contact named without a source in the input.
• A parent account confused with a subsidiary.
• An existing opportunity omitted from the relationship score.
• Two owners assigned to the same first action.
• A high score driven by generic fit while no route in exists.

7. Hand over the territory plan

Save the reviewed sheet in the agreed team location. Update the CRM owner field only after the ownership decision is confirmed. Send the territory lead a short handover note containing:

• Number of accounts in each action list.
• Accounts assigned, held and escalated.
• The owner and due date for each unresolved conflict.
• The date for the next review, usually after new activity or account data has been recorded.

When the workflow does not work, do not ask the model to make a stronger guess. Go back to the failing input: clarify the territory rule, repair the account hierarchy, confirm the relationship record or collect the missing trigger evidence. Then rerun only the affected accounts and record what changed.