Project Support
August 2026Global Energy Asset Cost Estimation Software
01
The problem
A global energy operator had no single, structured view of what an asset class should cost. Benchmarks were held in individual heads and ad hoc spreadsheets, estimates were rebuilt from scratch each time, and there was no consistent reference point across the asset class. Cost estimating teams had no shared foundation to work from, so every estimate carried the risk of someone quietly working from a different baseline.
02
The build
This project is at pilot stage. Amo Veritas built custom cost estimation software focused on cost estimating teams. The product was built using third-party app builders such as Base44 and Lovable, and runs on third-party systems rather than our own servers. It is currently built on HTML, which can be converted into a full-stack deployment. It holds confidential benchmarks of specific energy assets and gives clear, structured visibility of an entire asset class, custom-built to the client's own structure and categories rather than an off-the-shelf model. The software is the reference point: every estimator works from the same benchmarked baseline, structured the way the client actually thinks about its assets.
03
What changed
- Estimates built from shared, benchmarked baselines, not individual memory
- Structured visibility across an entire asset class, in one place
- Asset categories and structure modelled to the client's own way of working
- Confidential benchmarks held within the client's own deployment
04
Security and deployment
Client confidential. The software runs on third-party systems, not the client's own servers, and was built using third-party app builders such as Base44 and Lovable. Access is scoped to the client's own cost estimating teams, and nothing is pooled with other clients or exposed outside their operation.
05
Why it matters
Cost estimating teams now work from one benchmarked, structured view of the asset class, built to their own categories. Estimates start from a shared baseline instead of a blank sheet, and the reference point is held within a deployment scoped to their operation.