Phase 3 of Basalt Core
Measure
How has the AI workflow affected your baseline. Make the results clear.
01
What you get
- A workflow the team understands and uses. An agent nobody uses is a failure, not a feature.
- Clear governance: who can use what, what agents may prepare independently, what still needs human approval, what gets logged, where to check it, when to stop an agent and who decides.
In short, you recover time, your team knows how to control the agents, and every important action has a clear record.
02
How it works
Over the next two to four weeks, we measure how the work has changed and adjust the agents where needed. Short forms or focused meetings let us compare the hours the workflow now takes across the team each week. We also track the other measures agreed during Map, such as human error, client experience or missed opportunities.
03
What we need from you
Up to 30 minutes a week, to gather your feedback and attend meetings as needed.
04
Anything else
Ask us all your questions. We want you to own and understand your Basalt workspace and agents.
The phase is complete when
Three checks before the next phase
- 1
Improvements
- 2
Clarity
- 3
ROI
Measurement and adoption
Which indicators do you measure?
Those agreed during Map: time returned by workflow, volume handled with review, usage, errors or exceptions, and processing time when it matters.
How do you avoid vague ROI estimates?
We date a baseline before deployment and compare the same activity afterwards. The result belongs to one workflow and one team, not a general percentage.
What if nobody uses the agent?
We treat that as a deployment problem. We observe the real task, simplify access, retrain the team or remove the agent if the need was not strong enough.
Is training only for end users?
No. Users learn how to check the work, while managers learn how to follow usage, exceptions, permissions and stop conditions.
How long do you measure before drawing a conclusion?
Long enough to cover a representative volume. Some workflows become clear in a few weeks, while others require a complete monthly cycle.
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