Would you build it this way today? What succession reveals about AI Readiness

Every business hits a point where ownership changes hands — through retirement, sale, or a next generation stepping in. Many people think of that moment in financial or legal terms: valuations, contracts, handover periods. I think it's something else too: it's one of the only times a business gets to ask, without a crisis forcing the question, the founder's question — would we build it this way if we started today?

How often does anyone actually stop to ask it? In my experience, rarely — and whether they do or don't often comes down to what the incoming and outgoing owners are each optimising for.

Wattle tree in bloom, Geraldine, South Canterbury

Founders build the thing. Everyone after inherits the machine.

Fisher Funds portfolio manager Matt Logan wrote a piece for NBR earlier this year that's stuck with me, about AI as a stress test for organisations. His argument was aimed at investors, but, for me, it lands just as hard on small business succession.

His argument, in short: founders build a company around a customer problem. The structure — the processes, the approvals, the way things get done — gets added later, but it stays in service of that original problem. Whoever inherits the business afterwards inherits something different. They inherit the machine: the reporting lines, the workarounds, the "way we've always done it." And it's easy, he argues, to mistake that machine for the asset itself, when really it's just the delivery mechanism the founder happened to build.

That distinction — asset versus delivery mechanism — is exactly what's at stake in small business succession too. Just at a smaller, more paper-based scale.

The exit-focused owner has no reason to touch it

I see plenty of small businesses running on manual, paper-based processes, or on systems nobody's touched in years — often because the owner is a handful of years from retirement and has no appetite left for the upheaval that comes with a technology or change project. That's an understandable instinct. Nobody renovates a house the week before settlement.

But it's worth asking the uncomfortable question anyway: how much value do those paper-based, inefficient processes actually add? How much of what an owner thinks of as their competitive advantage — the way they've always done things — is really just accumulated inefficiency that's never been tested against something faster? That kind of "advantage" can look solid for a long time, right up until a competitor adopts AI and exposes it.

This is the small-business version of the incentive problem Logan describes: a professional operator is rewarded for hitting next year's budget, not for reinventing the company, so the machine never gets questioned. An owner a few years from retirement has the same instinct for a different reason — they're not looking to take on the disruption of a change project right before they step away from the business. Neither is doing anything wrong. But neither has a reason to ask the founder's question either.

Digital natives don't inherit the attachment — and they don't need as much translation

The people now stepping into ownership are often digital natives, and I think what actually matters about that isn't their age. It's two more specific things.

First, they don't carry the same attachment to the existing machine. They didn't build it, and — unlike a professional operator protecting their budget, or an owner protecting their sale price — they're not personally invested in defending it. That alone makes it easier to ask what should be kept and what's just inertia.

Second, in my own work I've noticed digital natives grasp the concept of a low-code platform far faster than older owners do — the idea that something can be genuinely custom without being built entirely from scratch. That same fluency seems to extend to AI: they tend to understand what it can and can't do without needing to be walked through where it fits, in a way older owners often do need. Less translation required means less time between "we could change this" and actually changing it.

Succession is the reset point — if it's used as one

None of this makes digital-native successors automatically better at running a business. But it does mean they're structurally well placed to do the thing Logan describes: separate the customer outcome from the machinery built around it, and ask whether the machinery still earns its place.

The risk is that this window closes fast. A new owner inherits the business and, within a few months, inherits the old habits along with it — the same paper trail, the same systems, kept out of comfort or because staff expect continuity. AI readiness, in a succession context, isn't really about the technology stack at all. It's about whether the moment ownership changes is treated as a deliberate chance to ask the founder's question again, before the machine reasserts itself.

Framing on founder versus inherited-operator incentives draws on Matt Logan's "AI: The organisational stress test", Fisher Funds, 2026.

We use the AI Contribution Scale defined by Blair Enns to disclose the use of AI in our written content.  This article is rated as: AI-4: AI Drafted. The content was drafted by Claude from our own content and ideas, we then refined the output.