Skip to Content

Odoo vs AI: Should AI Build Your Business Software?

AI can build an app in minutes - so why not replace your ERP? An honest build-vs-buy answer from someone who sells both Odoo and custom AI software.

Odoo + AI, not Odoo vs AI


A developer who has been shipping AI-built apps in production for a year put the whole "is software dead" debate into one line:

"The difference between AI slop and a proper app is who is directing the app."

I spent five years as a developer, and I always wanted to work in AI. So I'm not watching this shift nervously from the sidelines, I'm walking into it on purpose. I sell both Odoo and custom AI builds. Let me tell you why he's right, and what the demo everyone keeps sharing quietly leaves out.

You have seen the demo by now. Someone types a sentence, an AI builds a working invoice screen in two minutes, and the conclusion writes itself: software is dead, just build whatever you need. If you are a founder or ops lead trying to decide between adopting a platform like Odoo and building something custom with AI, that demo is probably sitting in the back of your head right now.

The demo is real. The conclusion is wrong.

What did AI actually make cheaper?

Building the software was never the expensive part. That is the part the demo hides.

Across the industry, maintaining software runs 50 to 80 percent of its lifetime cost, often two to four times what you spent building it (Pegotec, 2026). The build is the small number. Everything after launch, maintaining it, upgrading it, keeping it compliant, integrating it with the next tool you adopt, is the big one.

So when AI makes the build 10x cheaper, it discounts the small number and leaves the big one untouched. Worse, it can make the big number harder. A December 2025 report in The Register, citing survey data, put AI-generated code at roughly 1.7x the bug rate of human-written code (and that is code shipped without human-review gates, not AI-assisted work a developer actually checked). The screen appears in minutes. The consequences arrive later.


What can't AI shortcut?

When a client asks me "why not just build it?", I don't argue with the demo. I point at the three things the demo quietly skips.

Correctness, proven by millions of users. An AI generates an invoice screen in minutes. It cannot guarantee the books reconcile, the tax rounds correctly across currencies, and the audit trail survives a visit from the tax authority. That correctness isn't clever code. It is decades of encoded edge cases, Korean VAT and 전자세금계산서 included. And it has been proven the hard way: more than 15 million users have run Odoo and surfaced those edge cases over years of real use. Your AI-built version has been tested by exactly one party, the AI that wrote it. Getting it wrong is legal and financial exposure, not a bug you patch on Friday. And the liability doesn't transfer - using a third-party AI to build the thing doesn't move the compliance risk off you. If the generated code gets your VAT wrong, you're still the one the tax authority calls.

Integration over fragmentation. Five beautiful AI-built apps just recreate the data silos ERP was invented to kill. One shared model across sales, inventory, accounting, and HR is the genuinely hard, expensive work. A pile of standalone tools is not a system.

Maintenance. Software that only the AI (or the one person who prompted it) understands is an orphan the moment it ships. Who fixes it at 2am? Who patches the security hole? Who owns the upgrade path in three years? Odoo's vendor, community, and patch cycle are, in plain terms, an insurance policy. Bespoke code has no one on call. And there's a human cost stacked on the technical one - your team has to actually trust the thing - but that's a big enough problem that I'll come back to it.

If you want the cautionary tale: in 2025, during a 12-day test run by the founder of SaaStr, an AI coding agent on Replit's platform deleted a live production database during an explicit code freeze, fabricated thousands of fake records, then told the tester that recovery was impossible. It wasn't. Replit's CEO called it unacceptable, said it should never have been possible, and shipped new safeguards. It was a controlled experiment, not a normal client deployment, but that is precisely the governance gap that matters: the AI did exactly what no junior engineer would ever be allowed to.

Strip it all down and the real question isn't whether AI can build business apps. It is whether it can carry the liability, the integration, and the longevity that businesses actually pay for. Right now, on its own, it can't.


Where does AI genuinely win?

Now the other side, because pretending AI changes nothing is its own kind of dishonest.

For the long tail of simple, greenfield tools, a lightweight CRM, an inventory tracker, a booking form, a small internal app sitting next to your Odoo, AI-native genuinely wins today. Basic data entry with a little workflow, no decades of compliance baggage, no legacy to wire into. "Why configure Odoo's unused 80 percent when AI builds exactly what I asked?" isn't a weak question there. It's the right one. The cost barrier that used to make off-the-shelf the only sane choice is gone: a tool that once cost six figures can now land in weeks for a fraction of the price. For that slice, I would tell a client to build, not buy.

So the build-vs-buy line moved, and it is still moving. The simple, greenfield end belongs to AI now, and that end is growing. What AI eats first is the button-clicker, the consultant who just installs modules and clicks settings, and yes, part of that was my own market. What it can't yet carry is the judgment that gets heavier as the system gets more business-critical: understanding your operation, designing the data model, ensuring compliance, integrating the pieces. So the line keeps climbing the stack, and nobody, me included, should assume it stops where it sits today.


So where is the debate actually happening?

What's most telling, and it surprised me:

The "replace your ERP with AI" argument is loud in blog posts and on stock tickers. In the rooms where people actually run Odoo, it is almost absent. Go read the practitioner forums. Nobody there is asking "should I replace Odoo with an AI build?" They are asking "what's the best AI agent to build on Odoo?"

That is the real shift. Not AI versus the platform. AI as the fastest builder we have ever had, pointed at a governed system that already knows how to keep your books straight. The scarce skill stopped being "can you write the code." It became "do you know what to build, and can you direct the machine that builds it." Which is exactly what that developer meant: who is directing the app.

But that's only half of it. Knowing what to build is one thing. Whether anyone will trust it is another.


But will people even accept it?

Because a lot of people don't want it, at least not with the label on. And that resistance splits into two very different things.

Most of today's distrust is really the technical question seen from the other side. Just 9 percent of workers say they trust AI for business-critical decisions (Fortune, 2026), but that's trust in unproven AI. Show a team a system that has run their numbers clean for a year and that number moves. This part of trust isn't a separate problem. It's the same technical gap seen from the worker's side, and it closes the moment you have a track record.

The part that doesn't move is different. "AI slop" was the word of the year. Sixty percent of consumers say "AI" in marketing is a turnoff, "no AI" is now a selling point, and only 16 percent of Americans think AI will make society better (Pew, 2026). That resistance isn't about whether the thing works. Sometimes it's strongest because it works. It's about not wanting "made by AI" on the face of your business, and no track record fixes it.

Here's the useful part: that durable resistance is about the label, and the smart architecture routes around it. AI doing the work quietly, underneath a system people already know and trust, never trips it. Which is the same conclusion everything else here points to: not "AI, look, AI," but AI under something proven.


So, should you build or buy?

The rule I actually use with clients:

Lean Odoo when the work is business-critical and standard, real accounting, tax, inventory, the things that have to reconcile and survive an audit, you need to go live in weeks, and you want a platform other people maintain. For most established businesses, that is the faster, cheaper, safer call today. Today being the operative word.

Lean AI-native when the tool is simple or greenfield, the compliance surface is light, iteration speed matters more than a decades-deep feature set, or your workflow genuinely fits no platform, and you have the discipline to direct the build and own what it produces. That set is smaller today. It will not stay smaller.

Most of the time the best answer is neither pure option. It is Odoo as the governed core, your system of record, with AI agents as the build-and-action layer on top, automating the work and extending the system without turning your business into an orphaned science project.

That is what I mean by Odoo + AI, not Odoo vs AI.

And because I sell both, lock-in isn't in my interest. Your data is always yours, exportable. If a custom build ever genuinely fits you better, I will say so, honestly, in the room. You don't need a vendor who only knows one answer. You need someone who knows both well enough to tell you the truth.

And the truth, today, is this: on its own, AI can't yet carry the hard part, the liability, the integration, the longevity. The technical gap is closing fast. Trust closes slower - it's earned by track record, not benchmarks. And the sliver that just doesn't want "AI" in the room may never fully close at all. So even when AI-native can carry the weight, it won't be an instant yes. The day it is both proven and trusted, openly, is the day I build there. This isn't me defending Odoo. It's me calling the line where it sits today, and moving with it as it shifts.

If you are weighing build-vs-buy for your own operation, comment "Odoo" or send me a message and I will share the one-page checklist I actually use with clients.


Link references




Peter Markus June 22, 2026
Share this post
Archive