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

Professional Services

Odoo shows the profitability of one project. The problem is seeing all forty in time to act. Basalt ranks the open portfolio, drafts the extra work nobody turned into a quote, and checks the week’s hours before they reach an invoice.

Where your team’s time goes

01 / 04

Working out what is left to spend on each project by hand before the steering meeting, with hours in one place and subcontractor invoices in another.

The portfolio view has to be rebuilt before leaders can see which projects still have room to recover their margin.

Where your team’s time goes

02 / 04

Work done outside the sold scope, agreed in an email thread, never quoted.

The evidence of extra work exists, but it remains disconnected from the commercial step needed to protect the project.

Where your team’s time goes

03 / 04

Time booked on a closed project, or on the wrong one, found at invoicing.

A late correction delays billing and asks project managers to reconstruct where the hours should have gone.

Where your team’s time goes

04 / 04

Pricing the next job from memory, because nobody added up what the last one really cost.

Without a comparable-job view, the next estimate repeats assumptions instead of learning from delivered work.

Workflows

Put the projects that need attention first

  • The agent brings every open project into one ranked view, cost to date against the work left to do.
  • It reads Odoo’s project profitability rather than replacing it.

Turn scope creep into a quote

  • When the hours booked catch up with the hours sold, the agent finds the tasks behind the drift and the out-of-scope requests recorded in the threads, then drafts the additional quote at contract rates.
  • A person prices it and decides.

Check the week’s hours before they are invoiced

  • The agent flags time booked with no order line on a billable project, hours on a project already closed, and anything past the time allocated.
  • It proposes where each one belongs, and the project manager decides.

Across your projects

Odoo already shows project profitability. What do you add?

Native profitability remains the source. Basalt can bring projects into one operating view, compare similar work and expose drift that deserves review.

What if timesheets are incomplete?

We do not hide the problem. Map measures coverage and the workflow flags missing data. A financial conclusion is shown only within the limits of the available data.

Does it work for time and materials and fixed-price work?

Yes, but the indicators differ. Time and materials focuses on billable time and invoicing. Fixed-price work compares progress, hours, purchases and sold scope.

Can subcontractor costs be included?

They can when purchases are linked correctly to projects or analytic accounts. Map checks that link before promising a consolidated view.

Are expected payment dates accounting forecasts?

No. They are operational guidance based on open invoices and observed history, with assumptions visible. Your team remains responsible for cash management.

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