The most expensive spreadsheet in construction is rarely the one with the flashiest formulas. It is the one quietly circulating among 40 people, each certain that their copy is current. A revised budget sits in finance. A field photo lives on somebody's phone. The reason a change order was approved is entombed in email. At project handover, the people who must operate the building receive a heroic dump of files and a polite wish of good luck.
Kahua exists for that mess. The Alpharetta, Georgia, company sells a cloud project-management information system, or PMIS, for organizations running complicated capital programs. Its platform connects planning, sources of funds, bids, contracts, costs, documents, approvals, schedules, field records, analytics and asset handover. The buyers are owners, public agencies, program managers, general contractors and specialty contractors. The product is less a digital clipboard than the institutional memory of a building program.
The unusual part is not the checklist of features. Rivals can produce very long checklists too. Kahua's argument is architectural: keep the data, permissions and audit record consistent, but let each organization configure the forms, workflows, language and reporting that sit on top. A school district does not approve money like a retailer opening 30 stores. A federal agency cannot govern files like a small commercial builder. Kahua would rather bend than make all three pretend they are the same customer.
01 / The second foundation
They had already built the first version
Co-founders Scott Unger and Brian Moore did not arrive as tourists carrying a deck about digitizing construction. They had built Constructware, an early internet-based construction project-controls business that Autodesk acquired in 2006. Unger also came from commercial contracting; Moore trained as an industrial engineer. By the time they founded Kahua in 2009, they knew both the software and the arguments that erupt around it.
What failed first was the fixed foundation of conventional SaaS. Their earlier product helped move an industry from local networks to the web, but a mature software stack accumulates assumptions. A workflow that feels universal when designed becomes a constraint when a customer's process changes. Rebuilding the base years later is like trying to move the elevator shaft after tenants have arrived.
Software should work the way you do.Kahua's founding idea
That realization changed their minds about what the second company should sell. Kahua would not merely ship another set of prescribed workflows. It would provide a low-code platform on which customers and certified partners could alter existing applications or build new ones. The name is not coy: kahua is a Hawaiian word for platform or foundation. Moore has compared the model to Lego - supply sound pieces and examples, then let the user assemble what is needed.
This is the first lesson worth stealing. When customers disagree about the final workflow but agree on the underlying objects, productize the objects. Keep identity, security, records and reporting stable. Make the messy operational layer configurable. That is harder than writing a form builder, but it can turn customer eccentricity from a roadmap crisis into part of the product.
02 / What the buyer gets
One record, fewer scavenger hunts
Kahua's customer list explains its shape. The company cites CBRE, Clark Construction, Floor & Decor, the Pennsylvania Turnpike Commission, public school districts and the U.S. General Services Administration. These organizations oversee many projects, many outside firms and many kinds of money. Their pain is not simply assigning tasks. It is knowing which budget, approval, drawing and forecast is authoritative across an entire portfolio.
Floor & Decor, for example, needed more consistent visibility while expanding. Reporting was manual, documents had to stay connected to the right cost entities and a large migration could not interrupt current projects. Its published case study says Kahua linked analytics and accounting information, automated workflows and supported hundreds of vendors and users. An executive there said embedded permissions eliminated the need to generate separate reports for different audiences.
Clark Construction selected Kahua after reviewing its systems and processes, seeking something that could meet current requirements and adapt later. On the Chase Center project in San Francisco, a Clark executive described the value in simpler cost-change management and earlier visibility into issues. Pennsylvania Turnpike Commission emphasized the opposite side of the same coin: it could build applications around its business process instead of tailoring the business to the system.
The record follows the asset
That last handoff is a particular Kahua obsession. Most project software is optimized for the temporary team that builds the asset. Then the team disperses and an operator inherits a building with thin context. Asset-Centric Project Management, Kahua's trademarked approach, collects equipment and facility information as work proceeds so operations receives usable records on day one. The company is selling continuity through the least glamorous moment in the lifecycle.
03 / The new machinery
AI, but inside the fence
In May 2026, Kahua launched Noa, an AI assistant embedded in the platform. The practical jobs are deliberately ordinary: find an authorized project record, summarize information, create a record, reduce repetitive entry and help users build apps or workflows in plain language through kBuilder Canvas. The more consequential detail is where Noa operates. It inherits the platform's roles, permissions and project context instead of asking employees to ferry sensitive documents into a public chatbot.
A month later, Kahua announced federal approval to deploy AI inside its FedRAMP-certified boundary. The platform also reports ISO 27001 certification and SOC 2 Type 2 compliance. For a consumer app, this would sound like plumbing. For an agency or defense contractor handling controlled information, the plumbing determines whether the tap can be turned on.
Kahua is also connecting the digital record to physical evidence. kCapture brings 360-degree site imagery into project workflows, pins conditions to drawings and preserves a visual timeline for progress, changes and later operations. Together, Noa and kCapture extend the original thesis: the system becomes more useful when new tools live beside the governed record rather than creating another island of data.
The distinction matters because construction AI has an input problem before it has an intelligence problem. A model cannot produce a trustworthy forecast from five versions of the same budget. It cannot explain an approval whose rationale disappeared into a departed consultant's inbox. The mundane work of structuring records, controlling access and preserving history is what makes the glamorous layer possible. Kahua spent years selling the filing cabinet before asking the filing cabinet to answer questions.
There is sensible restraint in the rollout. Noa's published capabilities are framed as assists, searches and record actions, with human review and existing permissions still in force. The platform is not being presented as an autonomous superintendent. Construction decisions carry safety, contractual and financial consequences; a confidently invented answer can become a claim. Kahua's governed approach will still depend on current source material and disciplined users, but it gives buyers a clearer place to assign responsibility.
The moat is not a dashboard. It is the history underneath the dashboard.YesPress analysis
04 / The bill and the bargain
Enterprise software costs more than the license
What does Kahua cost? For most commercial customers, there is no universal sticker. The company quotes based on organization type, program scale, package, deployment environment and implementation requirements. Buyers choose packages for owners and program managers, general contractors or specialty contractors, then add applications, integrations, migration, training and configuration. Historical federal schedules publish line-item annual prices for specific products, but those figures are contract artifacts, not a reliable quote for a private buyer in 2026.
The more honest cost includes attention. Someone must decide which process deserves to survive, clean the data, settle permissions, manage integrations and persuade busy project teams to use the system. Low-code reduces the need for conventional development; it does not abolish governance. Kahua's network of more than 500 certified partners is partly a distribution engine and partly an admission that complex software needs skilled implementation.
The business model follows that reality: recurring enterprise subscriptions, specialty applications and professional services, with partners extending delivery. Public company data is unavailable because Kahua is privately held. A supplied third-party company record estimates about $23.7 million in annual revenue and roughly 390 employees, but neither number is audited public reporting. The firm has raised venture funding over several rounds, including a reported $7 million Series A in 2015 and a $16.36 million round recorded in 2021; its valuation is not public.
Its achievements suggest the niche has room. Kahua appeared on the Inc. 5000 in 2024, 2025 and 2026. The latest listing put it at No. 2,359 and cited 142 percent three-year growth. In 2025, the company said 16 federal agencies trusted its platform. Those are useful signals, not proof that every rollout succeeds. Enterprise software announcements tend to celebrate selection day; the difficult evidence arrives later in adoption rates, clean migrations and fewer hours spent assembling reports.
Copy this
Standardize the trusted data layer. Let customers configure the operational edges. Build implementation partners before services become the bottleneck.
Skip this when
Your team is small, the workflow is ordinary, compliance is light or nobody owns configuration after launch. Flexibility without stewardship becomes clutter.
05 / Where it lands
A platform for the complicated buyer
Kahua sits in a crowded field with Procore, Oracle Primavera Unifier, Trimble e-Builder, Autodesk Construction Cloud, PMWeb and InEight. Procore has broad contractor recognition and a large ecosystem. Oracle carries deep scheduling and enterprise credentials. Autodesk can connect design and construction tools. Kahua's sharpest case is for the owner or delivery organization that values configurability, controlled data, portfolio reporting and regulated deployment more than a standardized out-of-the-box routine.
The company also uses specialization as a route into the market. Its packages and partner offerings address federal work, education, healthcare, transportation, retail, utilities and public-private infrastructure. Aprio brings CMMC advisory expertise for defense contractors. OnIndus focuses on implementation and return on investment. WSP selected Kahua for Canadian real-estate development program management. Superset Infrastructure adds knowledge of alternative-delivery and P3 programs. The pattern is repeatable: pair a horizontal platform with people who speak a buyer's regulatory and operational dialect.
That case does not work everywhere. A small contractor with repeatable jobs may get faster value from simpler software. A company hoping the platform will repair unresolved process disputes will merely digitize them. A buyer without a product owner, training plan or data discipline can turn configurability into an expensive attic of abandoned forms. Kahua is strongest when complexity is real, durable and worth governing - not when complexity is simply fashionable.
The founders' second act now looks less like a rejection of SaaS than a correction to it. Standard cloud software made deployment easier by deciding how work should happen. Kahua accepts that construction's largest programs cannot always be flattened into one template. It keeps the foundation firm and lets the rooms move. For people responsible for billions in capital, that is not a poetic distinction. It is the difference between a record they own and another spreadsheet they have to chase.
Keep digging