Phase 1 of Basalt Core
Map
Where your team’s time goes, set the baseline, select priority AI workflows.
01
What you get
- Your workflows observed and measured.
- A baseline for your ROI.
- Your own Basalt workspace (optional).
- A prioritisation of the AI agents worth building, and why.
- A roadmap on how to move forward.
In short, a report that covers your workflow: where the hours go, the state of your Odoo, what to build first, and the numbers to judge us by later.
02
How it works
We spend one hour with the people who know the workflow. They share their screen and take us through every step: the spreadsheets, the second project tool, the shared inbox, the Odoo modules, everything involved in getting the work done.
03
What we need from you
Before we meet, ideally estimate how many hours these workflows take across the whole team each week. Share any other measures that matter too, such as human error, client experience or missed opportunities.
04
Anything else
Optionally, we connect your Odoo instance to the Basalt workspace. This lets us assess account health, half-used modules, untouched rules, drifted or unclean data, missed opportunities and the questions your instance cannot answer today.
The phase is complete when
Three checks before the next phase
- 1
- 2
- 3
Questions you may have
What do we receive at the end of Map?
A view of the workflows, a measured baseline, data blockers, a list of possible agents and a prioritised plan. The document remains yours if you decide not to continue.
Does the audit cover the whole company?
It looks broadly enough to understand where time goes, then goes deeper into the team and workflows most likely to produce a useful first result.
How much time does this require from our team?
Usually under two hours on your side: read-only access, a conversation with the people doing the work and one review of the plan.
How do you choose the first workflow?
We compare lost time, repetition, data quality, risk and measurability. The first workflow must be useful, observable and bounded enough to deploy cleanly.
Can we stop after the audit?
Yes. You keep the scope, baseline and action plan. You can give it to your own team or your integrator.
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