Most sales managers running Odoo can see where an opportunity sits today, but not how it got there or how long it has been rotting in a stage. Odoo core stores only the current stage_id on crm.lead, and while the kanban tracks date_last_stage_update, it silently overwrites on every move — so the history of who moved what, when, and how long each stage actually took is lost. The mail.thread chatter logs stage changes as free-text messages, but you cannot report, filter, or sum durations from a chatter feed. The result: no reliable answer to "which deals have been stuck in Proposal for over 21 days?", no per-stage cycle-time analysis, and no early warning when pipeline goes stale.

We build a dedicated Odoo module that captures a durable, queryable stage-transition ledger and turns it into pipeline-aging intelligence. A new model (e.g. crm.stage.history) records one immutable row per stage change — lead_id, stage_from, stage_to, user_id, date_entered, date_left, and a stored computed duration_hours — written from an override of write() on crm.lead (and via an automated action / base automation fallback so bulk kanban drags and RPC updates are also captured). On crm.lead itself we add stored, indexed compute fields via @api.depends: days_in_current_stage, total_pipeline_age, is_stuck (a boolean driven by a configurable per-stage aging threshold you set on crm.stage), and last_stage_change. Because the aging fields are stored and indexed, they filter and group fast even on tens of thousands of leads, and a scheduled action (ir.cron) recomputes "stuck" flags nightly and can trigger the notifications you want.

On top of that data we build the reporting and UX: a crm.stage.history list/pivot/graph view for cycle-time analysis (average days per stage, per salesperson, per team), kanban and list decorations that visually flag stuck deals, a "Pipeline Aging" filterable dashboard, and a QWeb PDF aging report you can schedule or export. Security is done properly — ir.model.access.csv for the new model plus record rules so salespeople see only their own history while managers see the team's, matching your existing CRM access model. Everything is exposed over the standard XML-RPC/JSON-RPC API so BI tools or app.ecosire.com mirrors can read the aging data. The module targets Odoo 17.0, 18.0, and 19.0, works on both Community and Enterprise (Enterprise-only niceties like dashboard studio widgets are used only where present, with a Community-safe view fallback), and ships with a clean __manifest__.py declaring dependencies on crm alone so it drops into any CRM install.

Because this is build-to-order, nothing is downloaded from a marketplace — ECOSIRE scopes it to your stages, thresholds, and reporting needs on a short call, then builds, tests on a staging copy of your database, and installs it. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company pipelines, historical back-fill of stage durations from existing chatter/audit data, deeper BI or external-dashboard integrations, and heavier data-migration volume increase the quoted scope. You get a fixed quote after the scoping call, not a surprise invoice.