The Future of Software Will Be Defined by Stewardship
This summer, my colleague Diego Lo Giudice and I explored a deceptively simple question: What happens to enterprise software when AI makes software creation abundant?
We found a paradox: Get more of what you want, and you also get more of what you don’t want.
Get more of what you ask for
AI writes code, generates requirements, builds workflows, creates tests, and accelerates delivery. But creation will not be the defining constraint. Governing the resulting abundance will be.
As creation costs fall, more ideas become economically viable. More teams can build software, more functions can automate work, and more specialized problems can justify digital solutions.
Live with the consequences of what you create
Abundance never produces only excellence. It produces a spectrum of outcomes. Some software creates value. Some creates complexity. Some should be scaled. Some should never have been built in the first place.
That is why stewardship will become a defining responsibility for technology leaders. Stewardship means inspecting outcomes and deciding what should be promoted, reused, funded, governed, or retired.
Prepare to decide what remains
Leaders must prepare now. You will make more decisions about what remains than at any other point in your career.
Stop obsessing over whether you can build it. Start deciding whether you should own it and, if so, how.
At my Future of Software keynote in New York, I’ll explain why stewardship, not creation, will separate leaders from laggards. And I’ll bust some popular myths along the way: SaaS is dead, developers are dispensable, and software will become nearly free. Spoiler: There is no free lunch.

I’ll say more at Technology & Innovation Forum East on November 4–5, 2026. If you missed Austin or can’t join us in New York, schedule an inquiry or guidance session with me or Diego.