{"id":3777,"date":"2026-08-30T09:00:00","date_gmt":"2026-08-30T07:00:00","guid":{"rendered":"https:\/\/brentasoft.com\/blog\/multi-team-sales-crm-odoo-19-pmi-italiane-guida-11\/"},"modified":"2026-06-10T15:10:58","modified_gmt":"2026-06-10T13:10:58","slug":"multi-team-sales-crm-odoo-19-pmi-italiane-guida-11","status":"publish","type":"post","link":"https:\/\/brentasoft.com\/blog\/multi-team-sales-crm-odoo-19-pmi-italiane-guida-11\/","title":{"rendered":"Multi-team sales organization CRM Odoo: territory, routing, KPI (guida 11 di 15)"},"content":{"rendered":"<p><em>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 &#8220;tutti vedono tutto&#8221; diventa caotica. Lead persi, opportunity duplicate, ownership conflicts, no specialization. La risposta \u00e8 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.<\/em><\/p>\n<p>Vediamo: setup teams, criteri di segmentazione, permissions + visibility, territory management, lead routing inter-team, KPI per team, casi pratici PMI italiane.<\/p>\n<h2>Quando serve multi-team<\/h2>\n<h3>Trigger per multi-team<\/h3>\n<ul>\n<li>Sales team &gt; 5-7 persone<\/li>\n<li>Multiple geografie servite<\/li>\n<li>Multiple customer segments<\/li>\n<li>Multiple product lines<\/li>\n<li>Different sales cycle per segment<\/li>\n<\/ul>\n<h3>Beneficio business<\/h3>\n<ul>\n<li>Specialization deep per area<\/li>\n<li>Ownership clear<\/li>\n<li>Coaching team-specific<\/li>\n<li>KPI accountability<\/li>\n<li>Career path management<\/li>\n<\/ul>\n<h2>Setup teams<\/h2>\n<p>Settings \u2192 CRM \u2192 Sales Teams. Crea N teams, assegna leader, configura email alias, currency, pricelist. Ogni team diventa &#8220;azienda nell&#8217;azienda&#8221; con propria identit\u00e0 ma sotto cap unico:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-01-team.png\" alt=\"Sales team setup CRM Odoo 19 PMI italiane multi-team\" class=\"aligncenter size-full wp-image-3772\"\/><\/p>\n<ul>\n<li>Team name + description<\/li>\n<li>Team leader assigned<\/li>\n<li>Members list<\/li>\n<li>Currency + pricelist team<\/li>\n<li>Email alias per team (es. nord@azienda.it)<\/li>\n<li>Invoicing target \/ quota<\/li>\n<li>Working hours \/ timezone<\/li>\n<\/ul>\n<h2>Criteri segmentazione team<\/h2>\n<h3>Per geografia<\/h3>\n<ul>\n<li>Italia Nord \/ Centro \/ Sud<\/li>\n<li>Europa \/ Americhe \/ APAC<\/li>\n<li>Province \/ Regione specifica<\/li>\n<li>Best per coverage local<\/li>\n<\/ul>\n<h3>Per segmento customer<\/h3>\n<ul>\n<li>SMB (small) \/ Mid-Market \/ Enterprise<\/li>\n<li>By annual revenue<\/li>\n<li>By employee count<\/li>\n<li>By industry vertical<\/li>\n<\/ul>\n<h3>Per prodotto<\/h3>\n<ul>\n<li>Product line A vs B<\/li>\n<li>Hardware vs software vs services<\/li>\n<li>New vs existing customers<\/li>\n<li>Cross-sell vs hunt<\/li>\n<\/ul>\n<h3>Per canale<\/h3>\n<ul>\n<li>Direct sales<\/li>\n<li>Channel\/Partner<\/li>\n<li>Inbound vs Outbound<\/li>\n<li>Self-service<\/li>\n<\/ul>\n<h2>Territory management<\/h2>\n<p>Territory = mapping geografico + segment per ogni team. Lead assignment automatico basato su rule. No overlap, clear ownership. Cambio territorio = trasferimento opp ordinato:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-02-territory.png\" alt=\"Territory management CRM Odoo 19 PMI italiane sales\" class=\"aligncenter size-full wp-image-3773\"\/><\/p>\n<ul>\n<li>Rule: customer country + segment \u2192 team<\/li>\n<li>Auto-assignment on lead creation<\/li>\n<li>Override possibile (con approval)<\/li>\n<li>Transfer process documented<\/li>\n<li>Historical data preserved<\/li>\n<li>Reporting per territory<\/li>\n<\/ul>\n<h2>Lead routing inter-team<\/h2>\n<p>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:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-03-routing.png\" alt=\"Lead routing inter-team CRM Odoo 19 PMI italiane\" class=\"aligncenter size-full wp-image-3774\"\/><\/p>\n<ul>\n<li>Routing rules priority<\/li>\n<li>Geography first, segment second tipico<\/li>\n<li>Score-based override<\/li>\n<li>Manual transfer process<\/li>\n<li>Alert su conflict<\/li>\n<li>Cross-team collaboration field<\/li>\n<\/ul>\n<h3>Routing decision tree esempio<\/h3>\n<ul>\n<li>If revenue &gt; 1M \u20ac: Enterprise Team<\/li>\n<li>Elif country = US: Americas Team<\/li>\n<li>Elif country = EU: Europe Team<\/li>\n<li>Elif product = X: Product X Team<\/li>\n<li>Else: General Team<\/li>\n<\/ul>\n<h2>Permissions + visibility<\/h2>\n<p>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:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-04-perm.png\" alt=\"Permissions team visibility CRM Odoo 19 PMI italiane access\" class=\"aligncenter size-full wp-image-3775\"\/><\/p>\n<ul>\n<li>Sales User: vedi own opp<\/li>\n<li>Sales User All: vedi all opp (limited)<\/li>\n<li>Sales Manager: full team<\/li>\n<li>Sales Manager All: cross-team<\/li>\n<li>Privacy enforced<\/li>\n<li>Audit log accessi<\/li>\n<\/ul>\n<h2>KPI per team dashboard<\/h2>\n<p>Ogni team ha proprio dashboard: pipeline, forecast, win rate, activity volume, quota attainment. Confronto cross-team possible per management. Healthy competition stimulated:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-05-kpi.png\" alt=\"KPI per team dashboard CRM Odoo 19 PMI italiane sales\" class=\"aligncenter size-full wp-image-3776\"\/><\/p>\n<ul>\n<li>Pipeline value team<\/li>\n<li>Forecast vs quota team<\/li>\n<li>Win rate trend<\/li>\n<li>Activity volume per rep<\/li>\n<li>Average deal size team<\/li>\n<li>Cycle time team<\/li>\n<li>Leaderboard cross-team<\/li>\n<\/ul>\n<h2>Team setup tipici per PMI italiana<\/h2>\n<h3>Small PMI (5-15 sales)<\/h3>\n<ul>\n<li>2 teams: Inbound + Outbound<\/li>\n<li>O: Italia + Estero<\/li>\n<li>Simple structure<\/li>\n<li>Manager unico<\/li>\n<\/ul>\n<h3>Mid PMI (15-50 sales)<\/h3>\n<ul>\n<li>3-5 teams: per region\/segment<\/li>\n<li>Dedicated managers<\/li>\n<li>SDR team separato<\/li>\n<li>Enterprise team se applicabile<\/li>\n<\/ul>\n<h3>Large PMI (50+ sales)<\/h3>\n<ul>\n<li>6-10 teams: multi-axis (geo + segment + product)<\/li>\n<li>Director level oversight<\/li>\n<li>Specialized roles<\/li>\n<li>Cross-team coordination council<\/li>\n<\/ul>\n<h2>Cross-team collaboration<\/h2>\n<h3>Account ownership rules<\/h3>\n<ul>\n<li>Single account = single team owner<\/li>\n<li>Multi-product opp visible cross-team<\/li>\n<li>Conflict resolution process<\/li>\n<li>Account splits documented<\/li>\n<\/ul>\n<h3>Inter-team referral<\/h3>\n<ul>\n<li>Cross-sell opportunity<\/li>\n<li>Commission split agreement<\/li>\n<li>Tracking referral source<\/li>\n<li>Recognition program<\/li>\n<\/ul>\n<h3>Knowledge sharing<\/h3>\n<ul>\n<li>Best practice documentation cross-team<\/li>\n<li>Win\/loss insights shared<\/li>\n<li>Battle cards per competitor<\/li>\n<li>Internal community<\/li>\n<\/ul>\n<h2>Compensation per team<\/h2>\n<h3>Quota assignment<\/h3>\n<ul>\n<li>Team quota aggregate<\/li>\n<li>Individual quota per rep<\/li>\n<li>Bottom-up vs top-down planning<\/li>\n<li>Adjustment per ramp\/new rep<\/li>\n<\/ul>\n<h3>Commission structure<\/h3>\n<ul>\n<li>Base salary + commission<\/li>\n<li>SPIFFs per push<\/li>\n<li>Accelerators sopra quota<\/li>\n<li>Team bonus per achievement<\/li>\n<\/ul>\n<h3>Territory protection<\/h3>\n<ul>\n<li>Lead generated in territory \u2192 commission to rep<\/li>\n<li>Cross-territory referral split<\/li>\n<li>Disputes process clear<\/li>\n<li>Annual territory review<\/li>\n<\/ul>\n<h2>Team rollout strategy<\/h2>\n<h3>Phase 1: Design (settimane 1-2)<\/h3>\n<ul>\n<li>Segmentation criteria<\/li>\n<li>Team structure draft<\/li>\n<li>Management review<\/li>\n<li>Stakeholder input<\/li>\n<\/ul>\n<h3>Phase 2: Setup (settimane 3-4)<\/h3>\n<ul>\n<li>Odoo team configuration<\/li>\n<li>Routing rules implementation<\/li>\n<li>Permission configuration<\/li>\n<li>Pilot team training<\/li>\n<\/ul>\n<h3>Phase 3: Launch (settimana 5)<\/h3>\n<ul>\n<li>Communication org-wide<\/li>\n<li>Migration opp esistenti<\/li>\n<li>Q&amp;A sessions<\/li>\n<li>Monitoring intensive<\/li>\n<\/ul>\n<h3>Phase 4: Iterate (mese 2+)<\/h3>\n<ul>\n<li>Feedback collection<\/li>\n<li>Rule refinement<\/li>\n<li>Dashboard tuning<\/li>\n<li>Process improvement<\/li>\n<\/ul>\n<h2>Errori comuni multi-team<\/h2>\n<h3>&#8220;Troppi teams&#8221;<\/h3>\n<p><strong>Problema<\/strong>: 20 team per 30 venditori, overhead.<br \/>\n<strong>Soluzione<\/strong>: 3-7 team massimo per PMI media.<\/p>\n<h3>&#8220;No routing rules&#8221;<\/h3>\n<p><strong>Problema<\/strong>: ogni lead routing manual, errori.<br \/>\n<strong>Soluzione<\/strong>: rules clear + auto-assignment.<\/p>\n<h3>&#8220;Conflict ownership&#8221;<\/h3>\n<p><strong>Problema<\/strong>: 2 team claim stesso account.<br \/>\n<strong>Soluzione<\/strong>: rules priority + escalation manager.<\/p>\n<h3>&#8220;No cross-team coordination&#8221;<\/h3>\n<p><strong>Problema<\/strong>: teams siloed, no synergy.<br \/>\n<strong>Soluzione<\/strong>: weekly cross-team sync + shared platform.<\/p>\n<h3>&#8220;KPI dashboard absent&#8221;<\/h3>\n<p><strong>Problema<\/strong>: team performance non visible cross-team.<br \/>\n<strong>Soluzione<\/strong>: dashboard per team + leaderboard.<\/p>\n<h2>Casi pratici PMI italiane<\/h2>\n<h3>Caso 1 \u2014 SaaS: 4 teams geografia<\/h3>\n<ul>\n<li>Italia + Iberia + DACH + UK<\/li>\n<li>Dedicated manager per team<\/li>\n<li>SDR team separato cross-region<\/li>\n<li>Quota: 1M \u20ac\/team\/quarter<\/li>\n<\/ul>\n<h3>Caso 2 \u2014 Manifattura: 3 teams segment<\/h3>\n<ul>\n<li>SMB \/ Mid-Market \/ Enterprise<\/li>\n<li>Different sales cycle per segment<\/li>\n<li>Specialized expertise<\/li>\n<li>Win rate +15 points<\/li>\n<\/ul>\n<h3>Caso 3 \u2014 Servizi: 2 teams hunting\/farming<\/h3>\n<ul>\n<li>New Business Team (hunting)<\/li>\n<li>Account Management Team (farming)<\/li>\n<li>Clear handoff process<\/li>\n<li>Customer success focus<\/li>\n<\/ul>\n<h3>Caso 4 \u2014 E-commerce B2B: 5 teams hybrid<\/h3>\n<ul>\n<li>Geography + product line<\/li>\n<li>Complex routing<\/li>\n<li>Cross-team collaboration<\/li>\n<li>Revenue +28% in 18 mesi<\/li>\n<\/ul>\n<h2>FAQ<\/h2>\n<h3>Quanti team massimo?<\/h3>\n<p>PMI sweet spot: 3-7 team. Pi\u00f9 di 10 = overhead coordination. Adjust per dimensione totale + complexity.<\/p>\n<h3>Posso cambiare team setup later?<\/h3>\n<p>S\u00ec, restructuring possible. Migration opp + history preserved. Plan rollout carefully (2-4 settimane tipico).<\/p>\n<h3>Team manager full-time?<\/h3>\n<p>Per team &gt; 6-8 rep: dedicated manager. Per piccoli team: player-manager hybrid. Coaching time critical.<\/p>\n<h3>Commission split tra team?<\/h3>\n<p>S\u00ec configurable. Esempio: hunter 80% \/ farmer 20% per cross-sell. Documented in compensation plan.<\/p>\n<h3>Reporting consolidate cross-team?<\/h3>\n<p>S\u00ec, executive view consolidate. Plus per-team drill-down. Best of both views.<\/p>\n<h2>Prossimi passi<\/h2>\n<p>Nella prossima guida (12\/15 serie CRM) vedremo <strong>lost reasons + sales analysis<\/strong>: structured lost reasons, win\/loss interview process, action plan per pattern, sales coaching basato su data.<\/p>\n<p style=\"margin-top:30px;background:#f4f4f8;padding:18px;border-radius:8px;\"><strong>Vuoi multi-team CRM nella tua PMI?<\/strong><br \/>\nG 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.<br \/>\n<a href=\"https:\/\/brentasoft.com\/preventivatore.php\"><strong>Richiedi un preventivo gratuito<\/strong><\/a> oppure prova la nostra <a href=\"https:\/\/odoo.brentasoft.com\/\">demo Odoo 19 live<\/a>. Oppure <a href=\"https:\/\/www.odoo.com?utm_campaign=partner-d192ce8a&amp;utm_source=partner_ref\" target=\"_blank\" rel=\"noopener noreferrer\">prova Odoo direttamente su odoo.com<\/a> (link partner Brentasoft).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ottantaquattresima guida Odoo 19, undicesima serie CRM: multi-team sales organization. Segmentation, territory, routing, permissions, KPI per team, casi pratici PMI.<\/p>\n","protected":false},"author":2,"featured_media":3772,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_titles_title":"Multi-team sales CRM Odoo: guida PMI","_seopress_titles_desc":"Multi-team sales organization CRM Odoo 19 per PMI italiane: territory, routing, permissions, KPI per team, casi pratici sales.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"https:\/\/brentasoft.com\/blog\/multi-team-sales-crm-odoo-19-pmi-italiane-guida-11\/","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"https:\/\/brentasoft.com\/blog\/wp-content\/uploads\/2026\/06\/odoo-tm-01-team.png","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","footnotes":""},"categories":[1,689],"tags":[],"class_list":["post-3777","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crm","category-guide-odoo"],"_links":{"self":[{"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/posts\/3777","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/comments?post=3777"}],"version-history":[{"count":1,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/posts\/3777\/revisions"}],"predecessor-version":[{"id":5974,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/posts\/3777\/revisions\/5974"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/media\/3772"}],"wp:attachment":[{"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/media?parent=3777"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/categories?post=3777"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/brentasoft.com\/blog\/wp-json\/wp\/v2\/tags?post=3777"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}