Kahua's $1bn Moment: The Platform Bet In A Market That Will Never Just Have One Standard

“We knew we were the number one asset in the space”, Scott Unger, CEO and co-founder of Kahua, told me, a week after Bain Capital Tech Opportunities announced a minority growth investment in the construction platform at a valuation above $1 billion. Bain Capital has been studying this market for a decade, and courting Kahua for around six years, said Unger; it has clearly done its homework.

With $100 million in annual revenue, more than 2,500 customers and over $400 billion in capital programmes using the software, the numbers appear solid. The structure of the deal tells us even more. Most of the money is “not going on our balance sheet” – the deal is mostly about allowing longer-standing investors to sell down shares – and Bain Capital’s stake sits below 25%. Why only a minority? Because, says Scott Unger, “our greatest growth is still ahead of us”. Every CEO says that, of course. However, given that Verdantix sees market growth for construction management software hovering around 10% in many markets, with the Bain Capital injection and its platform play, the firm has a good shot at turning this optimism into reality.

Platform, not product

Scott Unger’s case for Kahua’s “right to win” is architectural. Rather than one fixed Software as a Service application, Kahua describes itself as a low-code platform as a service, configured for sub-verticals as different as healthcare, defence, energy and mining – and then re-configured as those processes change. He calls it “continuous implementation”, a departure from only installing and revisiting software as part of a procurement cycle.

It’s a good pitch – but it’s not a unique one. Almost every vendor in real estate and building tech now calls itself a platform, and “no one else is doing it” is a claim that deserves some scrutiny. Configurability isn’t free, either: someone has to do the configuring, and Kahua leans on around 500 partners to deliver services.

However, tailoring the product to industry-specific needs sits well. One-size-fits-all offerings have “no chance” with project owners, posits Scott Unger – whose previous company Constructware was sold to Autodesk in 2006 – “there’s not going to be any one system of record on a project”. Owners, general contractors, architects, subcontractors and suppliers all run their own system, their own way. Kahua’s answer is to network those separately configured systems, so each party chooses which data, documents and workflows to share. This is the part that makes the most sense for me and hangs well with the CDE-fever that the rest of the industry has caught. With every stakeholder using different tools, vendors will either have to be genuine platforms that play well with everything around them, or offer a common data environment (CDE) good enough that every party is willing to work in it. One standard for the whole project ecosystem? It isn’t coming, and AI says it doesn’t have to.

Transparency needs accuracy

The project-owner-as-buyer is the second driver behind the platform’s tailoring, as owners are now “forced” to have these systems for reasons of transparency and to enforce accountability. And with owners as the ultimate source of project funds, their choice of system and tools will be pushed down through the layers of the project pyramid. As Scott Unger put it, “who has the gold makes the rules”.

But transparency is only as good as the data underneath it, and can be especially risky if all the data are owned by a varied group of contractors. If owners are going to be held to account on the numbers in their systems, those numbers had better be right – a reason why plenty of people in the industry are still uncomfortable about automating too much, particularly in regulated settings.

So start small. Scott Unger pointed to using photos to generate the punch list log and to submittals, where project specifications are turned into submittal logs. With claimed time savings of more than an hour a day, the savings add up. These are bounded, checkable tasks – the easiest place to build trust before handing the software anything more consequential.

The question left open

I asked Scott Unger whether he sees big changes coming for services in AEC as AI takes on project controls, reporting and document management. The answer focused on the digitization of the market and the inevitability of AI, not on what happens to the consultants and integrators doing that work today. For an organization with hundreds of service partners, that is the question to watch.

Bain Capital’s money confirms there is serious appetite for owner-side construction software. Whether Kahua lives up to its “number one” billing depends on two things: proving that configurability scales without ballooning implementation costs, and convincing owners to trust automated data enough to act on it. In a market that will never settle on one standard, can Kahua become the system every other system is willing to talk to?

For more analysis on the AEC market, check out Verdantix Insights.