Growth is typically a good problem to have. More projects, more people, new locations and larger clients are all signs that a construction business is moving in the right direction.
But growth also has a habit of exposing weaknesses that were easy to live with when the business was smaller.
Technology is a good example. A finance system gets introduced because finance needs it. Project teams adopt applications that work for them. Microsoft 365 becomes part of everyday working. SharePoint is introduced for documents and collaboration. Specialist systems appear for particular operational requirements. And wherever there is a gap between them, someone creates a spreadsheet.
Nothing is necessarily wrong with any of those decisions. But the problem is that, after several years of growth, the business can end up with a collection of perfectly reasonable individual systems that don’t work particularly well together.
That is when disconnected technology starts becoming more than an IT inconvenience. It begins affecting how easily the construction business itself can operate and grow.
How Construction Technology Becomes Fragmented
Very few construction companies sit down and consciously decide to create a fragmented technology environment.
It happens gradually. A requirement emerges, so an application is introduced to solve it. Another department has a different requirement, so another solution is added. An acquisition might bring additional systems into the organisation. A major customer could create new reporting requirements. Or a process that doesn’t quite fit the available technology gets managed through Excel instead.
This can work surprisingly well for a long time. People know how to navigate the environment. Experienced employees understand which spreadsheet contains the right information. Teams develop processes for moving information from one system into another.
Then the business grows. Suddenly there are more people involved, more projects running simultaneously and much larger volumes of information moving around the organisation. The informal connections between systems start coming under pressure. What worked when ten people understood the workaround becomes considerably more difficult when 50 people need to follow it.
That’s often the real point at which disconnected systems become a business problem.
What Do Disconnected Systems Actually Look Like?
The symptoms aren’t always dramatic. In fact, one reason technology fragmentation can continue for so long is that everything appears to be working. Finance can still produce the numbers. Project information can still be found. Reports still get created. People can still collaborate. It simply takes far more effort than it should.
A commercial team might pull information from one system and put it into Excel before finance can use it. Someone might spend several hours every month creating a management report by combining information from different sources.
Project information might technically be available, but finding the latest version means checking SharePoint, Teams, email and a project application’s document store. Employees may repeatedly enter the same client, supplier or project information into different systems. Individual teams develop their own way of working because the technology environment doesn’t provide a consistent one.
These are not catastrophic failures. They are small points of friction that accumulate across the organisation. And that accumulation matters.
When Excel Starts Holding Everything Together
It’s easy to blame spreadsheets for technology problems, but that misses the point.
Excel is an enormously useful business tool. Construction companies will continue using spreadsheets regardless of how sophisticated their technology becomes. The question is what are those spreadsheets are being asked to do?
There is a big difference between using Excel to analyse information and relying on a spreadsheet to compensate for systems that don’t communicate. If employees routinely export data from one platform, manipulate it in Excel and then upload or re-enter it elsewhere, Excel has effectively become the integration between those systems.
If critical reports depend on spreadsheets maintained by one or two employees, there is also an obvious continuity issue. And if the organisation needs another workbook every time it launches a new project, acquires a company or introduces a service, growth is effectively multiplying the amount of administration required.
The objective therefore shouldn’t be to get rid of spreadsheets. It should be to stop using them to solve problems that should really be addressed by the underlying technology.
Reporting Is Often Where The Problem Becomes Visible
Disconnected systems frequently reveal themselves most clearly when a construction business tries to understand its own performance. The data exists. Finance has financial information. Project teams have project information. Commercial teams have their information. Operations have theirs.
But can leadership easily see the complete picture?
If producing a management report requires several people to collect, reconcile and manipulate information before anyone can begin analysing it, the reporting problem may actually be a systems problem. The same applies when different departments are looking at different versions of apparently identical information.
Once leadership starts questioning which number is correct, technology fragmentation has moved beyond an inconvenience. It begins affecting confidence in decision-making.
Better Connections Create Better Visibility
The commercial argument for connecting construction technology isn’t simply that it saves employees a few administrative hours. The more important benefit is visibility. A better-connected environment can make it easier to understand what is happening across projects and operations without repeatedly assembling the picture manually.
It can also improve collaboration between office teams and people working across sites. That doesn’t necessarily require one enormous system managing everything – a connected technology strategy can still involve specialist applications.
The difference is that each system has a clear role and information can move appropriately between them. Microsoft technologies can play an important role here. Microsoft 365 and SharePoint can support communication, collaboration and information management. Power Platform can help connect systems and automate processes. Dynamics 365 applications can support core business processes where appropriate.
But adding Microsoft technology to a fragmented environment doesn’t automatically make that environment connected. The architecture still matters.
Do You Need To Replace Your Systems?
Not necessarily. This is where construction companies should avoid jumping too quickly from recognising a problem to buying new software.
There are three broad questions worth asking.
Can You Connect What Already Works?
If the existing applications perform their individual roles well, integration may be the answer.
That could involve APIs, Power Platform or other integration technologies that allow relevant information to move between systems.
In this situation, replacing everything could create considerable cost and disruption without addressing a fundamental weakness in the existing applications.
Could You Rationalise The Environment?
Sometimes the problem is duplication. Perhaps two departments have adopted applications that perform broadly similar functions. Multiple document repositories may have developed. Or an application introduced for a temporary requirement has gradually become part of the permanent technology landscape.
In these circumstances, rationalisation can simplify the environment before any additional technology is introduced.
Is Something Genuinely Holding The Business Back?
Sometimes the answer really is replacement.
A legacy system may no longer integrate effectively. An application designed for a much smaller business might struggle to support current requirements. Reporting may be fundamentally limited or remote access poor.
Businesses shouldn’t preserve an unsuitable platform simply because considerable time has already been invested in it.
The objective is to distinguish between a connection problem and a technology problem. They require different solutions.
Think About The Business You’re Becoming
Perhaps the most useful way to assess the current environment is not to ask whether the technology works today.
Ask whether it will work if the business continues growing.
- What happens if project volumes increase significantly?
- Could another office or business unit be incorporated easily?
- Would another 50 employees mean another layer of spreadsheets and manual processes?
- If the business acquired another contractor, how difficult would systems integration become?
- Would management maintain the same visibility as operational complexity increased?
Technology strategy should be based on the organisation you’re becoming, not simply the one you are today. If growth means multiplying existing inefficiencies, those inefficiencies will eventually begin constraining growth itself.
Connect. Modernise. Apply AI. Protect.
For construction companies, better technology doesn’t necessarily mean more technology. It means understanding what already works, where the gaps exist and what needs to change.
Connect systems and information where fragmentation is creating unnecessary friction. Modernise technology that genuinely limits the business. Apply AI and automation where they can remove repetitive administration or help people work more effectively with information. And protect the increasingly connected people, systems and information on which the business depends.
Akita’s Construction Technology Review provides an opportunity to step back from individual products and look at that bigger picture, identifying where disconnected systems are creating complexity, where technology could be modernised, where AI and automation could add practical value, and where security needs strengthening. Get in touch to arrange a review:
Request A Technology Review
