Peter Herd | UK Business Insight All articles
Project Delivery

Five Quiet Habits That Push UK Project Costs Up (and How to Catch Them)

Peter Herd | UK Business Insight
Five Quiet Habits That Push UK Project Costs Up (and How to Catch Them)

Photo: Francisclarke, CC BY-SA 4.0, via Wikimedia Commons

Nobody sets out to waste money on a project. Yet plenty of UK projects end up costing more than anyone expected, and the reasons are rarely dramatic. Costs do not usually explode. They leak. A small request here, a delayed review there, a call that could have been an email — each one looks harmless on its own. Together they compound into a number that surprises everyone at invoice stage.

These five habits are common in small and mid-sized UK businesses. They are not signs of incompetence. They are signs of speed, informal communication and good intentions. But they cost money, and they are much easier to fix when you spot them early.

1. Scope creep by email

It starts with a friendly message: ‘While you are in there, could you also just…’ The word ‘just’ is doing a lot of heavy lifting. One extra report becomes a new data source. A small layout tweak becomes a redesign of the booking flow. Nobody formally approves anything, but the work keeps expanding.

UK example: A Manchester-based supplier is building a customer portal for a Yorkshire retailer. A marketing manager asks by email for an extra dashboard ‘for a quick view’. The supplier absorbs it to keep the relationship warm. Three weeks later, the same dashboard needs two more filters and a scheduled export. The original quote is now quietly underwater.

The fix: Use a one-line scope check. When an extra request arrives, reply with: ‘Happy to look at that. It sits outside the agreed scope, so here is the impact in time and cost.’ You do not need a formal change board. You need a consistent response that makes the trade-off visible.

2. Unclear approval chains

Projects get delayed when nobody is sure who can actually say yes. The supplier thinks the operations manager approved it. The operations manager thought the finance director had signed it off. The finance director has never seen it. Everyone is waiting for everyone else, and the meter is running.

UK example: A Bristol web agency is waiting for sign-off on a new checkout flow. The client’s project lead is on annual leave. The marketing director assumes the finance team has approved the budget. The finance team assumes the project lead has signed it off. Two weeks pass. The agency has to rebook development time and push back another client.

The fix: Name one approver and one backup at kickoff. Put it in writing. Make clear what counts as approval — an email, a signed form, a ticket comment — and what does not. If someone tries to approve outside that route, redirect them politely. Clarity here saves far more time than it costs.

3. Delayed feedback

Feedback is supposed to make the work better. Delayed feedback makes it more expensive. A two-week review turns into four. The supplier has already moved on to the next phase. When comments finally arrive, the team has to rework something that was nearly finished.

UK example: A Midlands manufacturer asks a design studio for website copy feedback. The marketing team is busy with a trade show. The comments arrive three weeks late, by which point the studio has built the pages and scheduled the launch. The changes are not huge, but they reopen design, copy and QA. The launch slips, and the studio charges for the extra round.

The fix: Agree review windows at the start and treat them as part of the project plan. Ask for one consolidated round of feedback, not a trickle of comments from different people. If a review window is going to slip, say so early. A five-minute warning is cheaper than a three-week silence.

4. Over-customisation

Custom work feels valuable. Sometimes it is. Often it is a expensive way to solve a problem that a standard option would handle perfectly well. UK small businesses are especially vulnerable here because they are close to their customers and want to say yes to specific requests.

UK example: A London-based software supplier is asked to build a bespoke reporting module for one client user. That one user wants a format that matches an old spreadsheet. The supplier builds it, then discovers the format is needed once a month. The maintenance burden is permanent. The original standard report would have done the job.

The fix: Start with the default option and prove the need. Ask what decision the customisation supports and how often it will be used. If it is genuinely important, price it separately and make the ongoing maintenance clear. Customisation is not wrong; unexamined customisation is what costs money.

5. ‘Quick calls’ with no agenda

A 15-minute call becomes 45 minutes. Three people join who did not need to be there. A decision is vaguely reached, but nobody writes it down. The next call repeats the same discussion because nobody is sure what was agreed. The cost is not just the call itself; it is the rework, the follow-up and the drift.

UK example: A Leeds-based consultancy joins a ‘quick catch-up’ with a client’s marketing and operations teams. There is no agenda. The conversation ranges from campaign timing to invoice queries to a new feature idea. The feature idea sounds approved, but it was never costed. The consultancy spends a day scoping it. The client is surprised by the invoice.

The fix: Require a two-line agenda before any call that involves a decision. End with a five-minute wrap: what was decided, who owns it and what happens next. If a call has no agenda and no decisions, it probably could have been an email. That is not anti-meeting; it is pro-clarity.

Spot the habit, not the blame

None of these habits are unusual. They show up in projects of every size, and they are easy to miss because everyone is busy doing the work. The point of spotting them early is not to point fingers. It is to change the default.

Suppliers should flag cost drivers when they see them, even when it feels awkward. Clients should ask where decisions are recorded and who approves what. A short conversation at kickoff is cheaper than a long one at invoice stage. The projects that stay on budget are rarely the ones with the most paperwork. They are the ones where the small habits are managed before they become big costs.

All Articles

Related Articles

End at 45 Past: The Meeting Reset UK Project Teams Need

End at 45 Past: The Meeting Reset UK Project Teams Need

The One-Page Record That Stops UK Projects Going Sideways

The One-Page Record That Stops UK Projects Going Sideways

The Cheap Proposal Trap: Five Questions UK Clients Should Ask Before Signing

The Cheap Proposal Trap: Five Questions UK Clients Should Ask Before Signing