By Colin Manson, Co-founder, Proteus

A few days ago I was sitting across the table from a project director at a mid-sized energy consultancy. It’s a good company with smart people and a solid reputation for delivery. They’d just invested heavily in a new ERP rollout. Eighteen months of work, significant cost, full upheaval. And yet when I asked how they tracked live project margin, the answer was a tight smile and “we have a spreadsheet for that.”

I hear some version of this story almost every week. And I’m not sharing it to criticise the decision as I truly believe ERP investments are necessary. I’m sharing it because it illustrates something that I think a lot of people in the project-based world feel: ERP systems were never really built for the messy, dynamic reality of project delivery. And the gap between what they promise and what they actually do at the execution layer is costing firms real money.

The spreadsheet is the symptom not the problem

When you walk into most engineering or energy project businesses and look at how work actually gets managed and not how the org chart says it gets managed, you find a patchwork. CRM here, ERP there, project schedules in one tool, cost tracking in another, and somewhere in the middle, a collection of spreadsheets doing the job that none of the other systems quite manage.

The spreadsheets exist because the people running projects are resourceful and they will always find a way to get the information they need. But the hidden cost is enormous. Someone is manually moving data between systems. Someone else is rebuilding the same cost model from scratch because the last one lived on a colleague’s laptop. A project manager is spending a day and a half every month pulling together a status report that should take twenty minutes.

And critically by the time any of that information surfaces, it’s already out of date. Decisions get made on last month’s numbers. Margin drift goes undetected until it’s too late to do much about it. Variations get managed reactively rather than proactively.

What ERP is actually good at 

To be clear: I’m not anti-ERP. SAP, Oracle, Microsoft Dynamics are serious platforms built to solve serious problems. They handle financial consolidation, compliance, intercompany accounting, payroll, procurement workflows undeniably well. For any organisation of meaningful scale, some kind of ERP backbone is critical.

But ERP systems were designed around transactions and periods, invoices raised, costs posted, time booked reconciled at month end. Project delivery doesn’t work like that. It works in real time, with scope that shifts, resources that move between jobs, commercial assumptions that were made six months ago and may no longer be correct, and a cost of completion that changes every week.

The result is a fundamental mismatch. ERP tells you what happened. Project delivery requires you to know what’s happening right now, and what’s likely to happen by the time you reach final account. Those are different questions.

The fragmentation this creates is well documented, but still under-appreciated at the strategic level. Commercial teams price work in one system. Delivery teams execute in another. Finance reconciles in a third. Nobody has a complete picture, and reconciling those three views typically requires manual effort that wouldn’t be necessary if the data were connected in the first place.

The bid-to-delivery disconnect: where margin goes to die

One of the most consistent patterns I see across project businesses is what I’d call the bid-to-delivery disconnect. A project gets won on a certain set of commercial assumptions. For example, a cost model, a resource plan, or a set of margin expectations. Those assumptions live in a proposal document, or a pricing spreadsheet, or someone’s head. The moment the project moves into delivery, that information rarely travels with it in any meaningful, accessible way.

I’ve spoken with consultancies where the project manager delivering the work had never seen the original cost model. That was managed by a team on the other side of the world in a completely different timezone. They’re executing against a scope, but they have no visibility on the margin profile they’re supposed to be protecting. So when scope creep starts (which it always does), there’s no baseline to push back against. Variations get absorbed, additional work gets done, and the gap between “as-sold” and “at-completion” quietly widens.

Businesses that manage this well are the ones that have found a way to keep the commercial picture alive through the delivery phase, not just at contract award, but continuously, so that the team on the ground can see in real time whether what they’re doing maps to what was priced.

What a project performance control layer actually does

The phrase “project performance control layer” might sound like a new made-up software category that you don’t have any need for, but in reality,  it’s simple. It’s a layer of software that sits on top of and integrates with existing ERP systems, and provides continuous visibility into the things ERP can’t tell you in real time. 

Practically, that means:

• A live connection between the bid model and the delivery actuals, so the “as-sold” margin is always visible alongside the “current forecast”
• Early-warning signals when cost or schedule are drifting, before they become problems that require executive attention
• Resource visibility across the portfolio, not just per-project, so you can see bottlenecks before they affect delivery
• Automated project setup and reporting cycles, removing the admin burden that currently sits on project managers and commercial teams
• Variation and change-order management that’s tracked and auditable, not managed through email chains

The important thing to understand is that this doesn’t replace ERP. The financial record of truth still lives there. What it does is fill the gap between financial record-keeping and live operational management, where most project businesses bleed margin without realising it.

What better looks like in practice

Organisations that have implemented this kind of connected layer tend to describe similar outcomes, and they’re not always the ones you’d expect.

Yes, the reporting cycles get faster, sometimes dramatically. Month-end processes that took days get reduced to hours. That’s real, and it matters. But the more significant shift is behavioural. When project managers can see live margin data without having to request a report, they start making different decisions day to day. When commercial teams have visibility into delivery performance, they price future bids more accurately. When bid/no-bid decisions are supported by real data on which project types the firm actually performs well on, win rates improve and margin quality improves with them.

What is harder to quantify but genuinely important is the other thing that tends to happen: the relationship between the commercial and delivery teams changes. In most businesses, those two functions operate with a degree of mutual suspicion. Commercial thinks delivery gold-plates. Delivery thinks commercial under-prices. When they’re both working from the same data, that tension doesn’t disappear, but it becomes a more productive conversation.

There’s also a growing urgency to include AI in project delivery, and rightly so. Better forecasting, writing and decision support will all play a role over time. But in practice, AI is only as useful as the data it sits on. If your commercial model, delivery data, and financials are still fragmented, AI tends to amplify noise rather than clarity. The organisations seeing real benefit are the ones that have first connected their core project data, and are then layering intelligence on top of that foundation.

Where does Proteus fit in this picture?

Proteus, the platform we’ve built at Xergy, sits in this space. It’s designed specifically for engineering consultancies, not as a generic project tool retrofitted to the sector, but as something built from the ground up around the bid-to-invoice lifecycle those businesses actually run. It connects the sales and delivery phases, integrates with existing CRM and ERP systems rather than competing with them, and gives project and commercial teams a single place to see what’s actually happening on a project at any point in time.

I mention it not to pitch it but because I think it’s illustrative of a broader category of tooling that’s emerging in response to this problem. The market is beginning to recognise that the ERP-plus-spreadsheet model has a ceiling, and that engineering and energy businesses specifically need something purpose-built for the complexity of project delivery.

The real barrier isn’t the technology at all. It’s the change.

I want to end on something that doesn’t get said enough in conversations about project technology: the biggest risk isn’t picking the wrong platform. It’s buying the right one and then implementing it in a way that doesn’t actually change how people work.

I’ve seen organisations invest in genuinely capable software and still end up with the spreadsheets six months later, because the rollout didn’t address the underlying processes, or because adoption was treated as an IT problem rather than an operational one, or because the tool was configured to mirror existing broken workflows instead of replacing them. It’s a frustrating fact because it actually makes my life selling in a new system harder: once bitten twice shy is a fact!

We see that the companies that get the most out of this shift are the ones that treat it as a change programme with a technology component, not a technology programme they hope will drive change on its own. That means executive sponsorship, clear ownership of the new processes, and an honest conversation about why the old ways persist even when everyone knows they’re suboptimal.

The good news is that the friction is lower than it used to be. Modern tools in this space are genuinely easier to adopt than the clunky ERP implementations of a decade ago. They are faster to configure, easier to integrate, and increasingly designed around the day-to-day experience of the people actually running projects rather than the people in the finance team month-ending them.

But the fundamentals of change management still apply. Adoption matters more than features. Integration matters more than functionality. And getting the right data in front of the right people at the right time, consistently, reliably (and without relying on an error-prone spreadsheet) is still the thing that separates the businesses that manage projects predictably from the ones that are always a little bit surprised by how they turn out.

Colin Manson

About Proteus

Proteus developed by a Scottish-based tech company, Xergy Group, is an end-to-end project management solution developed for the energy and engineering consulting industries. 

Proteus is industry-proven and enables consultancies to meet project demands across the full lifecycle, from proposal development to project delivery. With robust sales and project delivery modules, Proteus helps its customers win more business, increase efficiencies, manage expenditures, and improve project controls.

Critical workflows, automation, and controls are integrated into Proteus. These include opportunity evaluation, proposal building, resource planning, budget tracking and forecasting, real-time multi-level restricted dashboards, and project performance analytics.

Third-party integrations and customised solutions allow Proteus’ users, which include C-suite, project leads, and engineers, to get the exact software solution needed for their business.

We offer a free onboarding consultation service to ensure your company account is set up to your company’s needs.

How to get Proteus

Proteus operates under a software-as-a-service (SaaS) model. We offer Enterprise packages and flexible pricing solutions: contact our team to learn more.

We designed Proteus to be simple, and that means you can get up and running on Proteus without an IT team or support from a programmer. You will want to spend a bit of time configuring the admin console so that you have everything set up to suit your company structure, but it’s very intuitive and you don’t need a PhD in IT.

However, we want you to get the best out of what is a brilliantly powerful tool, so don’t hesitate to ask for our support. We have a team of product experts who are ready to help you with the configuration process, so get in touch today by filling out the form below: