Case study · SaaS platform · early team

Proteus: building the Delivery module of a project platform for oil, gas and engineering

From 2020, IlahSol's founder was part of the initial engineering team at Xergy in Scotland, building the Delivery module of Proteus: the part that runs a project after the bid is won.

Illustration of a Proteus Delivery module project dashboard with earned value, CPI, SPI and a progress curve

01 — The challenge

What did the client need?

Engineering consultancies and energy companies often win work in one system and run it in another: bids in spreadsheets, timesheets in a separate tool, budgets and invoices in finance, and progress reports assembled by hand. By the time a project manager sees that cost or schedule is drifting, the margin has usually gone. Xergy set out to build Proteus as one platform that carries a project from bid to close-out on the same data.

02 — The solution

What did we build?

The Delivery module is the part of Proteus that takes over once a bid is won. It turns the work breakdown and estimate into a baseline, puts the right people on each work package, and captures timesheets, progress and scope changes as the work happens. From that data it calculates project controls such as earned value, CPI, SPI and estimate at completion, raises early warnings, and feeds invoicing and client reporting.

Five steps from a won bid to a closed-out project: bid won, plan and resource, track, control, invoice and close
Where the Delivery module fits: from a won bid to a closed-out project.

03 — Key features

What's inside

The Delivery module

01

Project controls

Earned value, CPI, SPI and estimate at completion, so cost and schedule drift is visible while there is still time to act.

02

Progress tracking

Progress recorded by work package and deliverable, rolled up into project and portfolio dashboards.

03

Resourcing

Planning and allocating engineers across projects, so teams are neither overbooked nor idle.

04

Timesheets and approvals

Time captured against projects and non-billable codes, with one approval flow for time and purchases.

05

Variations

Scope changes raised as variations that update the cost baseline instead of quietly eating the budget.

06

Finance and reporting

Invoicing, cash flow and client reports generated from the same project data.

04 — Gallery

05 — In short

The project at a glance

Our role

Part of Xergy's initial engineering team, from 2020

IlahSol founder

Focus

The Delivery module: running projects after the bid is won

IlahSol founder

Who uses Proteus

Bid, project controls and finance teams at engineering consultancies and project owners

Xergy, xergy.com

Where it is now

Xergy reports more than 10,000 users of Proteus

Xergy, xergy.com

06 — Architecture

How the pieces connect

  1. 01Bid won (Sales module)
  2. 02Plan and resource
  3. 03Time, progress and variations
  4. 04Controls, invoicing and reports