Agentic AI Is Coming to Your CRM and ERP This Month: What Dreamforce 2026 and Odoo 20 Mean for Growing Businesses
September 2026 is the busiest month the CRM and ERP world has seen in years. Salesforce hosts Dreamforce in San Francisco from September 15–17, built entirely around what it now calls the "Agentic Enterprise." One week later, Odoo unveils Odoo 20 at Odoo Experience in Brussels (September 24–26), with autonomous AI agents as the headline feature.
Two platforms. Two conferences. One message: the software is no longer waiting for your team to click buttons. It is starting to act on its own.
If you run a growing business anywhere in the world, you will hear a lot of noise about this over the next few weeks. This guide cuts through it — what is actually shipping, what is still on a roadmap, and what a manufacturer in Ohio, a distributor in Dubai or a services firm in Manchester should actually do about it.
First, What Does "Agentic" Actually Mean?
For the last two years, AI in business software mostly meant assistants: a chatbot that drafts an email, summarizes a call, or answers a question about your data. Useful, but you still did the work.
An AI agent is different. It is given a goal, a set of permissions, and access to your business data — and it completes multi-step tasks without a human driving each step. Think:
- A sales agent that researches accounts overnight, ranks them, drafts outreach, and books meetings for your reps.
- A service agent that resolves a customer's issue end-to-end — checks the order, issues the credit, schedules the visit — rather than handing it to a human.
- A finance agent that runs audit checks across your ledger, flags anomalies, and summarizes what needs attention.
Both Salesforce and Odoo are betting their next release cycle on exactly this shift. Here's what each is bringing.
What Salesforce Is Shipping: The Agentic Enterprise
Salesforce has spent nearly two years and a great deal of money on Agentforce. Dreamforce 2026 is where the company has to prove it works at scale — and the pre-conference announcements suggest it is pushing hard.
What's confirmed for September 2026:
- New Agentforce editions. On September 3, Salesforce announced simplified Core, Advanced and Max editions for Agentforce Sales, Service and Industries. Each bundles Slack, Tableau Next analytics, premier support and role-specific AI into a single purchase — a clear signal that AI agents are now the default, not an add-on.
- Agentforce Help Agent with pay-per-resolution pricing. Generally available since July, this service agent grounds itself on your Salesforce Knowledge base, takes real actions (managing cases, scheduling, updating orders) and charges only when it resolves an issue.
- Prospecting Agent with plain-English configuration. Admins can now describe their ideal customer profile in natural language and let the agent research, rank and reach out — no complex rule-building.
- Data 360 and Tableau MCP. The plumbing that lets agents query your analytics directly, with a Trust Layer governing what they can see and do.
The adoption numbers back the momentum: Salesforce reported Agentforce annual recurring revenue above $1.5 billion in its latest quarter, up more than 240% year on year.
What this means for you: If you already run Sales Cloud or Service Cloud, agentic capability is coming to your org whether you plan for it or not. The question is whether your data, workflows and governance are ready to let an agent act — or whether it will simply automate your existing mess faster.
What Odoo Is Shipping: Odoo 20 and the Native AI Layer
Odoo's approach is characteristically different — less marketing, more engineering, and priced for SMEs rather than enterprises.
Odoo has been building toward this for three versions: content generation in v17, practical utility (OCR, invoice automation) in v18, and a full AI infrastructure layer with agents and "Ask Odoo" natural-language search in v19. Odoo 20 is where those pieces become autonomous.
What the Odoo 20 roadmap (presented at Partner Days, April 2026) points to:
- Agentic AI across modules — agents that can autonomously create purchase orders, build projects from a PDF design document, and chain multi-step tasks across apps.
- A native MCP server for Enterprise users — meaning any external AI assistant can connect directly to your Odoo database without a middleware layer. This is a big deal for integration architecture.
- AI accounting audit — treasury and financing checks that flag anomalies and explain them in plain language for non-finance users.
- Natural-language database search — ask for "the latest PO from that supplier" or "summarize this week's helpdesk complaints" and get an answer.
- A rebuilt mobile interface and simplified payroll dashboard.
One honest caveat: Odoo itself jokingly calls its roadmap "a list of things we will maybe do." The official feature set is confirmed only at launch, and the first stable, production-ready patch typically arrives in October or November. Experienced partners recommend planning your upgrade for the window between November 2026 and January 2027 — not launch week.
What this means for you: If you are starting a new Odoo implementation this quarter, Odoo 19 remains the safe, mature choice with a planned upgrade to 20 in early 2027. If your project kicks off in late autumn, you may be able to go straight to 20.
Salesforce vs Odoo on Agentic AI: Where Each One Wins
| Primary strength |
Customer-facing agents: sales, service, marketing, commerce |
Operations agents: accounting, purchasing, projects, inventory |
| Maturity (Sept 2026) |
Generally available, $1.5B+ ARR, enterprise-proven |
Unveiled this month; stable release Oct–Nov |
| Pricing model |
Edition bundles; pay-per-resolution for service |
Included in Enterprise subscription; SME-friendly |
| Integration approach |
Data 360, Trust Layer, MCP for Tableau |
Native MCP server; open-source foundation |
| Best fit |
Businesses where revenue and customer experience are the bottleneck |
Businesses where back-office friction is the bottleneck |
For most growing businesses, the answer is not one or the other. It is Salesforce agents handling the front office, Odoo agents handling the back office, and clean, governed data flowing between them.
The Uncomfortable Truth: Agents Are Only as Good as Your Data
This is the part vendor keynotes gloss over.
An AI agent that autonomously raises purchase orders is powerful inside a supply chain with consistent SKU data and mapped reorder rules. It is dangerous inside a database that has accumulated five years of duplicate product records, inconsistent customer names and half-finished workflows. Salesforce's own product team has said messy data is the single biggest reason agents fail.
Before any agentic rollout — on either platform — the businesses that succeed will have done four things:
- Cleaned and deduplicated master data — customers, products, vendors, chart of accounts.
- Documented existing customizations — so agents don't break, and upgrades don't stall.
- Defined what an agent is allowed to do — spending limits, approval thresholds, escalation paths.
- Mapped their highest-friction workflows — because that's where agents pay back fastest.
Organizations that started this readiness work in Q2 will hit the ground running in Q4. Those that wait for the keynote will spend the next two quarters catching up.
A Practical 90-Day Plan for Any Growing Business
September — Assess. Audit your current Salesforce org or Odoo instance. Identify data quality issues and undocumented customizations. Watch Dreamforce and Odoo Experience with a specific question: which one announced capability would remove our biggest daily bottleneck?
October — Prepare. Clean master data. Define agent governance rules. If on Odoo, wait for the first stable 20.x patch and test in a sandbox. If on Salesforce, pilot one agent (Help Agent or Prospecting Agent) in a low-risk team.
November–December — Pilot and measure. Run one agent in production with clear success metrics — resolution rate, response time, hours saved. Decide on Odoo 20 upgrade timing. Plan the Salesforce–Odoo integration if you run both.
Why This Matters Most for the Mid-Market
Enterprises have data teams, governance boards and budgets to absorb a failed pilot. The global mid-market does not. A manufacturer in the Midwest, a distributor in the Gulf, a healthcare group in Southeast Asia or a professional-services firm in Europe typically shares the same profile: the business grew faster than its systems. Sales in one tool, inventory in another, accounts in a third, and email or WhatsApp holding it all together.
Agentic AI does not fix disconnected systems. It amplifies whatever you already have. Businesses that consolidate onto a well-implemented Salesforce and Odoo foundation now will be the ones whose agents actually deliver in 2027. The rest will be automating chaos.
Frequently Asked Questions
1. Do I need to upgrade to Odoo 20 immediately when it launches? No. Odoo's first stable patch usually lands one to two months after Odoo Experience. Most partners recommend upgrading between November 2026 and January 2027, after a customization audit and sandbox test.
2. Is Agentforce available to small and mid-sized businesses, or only enterprises? The new Core, Advanced and Max editions are designed to make agentic capability accessible at different scales. Pay-per-resolution pricing on the Help Agent also lowers the entry cost for service teams.
3. Can an AI agent in Salesforce trigger actions in Odoo? Yes, with the right integration. Odoo 20's native MCP server and Salesforce's Data 360 and MCP support make cross-platform agent workflows significantly easier than they were a year ago.
4. What is the biggest risk in deploying AI agents? Poor data and undefined guardrails. An agent acting on inaccurate records or without spending limits can create problems faster than a human ever could. Readiness work comes before rollout.
5. Should a new implementation start on Odoo 19 or wait for Odoo 20? If you go live before the Odoo 20 stable release, start on 19 and plan an early-2027 upgrade. If your project begins in late autumn, adopting 20 directly may make sense — a partner can assess this based on your customization needs.