Construction contractorConstruction & Trading

One ledger for a contractor running six disconnected systems

A multi-site contractor ran procurement, payroll, project costing and accounts in six tools that never agreed. We deployed and configured Oplyra ERP as the single ledger, migrated and reconciled the data, and cut the month-end close.

40%
Less time closing the month
6 → 1
Systems replaced by one ledger
2 days
Variation approvals, down from 3 weeks
18%
Fewer cost overruns at final account

Overview

The challenge and our approach

01The challenge

Estimates lived in spreadsheets, purchase orders in a trading system, site progress in WhatsApp groups and invoices in an accounting package that knew nothing about any of them. Finance spent the first two weeks of every month stitching the pieces together.

Variation orders were the real leak. A change agreed on site took weeks to reach a priced, approved document, so work was often done — and paid for — before anyone knew what it would cost.

02Our approach

We built one ledger that every department writes to. A project starts as an estimate, becomes a budget when the tender is won, and every purchase order, site report, variation and invoice posts against that budget line as it happens.

Variations got their own flow: a site engineer raises one from a phone, the estimator prices it against the original rates, and approval routes to whoever holds that budget. Month-end stopped being a reconciliation exercise because the numbers were already joined.

Explore our platforms
Site engineer reviewing a project dashboard on a laptop
Client
Multi-site contractor (anonymised)
Region
Saudi Arabia
Engagement
18 months, phased roll-out
Services
Platform build, AI & Data, Integration

The build

What we built

Modules rolled out department by department, each replacing one legacy system.

Oplyra dashboard showing quotations, active projects and revenue
  • Estimation & tendering

    Rate libraries and bills of quantities that turn straight into a project budget when the job is won.

  • Variation orders

    Raised on site, priced against contract rates and routed to the budget owner for approval.

  • Procurement

    Requisitions, supplier quotes and purchase orders committed against the right budget line.

  • Project ledger

    Committed, actual and forecast cost per line — the single number finance and site both read.

  • Forecasting

    Cost-to-complete predictions trained on past projects, flagging overruns while they can still be fixed.

  • Approvals & audit

    Role-based limits and a full trail of who approved what, against which revision.

Results

Month-end stopped being a project of its own

Measured across the first twelve months with every department live.

  • 40%

    Faster month close

    Costs post against the budget as they happen, so there is little left to reconcile.

  • 6 → 1

    Systems

    Estimating, trading, site, HR, approvals and accounting run on one ledger.

  • 2 days

    Variation turnaround

    Changes are priced and approved before the work is done, not after.

  • 18%

    Fewer overruns

    Forecasts flag a line drifting over budget weeks before the final account.

Tech stack

What it runs on

  • Application

    • React
    • TypeScript
    • Node.js
  • Data

    • PostgreSQL
    • Redis
    • n8n
  • Infrastructure

    • Azure
    • Docker
    • Git

Senior people, every call, for eighteen months. That is the whole difference and it shows in the product — our finance team closes the month in days, not weeks.

Ayesha KhanManaging Director, OplyraConstruction contractor

More case studies

Other work we are proud of

All case studies

Facing a problem like this one?

Thirty minutes with a solution architect — walked through your own system, with an honest answer on whether we are the right team for it.

Book a free call