Diagnosis · Engineering · fewer than 10 people
Before changing the ERP, look at what is in it
1 in 7
working hours did not count towards the cost of any project.
Audit delivered. Implementation in progress until May 2027.
The process, before and after
- Site visit without a checklist, memory
- Number assigned by hand, shared list
- Look for a similar proposal, old proposals
- Ask for prices, email, phone
- Wait for software timings
- Do the maths, Excel
- Exclusions from memory, Excel
- Revisions with no history, Excel
- Send to the client
- Bill of materials, Excel
- Order items one by one, ERP
- Ask whether it arrived, phone
- Tell someone to invoice, email
- Issue the invoice, invoicing
- Site visit with a checklist, ERP, planned
- Automatic number, ERP, planned
- Start from a template, ERP, planned
- Maths in Excel, Excel, stays as is, the client decided
- Prices with a date, ERP, planned
- Import validated prices, ERP, maybe in phase 2
- Mandatory exclusions, ERP, planned
- Revisions with history, ERP, planned
- Reason for loss, ERP, planned
- Materials per item, ERP, planned
- Order with cost, ERP, planned
- Pending orders in view, ERP, planned
- Requests from the site, field app, waiting on the supplier
- Mark instalment ready, ERP, planned
- Issue the invoice, invoicing, unchanged
- Cost alert, ERP, planned
See all the steps
Before: 14 steps, 13 outside the ERP, 1 in the ERP. After: 16 steps, 3 outside the ERP, 13 in the ERP. The after has more steps because it records things that nobody records today.
Before
- Site visit without a checklist, memory
- Number assigned by hand, shared list
- Look for a similar proposal, old proposals
- Ask for prices, email, phone
- Wait for software timings
- Do the maths, Excel
- Exclusions from memory, Excel
- Revisions with no history, Excel
- Send to the client
- Bill of materials, Excel
- Order items one by one, ERP
- Ask whether it arrived, phone
- Tell someone to invoice, email
- Issue the invoice, invoicing
After
- Site visit with a checklist, ERP, planned
- Automatic number, ERP, planned
- Start from a template, ERP, planned
- Maths in Excel, Excel, stays as is, the client decided
- Prices with a date, ERP, planned
- Import validated prices, ERP, maybe in phase 2
- Mandatory exclusions, ERP, planned
- Revisions with history, ERP, planned
- Reason for loss, ERP, planned
- Materials per item, ERP, planned
- Order with cost, ERP, planned
- Pending orders in view, ERP, planned
- Requests from the site, field app, waiting on the supplier
- Mark instalment ready, ERP, planned
- Issue the invoice, invoicing, unchanged
- Cost alert, ERP, planned
The problem
A quote takes a month. The company was about to invest in an ERP it partly had already, without knowing what was set up well and what was not.
What we did
Diagnosis
We audited the ERP in read-only mode, without changing a single record. That produced five findings and three decisions set out for management.
Tidy up
The plan started from what the system already has. The quoting spreadsheet stayed, because that is where the person who prices the work does the sums. The ERP will keep the proposals, their status and the history.
Build
The implementation goes in phases and starts with the warehouse.
Train
Testing is done with real work, such as a real proposal or a real bill of materials, so the time spent testing also counts as work done.
The result
- 1 in 7 working hours did not count towards the cost of any project, so margins looked better than they were.
- On one project, the hours delivered were more than eight times the hours sold, because of a configuration error.
- Fewer than 1 in 10 projects had a sales order.
The company knew all this before investing. In the plan, the quoting steps outside the ERP go from 13 to 3, and the client’s goal is a quote in two weeks on large projects and two days on small ones, instead of a month.
Tell us where your team loses time.

Prefer to write? marta.matos@withzeno.com