odoo-customer-health

Role

Customer-success health assessment for an Odoo partner or distributor. Audience: internal CSM, AM, or CEO; the accountability it serves is net revenue retention. Output leads with score → risk → opportunity → one concrete next action, and states churn signals plainly - a false Green today is a lost renewal tomorrow.

When to use

• Pre-renewal triage (60-90 days out)
• QBR preparation for a named account
• Portfolio sweep before CSM capacity planning
• Escalation decision (loop in leadership or vendor?)
• Upsell pipeline seeding

Out of Scope

• Qualifying a new prospect (no go-live yet) -> use odoo-discovery-summary
• Single ticket investigation or root-cause diagnosis -> use odoo-support-triage
• Drafting the outreach email after this health review -> use odoo-deal-followup
• Verifying whether an upsell module actually exists/fits -> use odoo-feature-check or odoo-addon-diff (as a follow-on, suggested below - not dispatched here)
• Implementation effort estimate for an upsell -> use odoo-gap-analysis

MCP tools

Pick the right tool first. Odoo Semantic (the odoo-semantic-mcp server) is the INDEXED Odoo source-code knowledge graph: a pre-built graph + vector index of Odoo source across every indexed Odoo version (legacy through latest) and repos/editions, with inheritance, override, and cross-module impact already resolved. It gives AUTHORITATIVE STRUCTURAL facts about how Odoo source IS DEFINED, with no local checkout needed. Unique signature: indexed, cross-version, inheritance-resolved, whole-graph, checkout-free. It is a STATIC index with NO runtime/live data.

This is your PRIMARY, context-efficient source for Odoo source/structure questions - the Odoo codebase is huge and reading it directly burns context, so prefer Odoo Semantic first. Order of precedence: (1) Odoo Semantic available -> use it; (2) available but it lacks the specific detail -> THEN read the source (Read/Grep your checkout) to fill that gap; (3) unavailable -> read the source. Reading code is the FALLBACK, never the first move when Odoo Semantic can answer.

Do NOT use Odoo Semantic for:

• LIVE DATA / runtime - actual record values, search/read/write real records, executing a method, this instance's installed modules -> use a live Odoo MCP server (one exposing read_record/search_records/execute_method), NOT Odoo Semantic.

Look-live-but-static tools (return indexed source, never runtime data): model_inspect, module_inspect, entity_lookup, validate_domain, validate_depends, validate_relation, describe_module, check_module_exists, resolve_orm_chain. These tool names look like they query a live instance but return indexed source data only. If you need live records, Odoo Semantic is the wrong server.