Your role
The integrator keeps Odoo
Implementation, migration, configuration, upgrades, hosting, support and the ERP relationship remain yours.
For Odoo integrators
Answer client demand for AI without building a new team.
You keep the relationship and the Odoo scope. We map, deploy and measure the first workflow with your team, under a written commercial boundary.
A written boundary, a shared scope and a measured result.
The responsibility boundary
Two areas of expertise. No gap for the client.
The partnership works only when everyone knows precisely what they own, what they deliver and what they do not sell.
Our role
Basalt takes the AI layer
Workflow mapping, agents adapted to the data, safeguards, adoption and measured results.
Together
The client sees one team
Scope, access, dependencies and approvals are shared before anything is built.
Two ways to work
You choose how involved you want to be.
The commercial model and responsibilities are written for each opportunity before the first client conversation.
01
Co-delivery
You stay in the project. We run Basalt Core on the chosen scope and coordinate dependencies with your team.
The best format when the workflow touches Odoo configuration or roadmap.
02
Referral
You make the introduction, then we qualify and deliver the AI scope. You retain the agreed visibility and the commercial terms are set in writing.
The simple format when you do not want to allocate a delivery team.
What the client receives
The same four phases, with the integrator in the right place.
The project stays bounded and legible. Data cleaning, security and human approval live inside these phases, not beside them.
The first opportunity
A short path before discussing a partnership at scale.
01
You share the context
The client, Odoo version, relevant modules and the question they are asking you.
02
We check the boundary
What is native in Odoo, what belongs to your configuration and what genuinely needs an AI layer.
03
We scope it together
Roles, access, scope, baseline and commercial terms are written down.
04
We start Map
The client sees where time goes and receives a first plan before deployment.
Why do it together
A new capability without putting the account at risk.
No speculative hiring
Add AI delivery capability for uneven demand without immediately creating a new team.
The account stays protected
Our commercial boundary is explicit. We do not bid on the ERP work that is your business.
A measurable method
The client is not buying a demonstration. They approve a workflow, a baseline and an observable result.
FAQ
Questions to settle before the first engagement.
The partner relationship
Does Basalt become the client’s main contact?
No. Each role is agreed before the introduction. In co-delivery, you remain in project governance and keep the ERP relationship.
Do you bid on Odoo implementation or migration work?
No. We do not sell implementation, migration, upgrades or Odoo support. Those engagements remain with the integrator.
Can the offer carry both brands?
Yes. The format, visible roles and client communication are defined for each engagement.
How is the partner compensated?
It depends on the chosen model, co-delivery or referral, and the real role of each team. Terms are written before the client proposal.
Is there a commitment or minimum volume?
No. The simplest route is to start with one real opportunity, then decide whether a broader framework is useful.
Delivery for the client
Who chooses the first use case?
The client and integrator choose it during Map from lost time, available data, risk and measurability.
What access do you need?
The audit starts read only. Deployment then uses a dedicated service user with the minimum permissions required for the approved workflow.
What if Odoo already covers the requirement natively?
We say so and do not resell it. The scope moves to genuinely missing work around the native function, or it is dropped.
Who approves agent actions?
The client does. New agents run dry first. Sensitive decisions and external communications remain controlled by a person.
How do you measure success?
Against the baseline written during Map, then usage, volume, exceptions and time returned on the same workflow. An unused agent is not counted as a success.
Start with one real opportunity.
Bring a client context or a demo instance. In one conversation, we check the boundary, the first viable workflow and the best way to deliver it together.
No volume commitment. A broader framework comes after the first engagement, if it is useful.