Phase 4 of Basalt Core
Expand
Where to next? What’s your current AI priority.
01
What you get
A written plan for the next cycle before you commit to it. Usually it’s the next department. Sometimes it’s going deeper on the first cycle or workflow.
02
How it works
We revisit the numbers from Measure and the priorities from Map. About three months have passed, and your priorities or the available AI may have changed. Together, we decide where the next Basalt Core cycle will create the most value.
The first cycle often reveals further opportunities. Agents need updates, AI models change, Odoo is upgraded, processes move, people leave and new tools enter the workflow.
03
What we need from you
Up to 90 minutes once a quarter: review the time recovered and decide where the next cycle goes. Everything between those reviews is documented in writing.
04
Anything else
You can opt out after the initial three-month cycle. If you want to bring the work in-house, we help with the handover. No hidden costs or terms.
The phase is complete when
Three checks before the next phase
- 1
Reviewed
- 2
Prioritised
- 3
Aligned
The next cycle
How do you choose the next workflow?
We return to the initial map and the results actually measured. Priority goes to the adjacent workflow that creates the most value without weakening what is already running.
Do we have to open another cycle?
No. You can keep the current production scope, pause expansion or stop. The plan for the next cycle is written before you decide.
What happens to agents already deployed?
They remain monitored during the agreed cycle. Process, data or Odoo version changes are reviewed so an agent does not drift silently.
Can we expand into another department?
Yes. That is often the best route because the first workflow has already clarified permissions, data and measurement inside the organisation.
How do you avoid accumulating unused agents?
Every agent keeps an owner, an indicator, a log and a stop condition. Anything no longer used or returning time is improved or removed.
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