Five key messages and the ten questions the committee will ask. Click to expand each.
Message 1
Carrier doesn't need a new CIO. It needs a Competitive Advantage Architect.
There is a fundamental difference between managing data and AI as IT support and using them as the primary engine of value creation. I'm here to do the second — and I have a specific perspective on how to do it in Carrier's unique 2026 context.
Message 2
The AI business case at Carrier is not speculative — it's already in the numbers.
40,000 dispatches avoided, 650M kWh saved, data center orders growing 4x YoY. My job is not to invent the business case — it's to build the architecture that scales those proof-of-concepts by a factor of 10 in 36 months.
Message 3
I understand the financial context completely — and I respect it as a Day 1 constraint.
With Debt/EBITDA at 5.66x vs. the 3.47x historical median, every technology investment must demonstrate return in 18–24 months, not 5-year theoretical horizons. My digital agenda is designed with capital discipline built in from the first day, not as an afterthought.
Message 4 — Contrarian
The Abound vs. OpenBlue battle isn't won in Gartner comparisons. It's won through data lock-in.
Johnson Controls is already using software as a lock-in mechanism in their bids. Carrier has the largest installed equipment base — the most valuable data source. The winning strategy: make customer data so valuable inside Abound that switching becomes prohibitively costly. This requires a customer data strategy unlike anything the HVAC industry has attempted.
Message 5 — Priority
Viessmann data integration is the biggest competitive advantage opportunity — and no one in the market is looking at it correctly.
Analysts model heat pumps + brand + European distribution. Nobody has modeled the data from millions of connected European homes. Connecting that to Abound's architecture — the work I'm committing to in the first 90 days — is how the $14.2B bet becomes genius, not just scale.
Q1: Why are you the right person for this — what CDO AI role of this scale have you run?+
The Question Behind the Question:
They're testing whether you oversell or have a credible answer. Don't claim you've run a $22.5B industrial pure-play — nobody has. Answer: "I haven't run a role at this exact scale — and I'd be suspicious of anyone who claimed they had, because this role, in this company, at this moment, doesn't have a direct precedent. What I bring is [specific: industrial IoT architecture experience / cross-segment data integration at scale / AI deployment in safety-critical physical environments]. The 90-day audit I described isn't a placeholder — it's how I de-risk the transition and move fast without moving reckless."
Q2: With 5.66x Debt/EBITDA, how do you justify $820M in AI investment over 3 years?+
The Right Frame:
"The 5.66x constraint is exactly why this investment is necessary, not despite it. Software margins at Abound run 60-70% gross vs. 30-35% hardware. A 5-point mix shift toward recurring software revenue adds ~$200M to EBITDA without a single additional hardware unit. The $820M is not a cost — it's the mechanism for reducing the debt burden faster than the bear case assumes. Year 1 investment is $220M. The payback on service dispatch avoidance alone — 40,000 dispatches at ~$800 average — is $32M per year from one use case. The committee should challenge me if the numbers don't hold. But the frame is: this is the deleveraging vehicle, not competing with it."
Q3: Bobby George left. What went wrong, and why would your approach be different?+
Answer with Precision:
"I don't have visibility into what drove Bobby's decision, and I'm not going to speculate. What I can say is that the role he held was architected as a traditional CIO role — systems, infrastructure, IT governance — with AI added as a secondary mandate. That architecture is the wrong frame for 2026. The question Carrier needs answered is not 'how do we run IT efficiently' — it's 'how does data become a competitive asset that changes our pricing power, our retention, and our P&L mix.' Those are different jobs. The role I'm proposing to perform is the second one."
Q4: How do you handle AI failures in critical environments — hospital HVAC, cold chain, data centers?+
This is a Safety and Trust Test:
"The governance framework I described — three non-negotiable axes — isn't corporate defensive bureaucracy. It's the engineering discipline that makes fast deployment possible. A model failure in a hospital isn't a software bug — it's a potential patient safety event. My answer to 'how do you handle it' starts with 'we don't get into a position where there's an autonomous AI decision in a critical system without a documented human checkpoint.' The companies that have deployed industrial AI fastest are the ones that built governance before their first incident. Carrier will be in that category. The audit trail, the human verification gate, the mandatory review cadences — those aren't slowing us down. They're what lets the board and the regulators say yes to scale."
Q5: What's your timeline to first measurable P&L impact?+
Commit to a Number:
"18 months to first verifiable margin impact. Not a demo, not a proof of concept, not a pilot — a number in the management accounts. The Abound service dispatch use case is already proven at 40,000 avoidances per year. Scaling that model across the remaining addressable building base while simultaneously adding Viessmann fault data generates measurable OpEx reduction in the first year. The 18-month commitment is: X basis points of margin improvement in the Abound segment, verifiable against Q1 2027 baseline. I'll put that on the table if the committee wants a commitment tied to performance metrics."
Q6: How do you manage the Viessmann cultural integration while also pushing AI transformation?+
Two-Speed Problem:
"The Viessmann integration and the AI transformation are not competing priorities — they're mutually reinforcing if sequenced correctly. The data audit in Month 1 is not IT due diligence — it's building the relationship with Viessmann's engineering leadership by demonstrating that I want to learn their data architecture, not override it. The AI Champions program gives Viessmann teams local ownership of the transformation rather than feeling like they're being absorbed. The German market context specifically requires visible local leadership. My approach is to have a Viessmann-side AI Champion lead visible from month 3 onward — someone from inside their engineering organization who has credibility with the team."
Q7: OpenBlue from Johnson Controls is ahead. Why can Carrier win?+
The Contrarian Answer:
"Johnson Controls has more features in production today. That's true. But they don't have Carrier's installed equipment base — which is the actual source of the most valuable training data. OpenBlue learns from building systems; Abound can learn from the equipment that creates the conditions those systems respond to. The winning strategy is not to build more features than OpenBlue. It's to make the customer's own equipment data so deeply integrated into Abound's performance models that the switching cost becomes prohibitive. A building operations director who has 3 years of AI-optimized performance data inside Abound is not switching to OpenBlue for a feature — they'd be destroying a competitive asset they own. That's the moat we're building."
Q8: How do you work with the Board and CFO on this agenda?+
Demonstrate Financial Fluency:
"The CFO and I need to be aligned before anything goes to the Board — not because I need approval for every decision, but because the Debt/EBITDA context means every investment proposal needs to be presented as a capital allocation decision with explicit payback timeline and downside protection. I would establish a quarterly CFO alignment session where we review the digital portfolio against financial KPIs: revenue attributed to AI-enhanced contracts, OpEx savings from service dispatch avoidance, software margin mix shift progress. The Board gets a semi-annual view — strategic progress plus the Organizational AI Capability Index that CHRO co-owns. I want the Board to feel that AI governance at Carrier is a board-level capability, not a CIO's pet project."
Q9: What would make you quit this role in 12 months?+
An Honest Answer Builds Trust:
"If after 12 months the organizational model doesn't give this function direct influence on how Abound's product roadmap is prioritized, or if the data integration decisions for Viessmann are being made by the business units without a unified architecture standard, I would surface that as a structural failure and have a direct conversation with David Gitlin. I'm not describing a scenario where I'd quietly exit — I'm describing a scenario where I'd escalate clearly. What I need to succeed is not headcount or budget — it's clarity that the CDO AI function has a seat at the table where product strategy decisions are made, not just a mandate to 'do AI things.' If that's not the design, I'd rather have that conversation before I start."
Q10: What's the first thing you do on Day 1?+
Be Specific, Not Generic:
"Day 1: Three conversations. First, with the Abound product team — I want to understand what data is being collected that is not being used, and what questions their customers are asking that the current platform can't answer. Second, with the Viessmann CTO in Munich — I want their read on the state of their data infrastructure and what they'd want from a unified architecture. Third, with the CFO — to establish the financial KPIs that will measure my success and the investment gates we'll use together. I'm not going to walk in with a transformation plan on Day 1. I'm going to walk in with questions that demonstrate I understand the business deeply enough to be dangerous. The plan gets written in Month 2, after I've listened."