Odoo CRM Pipeline Configuration Problems
A pipeline works when its stages mirror decisions the customer makes, not tasks your team does. Stages like "Follow-up 1 / Follow-up 2" tell you nothing; stages like "Requirement confirmed / Quote approved / PO awaited" make every kanban column a forecast. Configure stages around the buyer, keep activities mandatory, and the pipeline starts predicting.
First, confirm the symptom
- Deals live in one giant stage; the columns mean nothing
- Expected revenue wildly overstates what actually closes
- Every team fights the same stage names meant for another team
- Management reads reports, sales ignores them
1. Stages describe your tasks, not the buyer's journey
"Called / Emailed / Following up" are activities, not stages. When stage = activity, cards never move and the kanban rots.
- Rewrite stages as buyer milestones: New → Qualified → Requirement mapped → Quote sent → Negotiation → Won (tune to your motion).
- Define entry criteria per stage in one line each — and put it in the stage description so everyone moves cards the same way.
2. One pipeline forced on every team
Spares counter sales and project sales do not share a journey. One-size stages fit no one, so each team invents shadow processes in Excel.
- Separate sales teams with team-specific stages where the motion truly differs.
- Keep shared reporting via tags/sources rather than forcing shared stages.
3. Probabilities that mean nothing
Default or hand-tweaked probabilities produce expected revenue no one believes — then no one uses the forecast at all.
- Either commit to stage-based probabilities reviewed quarterly against actual win rates, or turn on Odoo's predictive scoring and let history speak.
- Forecast from a filtered view (this quarter, committed stages) — not the whole pipe.
4. Cards without a next activity
A deal without a scheduled next step is a deal drifting. The kanban shows it — the little clock icon — if you enforce it.
- Team rule: no card without a next activity; the "no activity" filter is the manager's daily view.
- Automate first activities on lead creation (see assignment guide).
5. Reports measuring the wrong thing
Reading "Expected Revenue" as commitment, ignoring stage-age, and never analysing lost reasons turns CRM reporting into decoration.
- Watch three numbers weekly: new qualified value, win rate by stage, and average days-in-stage (deals stuck > X days get reviewed).
- Make Lost Reason mandatory — six months of honest lost data is a strategy document.
We redesign stages around your real sales motion, wire activity discipline and build the three-number weekly dashboard — then coach the team through the first month.
Frequently asked questions
How many stages should a pipeline have?
Five to seven. Fewer hides progress; more creates stage-splitting debates. Each stage must map to a buyer decision you can verify.
Can we restructure stages without losing existing deals?
Yes — existing opportunities are remapped to new stages in bulk. We plan the mapping before touching anything.