5 skills of highly successful CFOs who don't let AI fail in finance
HPE cut reporting cycles 40%. Dell built proprietary agents inside finance. DBS Bank generated $1B in AI value. Here are 5 skills most CFOs are ignoring.
Every CFO I know has tried Claude.
Every one of them walked away with the same story.
The tool that was supposed to save three hours added a fourth. The board memo came back polished. Then you check the math.
The gross margin is wrong. The variance commentary cites a driver that doesn’t exist in your P&L. A footnote references a vendor you stopped working with two quarters ago. Everything reads beautifully. Nothing ties.
You send it back. The AI fixes the three things you caught and introduces two you didn’t. You fix those. You miss a third. The board sees it in a pre-read and sends you a message at 11pm asking what happened to the Southeast region.
This is what most CFOs are actually living through with AI right now. Not a revolution. A second shift.
Then there are the others. They hand Claude the same messy pile and get a clean reforecast back in 40 minutes.
The difference isn’t talent. It isn’t budget. It isn’t a better prompt.
It’s architecture.
There are five specific skills these CFOs built before they ever opened a chat window. Each one is boring on its own. Together they separate the CFOs, Controllers and FP&A compounding advantage quarter by quarter from the ones still doing the work twice.
HPE cut their reporting cycle by 40%.
DBS Bank generated S$1 billion in AI value in 2025.
Dell built its own agent team inside finance.
None of them started with AI. All of them started with how the work happens.
Here are the 5 skills they built that the rest haven’t.
Let’s dive in.
Skill 1. Separating deterministic math from probabilistic words
The single architectural decision that separates the 7% from the 93%.
The 93% ask Claude to calculate. It gives them a number that looks right, sounds confident, and fails most of the time. Patronus AI’s FinanceBench tested GPT-4 on questions pulled directly from public company filings. Best result with retrieval: 19% correct. An 81% failure rate.
The 7% never ask Claude to calculate anything.
Excel, Python, or the ERP does the math. Claude writes the narrative around the verified numbers.
Every Monday at HPE, 40 to 50 business leaders join a 90-minute operational performance review. The finance team used to prepare roughly 100 pages of PowerPoint for that call.
It took hundreds of hours across the business. People scrambled over weekends to pull reports, reconcile data, and format slides.
Marie Myers, HPE’s CFO, called that meeting the “heartbeat of the company.” But the effort required to assemble the deck left almost no time to shift the conversation from what happened to what to do about it.
So she built an AI analyst called Alfred.
Named after Batman’s butler. Built on Deloitte’s Zora AI platform running on HPE’s own private cloud infrastructure. Alfred combines agentic and generative AI to interact with over 300 million line items of HPE data in near real time.
The result?
90% reduction in manual effort for the weekly review.
Financial reporting cycle time dropped 40%.
Processing costs fell 25%.
Users must get the same answer every time they ask the same question.
That’s not a property of LLMs. That’s engineering. Alfred routes every calculation through structured pipelines. The LLM handles interpretation and natural language queries only.
Math on one side. Narrative on the other. Never reversed.
Glenn Hopper puts it bluntly:
If Claude is hallucinating in your finance work, the problem isn’t Claude. The problem is that you’re asking it to answer questions without the context an experienced analyst would have.
The fix sits at the architecture layer. Not the prompt.
Skill 2. Owning AI outcomes personally
Fortune named the principle directly in March 2026.
CFOs, not Chief AI Officers, are the secret to getting real value from AI.
The Babson/MIT/Return on AI Institute study of 1,006 C-suite executives across 11 countries backs it up. Where CFOs formally own AI value, 76% of companies report “great value” from AI. Everywhere else, most report nothing.
Gartner’s most recent AI in Finance Survey delivered the other number every CFO should have memorized by now.
Only 7% of CFOs report strong impact from their AI investments.
DBS Bank in Singapore built the blueprint for joining that 7%.
DBS generated S$1 billion in economic value from AI in 2025. Up from S$370 million at the end of fiscal 2023. A 2.7x run in two years. The number was announced by Nimish Panchmatia, DBS Bank’s chief data and transformation officer, in The Business Times.
The billion isn't the story.
How DBS measures it is.
Forrester's analyst Tom Mouhsian lays it out plainly:
"Unlike vague projections, DBS uses a rigorous benchmarking approach to quantify AI-driven value. Customer outcomes from AI-powered solutions are compared against control groups, ensuring that the S$1 billion figure reflects tangible, measurable benefits rather than theoretical estimates."
Control groups. Not PowerPoint estimates. That's why DBS's billion-dollar figure survives scrutiny while most corporate AI ROI claims collapse under a partner review.
The lesson for CFOs in the 7%: if you can’t defend the number with a control group, you don’t own the AI value. You hope for it.
Glenn Hopper makes the same point bluntly.
The choice isn’t between AI and not AI. The choice is between using it with your rules or pretending AI isn’t already part of your finance function.
Skill 3. Redesigning the workflow before buying the tool
AI high performers are nearly 3x as likely to have redesigned their workflows as companies that added AI to existing processes.
MIT NANDA confirmed it from the opposite angle. Their July 2025 study found 95% of enterprise AI pilots deliver no measurable P&L impact. External vendor-built tools succeed 67% of the time. Internal AI overlays on existing processes succeed 33% of the time.
AI doesn’t fix broken workflows. It amplifies them.
David Kennedy, CFO of Dell, did the thing most CFOs won’t.
He incubated a team of data scientists inside finance. Not in IT. Not in a central AI Center of Excellence. Inside finance. Those embedded engineers now build proprietary agents inside Dell’s governance framework. They streamline Kennedy’s calendar, automate emails, drill into forecast data by country and segment, run reconciliations, and draft journal entries. Dell spent the prior two years modernizing and standardizing systems to make these tasks possible.
That’s the part most CFOs skip.
Dell fixed the data before they built the agent.
Meta went further at the transactional layer.
At the Economist’s AI for CFOs summit in March 2026, Meta Finance Director Ailbhe Moynihan walked through what happened when her team deployed agentic field-editing on invoice data. Meta processes around 600,000 invoices per month. Manual intervention collapsed from 100% to 7%. In seven days.
This is the sequencing no one publishes but everyone winning at this follows.
AP and invoice automation first.
Transaction matching and reconciliations second. Close orchestration third. Management reporting is fourth. FP&A and forecasting fifth. Investor relations and board narrative last.
Teams that invert this… starting with forecasting because it sounds strategic … end up disproportionately in the 93%.
Start where the volume punishes humans and the logic bores them.
Strategy comes later.
Skill 4. Building a memory layer
A generic LLM is an analyst with amnesia.
Every conversation starts from zero. You paste the P&L. You re-explain the business. You re-describe what good looks like. Most CFOs experience AI as frustrating even when it works because the setup cost per prompt is too high.
The fix is a persistent context layer. A Claude Project. A workspace that remembers your business across sessions.
Glenn Hopper demonstrated this live in his April 9 insider session. He built a Claude Project for a synthetic three-location guitar retailer, loaded multiple years of financials, and set custom instructions before running any prompts. His framing from the session:
Projects are great. Several years of financial data, the full GL, all the context an employee would have. The more context you give it, the less it makes up.
JPMorgan built the same principle at enterprise scale.
Their LLM Suite, built in-house, reached more than 200,000 employees across consumer, investment, and asset/wealth divisions. President Daniel Pinto positioned it publicly as delivering $1 billion to $1.5 billion in annual value. Not through forecasting heroics. Through email drafting, document summarization, research retrieval, and Excel problem-solving inside an environment that already knows how JPMorgan operates.
Chief Data and Analytics Officer Teresa Heitsenrether sits on JPMorgan’s operating committee. That placement was deliberate. AI became an executive function, not an IT project.
You can build the same memory layer for your finance function this weekend.
20 minutes on Sunday.
Skill 5. Building governance before intelligence
KPMG’s Q4 2025 AI Pulse Survey delivered the number that explains every serious 2026 finance deployment.
75% of business leaders rank security, compliance, and auditability as the most critical requirements for agent deployment.
That’s why every firm winning at enterprise AI built it on tightly scoped internal platforms, not public chatbots.
Morgan Stanley is the cleanest proof of the principle in wealth management. Their OpenAI-powered AI @ Morgan Stanley Assistant, reached 98% adoption among financial advisor teams. 98% in a profession famously allergic to new tools.
Jeff McMillan, Morgan Stanley's head of firmwide AI, credits eval discipline, not the model, for the adoption rate. Every use case tested before deployment. Every output logged. Every decision traceable.
The companies that really have the highest security risk are the ones that are locking it down completely. Employees are going to find the most efficient way to do the job, and the company can either benefit from it or not.
Most mid-market finance teams can’t build Morgan Stanley’s eval infrastructure internally. But they can write the one-page policy that enforces the same principles.
The Bottom Line
AI isn’t a tool you buy. It’s an architecture you build.
Math separated from narrative. The CFO is accountable for outcomes. Workflow redesigned before the tool. Memory layer loaded with real context. Governance before intelligence.
HPE built it.
DBS built it.
Dell built it.
Meta built it.
JPMorgan built it.
Morgan Stanley built it.
None of them did it with a better model.
They did it with better architecture around the same models the 93% are using.
Don’t try to do everything.
Pick one problem and solve it.
And that’s all for today.
If you found this useful, forward it to one CFO who needs to see it.
See you on Thursday!
Whenever you’re ready, there are 2 ways I can help you:
If you’re building an AI-powered CFO tech startup, I’d love to hear more and explore if it’s a fit for our investment portfolio.
I’m Wouter Born. A CFOTech investor, advisor, and founder of finstory.ai
Find me on LinkedIn