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

Basalt
Menu

Language

MapLet’s understand your processDeployLet’s improve your processMeasureLet’s ensure team adoptionExpandLet’s save you more timeShow me the money.A clear price and scopeManufacturing & ProductionProduction, BOM, and Work Center TrackingWholesale & DistributionMulti-Warehouse Logistics, Supply Chain, and ShippingFood & BeverageBatch Lots, Traceability, and Expiration DatesRetail & E-commerceOmnichannel Sales, POS, and Storefront InventoryProfessional ServicesMilestone Projects, Timesheets, and Helpdesk TicketingConstruction & Field ServiceSubcontracting, On-Site Jobs, and Resource SchedulingPartnersOdoo integratorsLog in to your Basalt workspaceOpen your workspaceAboutWho builds BasaltCareersWhat we look forContactWrite or callCase studiesWork and resultsBlogNotes and guides

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

See the cost arrive before the invoice does

  • The agent puts the hours, deliveries and plant booked to a live job next to the purchase orders behind them, and flags the jobs where cost is landing with nothing committed against it.
  • Your project manager sees it while there is still something to agree, not at month end.

Turn extra work into a change order

  • The hours and purchases beyond the sold scope are already in Odoo.
  • Nobody has time to read them job by job, so the work gets absorbed.
  • The agent brings the difference together and drafts the change order.
  • A person prices it and decides what to send.

Prepare Monday before Monday

  • Odoo plans the resources.
  • What it does not do is assemble the picture: who is available, which callouts are open, what was promised to the client and how far apart the sites are.
  • The agent prepares it, and a person decides who goes where.

On your sites

Does the work have to be recorded in Odoo the same day?

No, but the later it lands the less an agent can prepare. Map measures how site activity actually reaches Odoo today and says plainly what that allows.

Can an agent approve a subcontractor invoice?

No. It can place the invoice beside the order, the site activity and what was agreed, then isolate what does not match. A person approves the payment.

Odoo already plans resources. What do you add?

Planning and its rules stay native and Basalt does not resell them. The work starts where the picture is spread across holidays, open tickets, promised dates and travel, and someone rebuilds it by hand each week.

Can an agent send a change order to the client?

No. It prepares the draft from hours and purchases already recorded beyond the sold scope. A person prices it, decides whether to send it and keeps the client relationship.

What if we use subcontractors for most of the work?

That is the usual case. The workflow then centres on commitments, what was ordered and what arrived, rather than on internal hours.

Deployment and results

Does the whole process need to be in Odoo already?

No. Map also looks at spreadsheets, shared inboxes and tools around Odoo. The first workflow still needs a reliable source and a clear boundary.

How do you work with our integrator?

They remain responsible for the ERP. We document access, objects read or written and dependencies so everyone knows what belongs to Odoo and what belongs to Basalt.

How long does the first deployment take?

The scope aims for a first real use in the first month. Your team mainly explains the task, reviews exceptions and approves production.

Who keeps the final decision?

Your team does. Agents prepare, reconcile, flag and document. A person approves sensitive decisions and sends external communications.

How do you prove the workflow is useful?

We compare time, volume, exceptions and usage with the baseline written during Map. If the result is unclear, the workflow is not presented as a success.

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