What teams actually ask Claude about their Odoo (real use cases by role)

Most people don’t use Claude on their Odoo to “chat with an AI” — they use it to skip a search, a filter, or a report they’d otherwise build by hand. A salesperson asks about their own pipeline. A warehouse lead asks what’s about to run out. A manager asks a question that spans three apps. An admin asks who touched what. Below are the real questions each role asks, what Cledoo MCP actually does to answer them, and where the answer runs out.

Sales & CRM

The Sales/CRM app already has structured pipeline stages — Odoo’s own documentation describes how opportunities move through configurable stages from new lead to won or lost. Claude doesn’t replace that view; it lets you query and act on it in one sentence instead of three clicks and a filter.

• "What deals in my pipeline haven't moved in two weeks?" — Claude calls search_records on crm.lead, filtered to the connected user’s own opportunities (that’s the record rule, not a Claude setting), and checks stage_id write dates.
• "Summarize the Dupont Industries deal — where does it stand?" — a get_record pull on the opportunity plus its linked activities and messages, turned into a paragraph instead of a scroll through the chatter.
• "Log a call with them: discussed pricing, they want a revised quote by Friday." — this is a write: Claude posts to the opportunity’s chatter (message_post) or creates an mail.activity. It only works if the connected user has edit rights on that record — same as if they typed it into Odoo themselves.
• "How many opportunities did my team create this month, by stage?" — an aggregate call grouping by stage_id, scoped to whatever team-level visibility the user’s role grants.

What it won’t do: invent a stage that doesn’t exist in your pipeline configuration, or show you a colleague’s deals if your record rules say you shouldn’t see them. It reads and writes through the same CRM structure Odoo already documents — it doesn’t get a side door.

Production & Inventory

Odoo’s replenishment logic is real math, not a Claude feature: reordering rules trigger a purchase or manufacturing order when forecasted stock falls below a configured minimum, per Odoo’s own documentation on reordering rules. Claude’s job here is to surface that state in plain language, and occasionally to help you look one layer deeper.

• "Which products are below their reordering minimum right now?" — Claude runs search_records on stock.warehouse.orderpoint (or product.product with a computed quantity filter) and lists what’s already below the Min your team configured — it’s reading the same trigger point Odoo’s reordering engine uses, not a separate AI-invented threshold.
• "What's blocking manufacturing order MO/00234?" — a get_record on the MO plus its component availability, so you’re not clicking through the production order and each stock move separately.
• "What components go into the BoM for our oak table, and which one is the long-lead item?" — Odoo’s BoM documents the exact components and quantities needed to produce an item; Claude reads that structure via get_record on mrp.bom and cross-references component stock, it doesn’t guess at what’s in the bill.
• "How many finished units can we build today with current stock?" — this is closer to Odoo’s own component availability check than a Claude calculation; Claude reads the numbers and states the constraint, it isn’t running a new MRP algorithm.

Honest limit: Claude reports what reordering rules and BoMs already say. If your minimums are wrong, or your BoM is outdated, the answer will be confidently wrong too — garbage in, garbage out, same as any report.

Leadership

This is the role where the value is least about any single app and most about not opening five of them. Claude can cross reference Sales, Inventory and Accounting in one answer because MCP tools aren’t siloed by app — they’re scoped by the manager’s own Odoo permissions across whatever models they can see.

• "Give me a one-paragraph view of where the business stands this quarter — pipeline, backlog, and cash." — several aggregate and count_records calls (CRM won/lost, sale.order backlog, account.move balances) stitched into one narrative. This is a live snapshot, not a dashboard someone maintains.
• "What's our gross margin per subsidiary this month?" — if the connected user’s rights span multiple companies in a multi-company Odoo, Claude aggregates revenue and cost of goods by company_id. If they don’t, the answer is scoped to what they can see, same as the Odoo UI would show them.
• "Which customers grew and which shrank compared to last quarter?" — a comparison built from two aggregate calls on sale.order grouped by partner_id, not a forecasting model — it’s arithmetic on real orders.
• "Draft a two-line summary I can send the board." — Claude can write the summary; whether it emails or posts it anywhere is still an explicit, reviewable action, not something that happens silently.

Where it stops: Claude does not build you a maintained dashboard. It answers the question you asked, once, from live data. If you want the same view every Monday, that’s a saved report or a scheduled export — a different tool for a different job.

IT & Admin

Admin questions tend to be about the system itself, and they’re often the ones people forget to check until something’s wrong.

• "Which users haven't logged in for 90 days?" — search_records on res.users filtered on login_date, useful before a license renewal or a security review.
• "Export the AI access log for the last 30 days — who asked what, and what did Claude read or change?" — this is where the free tier and Cledoo MCP Pro diverge. The base module gives you accurate access (every call runs through Odoo’s real permissions); Pro adds the audit trail itself — who connected, which tool ran, on which records — plus data privacy masking and confirm-before-write for risky actions. If audit is what you need, that’s the Pro layer, not something the free 17 tools log for you today.
• "List all the custom fields on the Contact model and who added them." — get_model_fields, useful for cleanup before an upgrade.
• "Which groups have delete rights on Invoices?" — Claude reads Odoo’s own access rules and reports them; it doesn’t change them unless you explicitly ask it to, and even then only if the connected admin account actually has that right.

What this doesn’t replace

None of the above is Claude doing something Odoo couldn’t already do — it’s Claude doing it in one sentence instead of a filter, a report builder, or a support ticket to “someone who knows the CRM view.” The boundary that keeps this honest is the same one across every role: Claude reads and writes as the connected user, in their scope, through Odoo’s own rules. It shines at questions over live data phrased in plain language. It does not replace a maintained dashboard, doesn’t override anyone’s access rights, and won’t notice a wrong reordering minimum or a stale BoM was wrong to begin with.

The takeaway

The pattern across every role is the same: turn a multi-click lookup, a “can someone check,” or a scattered report into one sentence — answered from live Odoo data, under the asker’s own permissions. That’s a narrower promise than “AI runs your ERP,” and it’s the one that actually holds up when you use it every day.