Sales teams lose hours retyping company names, sizes, industries and LinkedIn URLs that a lead's email domain already implies. Odoo's native crm.lead captures whatever the web form or import gives you and stops there — the built-in "Enrich Company" and "Autocomplete" features route through Odoo IAP, which bills per credit, locks the data source to Odoo's partner, and leaves nothing in your control when credits run dry. For a high-volume B2B pipeline that quickly becomes an unpredictable line item, and it can't be pointed at the enrichment provider you already pay for. That is exactly the gap this build-to-order module fills.

ECOSIRE builds a self-hosted enrichment engine that extends crm.lead (and optionally res.partner) with a structured firmographic layer: parsed email domain, legal company name, employee-count band, industry/NAICS-style classification, HQ country and city, revenue band, technology hints, and social handles (LinkedIn, X, Facebook). New fields are declared on a proper models.Model inheritance layer with @api.depends('email_from') compute triggers so a domain change re-derives what it can, while append-only fields stay editable. Every write is scoped by ir.model.access.csv plus record rules so enriched data respects your existing CRM visibility, and all enrichment activity is logged to a companion model for audit and re-run.

Technically, the append logic is provider-pluggable. We implement a thin adapter interface — a Python abstract layer with one concrete adapter per source (Clearbit-style REST, self-hosted domain-WHOIS, your existing data vendor, or an internal MMDB/CSV) — so you are never welded to one vendor's pricing. An ir.cron automated action sweeps freshly created leads on a schedule and enriches them in batches with rate-limit and back-off handling; a manual server action lets a rep enrich one record on demand from the form view; and a bulk action on the list view re-enriches historical leads without re-importing. Calls are resilient by design: cached per domain (so 40 leads at acme.com cost one lookup), retried on transient failure, and never block the salesperson — enrichment runs post-commit, so the lead saves instantly and fills in seconds later.

Because it exposes clean fields on crm.lead, everything downstream just works: filter and group your pipeline kanban by employee band or industry, drive routing/assignment rules off firmographics, feed QWeb reports and Odoo dashboards, and query the enriched attributes over the standard XML-RPC/JSON-RPC API for your data warehouse. It targets Odoo 17.0, 18.0 and 19.0 and works on both Community and Enterprise — no Enterprise-only dependency, and no reliance on the paid IAP autocomplete.

Delivery is build-to-order: nothing here is an instant apps.odoo.com download. After a short scoping call we confirm your Odoo version, edition, hosting, and which enrichment provider(s) you want wired in, then build against that exact target. Typical delivery is one working week from confirmed scope. You get the installable source, UAT on a staging copy of your database, a documented rollback path, and a post-go-live support window — and you own the Git repository at handover.