Lost reasons + sales analysis CRM Odoo: coaching data-driven (guida 12 di 15)

Ottantacinquesima guida operativa Odoo 19 per PMI italiane. Dodicesima della serie 15 guide CRM Odoo. “Perché abbiamo perso?” è la domanda più produttiva in sales. Una opp lost ben analizzata = lesson learned. 100 opp lost senza analysis = 100 errori ripetuti. Lost reasons strutturati in Odoo + win/loss interview disciplinato + action plan basato su pattern = cycle improvement continuativo. In questa guida vediamo come implementare sales analysis disciplinato nella PMI italiana.

Vediamo: structured lost reasons, win/loss interview process, pattern analysis, coaching basato su data, action plan per top issues, casi pratici PMI italiane.

Lost reasons setup

Configuration

• CRM → Configuration → Lost Reasons
• Crea list standard
• Mandatory al “Mark Lost”
• Comment field aggiuntivo
• Audit trail mantenuto

Lost reasons essenziali

• Price too high: pricing issue
• Competitor X chosen: lost to specific
• Project cancelled: customer-side change
• Timing not right: budget/season
• Wrong fit: qualification issue
• No decision maker engaged: process issue
• Status quo bias: change resistance
• Features missing: product gap

Pipeline analysis con lost dimension

Grouping pipeline per lost reason permette analysis aggregate. Pareto chart per top reasons. Trend over time. Identification problem areas. Foundation per process improvement:

• Group by lost reason
• Pareto: top 5 spesso 80% lost
• Trend mensile
• Per segment/team analysis
• Drill-down su opp specific
• Export per board review

Mark Lost workflow

Quando opp è persa, mandatory selezionare reason + commentare. Sales spesso tentati di “Lost” generico — discipline mandatory campo dettaglio. Quality dei lost data = quality dei learning:

• Button “Mark Lost”
• Reason mandatory
• Comment 1-2 sentence
• Next steps optional
• Notification manager
• Status changed + archived
• Stay accessible per analysis

Lost reasons categorization

Pricing-related

• Price too high (absolute)
• Better deal from competitor
• Budget cuts
• Payment terms unacceptable

Product-related

• Missing features
• Performance concerns
• Integration issues
• Support concerns

Process-related

• Slow response
• Poor communication
• Demo unconvincing
• Proposal weak

Customer-related

• Project cancelled
• Timing wrong
• Decision maker changed
• Organizational shift

Competitive

• Specific competitor named
• Incumbent retained
• Lower-tier solution chosen

Lost reason analysis dashboard

Dashboard dedicato: top 5 reasons per quarter, trend monthly, per team analysis, per segment, per product. Pattern detection fa la differenza. Action items emerge:

• Top 5 reasons quarter
• Trend monthly comparison
• Per team breakdown
• Per segment analysis
• Per product lineup
• Average lost deal value
• Time-in-pipeline before lost

Win/Loss interview process

Quando fare

• Deal > threshold (es. 50k €)
• Strategic account lost
• Competitive replacement
• New market entry attempt

Chi conduce

• NON il sales venditore (bias)
• Sales Manager o external consultant
• Customer feedback honest
• 15-30 minute call

Domande chiave

• “Quali sono stati i 3 fattori principali decisione?”
• “Cosa avremmo dovuto fare diversamente?”
• “Come è stato il process interno decisione?”
• “Chi è stato decisive?”
• “Cosa ha fatto difference competitor?”
• “Saremmo considerati again per altri progetti?”

Documentation

• Recording (con consenso)
• Notes structured
• Insights database
• Share with team

Sales analysis aggregata

Combined analysis: lost reasons + win reasons + activity patterns + cycle time. Holistic view. Pattern emerge da combinazione: cosa funziona, cosa no. Action plan informed:

• Win patterns common
• Loss patterns common
• Activity per outcome
• Cycle time per win/loss
• Champion presence correlation
• Discount impact analysis
• Stage drop-off analysis

Pattern recognition

Pricing-driven losses

• Significantly higher % losses on price
• Action: pricing strategy review
• Action: value proposition strengthening
• Action: discount approval tier

Process-driven losses

• Slow response, unclear next steps
• Action: SLA response time
• Action: cadence enforcement
• Action: training process

Product-driven losses

• Missing feature mentioned repeatedly
• Action: product roadmap feedback
• Action: positioning adjustment
• Action: workaround documentation

Competitive losses

• Specific competitor winning
• Action: battle card update
• Action: feature gap closing
• Action: pricing competitive analysis

Coaching basato su data

1:1 weekly tra Sales Manager e venditore. Review losses last week, identify pattern, agree action. Non blame culture, learning culture. Data-driven specific feedback molto più potente di generic advice:

• Weekly 1:1 manager-rep
• Loss review specific
• Pattern identification
• Skill gap analysis
• Action plan documented
• Progress tracked weekly
• Improvement measured

Coaching framework GROW

• Goal: cosa miglioriamo
• Reality: cosa è successo
• Options: cosa potresti fare diversamente
• Will: cosa farai prossima volta

Action plan per top issues

Quarterly review

• Top 3 lost reasons aggregate
• Cost of these losses
• Root cause analysis
• Action plan formal

Cross-functional involvement

• Product: feature requests
• Marketing: messaging adjustment
• Pricing: review competitive
• Customer Success: testimonial

Initiative tracking

• Each action with owner + deadline
• Review monthly
• Impact measurement
• Iterate

Errori comuni lost analysis

“No mandatory reason”

Problema: lost reason vacuo, no learning.
Soluzione: mandatory + comment minimum.

“Lost reason vague”

Problema: “Other” usato per 60% losses.
Soluzione: granular categories + review quarterly.

“No win/loss interview”

Problema: sales perspective only, biased.
Soluzione: customer interview per strategic losses.

“Blame culture”

Problema: lost = sales fault, no improvement.
Soluzione: learning culture + cross-functional accountability.

“No action from analysis”

Problema: analysis fatta, nothing changes.
Soluzione: quarterly action plan formal + tracking.

Casi pratici PMI italiane

Caso 1 — SaaS: pricing-driven action

• 40% losses on price
• Revision pricing strategy
• Value-based pricing introduced
• Lost-on-price: -25 points in 12 mesi

Caso 2 — Manifattura: product gap closing

• Missing feature X in 30% losses
• Roadmap accelerated
• Feature released Q2
• Win rate: +18 points

Caso 3 — Servizi: process improvement

• Slow response identified
• SLA 24h implemented
• Cadence enforced
• Conversion +22%

Caso 4 — E-commerce B2B: competitive battle

• Specific competitor dominant
• Battle cards developed
• Training on objection handling
• Win rate vs competitor: +25 points

FAQ

Quanti lost reasons configurare?

Sweet spot 8-15. Sotto: too coarse. Sopra: usage drops. Review quarterly + consolidate similar.

Win/loss interview frequenza?

Strategic deals: always. Significant deals: 50%+. Routine: sample 10-20%. Cost vs insight ratio.

Posso chiedere customer feedback after loss?

Sì, sempre con professionalism. Most willing to share. Insight valuable. Maintain relationship per future.

Lost reason per opp old?

Historical data can be re-categorized se needed. Audit trail maintained. Important per trend long-term.

Coaching cadence?

Weekly 1:1 tipico. Daily standup quick. Monthly deep dive. Adjust per rep maturity + outcome.

Prossimi passi

Nella prossima guida (13/15 serie CRM) vedremo mobile app CRM: setup mobile, capabilities, voice notes, offline mode, productivity hacks field sales.

Vuoi sales analysis nella tua PMI?
G Tech Group implementa lost reason + sales analysis CRM Odoo per PMI italiane: structured reasons, win/loss process, pattern recognition, coaching data-driven. Track record di win rate +15-25 points in 12 mesi.
Richiedi un preventivo gratuito oppure prova la nostra demo Odoo 19 live. Oppure prova Odoo direttamente su odoo.com (link partner Brentasoft).