tl  tr
  Home | Tutorials | Articles | Videos | Products | Tools | Search
Interviews | Open Source | Tag Cloud | Follow Us | Bookmark | Contact   
 Generative AI > Google Gemini API > Territory Planning Agent

Territory Planning Agent

Author: Venkata Sudhakar

ShopMax India has a field sales team covering 12 cities. As the business grows, territory assignments made 2 years ago no longer reflect current market potential - some reps are overloaded while others have thin pipelines. A Territory Planning Agent analyses revenue potential, rep capacity, and account concentration to recommend balanced territory realignments.

This tutorial builds a Territory Planning Agent using Google ADK and Gemini 2.0 Flash. The agent evaluates each territory on market potential and rep workload, identifies imbalances, and recommends reassignments with projected revenue impact.

The below example shows the Territory Planning Agent analysing and rebalancing the West India sales territories.


It gives the following output,

TERRITORY REVIEW - WEST INDIA (Q2 2026)
========================================

Overall Market Penetration: 34% (Rs 563 L of Rs 1670 L potential)

Current Territory Status
Rep      City        Accounts  Workload     Penetration  Untapped
Vikram   Mumbai      42        OVERLOADED   42%          Rs 290 L
Kiran    Ahmedabad   35        OVERLOADED   37%          Rs 265 L
Anita    Surat       28        Balanced     30%          Rs 225 L
Meena    Pune        18        Underloaded  23%          Rs 215 L
Rajesh   Nashik      12        Underloaded  25%          Rs 112 L

Recommended Reassignments

1. Move 8 accounts: Vikram -> Meena
   Rationale: Pune has Rs 280 L potential with only 23% penetration.
   Meena has capacity and local market knowledge.
   Projected uplift: Rs 35 lakhs

2. Move 5 accounts: Kiran -> Rajesh
   Rationale: Nashik is underpenetrated at 25%. Rajesh needs
   more accounts to build pipeline momentum.
   Projected uplift: Rs 22 lakhs

Total Projected Revenue Uplift: Rs 57 lakhs
Implement by: 15-Apr-2026 before Q2 planning cycle closes.

The Territory Planning Agent can be run at the start of each quarter before quota-setting. Extend it to factor in travel time between accounts, rep seniority, and industry specialisation. Connect to your CRM to pull live account counts and pipeline values instead of static data.


 
  


  
bl  br