July 08 2025
You signed off on a £28,000 project. Now it’s £72,000. You’re over budget, under pressure, and wondering how the hell you got here. Again. Worse, everyone’s looking at you for answers.
Sound familiar? You’re not alone. But here’s what nobody tells you: this isn’t bad luck or poor planning. It’s the silent killer of automation projects lurking in every factory across Britain. Undefined expectations.
It hides in vague specifications, missing stakeholders, and those fatal “we’ll just figure it out later” decisions. Left unchecked, it eats your budget from the inside out, turning simple automation into expensive lessons in project management.
Why This Matters (And Why It Keeps Happening)
This isn’t just about money. It’s about your credibility. Blow one automation budget and you lose the trust needed to get the next one approved. Your manufacturing improvement plans stall. Competitors with better automation pull ahead. And you’re left explaining to senior management why a “simple” tank control system cost twice what they budgeted.
Research shows that 30-60% of large automation projects exceed their budgets by 25% or more. The culprit? Scope creep driven by undefined expectations. But here’s the kicker: these overruns aren’t inevitable disasters. They’re predictable consequences of predictable mistakes.
The Anatomy of a Budget Massacre: A Real Example
Let me walk you through exactly how a straightforward project becomes a financial nightmare. This happened to a client in the Midlands who brought us in after their original integrator had left them with a costly mess. Names changed, pain levels authentic.
After we helped them sort out what had gone wrong and get their project back on track, we realised they weren’t alone in facing this problem. We wrote them a comprehensive guide on how to avoid this nightmare in future projects. The lessons from their painful experience became the foundation for helping dozens of other manufacturers prevent the same costly mistakes.
The Original Brief: “Keep It Simple”
The operations manager was clear: “We need basic tank filling controls. Nothing fancy.” The brief seemed refreshingly straightforward. Basic relay-based controls with start/stop pushbuttons, high and low level switches to prevent overflow and dry running, two motor starters for filling and emptying pumps, plus manual inlet and outlet valves.
No fancy automation required. Just reliable hardwired controls in a basic electrical panel. Total quoted cost: £28,000.
The purchase order was signed. Work began. Then reality struck.
Change 1: “We Actually Need to Know How Much Is in There”
Three weeks into the project…
“Those on/off switches only tell us if the tank is full or empty. We need to know the exact level for production planning.”
Seemed reasonable, right? Just add a level sensor.
But that “simple” addition needed a continuous level transmitter, an industrial-grade device costing £400-£1,200. The existing relay panel couldn’t process analogue signals, so they added a basic display unit, modified the control panel layout, and updated all the documentation.
Cost impact: +£2,400
The operations manager felt slightly uncomfortable but signed off. “It’s still a reasonable addition.”
Change 2: “Hang On, Anyone Can Just Walk Up and Start This Thing”
Week 5…
During a safety review, someone pointed out the obvious: anyone could walk up to the basic control panel and start the system. Security risk. Safety risk. Insurance risk.
The solution? Password-protected access via an HMI touchscreen.
Here’s where everything changed. An HMI system requires intelligent control. You can’t just connect a touchscreen to relay logic. This “simple” security addition meant scrapping the relay-based approach entirely and implementing a full PLC-based control system.
The HMI panel cost £850. But the real expense was the complete system redesign: replacing relay logic with PLC programming, developing custom operator screens, programming user authentication, creating different access levels, rewiring the entire control panel, extensive testing.
What seemed like adding one component actually meant rebuilding the entire control philosophy from scratch.
Cost impact: +£8,900
The operations manager’s stomach started churning. “How did a touchscreen cost nine thousand pounds?”
Change 3: “Finance Wants Flow Data for Cost Accounting”
Week 8…
The finance team discovered they needed accurate flow data for inventory management. Another “small” addition.
At least the PLC system from the previous change could handle this more easily. An electromagnetic flow meter cost £1,400, but installation still required modifying pipework (shutting down the line), programming totalisation calculations, creating new HMI displays, and calibration procedures.
Cost impact: +£4,200
The project was now 50% over budget. Awkward conversations were happening.
Change 4: “Management Wants Weekly Reports”
Week 11…
“Can the system automatically generate weekly usage reports rather than manual data collection?”
This innocent request opened a can of worms. Data logging capabilities, report generation software, network connectivity for email distribution, database setup, integration with existing IT systems.
Cost impact: +£8,400
The operations manager was now having nightmares about the monthly budget review.
Change 5: “The Main Plant System Needs to Talk to This”
Week 14…
Someone finally realised the tank system needed to communicate with the main plant control system to coordinate production.
Protocol compatibility issues between different PLC brands, network infrastructure modifications, extensive testing, coordination with the main plant’s vendor, safety interlocks, failsafe procedures.
Cost impact: +£12,600
The Final Damage
What started as a £28,000 basic relay control project ended up costing £72,100. But here’s the real kicker: if they’d properly scoped this as a £40,000 integrated automation system from the beginning, they would have got everything they needed for £32,100 less than what they actually paid.
The most expensive lesson? That “simple” HMI request that triggered the fundamental shift from relay logic to PLC control.
But here’s the truly frustrating part: every single requirement was legitimate. Every addition made sense. Every change was justified.
Here’s What Really Hurts
If all these requirements had been identified upfront and designed as a complete system from day one, the total cost would have been around £40,000. That’s £32,100 less than what they actually paid.
Why? Because designing a PLC system with HMI, flow monitoring, data logging, and plant integration from the start is far more efficient than:
- Building a relay system (£28,000)
- Throwing it away when HMI was needed
- Rebuilding everything as PLC system
- Retrofitting each additional feature
- Reworking panel layouts multiple times
- Extending project timelines with multiple change orders
The piecemeal approach didn’t just cost more money. It cost 18 extra weeks of project time, strained relationships with the integrator, and created a system that was less elegant than it could have been.
So why did it feel like financial torture?
The Real Culprit: Undefined Expectations (Not Scope Creep)
Everyone blames “scope creep” but that’s not the real problem. The real villain is undefined expectations. Scope creep is just the symptom.
Here’s what actually happened in our example:
Nobody asked the right questions upfront. Did anyone sit down with all stakeholders and ask: “What data do you need? Who needs access? How does this integrate with existing systems?”
The initial brief was based on assumptions. “Basic tank control” meant different things to operations (start/stop buttons), finance (data tracking), IT (system integration), and safety (access control).
Each stakeholder discovered their needs when they saw the system. The finance team didn’t realise they needed flow data until they saw the project happening. IT didn’t consider integration requirements until someone asked about reports.
The relay-to-PLC shift was inevitable but invisible. As soon as anyone mentioned “user access control” or “data logging,” relay logic was dead. But nobody recognised this architectural decision point.
This wasn’t poor planning. It was predictable requirements discovery happening at the worst possible time: during implementation, when changes cost 10x more than they would upfront.
Why Smart People Keep Making This Mistake
You might think: “We’re not idiots. Why didn’t we think of this stuff earlier?”
Because undefined expectations are invisible until something forces them into the light. Here’s why they hide:
1. The Interconnected Trap Unlike installing standalone equipment, automation systems are interconnected. Change one thing, and ripple effects touch everything else. That HMI didn’t just add a screen, it changed the entire control architecture.
Most people underestimate these ripple effects because they think in components, not systems.
2. The “Simple Addition” Illusion “Can we just add a flow meter?” sounds simple until you realise it needs:
- PLC input configuration
- Display programming
- Totalisation logic
- Data storage
- Report generation
- Network connectivity
Each “simple” addition is actually a mini-project that wasn’t budgeted.
3. The Stakeholder Gap The person who requested the project (operations manager) isn’t the same person who uses the data (finance) or maintains the system (engineering) or ensures security (IT).
Different stakeholders discover their needs at different times, usually when they first see the system taking shape.
4. The “We’ll Figure It Out” Death Spiral Pressure to get projects started means deferring “details” until later. But in automation, today’s details become tomorrow’s expensive surprises.
The Hidden Cost of Undefined Expectations
Beyond the immediate financial pain, undefined expectations create problems that echo for months:
Relationship Damage: Trust erodes between departments when budgets keep climbing Project Delays: Each change extends timelines, affecting other planned work Resource Strain: Your team spends more time managing changes than delivering value Missed Opportunities: Budget overruns mean cancelling other automation projects Documentation Chaos: Rushed changes create gaps that haunt future maintenance
For our Midlands client, the £44,000 overrun represented half their annual improvement budget. Two other planned projects got cancelled. The operations manager spent the next quarter explaining budget variances instead of driving efficiency improvements.
That’s when they brought us in. After we helped them resolve the issues left by their previous integrator and implement proper project controls, we realised this wasn’t an isolated case. The systematic approach we developed for preventing these problems has since helped dozens of other manufacturers avoid the same expensive trap.
Early Warning Signs: When Undefined Expectations Are Lurking
Watch for these red flags that indicate trouble ahead:
During Initial Discussions:
- Stakeholders give vague answers like “suitable for purpose”
- People say “we’ll figure that out during implementation”
- You discover major process steps that weren’t mentioned initially
- Integration requirements are unclear or undefined
- Success criteria can’t be clearly stated
During Project Execution:
- Frequent “clarification” requests that are actually new requirements
- Stakeholders expressing surprise about system capabilities
- Change orders appearing within the first month
- Integration proving more complex than anticipated
- Multiple people saying “I thought this was included”
The Telltale Phrase Listen for: “Can we just add…”
In automation, there’s no such thing as “just adding” anything. Every addition has consequences.
Taking Control: What You Can Do Right Now
Here’s the uncomfortable truth: undefined expectations are largely preventable. The manufacturers who consistently deliver automation projects on time and budget aren’t lucky. They’re systematic about defining expectations upfront.
Immediate Action 1: Question the Control Philosophy Early Before settling on relay logic or PLC control, think about future needs. If there’s any chance you’ll want data logging, remote monitoring, or user access control, start with PLC-based systems. Yes, it costs more upfront. But it prevents that devastating architectural shift later.
Ask yourself: “What happens when someone inevitably asks for data, reports, or remote access?”
Immediate Action 2: Run the Stakeholder Gauntlet List everyone affected by the project: operations, maintenance, quality, safety, IT, finance, management. Schedule one-hour interviews with each group.
Don’t ask “What do you want?” Ask “How will this change your work?” and “What information do you need that you don’t get today?”
Immediate Action 3: Plan for the Inevitable Build change control procedures before you need them. When (not if) requirements emerge, you’ll handle them deliberately rather than reactively.
Define who can approve changes, how much authority they have, and what the process looks like.
The Bottom Line: Take Control of Your Next Project
Automation project cost overruns aren’t acts of nature. They’re predictable outcomes of undefined expectations. Every “surprise” requirement was discoverable upfront if someone had asked the right questions.
Your next automation project doesn’t have to become another budget casualty. Spend two weeks defining expectations properly, and you’ll save six months of financial pain.
Because the most expensive automation project isn’t the one that costs too much. It’s the one that destroys your credibility and kills future improvement initiatives.
The choice is yours: define expectations now or explain budget overruns later.
If you’ve ever had to apologise for a budget overrun, this is for you.
Download our Automation Project Checklist – the systematic approach we developed and used for rescuing our Midlands client from their £44k project disaster.
It’s the same guide that helps you uncover hidden requirements before they become expensive surprises. The difference between confident project approval and awkward budget conversations.
Welcome To Sull Systems 