New: Your Basalt workspace for Odoo. MCP, proactive agents, visualisation. Learn more

Basalt

Industries

Manufacturing & Production

Half your enquiries look like something you have already built. Basalt finds the closest past job, prepares the parts list and the routing, and shows what the work really consumed once the order closes. Your engineers keep their time for the jobs that need them.

Where your team’s time goes

01 / 04

An engineer pricing a job that looks almost exactly like one you priced last year.

The comparable job exists, but finding its parts, routing and final outcome still pulls an experienced person away from new engineering work.

Where your team’s time goes

02 / 04

Working out what a job cost after it shipped, with the material, the scrap and the hours in three different places.

The margin becomes clear only after someone reconstructs the full production record, often too late to correct the next similar quote.

Where your team’s time goes

03 / 04

A component short on Monday, and no single list of the work orders competing for it.

Planners need the affected orders, promised dates and available alternatives together before they can make a useful trade-off.

Where your team’s time goes

04 / 04

Answering “can we take this on for March” by opening three screens and adding it up yourself.

Capacity decisions slow down when demand, material availability and work-centre load cannot be read in one prepared view.

Workflows

Examples we can scope around your team’s work, Odoo setup and other tools. Your team reviews the agent’s work and approves the next step.

Workflow 1

Stop rebuilding the same quote from scratch

A familiar enquiry lands, but an engineer still has to hunt through old jobs to prepare the quote.

What the agent does: Finds comparable completed jobs and brings their parts, production steps and recorded costs into a draft for the engineer to review.

  • Relevant past jobs linked to the enquiry
  • Differences and missing specifications highlighted
  • Quote preparation ready for engineering review

Workflow 2

Find the jobs that cost more than planned

You know some jobs ran over budget. Finding which ones, and why, takes another spreadsheet.

What the agent does: Compares Odoo’s recorded costs with the original estimates across completed jobs, then gathers the material use, scrap and hours behind the largest differences.

  • Jobs needing attention brought to the top
  • Cost differences linked to production records
  • Findings ready to inform the next quote

Workflow 3

Decide what to build when parts are short

Several jobs need the same missing component. The planner has to work out which customer commitments are at risk.

What the agent does: Identifies production orders competing for scarce parts and prepares options using delivery commitments and supply dates.

  • Production linked to customer orders
  • Allocation and delay options compared
  • Planner approves changes before they apply

Deployment and results

Does our whole process need to be in Odoo already?

No. In the Map phase, we identify all the tools you use to run a specific workflow. We then move into the Deploy phase from there.

Does Basalt replace our Odoo integrator?

No. Your integrator maintains and develops Odoo. Basalt handles the AI layer on top: your workflows across Odoo modules and other software. Basalt works with the integrator where scopes meet.

How long before the first workflow is live?

Most companies have a first workflow in production within the first month. Timelines depend primarily on how quickly a client provides data access and approvals.

How do you measure results and ROI?

We determine the baseline, typically how many hours a workflow takes today, before deployment and compare the same workflow after it’s live. Ultimately, it depends on what we uncovered as your most important goals during the Map phase. We can also track metrics like cost to scale, process adoption, error reduction and qualitative team feedback. This is how we determine the result and ROI.

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