The Most Exciting Opportunity in Business History, and Why So Many Will Miss It

The answer that used to always be right

Ask a founder or a managing director what it would take to double the business over the next three years, and you will almost always get the same first answer: more people. More salespeople, more operations staff, more managers to hold the extra layer together. Growth needs headcount. It always has, and nobody thinks to question it.

That assumption has held for as long as anyone running a business today has been working. Which is exactly why it is worth noting that, for a small number of businesses right now, it has stopped holding, not because they found a clever trick, but because something in the underlying mechanics of how a business scales has genuinely changed. Most leaders have not yet tested whether it applies to them.

I want to make that argument carefully, because the subject has been badly served by how it is usually presented. This is not a case for optimism as a mood. It is a specific, structural claim: a small team with real conviction and domain expertise can now build and operate at a scale that would previously have required an organisation many times its size, not by working longer hours, but by no longer needing to carry the overhead that growth used to demand. To see why that matters, it helps to look at the last time a gap like this opened up.

What happened the last time this gap opened

At the start of the twentieth century, factories ran on steam. A single engine turned a central line shaft, and belts and pulleys carried that power out to every machine on the floor. It worked, and for decades there was no serious alternative.

Electric motors changed the arithmetic. Instead of one engine driving everything through a forest of shafts and belts, each machine could carry its own motor, sized for the job it did. Factories could be laid out around the logic of the work, not the logic of the power source. Output per worker rose, downtime fell, and capital that used to sit idle whenever a single belt snapped went to work instead.

The factories that did not switch were not necessarily badly run. Many had sensible owners with good reasons to wait: capital cost, disruption, genuine uncertainty about whether the new technology would earn out. But waiting did not preserve their position, it eroded it, year on year, as electrified operations pulled further ahead on cost, speed and flexibility. By the time the gap was undeniable, it was also very hard to close. The businesses that had not switched early did not find another way to compete. They mostly just stopped being competitive.

I want to be careful with this comparison, because it is easy to reach for lazily. AI is not electricity, the economics are different, and the timeline will not repeat in the same shape. But the structure of what happened is worth taking seriously, because something similar in kind, if not in scale, looks to be underway now. The businesses building real AI capability over the next two or three years, and the businesses sampling it through the odd licence or pilot, are not going to end up in comparable places. The gap between them is compounding while both groups are still deciding whether to take it seriously, and compounding gaps are always harder to close than they are to prevent.

The tax that used to come with every extra person

Here is the part of the story that rarely gets told, because it is less dramatic than a new tool or model release: almost every wave of business technology before this one made individuals faster without changing much about what happens when you put more of them together.

Take any business that has grown from twenty people to two hundred. The tools improved across that journey: spreadsheets, then cloud software, then dashboards. But the coordination cost of scale did not go away, it scaled roughly in proportion to headcount. More people means more status meetings to keep everyone pointed the same way, more handoffs where context gets lost between the person who knows something and the person who needs to act on it, and more data re-keyed from one system into another. None of this shows up as a clean line item. It shows up as the quiet tax every growing business pays on the way to being bigger: a layer of people whose real job, whatever their title says, is holding the organisation together as it stretches.

That tax is the thing that has actually changed. A meaningful share of the drudgery and coordination load that used to require proportionally more people, chasing updates, reconciling records, writing the same status report several different ways, can now be absorbed by systems that largely maintain themselves rather than needing a growing team to babysit them.

That is the mechanism behind the claim this piece opened with. It is easy to hear "a small team can now outbuild a much bigger one" and assume it means people working harder, or fewer people doing the same job. It means neither. This is not about becoming a smaller business that does the same things with less. It is about becoming a business five to ten times as capable with the same people who are already there, because ambition stops being capped by how many people it takes to hold the coordination together. That is a genuinely different shape of business than the one every leader running a fifty-to-two-hundred-person operation learned to manage.

How a real opportunity gets sold badly

If the argument so far is right, leaders should be moving on it with real seriousness. Most are not, and the reason is not that they doubt AI is powerful. It is that the loudest parts of the market talking about it have made the whole subject sound like something a sensible person should tune out.

Part of that market is selling urgency and shortcuts: the weekend transformation, the tool that will multiply your output by Friday, the framework promising revolution without changing anything structural about how your business runs. It is aimed at exactly the instinct that experienced leaders have learned to distrust, because they have been sold this kind of promise before, under different technology labels, and watched it fail to survive contact with a real business.

Another part is quieter and more corrosive: existing software and consultancies relabelling what they already sold as "AI-powered," changing a badge and some marketing copy without changing the substance underneath. The CRM works the way it did two years ago. The reporting process still runs the way it always did, just with a chatbot bolted to the side.

A third part of the noise is the framing used even by people who mean well: that the point of all this is fewer people. It is the wrong frame, and it is also the one most likely to make your best people defensive rather than energised, because nobody does their best work while bracing for their own redundancy.

Put those three things in front of a leader who has sat through a failed ERP rollout and a digital transformation that produced a new website and not much else, and scepticism is the correct response to what they have been shown. The trouble is that it does not stop where it should. Having correctly identified the noise as noise, good, experienced leaders often write off the opportunity underneath it too, because from the outside the two are hard to tell apart. That is the first way this gets missed.

Activity is not architecture

The second way it gets missed looks nothing like scepticism, and it can be harder to spot, because it looks like progress. These leaders do not dismiss any of this. They believe it, they are curious about it, and they act on that curiosity by trying everything at once: a new tool this month, a different pilot next month, a subscription here, an integration bolted on there, all pursued with real energy and no order behind any of it.

Six months in, there is usually a lot of activity and very little that adds up. A handful of point solutions that do not talk to each other. A team that has sat through three different "AI training" sessions and cannot describe how any of them changed what they do on a Tuesday. Spend that is hard to justify against outcomes, because nobody set out to build anything in particular. They set out to not be left behind, which is a feeling, not a plan.

The businesses that capture this advantage are not the ones who moved first or tried the most tools. They are the ones who treated it as infrastructure to build deliberately, over years, the same way they would treat a finance system or a supply chain, not a trend to sample through a pilot or a subscription. Architecture is boring compared with the tool of the month. It is also the only version that compounds in your favour instead of just generating activity.

The window will not stay open

None of this is a case for urgency. It is not a countdown, and nobody should rush a badly considered rollout because of an article. The right response to a genuine structural opportunity is seriousness, not speed: a multi-year capability-building programme worth resourcing and owning properly, not a line item you tick off with a subscription.

Seriousness has to start somewhere, and the honest starting point is admitting that the old assumption, that growth requires a proportional increase in headcount and the coordination overhead that comes with it, is no longer automatically true. It is worth testing, specifically and rigorously, against your own business, whether it still applies to you.

This is a genuinely rare moment. For most of business history, ambition has been capped by headcount: by how many people you could hire, train, manage and hold together as the coordination load grew alongside them. That cap is loosening, not for everyone, and not automatically, but for the businesses willing to build the capability properly rather than sample it. The leaders who take that seriously now, who commit the months and years it takes rather than the weekend it is often sold as, will end up on the far side of a gap the businesses who waited will find very difficult to close. That was true of the factories that did not electrify. It looks to be becoming true here too.