Funding 7 min read

Kahua Hit $100M in Annualised Revenue, and Bain Capital Priced It Above $1 Billion

A minority growth investment from Bain Capital's Tech Opportunities, announced 29 September. Kahua's own release gives no figure; Bloomberg put it at around $250 million. The company says it serves more than 2,500 customers and carries more than $400 billion in capital programs — and the cheque is signed on the owner's side of the contract.

The upper floors of a steel-framed high-rise under construction, wrapped in white safety netting, with three tower cranes above it and a flock of birds crossing a pale sky.

Kahua announced on 29 September that it has taken a minority growth investment from Bain Capital’s Tech Opportunities at a valuation above $1 billion. The company’s own release — and the same release on Bain Capital’s site — frames the round around a revenue milestone rather than a cheque: the subhead describes the investment as accelerating Kahua’s next phase of growth “following its achievement of $100 million in annualized revenue”.

Neither copy of the release says how much money changed hands. The wider record does. Bloomberg reported the figure at around $250 million on the day of the announcement, in reporting relayed by Bisnow via Yahoo Finance, which also put Kahua’s prior valuation at roughly $100 million following a 2019 round. We have not independently confirmed either number against a primary document, and both are reported here as the outlets’ figures rather than the company’s.

What Kahua did disclose itself is the shape of the business. It says it serves more than 2,500 customers and supports more than $400 billion in capital programs on its platform.

The Side of the Industry This Is On

Construction-software funding tends to follow the delivery side — the contractor, the crew, the drawing, the invoice. Kahua’s centre of gravity is on the other side of the contract. Its primary buyer is the organisation paying for the building — the transit authority, the health system, the school district, the federal agency, the hyperscaler — though its “Who We Serve” menu also addresses general, specialty and defence contractors as delivery participants, and Bain’s Meicler describes the platform as a backbone “for owners and delivery teams”. In that market the unit of work is not a project but a program — a multi-year portfolio with appropriated funding, statutory reporting obligations and a public auditor at the end of it.

The release describes the problem in those terms, and the language is worth reading as a sales thesis rather than a complaint. Capital programs in “highly regulated and mission-critical environments, including federal government and defense, transportation, healthcare, and education, are becoming larger and more complex”, it says, while “many organizations still manage these multi-year programs across fragmented systems and disconnected processes.”

That is the owner’s version of the integration problem, and it is a materially different problem from the contractor’s. A general contractor wants the field and the office to agree. An owner wants funding to agree — the appropriation, the budget, the commitment, the change order, the forecast and the handover record, across dozens of simultaneous projects run by dozens of different delivery teams, in a form that survives a legislative audit years later. Kahua’s product line reads accordingly: capital planning and sources of funds at the top, cost and change control in the middle, portfolio analytics and asset handover at the end.

The Multiple, and What It Implies

Put the two disclosed figures next to each other and the arithmetic is simple, if coarse: a valuation above $1 billion against $100 million in annualised revenue is a multiple of more than ten times revenue. That is our own calculation from the release’s two numbers, not a figure either party published.

Ten-plus times is not a remarkable multiple for enterprise software in 2026. It is a notable one for this corner of it, because owner-side program management has tended to be treated as sticky, slow-growing infrastructure software rather than as a growth asset. The customers are public bodies with procurement cycles measured in quarters and switching costs measured in years. Revenue is durable and expansion is gradual. That profile normally earns a lower multiple than a fast-growing contractor-side SaaS business, not a higher one.

Bain’s stated reason for paying it is the data position, not the growth rate. “Kahua has built the technology backbone for owners and delivery teams, connecting critical data across the full asset lifecycle—from funding and planning through construction and long-term operation,” says Philip Meicler, a partner at Bain Capital Tech Opportunities, in the release. The claim underneath that is a claim about AI: the release argues that as “a connected system of record, Kahua provides the governed data and context needed to make AI useful within the workflows where customers plan, manage, and make decisions across the asset lifecycle.”

This is the most interesting sentence in the document, because it concedes the sequencing. The asset being bought is not a set of AI features. It is the governed record that AI features need in order to be worth anything — and the governance is what makes it defensible. Kahua’s AI surface (Kahua AI, the kBuilder Canvas workflow builder, and the kCapture reality-capture product launched in August) sits on top of that record rather than beside it.

Scott Unger, Kahua’s chief executive and co-founder, puts the company’s own emphasis on the revenue line. “Reaching $100 million in annualized revenue is a milestone of which we are incredibly proud. It reflects the trust of our customers and the strength of our team,” he says in the release. He adds that the partnership is intended to “accelerate our AI capabilities and product innovation, deepen the value we deliver to customers, and invest in the talent needed for Kahua’s continued growth.”

Who Actually Runs On It

Neither release names a single customer. That is a conspicuous omission in a document that leans on “2,500 customers” and “$400 billion in capital programs” and it is the part of this story worth being careful about, because an unverified customer name is the most expensive kind of error a trade publication can make.

One can be confirmed from the customer’s own side. The New York City School Construction Authority runs a system it calls CAMP — Construction and Architecture Management Platform — and the authority’s own user-facing training and access pages refer to it in parentheses as “CAMP (Kahua)”. That is the authority documenting its own software to its own contractors, which is about as good as a customer confirmation gets.

Beyond that, Bisnow’s report names the Port Authority of New York and New Jersey and John F. Kennedy International Airport among Kahua’s clients. We found no primary confirmation of either and are not treating them as established; they are the outlet’s reporting, not ours.

If Bisnow’s two are right, the pattern across the three — large public transport and education owners in a single dense metro — is consistent with how this category sells. Owner-side program software spreads by agency reference within a jurisdiction, because the procurement officer at one authority reads the award notice from the one next door.

The Compliance Run-Up

The five months before this investment look, in hindsight, like a company assembling the paperwork that owner-side buyers require. Kahua’s newsroom records, in order: embedded AI inside the project management platform in May, a FedRAMP posture for running AI inside a federal boundary in June, the kCapture reality-capture launch in August, and on 22 September — a week before the Bain announcement — a BSI Kitemark certification for ISO 19650 information management.

That last one is the tell. ISO 19650 is the international standard for managing information across a built asset’s lifecycle, and a Kitemark against it is not a product feature — it is an answer to a question on a procurement form. It belongs to the same genre as Aurigo’s ISO/IEC 42001 certification, which the Austin capital-program vendor announced on the same day — certificates aimed at the procurement section of a request for proposal rather than at the end user.

Two capital-program software companies producing governance certificates on the same day looks less like coincidence than like a response to the same buyer: public bodies that have been told to adopt AI and simultaneously told to be able to justify it.

What To Watch

Three things, none of which the release answers.

Whether the $250 million number holds. It is Bloomberg’s figure, not Kahua’s, and minority growth rounds are frequently reported in ranges that firm up later. The valuation floor — “above $1 billion” — is the company’s own words and is the sturdier of the two claims.

Whether owner-side consolidation follows. Procore agreed to pay $845 million for DroneDeploy to extend down into the field, and Accenture spent the same September folding eleven acquisitions into a single capital-projects business aimed squarely at large owners. A newly capitalised Kahua at a billion-dollar valuation is a buyer as well as a target.

Whether “governed data” turns into a defensible moat or a slogan. Vendor after vendor in this category now argues that its system of record is the prerequisite for useful AI. Kahua has a stronger version of the argument than most, because the records it holds are funding records and the customers are auditable. But the argument is currently a thesis, and the next twelve months of product — not the valuation — are what will settle it.