The question of what it takes to achieve and sustain growth is not theoretical. It is a daily operating concern across multi‑billion‑dollar infrastructure portfolios, where AI deployment and investment must translate into measurable improvements in resilience, efficiency, and citizen experience rather than isolated proofs of concept.
AI‑driven growth stalls whenever we treat AI as an experiment rather than a capital programme. Cost and capex initiatives are governed with hard gates, weekly tracking, and executive accountability. AI initiatives are too often launched with a press release and left to drift.
Our own experience building and scaling platforms such as KELIX, digital twins, and integrated operation centres shows that sustainable impact comes only when an AI strategy is subjected to the same discipline as long‑term infrastructure investment.
In the built environment, city authorities and asset owners commission pilots for computer vision, generative design, or conversational agents. These pilots demonstrate potential, then stall at the edge of the organisation. The issue is rarely model performance. The issue is that the AI strategy is not backed by an operating architecture capable of carrying it from proof‑of‑concept to portfolio‑wide deployment.
Common failure modes include:
- AI programmes are framed as “innovation experiments” rather than as part of the core capital plan.
- No clear owner for AI value realisation at a portfolio or enterprise level.
- Underinvestment in data infrastructure, security, and change management compared with the investment in models and vendors.
- No baselined KPIs, so success is argued anecdotally rather than evidenced.
In engineering and urban operations, this is particularly acute because most of the value sits in cross‑cutting optimisation (across assets, disciplines, and time horizons), not in single‑use tools.
Method 1: Treat AI as a Capital Programme, Not a Pilot
Our approach begins with treating AI programmes in the same way as a major infrastructure or systems upgrade:
- AI roadmaps are integrated into the long‑term capital plan, with multi‑year budgets rather than annual discretionary spend.
- Each AI initiative (for example, KELIX‑enabled design-review automation or digital-twin-driven asset optimisation) has a defined investment case, a forecast benefit profile, and explicit acceptance criteria.
- Governance follows a stage‑gate pattern: concept, prototype, controlled deployment, and portfolio roll‑out. Progression between gates is contingent on evidence, not enthusiasm.
This reframing from “innovation” to “capital programme” forces rigour in design, resourcing, and sequencing. It also sends a signal to internal teams and external partners: AI is not an optional extra; it is a core part of how Meinhardt and its clients will design, deliver, and operate assets.
Method 2: Build a Portfolio of AI Use Cases Across Horizons
AI deployment is structured as a portfolio rather than a collection of isolated tools. The portfolio intentionally spans three horizons:
- Core horizon : Use cases that improve existing work in design, project management, and operations (for example, generative review checklists, RAG‑based access to standards, and computer vision for construction progress tracking).
- Adjacent horizon : New services made possible by AI, such as digital twin‑enabled advisory, predictive maintenance for client portfolios, or AI‑augmented control room operations.
- Transformational horizon : Longer‑dated bets such as adaptive urban platforms, AI‑optimised regulatory workflows, or autonomous optimisation across multiple infrastructure systems.
Each horizon is governed differently. Core use cases are expected to achieve positive ROI rapidly and be widely deployed. Adjacent and transformational use cases are sized and governed more like venture investments: smaller at the outset, with staged increases in investment as evidence accumulates.
The portfolio is reviewed periodically to ensure capital, engineering capacity, and data investments align with the most promising opportunities.
Method 3: Establish an AI Operating Model with Clear Ownership
AI growth fails when responsibility is diffused. We should address this with an explicit AI operating model:
- A central AI and innovation function defines reference architectures (for example, for RAG, Graph RAG, and digital twins), common platforms (such as KELIX), and governance policy.
- Domain teams (transport, water, buildings, industrial, urban planning) own specific AI use cases and KPI outcomes within their portfolios but operate on shared standards and infrastructure.
A cross‑functional steering mechanism arbitrates priorities, allocates scarce talent, and ensures that local initiatives do not diverge from the enterprise architecture.
This model avoids two extremes: fully centralised AI, which cannot understand domain nuance, and fully fragmented AI, which produces conflicting tools and duplicated effort. It also ensures that growth in AI usage is accompanied by growth in consistency, security, and maintainability.
Method 4: Apply Infrastructure‑Grade Governance to AI
Infrastructure and city‑scale projects operate under stringent regulatory, safety, and contractual obligations. AI must match that standard. Our deployments embed governance into the architecture rather than adding it as a procedural overlay:
- Access control and role‑based permissions around models and data.
- Data lineage and provenance , particularly for RAG and Graph RAG systems where decisions may be audited later.
- Model lifecycle management , including versioning, testing regimes, rollback mechanisms, and defined change windows.
- Risk classification of use cases , with clear boundaries between advisory, decision‑support, and autonomous actions.
Governance here is not only about compliance. It is about ensuring that AI‑driven growth is survivable under scrutiny from regulators, clients, and the public. Without this, any short‑term growth in AI usage is brittle; one adverse incident can stall adoption across an entire organisation or sector.
Method 5: Define and Track Return on AI Investment and Return on Employee
One of the fastest ways to stall AI growth is to measure it poorly. Traditional ROI calculations are often too narrow, focusing only on direct cost savings or licence costs. For AI in engineering and urban operations, we apply a dual lens:
- Return on AI Investment (RoAI) : Comparing the total cost of AI platforms (infrastructure, licences, data engineering, change management) against quantifiable outcomes such as design turnaround time reductions, fewer RFIs, lower unplanned downtime, improved asset performance and reduced lifecycle cost.
- Return on Employee (RoE) : Measuring how AI changes the productivity and effectiveness of engineers, planners, and operators. This includes time released from repetitive tasks, quality of design or decision outputs, speed of iteration with clients and regulators, and the ability to manage larger or more complex portfolios without proportionate headcount growth.
By baselining these metrics before deployment and tracking them through the life of the programme, Meinhardt ensures that AI growth is tied to tangible performance rather than anecdotal success stories. This also provides a basis for reinvesting gains into further AI capability and workforce development.
Method 6: Invest in Talent Rotation and Capability Building
AI investment fails when it is seen as a technology procurement exercise rather than a capability‑building agenda. Meinhardt treats AI growth as a talent strategy:
- High‑potential engineers, planners, and operations staff are seconded into AI initiatives to embed domain knowledge into solutions and to build AI literacy back into their home teams.
- Communities of practice are created around key domains (for example, Graph RAG for codes and standards, digital twins for specific asset classes, or AI‑supported design review) to diffuse methods and reusable components.
- Career pathways are established that recognise AI‑augmented roles rather than treating AI work as a side activity.
This approach ensures that AI‑enabled growth is sustainable. The people who will operate and extend these systems are involved from the outset, and the organisation is not dependent on a small, isolated “AI team”.
Method 7: Periodically Re‑underwrite the AI Strategy
AI technologies, regulations, and client expectations shift rapidly, therefore, we never freeze our AI strategy. Instead, it follows a cycle similar to how long‑term asset strategies are refreshed:
- Over a 3–5 year horizon, we commit to a defined set of AI themes and platform investments (for example, domain‑specific generative AI for design and review, cross‑portfolio digital twins, and AI‑enabled operations centres).
- At defined intervals, the full AI portfolio is reviewed and “re‑underwritten”: assumptions are tested against current technology capabilities, regulatory frameworks, client demand and internal adoption levels.
- Underperforming initiatives are either reshaped or retired, and capital and talent are reallocated to higher‑yield opportunities.
This periodic renewal prevents sunk cost bias and “project inertia”. AI growth remains aligned with real‑world conditions, rather than with the assumptions that happened to be true when the programme started.
Conclusion: Growth Requires the Same Discipline as Concrete and Steel
“Achieving and sustaining growth through AI is not about finding the right model or vendor.”
It is about treating AI as seriously as concrete and steel: as a long‑lived asset class that demands disciplined investment, engineering‑grade governance, and continuous optimisation. When AI programmes are governed like capital projects, organised as portfolios, owned through a clear operating model, grounded in hard metrics such as RoAI and RoE, and refreshed through structured re‑underwriting, growth becomes repeatable rather than sporadic.