Been a while since I reintroduced myself.
I write about CFO craft under The Secret CFO pseudonym.
Initially, that pseudonym gave me the freedom to talk about the CFO world in a way I never could with my name and company attached... and I guess it just stuck.
- Path: Big 4 → FP&A → Controller → Corp Dev → CFO (+ a few detours since)
- Experience: 25 years in finance, more than half of those in CFO roles
- Scale: Last CFO role as Group CFO in a $4bn revenue business
- Specialism: Special situations. High leverage, complex balance sheets, operational turnarounds and refinancings
- Transactions: 20+ M&A deals, integrations, exits, and major transformations
- Industries: Mature, 'real-world' businesses. Manufacturing, agriculture, hospitality, CPG, retail. Thin margins, operational complexity, high stakes.
A couple of years ago, I stepped away from the CFO seat for what I thought would be a year or so break. I had 20 years’ worth of handwritten notebooks full of things I’d learned, mistakes I’d made, frameworks I’d built, and lessons I wished somebody had taught me earlier. So I started writing them up and sharing them through my email newsletter.
As Steve Jobs once said, “You can’t connect the dots looking forward. You can only connect them looking backwards.” The more I wrote up, the more I shared. The more I shared, the more my platform grew.
And along the way I discovered I really love codifying and then teaching this stuff. I’d always enjoyed developing people in the teams I built. But suddenly, I could do it, at scale, for people I had never even met.
I started getting unsolicited emails from people who had landed their first public-company CFO job, completed a PE exit, escaped a boardroom bear trap, or simply made a better capital decision helped by one of the Playbooks I have written.
It humbles me every time. And it's addictive...
I’ve now written more than 500,000 words about the craft of being a CFO. Some came straight from those old notebooks. Some emerged from trying to make sense of a career’s worth of experience. And plenty has come from what I continue to learn from the incredible finance leaders I talk to everyday.
So, that’s why I’m here...
To codify the craft of finance leadership. To challenge and improve the fundamental ideas. And to put that context into the hands of the humans and machines building the finance function of the next decade.
It's an honor, thanks for following along.
Want to hear the story about a paper pulper who managed to lose over $2b betting on currencies?
Treasury teams are not supposed to be famous. Not even for one little minute. But in 2008, Brazil’s Aracruz Celulose found a spectacular way to break that rule.
This wasn’t a bank, hedge fund or trading house. They grew eucalyptus trees. Smashed them into pulp. And sold it to paper and tissue manufacturers.
And they were very, very good at it.
In 2007:
→ Revenue: ~$1.9bn.
→ Adjusted EBITDA: just under $900m.
Then came a currency derivatives loss bigger than an entire year’s revenue. All they had to do was protect that delicious pulpy margin. Instead, the paper boys and girls started playing with the wrong kind of paper.
How the hell did that happen? That’s where tomorrow’s edition of The Secret CFO's Playbook begins.
Then we get into the CFO’s job of making sure it doesn’t happen on your watch:
• What belongs in your Treasury policy.
• Which risks Treasury owns, and which it doesn’t.
• Financial exposures hiding inside everyday commercial decisions.
• Setting limits and delegating authority.
• My “flip chart test” for complicated Treasury proposals.
And remember ... treasury is there to protect the business you’re actually in, not start a little hedge fund on the side by accident.
The CFO’s Guide to Corporate Treasury, Part II. Tomorrow.
Subscribe here: cfosecrets.io/
Unlocking most enterprise workflows is now a context and connectors problem, not a model one.
The two key challenges I see most commonly are 1) getting enterprises to feel secure bringing in that context and 2) not having agents waste valuable tokens finding the right data.
The bottleneck of automation for 99% of enterprises is no longer smarter LLMs...
The current LLMs are capable enough
New models coming out now mostly just mean defaulting to higher costs. We force default earlier models unless there is a strong reason they need the latest.
Databricks CEO Ali Ghodsi says if frontier models stopped advancing, it wouldn't matter for most orgs because enterprise AI is bottlenecked on context, not intelligence:
"There's no agentic work that's automated the whole enterprise. That has just not happened. Why is that? The real reason is the models are smart enough, but they just don't have the context that exists inside of any organization."
"They have not been in every meeting. They don't know what's in everybody's heads. They don't know all the processes. There's always a couple of employees who know everything in every organization. You go tap on their shoulder, and everybody's like, 'Oh my God, what would happen if he or she quits?'"
"If you just fused that and gave that context into the AI models, just the frontier today, I think there's so much productivity gains you could get for any organization on the planet."
"For that, we actually don't need smarter models... If the frontier doesn't advance, it doesn't actually matter for the vast majority of organizations on the planet. They're just so far behind in the adoption curve of actually automating things and getting value out of this stuff."
@alighodsi
Read the latest Profiles of the Future by @bhorowitz and @mikemcg0 on Databricks & the Future of the Firm: a16z.news/p/databricks-and-t…
"I've been in rooms with too many finance people before. It's dangerous because the wrong things can end up dominating the conversation.
Most business problems are ultimately solved through better products, better marketing, and better sales.
Finance is a vehicle to help make that happen, not an end in itself."
-- wise words from @SecretCFO
[Two related ideas:
1) everyone, in particular those in finance, tends to over-emphasise things that are easy to measure (like marketing spend), and under-emphasise things that are hard or impossible to measure (like your brand value) which often leads to large errors
2) "The map is not the territory" -- what we see in finance on dashboards, in the P&L, is always an abstraction or representation of the business, not the business itself]
Reminds me of the guy that said he was going to open a dog training school called Harvard so all their MBAs would forever have to say “no… the one for humans”
One of my favorite ongoing bits is "confusing" someone's elite alma mater with a lower ranked college
"How was Boston College" (Harvard)
"Would you recommend Penn State" (Penn)
"What was Rutgers like?" (Princeton)
On the a16z piece on the rise of the engineering / builder CFO.
There are some great ideas there. But some points are viewed through a stunningly narrow lens. I find that a little unambitious given the size of the opportunity in front of us.
First, two things they definitely get right:
1) AI’s ability to make sense of messy data is a HUGE inflection moment for finance. Every bit of finance transformation advice always starts with “sort out your data”. Any idea how fucking hard that is? Teams have been grinding away on transformation and data hygiene projects for years. They often move slower than the businesses they’re supposed to support. AI unlocks the potential to destroy the biggest barrier to modernization of the CFO’s office.
2) Finance engineering is real, and should be thoughts of as a new core capability any ambitious finance team needs. The days of the systems accountants being the most tech-savvy people in the finance team, are thankfully ending. Real builders at the intersection of finance and engineering are worth their weight in gold and about to get more valuable. This is exciting, especially for smart young ambitious pros.
Beyond that, much of the rest of the piece only makes sense through a software industry lens.
It has the energy of tech people talking to other tech people about tech companies who sell to other tech companies. (Note - for the record, I’ve worked with some of the a16z portfolio companies mentioned in the piece, who definitely have the capability and appetite to serve outside tech.)
For example, the piece talks about finance going from 5% of company headcount as standard, to 2%. In my last role, we had 1.5% of headcount in finance. We weren't especially efficient, it's just a function of the headcount dynamic for the industry I was in.
So, unfortunately this falls into the trap that so much commentary on finance from the software industry does. It forgets that most companies are not tech companies. And therefore, most CFOs are not tech CFOs.
Software finance is characterized by being scalable with a supersonically simple P&L structure (which goes to the finance capability you need.)
I think it was Ben Horowitz himself who said that the biggest difference with hardware is "you need a much better CFO than in software."
Yeah ... that’s because the economics of a hardware business looks more like conventional manufacturing than it does software.
Now some of this has changed lately of course, as software consumes more AI, it takes on more of AI’s economics too; token costs, compute versus human decisions, usage-based pricing. More complicated margins and planning dynamics than before.
But take a petrochemicals manufacturer, as example. They are dealing with feedstock prices, energy costs, production yields, plant utilization and selling prices moving together, by the day. And always has done.
Now imagine doing that across a few hundred or a few thousand SKUs. Think about the dimensional complexity that brings.
That makes the story much harder to find, to tell, and then ultimately to fund. Imagine what they could do with better tooling.
So when the piece says (for example) finance can look forward to a "bigger mandate”, including pricing, capital allocation and people-versus-software decisions ... I’m a bit stunned. Any half-capable CFO I know would either be in the room when decisions of that financial magnitude were made. Or beating down the door to get in.
And then there’s the framing of successive CFO eras: accounting, fundraising, FP&A / business planning, and now building. They acknowledge that the dimensions of a great CFO have endured. But the framing still jars.
These aren’t things that most businesses have had the luxury of choosing between. I worked for CFOs twenty years ago who were incredible at controls, fundraising and business planning all at the same time.
So, when I read things like that, I don’t see an evolution… it feels more like catching up?!
Now … where plenty of finance teams outside tech ARE lagging is in the software available to them.
Take that multisite petrochemicals business. Give it four different legacy ERP systems and years of workarounds holding everything together.
The finance team is still delivering what the business needs despite poor, inflexible software. Impossible implementation conditions. So it's much slower and more manual than they need and would like.
This is where AI’s ability to work with messy data gets really exciting. Helping bridge those systems and workarounds could finally let teams make progress on problems that have defeated successive generations of transformation programs.
There is a world of businesses out there hostage to the legacy ERP industrial complex. I hope the investors and builders powering the next generation of CFO Tech have those businesses front of mind.
Because the TAM is far bigger than the one on their doorstep.
This is very good. Great exercise in thinking about good governance from first principles. Best business book I’ve read in quite some time.
Bravo @ericries
For those that didn't see the OP. See below. (I haven't been on X for a couple of days so only just now reading it, and these are my initial reflections).
Seema Amble @seema_amble Oct 8 Article You Need a New CFO In 2020, CFOs needed new tools. Now the tools are changing the role. The role was becoming more strategic, but the software was still stale. CFOs were part data analyst and part architect, stitching