In this article...
As Chief Operating Officer of RedSky’s parent company, JDM Technology Group, Mike Aspinwall has his finger on the pulse of construction. As we celebrate 50 years in business, we asked him how the industry and its software have evolved during his career, and what’s in the development pipeline.
Early Days of RedSky
Q: As the longest-serving member of the RedSky team, you were instrumental in developing the original RedSky software, back in the late ‘80s. How did that come about?
A: I first became involved in construction IT in 1986. At that point, software companies tended to build systems for specific customers with just a small amount of generic software available. They didn’t specialise in a particular industry sector so there were no ‘packages’ available for an industry like construction.

The business had just acquired another software company with around 100 staff, including a group of six who were doing all the construction stuff. We completely ignored that small group because we were focused on custom systems for large customers. Then one day in September 1986, three of its members (the two programmers and an analyst) announced out of the blue that they were leaving at the end of the week to start up their own construction software company.
We quickly called a Board meeting to decide who was going to pick up the construction side of the business in their absence. I got landed with that! I was given a Unix computer and a set of manuals to take home with me. I just had to get on with it. I found it kind of interesting, if I’m honest.
Q: What was it like to work in construction IT back then, and what were the challenges in terms of software development?
A: Strangely enough, it was both the same and different.
At that time, things were a lot simpler. The expectation was that the construction software would include the Sales Ledger, Purchase Ledger, General Ledger, Job Ledger and Subcontractor Ledger, together with a job-costed Payroll. That was the core functionality. The job costing and Subcontractor Ledger were our USP [unique selling proposition] – there was no other software around that could do this.
It was more straightforward in those days. Although a system would often support many users, the interface (a green screen) was very simple to programme because there were no opportunities for people to click randomly on the wrong part of the screen.
The biggest challenge by far was the limitations of the computer systems in terms of memory and disk space.
Q: How do those limitations compare with the capabilities that are available today?
A: Back in the late ‘80s, a typical entry machine would have a 10MB disk. A more expensive, top-of-the range version might have 20MB and programs needing to fit in 64K of memory.
That all pales into insignificance when compared with what’s available today, when entry machines routinely offer 16GB of RAM and a 512 GB disk.
When you consider that a gigabyte is a million times bigger than a kilobyte, you can imagine how frustrating the limitations were back then – for developers and customers alike.
Q: But you weren’t just dealing with limitations in terms of disk space… lack of speed must have added to the general sense of frustration?
A: Yes, we also had to contend with the huge amount of time it used to take to build the software.
I remember having to make one relatively small change at Payroll year end – it took the machine three days to compile everything and build the release. We then had to create tapes to send the software out to the 100+ customers we had at the time.
Nowadays, changes like that can be implemented very quickly – often within seconds and deployed to SaaS [Software as a Service] environments or delivered over the internet.
Q: Has the approach to software support changed much over the years?
A: Again, the answer’s not clear cut: in some ways it’s easier now, but in other ways it’s more difficult.
In the early days, a member of the Support team couldn’t connect remotely to a customer’s machine or jump onto a Teams call and start sharing screens. Instead, they would have to describe to the customer over the phone which buttons to click; and in return, the customer would have to describe what had happened on screen.
If we couldn’t resolve the problem during the call, we’d have to ask them to post a printout or back-up copy to us. We wouldn’t be able to start investigating the issue until two or three days later, once we’d received the post.
That approach and timescale are unthinkable these days. Customers can now log tickets directly onto our system or email us within a matter of minutes about an issue they are experiencing, with screenshots attached. Although that’s far more efficient than relying on the arrival of the post, it does sometimes create an expectation on the part of the customer that we will be able to jump on their email straight away and resolve their issue, there and then.
Providing an immediate response can at times be operationally challenging…
Evolution of the Industry
Q: What changes have you noticed in the construction industry in the last 30 years?
A: On the ground, in some ways not much has changed.
My house in the UK is a good example. It was built in 1906 using the same methods we use today: digging trenches, filling them in with concrete, gluing bricks together with sand, cement and water, and so on. The house was originally plumbed with gaslights in every room. That plumbing has now been replaced by wires channelled into the walls.
In a sense that’s why, at the sharp end, the physical process of construction hasn’t changed a great deal. What has changed a lot is the software, which has developed in response to customer needs.
When the RedSky team embarked on its construction software journey, customers in the UK and Ireland were very focused on the accounting side of things. They wanted to know the numbers, the costs and performance against budget, and that was it.
Since then, the focus has gradually moved away from pure accounting alone. It has branched out to include key operational processes, which can now be digitised and formalised on the system, enabling companies to track progress, issues and defects more consistently and effectively, and generally manage the process – not just the numbers on the systems.
It’s interesting to note that in regions like Australia, construction software development started not in the Accounts teams but in the site offices… so those systems had strong operational functionality and often quite limited accounting.
Q: What prompted RedSky’s move to support operational processes?
A: In the early ‘90s we started enabling customers to handle POs [purchase orders] within the system. Initially the uptake was relatively low, mainly because people were happy – and felt comfortable – with their paper-based systems.
Gradually, more and more Accounts departments started asking for better visibility on project commitments, including things like orders placed, orders delivered and orders outstanding.
Without this information, it was impossible for them to know if they were actually ‘under water’ on their projects.
Q: Was a lack of joined-up working exacerbating the problem?
A: Yes. The construction industry as a whole has been fairly slow in adopting joined-up working.
Some firms still struggle to get all their departments to pull together, to achieve broader organisational objectives. Without joined-up working, departments may be tempted to restrict the flow of information around the business, to protect their position. This silo approach has an impact on overall visibility and can create interdepartmental conflict.
Some of the more go-ahead management teams have tackled and resolved this issue, while others have not.
Current Trends and Future Outlook
Q: What about the move away from paper?
A: One of the biggest changes the construction industry has seen over the last 10 years is a radically different approach to managing the accounts payable process.
In construction companies across the UK and Ireland, it used to be paper based and heavily dependent on manual processing.
Invoices would come in by post, be photocopied and filed, then sent off to site for approval. Sometimes they ended up at the bottom of a pile of site paperwork, never to resurface. There was zero visibility in terms of outstanding commitments… unless a supplier rang to chase payment, of course.
Nowadays, many invoices are received by email. They can be scanned using an OCR [optical character reader] that populates the relevant
fields on screen; the invoice approval and payment processes follow automated workflows; and a digital copy of the invoice is stored securely on the system. It’s a much faster and more accurate approach that minimises the need for manual intervention.
Adoption of these digitised, automated methods has accelerated in recent years. I think that’s partly down to a change in attitudes since Covid, but it’s probably also because sending documents by post is now so expensive and slow, when compared to the digitised alternatives that are available.
We also see the heavy use of documentation management, so that all the construction documents are stored, versioned and searchable, again eliminating the paper.
Q: Major contractors in the UK are now carrying a heavy burden of responsibility – how has that influenced software development at RedSky?
A: The UK has taken a hard line on subcontractors for a long time. One of the reasons why main contractors need specialist construction IT is because tax collection for subcontractors had become their responsibility.
And the burden seems to be getting heavier. The government is now applying the same principle to VAT collection, with new requirements relating to CIS [Construction Industry Scheme] and PPR [Payment Performance Reporting] too. It’s all creating additional complexity, documentation and bureaucracy.
We don’t see that in other parts of the world where JDM Technology Group operates. In some countries, construction companies have to do basic reporting on subcontractors but it’s the government that charges the subcontractors for their tax.
Q: Supply chain management is indeed becoming an onerous and complex responsibility. Is that why RedSky partnered with Walls Construction to develop a robust solution?
A: Yes. Our Supply Chain Management solution is far more than a purchase-to-pay app.
It covers everything to do with the supply chain: from bringing suppliers on board and ensuring they meet the required standards; to monitoring their progress and performance; sharing out the work, to negate the risk of overloading good suppliers; and dealing swiftly with poor performance.
The knowledge-building process continues after the job is completed. Did the supplier price competitively? Did they get the job done on time? Was the quality of workmanship good? The answers to all these questions and more are recorded on the system, becoming part of an up-to-date supply chain knowledge bank that’s accessible across the business.
For many customers, RedSky’s Supply Chain Management solution is proving to be a game-changer.
Q: Another obvious change is the move into the cloud…
A: Yes, people used to be very reluctant to have a system ‘out there’ in the cloud – for many, it felt too fuzzy, too foggy, too insecure. But then Covid came and the urgent need for remote working smashed these barriers.
Most construction companies no longer have huge servers in their building, serviced by in-house IT specialists. Everything has moved to the cloud and there’s a lot more accessibility on mobile devices now.
Today, project managers and operatives can use their mobile devices to record things like work in progress, completed jobs and defects on site. But many construction companies still aren’t exploiting their system’s full potential.
We see it when we do practical demos to existing and future customers. We show them so much that the technology could do for them, but generally people only ever implement around 10% of what’s available.
Q: What about security?
A: Cyber security presents a challenge to all modern businesses.
At RedSky we took the ‘belt and braces’ approach by getting ourselves security certified (ISO 27001:2022).
The journey to accreditation was long and relatively painful. However, having come out the other side, it’s great to be able to demonstrate that we have a formal, robust process in place.
Long-Term Relationships and Future Directions
Q: Many customers have been with RedSky for 20+ years, just like yourself. How does it feel to have so many long-standing customers on RedSky’s books and what does this say about what RedSky is providing?
A: It says that we have the products – even our old ones – that meet our customers’ needs. We have then kept on developing innovative products. The move to web and mobile working has stepped up the pace significantly. Some customers have kept pace with these changes, but not all.
It also says that we have delivered a very decent standard of service to those customers. At times we didn’t get it right – for example, a few years back, we experienced some challenges on the support front and have worked hard to improve that over the years. But on balance, we have provided a good service level over many years.
Q: You certainly succeeded in keeping on top of all the legislative changes required by things like Making Tax Digital and Domestic Reverse Charge VAT…
A: Yes, the overall aim is to ensure that our products are 100% compliant and up to date.
As a business, we’re pretty good at managing this kind of stuff. That’s because we have robust processes in place for everything to do with product. Starting with a product steering process, it’s all very structured and formalised, right across the Group.
Q: Is it unusual to have such a structured approach to software development?
A: JDM has acquired several (34) software development businesses over the years, so I can say from first-hand experience that not everyone adopts this formalised approach.
In many firms, changes are sparked on an ad hoc basis by the owner of the business or sales director. They are then passed across to a developer to action (sometimes without the developer having a firm grip of what’s required or involved). Or the changes may take the form of an overly lengthy and unnecessarily complicated specification document that nobody can ever be bothered to read or understand.
That’s not how we approach software development.
Q: What is the RedSky approach to software development?
A: We bring many brains to the table, to discuss ideas openly. We encourage everyone in the business (Development, Sales, Implementation and Support teams) to put forward requests for enhancements to the system, including suggestions from customers.
The Steering Group explores the ideas put forward and decides if they are worth pursuing – either with a view to including them in the product as standard or creating a bespoke process for a customer.
We find that getting ideas from across the business and then discussing them together as a Steering Group produces a richer variety and depth of questions, along the lines of: “Have you thought about how that will affect x and y?” or “What if we did A and then B?”
We thrash out ideas up front, long before we task a programmer to create the code. This formalised process has been in place for many years at RedSky.
Q: As the Chief Operating Officer for JDM Technology Group, you have oversight of global development. What’s the grand plan for the Group?
A: The Group is one of the largest global suppliers of enterprise software for construction, operations and the built environment. Between our 34 businesses, we have a wealth of industry experience, knowledge and solutions to draw from – and share.
We have many areas of specialist expertise, ranging from 3D models and BIM [Building Information Management] to estimating. maintenance and service management. Our grand plan is to pull together all the components built by the individual businesses and make them available on a common platform.
These businesses have best-of-breed systems for their sector, in their own right. Going forward, the systems will be located in a common environment. They will use the same software and will be capable of ‘talking’ to each other.
As a Group, that will start to move us closer to the Holy Grail of software development: best of breed AND fully integrated.
Q: Will AI have a role to play on the common platform you’re developing?
A: Yes, we will be incorporating AI on the common platform. It’s currently at the internal development release stage and looks rather like a WhatsApp chat.
Drawing from the information in the system, AI will provide customers with fast responses to questions like: “What are the costs to date on the University project?”, “Where is digger number three?” and “Who are our top 10 debtors?” Using AI to access these ‘shortcuts’ will be very useful for our customers.
The AI we’re currently building out won’t be able to provide predictions. Not yet, anyway.
Customers will be able to ask questions about the anticipated profit on a job, because that can be based on the facts of the project, like forecast cost to complete.
But they won’t be able to obtain responses to questions like: “Will the Bruton Hall project be successful?”
Predictions like these are not realistic at this stage. That’s because they require data to have input into the system that quantifies if historical projects were a success. They also require detailed information about what the actual work was, how the project was tendered, who was managing it, and so on. Although that sort of data could have been entered by customers, we rarely see it in practice.
We also share customers’ concerns about data confidentiality, so we don’t expose the bulk data needed for those predictions to the AI.
We’re focusing on ‘keeping it real’. We won’t be giving AI no-holds-barred access to user information; the AI will only be able to access data related to the information directly requested by the user.
Final question: What does the future look like for the Group – and for RedSky and its customers in particular?
A: The JDM Technology Group is uniquely positioned for a very bright future. As a Group member, so is RedSky – and so, by extension, are its customers.
ABOUT MIKE ASPINWALL
Mike’s background is in the design and development of business application software. He graduated from Cambridge in 1983 with an engineering and computer science degree and has spent almost 40 years in the construction software industry.
As Development Director for RedSky, Mike was the driving force behind its award-winning construction-specific ERP solution. In 2007 Mike was appointed Managing Director for RedSky, with responsibility for its operations in the UK, the Republic of Ireland and the Middle East.
Today, Mike is the Chief Operating Officer for JDM Technology Group. He oversees global development for the company, including its European, North American and Australasia divisions.
