Industries

Construction & Field Service

Work happens on site and reaches Odoo late: in a van, on paper, or in someone’s head. Basalt puts labour, subcontractor cost and materials against the job while it is running, drafts the change order for work already done, and pulls Monday’s dispatch into one view. Your team reviews exceptions instead of rebuilding the picture in Excel every Friday.

Where your team’s time goes

01 / 03

A subcontractor invoices work nobody raised a purchase order against, and agreeing what is owed costs three phone calls.

The cost arrives after the work, leaving the site team and office to rebuild what was agreed before anyone can approve it.

Where your team’s time goes

02 / 03

Extra work gets done on site, recorded nowhere, and never becomes a change order the client is billed for.

When the operational record and sold scope stay separate, valid additional work is absorbed instead of reviewed commercially.

Where your team’s time goes

03 / 03

Deciding who goes where on Monday, with holidays, open callouts and travel between sites in three different places.

Dispatch depends on a current picture of availability, commitments and distance, but that picture is rebuilt by hand each week.

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

Catch site costs with no matching approval

Materials arrive and subcontractors do the work. The office only discovers missing approvals when the invoice lands.

What the agent does: Compares recorded site activity, deliveries and subcontractor charges with the job’s purchase orders and approvals to identify gaps for the project manager.

Unmatched costs grouped by job and supplier
Missing orders or approvals highlighted
Questions prepared before invoice approval

Workflow 2

Turn site extras into a draft change order

Extra work is recorded in site notes and messages, but never makes it into an additional quote.

What the agent does: Compares logged hours, agreed scope and project messages to identify work outside the original agreement.

Out-of-scope requests linked to evidence
Extra work priced at contract rates
Additional quote drafted for approval

Workflow 3

Prepare the week’s dispatch without the spreadsheet

Availability, urgent callouts and promises to customers sit in different places. Monday starts with a manual planning exercise.

What the agent does: Gathers recorded availability, open jobs, site locations and customer commitments, then highlights conflicts for the dispatcher.

Jobs and commitments brought into one briefing
Missing details and scheduling conflicts flagged
Dispatcher decides who goes where

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