Strucad Engineering Odooimplementation

01 /

The challenge

Jobs, costing and approvals sat in separate spreadsheets that nobody fully trusted. The true cost of a quote was often unclear until the job was already won. The firm also had years of project history in those spreadsheets — losing it was not an option.

02 /

What we did

1. 01

   Implemented and customised Odoo around the firm’s actual workflow — job cards, costing, approvals and reporting — rather than forcing the firm into Odoo’s defaults.

2. 02

   Mapped and migrated the existing project history into the new system rather than starting clean, so quotes can reference what similar jobs actually cost before.

3. 03

   Configured the approval chain to match how decisions actually get made: site engineer, then project director, with visibility for finance at each step.

4. 04

   Trained the people who run the system day to day — site engineers and the finance team — not just the managers who approved the project.

03 /

Outcome

One system the whole firm operates from. Quotes are built on recorded job history instead of memory, approvals follow the chain that actually exists, and finance can see committed cost against budget without chasing spreadsheets. The implementation was configured to the work they actually do, not the other way round.