Multi-team sales organization CRM Odoo: territory, routing, KPI (guida 11 di 15)

Ottantaquattresima guida operativa Odoo 19 per PMI italiane. Undicesima della serie 15 guide CRM Odoo. Quando il sales team cresce oltre 5-7 venditori, la gestione “tutti vedono tutto” diventa caotica. Lead persi, opportunity duplicate, ownership conflicts, no specialization. La risposta è organizzazione multi-team: gruppi specializzati per geografia, segmento customer, prodotto. Ogni team ha proprio dashboard, propri KPI, propria autonomia. In questa guida vediamo come setup organizzazione multi-team in Odoo CRM.

Vediamo: setup teams, criteri di segmentazione, permissions + visibility, territory management, lead routing inter-team, KPI per team, casi pratici PMI italiane.

Quando serve multi-team

Trigger per multi-team

• Sales team > 5-7 persone
• Multiple geografie servite
• Multiple customer segments
• Multiple product lines
• Different sales cycle per segment

Beneficio business

• Specialization deep per area
• Ownership clear
• Coaching team-specific
• KPI accountability
• Career path management

Setup teams

Settings → CRM → Sales Teams. Crea N teams, assegna leader, configura email alias, currency, pricelist. Ogni team diventa “azienda nell’azienda” con propria identità ma sotto cap unico:

• Team name + description
• Team leader assigned
• Members list
• Currency + pricelist team
• Email alias per team (es. nord@azienda.it)
• Invoicing target / quota
• Working hours / timezone

Criteri segmentazione team

Per geografia

• Italia Nord / Centro / Sud
• Europa / Americhe / APAC
• Province / Regione specifica
• Best per coverage local

Per segmento customer

• SMB (small) / Mid-Market / Enterprise
• By annual revenue
• By employee count
• By industry vertical

Per prodotto

• Product line A vs B
• Hardware vs software vs services
• New vs existing customers
• Cross-sell vs hunt

Per canale

• Direct sales
• Channel/Partner
• Inbound vs Outbound
• Self-service

Territory management

Territory = mapping geografico + segment per ogni team. Lead assignment automatico basato su rule. No overlap, clear ownership. Cambio territorio = trasferimento opp ordinato:

• Rule: customer country + segment → team
• Auto-assignment on lead creation
• Override possibile (con approval)
• Transfer process documented
• Historical data preserved
• Reporting per territory

Lead routing inter-team

Lead che cross multiple criteria (es. customer geografica X ma anche prodotto specifico Y): routing rule decide team primary. Escalation se ambiguous. Coordinamento smooth tra teams:

• Routing rules priority
• Geography first, segment second tipico
• Score-based override
• Manual transfer process
• Alert su conflict
• Cross-team collaboration field

Routing decision tree esempio

• If revenue > 1M €: Enterprise Team
• Elif country = US: Americas Team
• Elif country = EU: Europe Team
• Elif product = X: Product X Team
• Else: General Team

Permissions + visibility

Default: ogni team vede solo proprie opp. Manager vede team. Director vede all. Configurable per ruolo. Privacy protection + competition healthy. No info leakage tra team:

• Sales User: vedi own opp
• Sales User All: vedi all opp (limited)
• Sales Manager: full team
• Sales Manager All: cross-team
• Privacy enforced
• Audit log accessi

KPI per team dashboard

Ogni team ha proprio dashboard: pipeline, forecast, win rate, activity volume, quota attainment. Confronto cross-team possible per management. Healthy competition stimulated:

• Pipeline value team
• Forecast vs quota team
• Win rate trend
• Activity volume per rep
• Average deal size team
• Cycle time team
• Leaderboard cross-team

Team setup tipici per PMI italiana

Small PMI (5-15 sales)

• 2 teams: Inbound + Outbound
• O: Italia + Estero
• Simple structure
• Manager unico

Mid PMI (15-50 sales)

• 3-5 teams: per region/segment
• Dedicated managers
• SDR team separato
• Enterprise team se applicabile

Large PMI (50+ sales)

• 6-10 teams: multi-axis (geo + segment + product)
• Director level oversight
• Specialized roles
• Cross-team coordination council

Cross-team collaboration

Account ownership rules

• Single account = single team owner
• Multi-product opp visible cross-team
• Conflict resolution process
• Account splits documented

Inter-team referral

• Cross-sell opportunity
• Commission split agreement
• Tracking referral source
• Recognition program

Knowledge sharing

• Best practice documentation cross-team
• Win/loss insights shared
• Battle cards per competitor
• Internal community

Compensation per team

Quota assignment

• Team quota aggregate
• Individual quota per rep
• Bottom-up vs top-down planning
• Adjustment per ramp/new rep

Commission structure

• Base salary + commission
• SPIFFs per push
• Accelerators sopra quota
• Team bonus per achievement

Territory protection

• Lead generated in territory → commission to rep
• Cross-territory referral split
• Disputes process clear
• Annual territory review

Team rollout strategy

Phase 1: Design (settimane 1-2)

• Segmentation criteria
• Team structure draft
• Management review
• Stakeholder input

Phase 2: Setup (settimane 3-4)

• Odoo team configuration
• Routing rules implementation
• Permission configuration
• Pilot team training

Phase 3: Launch (settimana 5)

• Communication org-wide
• Migration opp esistenti
• Q&A sessions
• Monitoring intensive

Phase 4: Iterate (mese 2+)

• Feedback collection
• Rule refinement
• Dashboard tuning
• Process improvement

Errori comuni multi-team

“Troppi teams”

Problema: 20 team per 30 venditori, overhead.
Soluzione: 3-7 team massimo per PMI media.

“No routing rules”

Problema: ogni lead routing manual, errori.
Soluzione: rules clear + auto-assignment.

“Conflict ownership”

Problema: 2 team claim stesso account.
Soluzione: rules priority + escalation manager.

“No cross-team coordination”

Problema: teams siloed, no synergy.
Soluzione: weekly cross-team sync + shared platform.

“KPI dashboard absent”

Problema: team performance non visible cross-team.
Soluzione: dashboard per team + leaderboard.

Casi pratici PMI italiane

Caso 1 — SaaS: 4 teams geografia

• Italia + Iberia + DACH + UK
• Dedicated manager per team
• SDR team separato cross-region
• Quota: 1M €/team/quarter

Caso 2 — Manifattura: 3 teams segment

• SMB / Mid-Market / Enterprise
• Different sales cycle per segment
• Specialized expertise
• Win rate +15 points

Caso 3 — Servizi: 2 teams hunting/farming

• New Business Team (hunting)
• Account Management Team (farming)
• Clear handoff process
• Customer success focus

Caso 4 — E-commerce B2B: 5 teams hybrid

• Geography + product line
• Complex routing
• Cross-team collaboration
• Revenue +28% in 18 mesi

FAQ

Quanti team massimo?

PMI sweet spot: 3-7 team. Più di 10 = overhead coordination. Adjust per dimensione totale + complexity.

Posso cambiare team setup later?

Sì, restructuring possible. Migration opp + history preserved. Plan rollout carefully (2-4 settimane tipico).

Team manager full-time?

Per team > 6-8 rep: dedicated manager. Per piccoli team: player-manager hybrid. Coaching time critical.

Commission split tra team?

Sì configurable. Esempio: hunter 80% / farmer 20% per cross-sell. Documented in compensation plan.

Reporting consolidate cross-team?

Sì, executive view consolidate. Plus per-team drill-down. Best of both views.

Prossimi passi

Nella prossima guida (12/15 serie CRM) vedremo lost reasons + sales analysis: structured lost reasons, win/loss interview process, action plan per pattern, sales coaching basato su data.

Vuoi multi-team CRM nella tua PMI?
G Tech Group implementa multi-team CRM Odoo per PMI italiane: design segmentation, routing rules, permissions, KPI dashboard, change management. Track record di sales productivity +25% post-multi-team.
Richiedi un preventivo gratuito oppure prova la nostra demo Odoo 19 live. Oppure prova Odoo direttamente su odoo.com (link partner Brentasoft).