Phase 2 of Basalt Core
Deploy
Have your first complete AI workflow ready, ontop of Odoo, with your team in control.
01
What you get
Your Basalt workspace. One place to:
- Chat with your Odoo data.
- Use tailored reports and dashboards when they are useful.
- See the AI agents prioritised during Map.
- Receive a weekly Odoo data-quality review and a digest of the work your agents prepared.
In short, one source of truth for your Odoo and AI work. Reactive agents answer your questions. Proactive agents prepare recurring work and flag duplicates, missing fields and contradictions that affect live workflows. You keep control and recover time for higher-value work.
02
How it works
Over the next four to six weeks, we build and refine what Map uncovered with you. This is where repetitive work starts leaving your team’s week.
03
What we need from you
Roughly 30 minutes a week, with someone who can approve. Nothing goes live without your approval. Written updates in between.
04
Anything else
As repetitive work leaves the week, the next useful opportunities usually become easier to see.
The phase is complete when
Three checks before the next phase
- 1
Live
- 2
Training
- 3
Approved
What goes into production
What does Deploy include in practice?
Your Basalt workspace, an MCP connection adapted to your Odoo, the chosen agents, controls, data-quality monitoring and, where useful, tailored views or dashboards.
Can an agent act alone in Odoo?
Only within limits you have approved. It starts in dry-run mode, then simple actions can be opened gradually. Sensitive decisions remain human.
What is a proactive agent?
It watches an agreed signal and prepares the next step without waiting for a question. It can flag an exception or prepare a draft, but a person reviews and sends external communications.
How long before the first real use?
The scope aims for a usable first workflow in the first month. The exact date depends on access, data and the level of approval required.
Do our teams need to change tools?
Not by default. Odoo remains the system of record. The workspace or a dedicated view is added only when it makes the decision and review simpler.
Do we need to stabilise or clean Odoo completely first?
No. Map identifies the data that genuinely blocks the chosen workflow. We fix what matters for that deployment without turning the project into an endless general clean-up.
Does Basalt replace our Odoo integrator?
No. Your integrator maintains and develops Odoo. Basalt works alongside them on workflow mapping, agents, useful interfaces and measured results.
Which data can Basalt access?
Only the data required for the agreed scope, through a dedicated service user and explicit Odoo permissions. The audit starts read only.
Who approves what an agent prepares?
Your team does. A new agent runs dry first. Sensitive decisions and external communications remain reviewed and triggered by a person.
What happens if the result falls short?
Measure makes that visible. We improve the workflow, narrow it or stop it. You keep the documentation and what was built, with no annual commitment.
Bring us one workflow that takes too much time.
In 30 minutes, we will see whether it is worth mapping.
Book 30 minutes- Start with a real task
- Look at the modules involved
- Identify the control points
- Choose a clear next step