Odoo 19 CRM Pipeline Optimization:
Lead Scoring, Assignment Rules & Predictive Close Dates

Predictive Lead Scoring: Let the Data Pick Your Best Opportunities

Odoo 19's CRM module includes a predictive lead scoring engine that analyzes historical win/loss data to score incoming leads. Instead of salespeople guessing which leads are worth pursuing, the system assigns a probability score between 0 and 100 based on patterns from your closed deals.

How the Scoring Model Works

The predictive scoring engine lives in the crm module and uses a frequency-based approach. It examines the fields on your won and lost opportunities—country, industry, source, team, tags, email domain—and calculates which field values correlate with wins. The model is rebuilt daily by a scheduled action (ir.cron).

# Navigate to:
# CRM > Configuration > Settings > Predictive Lead Scoring

# Enable "Predictive Lead Scoring"
# Set the date range for training data:
#   - Start Date: 12-24 months back (need enough closed deals)
#   - Minimum deals for statistical significance: 200+ recommended

# Select scoring fields (the model analyzes these):
#   - Country
#   - State
#   - Industry (via partner tag or custom field)
#   - Email domain (free vs corporate)
#   - Source (website, referral, campaign)
#   - Sales Team
#   - Language

Adding Custom Fields to the Scoring Model

The default scoring fields cover basic demographics. For B2B pipelines, you often need to score on company size, annual revenue, or technology stack. You can register custom fields with the scoring engine:

from odoo import fields, models


class CrmLead(models.Model):
    _inherit = "crm.lead"

    x_company_size = fields.Selection(
        selection=[
            ("1-10", "1-10 employees"),
            ("11-50", "11-50 employees"),
            ("51-200", "51-200 employees"),
            ("201-1000", "201-1000 employees"),
            ("1000+", "1000+ employees"),
        ],
        string="Company Size",
    )
    x_annual_revenue = fields.Selection(
        selection=[
            ("under_1m", "Under $1M"),
            ("1m_10m", "$1M - $10M"),
            ("10m_50m", "$10M - $50M"),
            ("over_50m", "Over $50M"),
        ],
        string="Annual Revenue Range",
    )


class CrmLeadScoringFrequency(models.Model):
    _inherit = "crm.lead.scoring.frequency"

    # Register custom fields with the scoring engine
    x_company_size = fields.Float(string="Company Size Frequency")
    x_annual_revenue = fields.Float(string="Annual Revenue Frequency")

Understanding the Probability Calculation

The scoring model calculates probability using Bayesian frequency analysis. For each scoring field, it computes:

# For each field value (e.g., country = "United States"):
won_count  = deals WON where country = "United States"
lost_count = deals LOST where country = "United States"
total      = won_count + lost_count

field_score = won_count / total   # e.g., 0.72

# Final probability = weighted combination of all field scores
# adjusted by stage probability (each stage has a base %)

# Example:
#   Country score:    0.72
#   Industry score:   0.85
#   Source score:     0.40
#   Stage base prob:  0.50
#
#   Combined = stage_base * (country * industry * source)
#            = 0.50 * (0.72 * 0.85 * 0.40)
#            = 0.50 * 0.2448 = 0.1224 ... (normalized)

Predictive Close Dates: Replacing Gut-Feel Forecasts with Data-Driven Estimates

Sales forecasting in most organizations is a weekly ritual of fiction. Reps enter close dates based on when they hope the deal will close, not when the data suggests it will. Managers override those dates in the forecast meeting. Finance takes the pipeline total and applies a 40% haircut because they've learned not to trust it.

Odoo 19's predictive close date model solves this by analyzing historical stage durations for deals with similar characteristics. Instead of asking the rep "when will this close?", the system calculates "based on deals like this, the expected close date is X."

How the Predictive Model Works

The prediction engine tracks every stage transition timestamp on crm.lead. When a lead moves from Qualified to Demo, the system records the transition date. Over hundreds of deals, it builds a distribution of how long deals spend in each stage, segmented by scoring fields (country, source, team, deal size).

# For a lead currently in "Proposal Sent" stage:

# Step 1: Find similar historical deals
similar_deals = deals WHERE:
    country       = lead.country
    source        = lead.source
    revenue_range = lead.expected_revenue bucket
    stage_reached = "Proposal Sent" or later

# Step 2: Calculate median remaining days
remaining_stages = ["Negotiation", "Won"]
for stage in remaining_stages:
    median_days[stage] = median(
        similar_deals.stage_duration[stage]
    )

# Step 3: Sum remaining stage durations
predicted_remaining = sum(median_days.values())

# Step 4: Set predicted close date
predicted_close = today + timedelta(days=predicted_remaining)

# Example output:
#   Proposal Sent → Negotiation: median 8 days
#   Negotiation → Won: median 12 days
#   Predicted close: today + 20 days

Surfacing Predictions in the Pipeline View

By default, the predicted close date is available on the lead form. To make it visible in the Kanban and list views, add it via a view inheritance:

<odoo>
  <!-- Add predicted close date to Kanban card -->
  <record id="crm_lead_kanban_predicted"
          model="ir.ui.view">
    <field name="name">crm.lead.kanban.predicted</field>
    <field name="model">crm.lead</field>
    <field name="inherit_id"
           ref="crm.crm_case_kanban_view_leads"/>
    <field name="arch" type="xml">
      <xpath expr="//field[@name='expected_revenue']/.."
             position="after">
        <div class="d-flex align-items-center gap-1 mt-1">
          <i class="fa fa-calendar-check-o text-muted"
             title="Predicted Close"/>
          <field name="date_deadline"
                 widget="remaining_days"/>
        </div>
      </xpath>
    </field>
  </record>

  <!-- Add to list/tree view -->
  <record id="crm_lead_tree_predicted"
          model="ir.ui.view">
    <field name="name">crm.lead.tree.predicted</field>
    <field name="model">crm.lead</field>
    <field name="inherit_id"
           ref="crm.crm_case_tree_view_leads"/>
    <field name="arch" type="xml">
      <xpath expr="//field[@name='date_deadline']"
             position="attributes">
        <attribute name="widget">remaining_days</attribute>
        <attribute name="optional">show</attribute>
      </xpath>
    </field>
  </record>
</odoo>

Email Integration: Connecting Your Inbox to the CRM Pipeline

A CRM that lives outside the inbox is a CRM that gets ignored. Reps spend 60% of their day in email. If updating Odoo requires switching tabs, copying text, and manually logging activities, adoption collapses within weeks. Odoo 19 provides multiple email integration paths that keep CRM data current without forcing reps to change their workflow.

Catchall Email Alias for Lead Creation

Configure a catchall email alias so incoming emails automatically create leads:

# Navigate to:
# CRM > Configuration > Sales Teams > [Your Team]

# Set the Email Alias:
#   Alias: sales@yourcompany.com
#   Accept Emails From: Everyone (for inbound leads)
#                     or Authenticated Partners (for existing contacts)

# How it works:
# 1. Customer emails sales@yourcompany.com
# 2. Odoo fetchmail service picks up the email
# 3. A new crm.lead is created with:
#    - contact_name = sender name
#    - email_from = sender email
#    - description = email body
#    - message_ids = the full email thread
# 4. Assignment rules kick in (if enabled)
# 5. Rep receives notification of new lead

Outgoing Email Tracking and Activity Logging

class CrmLead(models.Model):
    _inherit = "crm.lead"

    def _track_email_activity(self, message):
        """Auto-create a 'follow-up' activity when an
        outbound email is sent from the opportunity."""
        if message.message_type == "email" and \
           message.author_id == self.env.user.partner_id:
            # Schedule a follow-up activity 3 days out
            self.activity_schedule(
                "mail.mail_activity_data_todo",
                date_deadline=fields.Date.add(
                    fields.Date.today(), days=3
                ),
                summary="Follow up on email sent",
                note=f"Auto-created after sending: "
                     f"{{message.subject}}",
            )

Two-Way Sync with Outlook and Gmail

Odoo 19 supports native integrations with both Microsoft Outlook (via Microsoft 365 OAuth) and Gmail (via Google Workspace OAuth). These integrations enable:

• Calendar sync — Meetings scheduled in Outlook/Gmail appear as CRM activities on the linked opportunity. No double-entry.
• Contact sync — New contacts added in the email client are pushed to Odoo's res.partner model. Duplicates are matched by email domain.
• Email logging — The Odoo plugin for Outlook/Gmail lets reps log emails to specific opportunities with one click. The email thread appears in the chatter on the CRM lead.
• Lead creation from inbox — Reps can create a new lead directly from an email in their inbox using the browser plugin, pre-populating the lead with sender info and email content.