Your ERP doesn't end at go-live: SLA-backed support and continuous evolution

You know the pattern. The partner disappears (or slows down) once the project is declared closed. Tickets sit in limbo, improvements land in an endless backlog, and an internal team inherits a half-finished Odoo. Go-live was an event. Operations happen every day.

If you already have Odoo or are about to, the right question isn't just "who implements it." It's who stays: Odoo support with an SLA, serious ERP maintenance and Odoo evolution as the business changes.

Why post-go-live orphans are so common

Projects are sold as go-live. The incentive of a fixed scope pushes toward "finishing." But implementations that stick need a different conversation:

• Real adoption issues (not just bugs).
• Configuration adjustments when the process is better understood in week three.
• New apps or flows when you open a channel, warehouse or product line.
• Upgrades and security without improvising.
• Training new people who weren't in the original workshop.

Without that, the spreadsheet comes back. Not because Odoo "doesn't work," but because nobody supports the habit.

Support with an SLA: what needs to be in writing

A useful Odoo SLA isn't a generic PDF. It spells out:

• Support channels and hours.
• Severity levels (what counts as "I can't invoice" vs. "I want a different color in this view").
• Response and containment times, not just "acknowledgment."
• What functional support covers and what counts as an improvement or a project.
• Who on the client side prioritizes and who on the partner side executes.

Maintenance isn't just restarting a service. It's caring for the platform so operations, finance and sales keep sharing the same system of record.

Continuous evolution: the system grows with the business

Evolve is the fourth stage of the KAI Consulting method on purpose. After Discover, Design and Implement, we stay:

• Improvements prioritized by real friction (not module whims).
• Configure before customizing, after go-live too.
• AI and Automation layers once adoption is there: documents, flows, copilots on live data.
• Reporting and processes recalibrated when operations change.

Odoo evolution isn't a demo lab. It's continuous delivery on top of what's already running.

What to ask an Odoo partner in Mexico (with a US presence, if that matters to you)

If you're looking for an Odoo partner in Mexico, look beyond the logo on the website:

• Do they have an explicit Support and Evolution practice, not just projects?
• Can they talk about SLAs without hiding behind "it depends"?
• Who stays your contact when the go-live PM rotates off?
• How do they handle upgrades and the debt from earlier customizations?
• Do they understand nearshore and bilingual operations if your group has a US entity and operates in Mexico?

KAI Consulting operates from Monterrey, with a US entity when the group's structure calls for it. What matters isn't geography in the abstract: it's a partner that doesn't fade away once the go-live ribbon is put away.

Signs you're about to be orphaned

• The contract ends on go-live day with no support addendum.
• Improvements are "left for phase 2" with no owner or cadence.
• Only IT talks to the partner; operations has no channel.
• Every small change is quoted as a new project with no clear criteria.
• Nobody reviews adoption at 30, 60 and 90 days.

If you're signing an implementation, negotiate the Evolve stage at the same time. Later, it hurts more.

What a healthy post-go-live feels like

It's not the absence of tickets. It's tickets that get answered, shared priorities and a backlog that moves. The team leaves the spreadsheet because the system responds. When the business asks for a new flow, there's a design path (configuration first) and a small go-live, not an annual drama.

You also feel it in the cadence: a regular adoption review (who went back to Excel, which report nobody opens, which permission is in the way), an upgrade plan without surprises and a channel where operations can speak without filtering everything through IT. The partner doesn't need to live in your office; it needs to not disappear once the go-live ribbon is put away.

That's consulting that delivers, not quarterly "opportunity" presentations.

A practical next step

If you're already on Odoo, list this week's five friction points (report, permission, flow, integration, user question). Mark each one as an incident, an improvement or a training need. That triage is the start of a serious support agreement.

If you haven't gone live yet, ask your partner for the plan for the first 90 days after go-live, with an SLA and an evolution cadence. At KAI Consulting, Odoo implementations go live and stay live: from the first workshop to SLA-backed support and new capabilities as your operation grows. Whenever you want to talk about not being orphaned, we start with how your business runs today.