New: Your Basalt workspace for Odoo. MCP, proactive agents, visualisation. Learn more
For Odoo integrators
You keep the relationship and the Odoo scope. We deliver the AI layer (map, deploy and measure) on top of your Odoo build.
A written boundary, a clear scope and a measured result.
The responsibility boundary
The partnership works only when everyone knows precisely what they own, what they deliver and what they do not sell.
Your role
Implementation, migration, configuration, upgrades, hosting, support and the ERP relationship remain yours.
The integrator keeps Odoo
Our role
Workflow mapping, agents adapted to the data, safeguards, adoption and measured results.
Basalt takes the AI layer
Together
Scope, access, dependencies and approvals are shared before anything is built. The client is clear on roles and responsibilities.
The client experiences us as one
Two ways to partner
The commercial model and responsibilities are agreed upon for each opportunity before the first client conversation.
Your Odoo expertise. Our AI delivery. One team for the client.
You stay in the project. We run our ‘Basalt Core’ 3-month cycle on the chosen scope and coordinate dependencies with your team.
Recommended format when the AI build relies on your ongoing Odoo implementation with the client.
You make the introduction. We take the AI project forward.
You make the introduction, then we qualify and deliver the AI scope. Our commercial terms are agreed upon prior to referral.
Recommended format when you don’t want to allocate any resources.
What the client receives
Our project scope stays bounded to the AI layer the client needs. Anything that requires an Odoo build or restructure will be handed to you as the Odoo integrator partner.
The first co-delivery opportunity
Here’s a 4-step guide on how we suggest moving forward.
01
The client details, their request, their Odoo version, modules, tech stack and other relevant information.
02
Basalt determines what is native to Odoo, what belongs to your configuration and what genuinely needs an AI layer.
03
Roles, access, scope, baseline and commercial terms are written down.
04
Prior to any commercial agreement with the client, they receive a plan and proposal, to be signed prior to deployment.
Why partner with Basalt
The value for referral is relatively self-evident. In terms of the co-delivery, see below.
Stand out in competitive ERP pitches by offering enterprise-grade AI capabilities out of the box. Increase contract value and unlock high-margin upsell opportunities across your existing Odoo client base without altering your core delivery scope.
Scale AI integration on demand without the fixed overhead, long recruitment cycles, or bench risk of building an in-house AI team. You capture AI revenue immediately while keeping your team focused entirely on Odoo implementation.
We function exclusively as your specialised AI layer. We never bid on, compete for, or touch core Odoo implementation, migration, or customisation work. Your client relationships and primary revenue streams remain 100% yours.
FAQ
It depends on what you prefer. Preferences differ between partners and between co-delivery and referral. Our roles are agreed before you introduce us.
No. We do not sell implementation, migration, upgrades or Odoo support. Those engagements remain with the integrator.
Yes. The format, visible roles and client communication are defined for each engagement.
It depends on the chosen model, co-delivery or referral, and the real role of each team. Terms are written before the client proposal.
No. The simplest route is to start with one real opportunity, then decide whether a broader framework is useful.
If this is a referral, it tends to be the client. If it’s a co-delivery, it’s typically decided between the client and integrator. Insights are also derived from the Map phase to help determine potential time savings, available data, risk and measurability.
We call it out early and determine whether there’s scope for a real client need that’s missing in Odoo. If not, we don’t move forward with the client / project.
The client does. We always conduct dry-runs first (safe ‘practice runs’ where the AI previews its actions before going live). Sensitive decisions and external communications remain controlled by a person.
We determine the baseline, typically how many hours a workflow takes today, before deployment and compare the same workflow after it’s live. Ultimately, it depends on what we uncovered as your most important goals during the Map phase. We can also track metrics like cost to scale, process adoption, error reduction and qualitative team feedback. This is how we determine the result and ROI.
Come ready with your client context. In 30 minutes we’ll determine what’s viable and the best way to move forward together.