Q1. Could you start by giving us a brief overview of your professional background, particularly focusing on your expertise in the industry?

I have spent nearly three decades at the intersection of enterprise technology, business transformation, and value creation. My background spans Oracle, SAP, cloud, analytics, AI, managed services, and large-scale ERP modernization across global organizations.
What has defined my career is not just implementing technology, but helping companies use technology to change how they operate. I have led ERP and cloud transformation programs across multiple industries, built and scaled practices, managed P&L, led global delivery teams, shaped go-to-market strategies, and worked directly with executive teams to connect technology decisions to measurable business outcomes.
Earlier in my career, I worked on the engineering, consulting, and pre-sales sides, so I learned both the architecture and the economics of transformation. Over time, that evolved into practice leadership roles across Oracle, SAP, cloud, and digital transformation. I have built ERP practices, scaled teams, originated large programs, and led enterprise transformations in which the real measure of success was not go-live but whether the business improved after go-live.
My core expertise is helping companies simplify complex operating models, modernize their digital core, improve decision-making, and create a line of sight between transformation investments and business value, whether that value shows up in working capital, margin improvement, close velocity, supply chain performance, or better executive decision-making. That has been a consistent theme across my background in ERP, cloud, AI, and enterprise architecture.

Q2. What structural shift is most fundamentally changing enterprise technology decision-making today?

The biggest structural shift is that technology decisions are moving from system selection to operating model design.
For years, companies asked, “Should we choose Oracle, SAP, Workday, Salesforce, or a best-of-breed platform?” That is still relevant, but it is no longer the highest-order question. The better question is, “What business architecture do we need to compete, adapt, and make decisions faster?”
That shift matters because ERP was once viewed primarily as a transactional backbone. Today, it is becoming the control layer for data, process, automation, AI, compliance, and decision intelligence. The decision is no longer just about which platform has the best functionality. It is about which architecture gives the business the right balance of standardization, flexibility, speed, risk control, and measurable value.
The companies that get this right are not buying software in isolation. They are redesigning how finance, supply chain, HR, procurement, operations, and commercial teams make decisions. The companies that get it wrong often modernize the technology but preserve the old operating model. That is like putting a jet engine on a covered wagon. Impressive noise, questionable mobility.

Q3. How are companies rethinking ERP architecture in a world increasingly shaped by AI, automation, and composable platforms?

Companies are rethinking ERP architecture around three principles: clean core, intelligent edge, and composable extension.
The clean core matters because ERP should be the trusted system of record, not a heavily customized museum of every exception the business has accumulated over 20 years. The intelligent edge matters because AI, automation, workflow, analytics, and industry-specific applications increasingly sit around the ERP, not necessarily inside every ERP transaction. Composable extension matters because companies need the ability to add capabilities without destabilizing the core.
The better architecture is not “one system does everything.” That is a comforting myth. The better architecture is a digital core that standardizes what should be standard, surrounded by modular capabilities that allow the business to innovate where differentiation matters.
For example, finance may standardize record-to-report, account reconciliation, tax, close, and controls in the ERP and EPM stack. But predictive cash forecasting, AI-enabled anomaly detection, supplier risk scoring, intelligent order fulfillment, or customer service automation may sit in the cloud, on data platforms, or in AI platforms integrated back to the ERP.
The leadership challenge is knowing where to standardize and where to differentiate. Standardize the plumbing. Differentiate the experience, intelligence, and speed of decision-making. Your materials repeatedly frame this as simplifying the business, reducing technical debt, enabling analytics, improving working capital, and creating a composable digital core. That is exactly the right framing.

Q4. What hidden inefficiencies still exist in global shared services models despite years of process transformation?

The hidden inefficiency in many global shared services models is that they centralize work, but they do not always eliminate complexity.
Many organizations moved work into shared services and declared victory because labor costs went down. But underneath the surface, they still have fragmented data, inconsistent local processes, poor master data governance, manual reconciliations, exception-heavy workflows, unclear ownership, and weak service-level accountability. The work moved, but the waste followed.
I see five recurring inefficiencies:
First, manual exception management. Shared services teams spend too much time fixing upstream process defects.
Second, fragmented data ownership. Everyone consumes master data, but no one truly owns its quality.
Third, shadow reporting. The ERP says one thing, the business trusts Excel, and leadership gets a polished PowerPoint that hides the reconciliation pain.
Fourth, process variation disguised as localization. Some localization is real. Much of it is habit wearing a compliance costume.
Fifth, weak value measurement. Shared services often measure cost per transaction, ticket closure, and cycle time, but they under-measure the value of fewer defects, faster decisions, improved cash flow, and stronger controls.
The next frontier is not simply lower-cost shared services. It is intelligent shared services, where automation, AI, workflows, and process mining reduce the need for manual intervention and improve decision quality.

Q5. What transformation KPIs do organizations overfocus on that may not reflect actual business value creation?

Organizations overfocus on activity KPIs and underfocus on economic outcome KPIs.
The classic examples are: did we go live on time, did we stay on budget, how many users were trained, how many test scripts passed, how many defects were closed, and how many processes were standardized. Those are important, but they are not the same as business value.
A program can hit the go-live date and still fail economically.
The more meaningful KPIs are tied to value creation. Did we reduce days' sales outstanding? Did we improve forecast accuracy? Did we reduce inventory months on hand? Did we shorten the close cycle time? Did we improve working capital? Did we reduce SG&A as a percentage of revenue? Did we increase automation rates? Did we improve compliance and reduce control failures? Did the business make better decisions faster?
Your value realization materials are directionally strong here because they connect transformation to free cash flow, working capital, inventory, receivables, payables, SG&A, cost reduction, and revenue loss avoidance. That is the right executive lens. Technology value is not created when the system turns on. It is created when the business performs differently.

Q6. How should enterprises think about resilience differently after recent global disruptions and supply chain volatility?

Enterprises need to stop treating resilience as a disaster recovery topic and start treating it as an operating capability.
Historically, resilience meant backup systems, redundant infrastructure, and business continuity plans. Those still matter, but they are not enough. The recent wave of disruption, from supply chain shocks to inflation, labor volatility, cyber risk, geopolitical uncertainty, and demand swings, exposed a larger issue: many companies could not see, decide, and act fast enough.
Modern resilience has four dimensions.
First, operational visibility. Companies need real-time insight into inventory, suppliers, capacity, orders, cash, and constraints.
Second, decision velocity. The winning organization is not the one with perfect data. It is the one that can make good decisions faster with the data it has.
Third, architectural flexibility. Rigid ERP landscapes, brittle integrations, and over-customized legacy systems reduce adaptability.
Fourth, financial resilience. Working capital, cash conversion, supplier terms, inventory strategy, and cost structure all matter. Resilience is not just uptime. It is liquidity, optionality, and speed.
The practical answer is to design ERP, planning, analytics, and automation around scenarios, not averages. Average demand, average lead time, average inventory, and average supplier performance are how companies get surprised. The world does not disrupt you on average. It disrupts you on a Tuesday morning when the board wants an answer by noon.

Q7. If you were an investor looking at companies within the space, what critical question would you pose to their senior management?

I would ask one question:
Can you clearly show how your technology investments convert into measurable enterprise value, and where that value is visible in the P&L, balance sheet, cash flow, customer experience, or risk profile?
That question cuts through the noise. Many companies can describe their transformation agenda. Few can prove that it changes business performance. As an investor, I would want to understand whether management views technology as a cost center, a modernization necessity, or a value-creation engine.
Then I would press on five follow-ups:
Where is the value expected to show up?
Who owns the value after go-live?
What operating metrics prove the business is improving?
What legacy cost, process debt, or technical debt is being removed?
How much of the transformation benefit is already embedded in the run rate versus still sitting in the business case?
The strongest management teams can answer those questions crisply. The weaker ones talk about platforms, roadmaps, and “digital transformation” in broad terms. That usually means the value case is still more aspirational than operational.
My investor lens would be simple: show me the value bridge. Not the slideware bridge, the real one. Where does the money move, where does risk decline, where does speed improve, and where does the company become harder to compete against?