Transcending the Loop
The Copilot Model Is a Fallacy
ESSAY
Thinking
Dewald Pieterse 2 November 2026
Transcending the Loop: The Copilot Model Is a Fallacy
Ask most executives what AI transformation looks like, and they will still describe an AI assistant at every desk. Each employee receives a licence for an AI ‘copilot’, which drafts their emails, summarises their documents, reviews their spreadsheets and answers their questions.
This, to be sure, is a real benefit, and a company that gives its employees a copilot is better placed than one that affords no AI enablement. But such a company remains, inevitably, the very same company with slightly faster employees.
By ‘the copilot model of AI’, I mean any arrangement in which a person performs each task and an AI helps them to do it. My chief aim in this essay is to suggest to you that this model, however useful for now, rests on a mistaken understanding of what AI has become, and that a company which treats it as the destination will never capture the upside that AI makes possible. Whereas a copilot makes a company’s people faster, real automation changes what kind of company it can be.
A Category Error
A category error is the mistake of placing something in a category to which it does not belong. The copilot model makes this mistake about AI. It treats AI as a tool to be wielded by a human, when instead it is an agent in its own right and can now do valuable cognitive work by itself.
I anticipate the objection that much knowledge work has long been automated (take bookkeeping software, for example). This may be so, but only where the work is reducible to deterministic rules that can be written down in advance. Software automated the rules, but AI is the first technology that can take on what remains, namely handling exceptions, navigating abstract frameworks and exercising judgement. This is the difference between a tool and an agent.
Given a well-defined task and access to the company’s systems, the best current models can plan the work, carry it out, review it and improve it, much as a capable member of staff would. What they largely cannot do (in the current regulatory paradigm) is answer for the work, as they lack legal personality, and therefore bear no responsibility and carry no liability. This is why a human must still remain accountable for results. But owning the work is not the same as doing it. No manager would hire a new rockstar employee and then insist on doing every piece of work personally, yet this is, in effect, how most companies now use copilot-style AI.
The error is understandable, because until recently the models could do useful work but still made too many mistakes, and could not carry out a long, complex task to its end without someone standing over each step. For that generation of AI models, the copilot was indeed the right design. For a large and rapidly growing share of cognitive work, however, it is no longer the correct model.
It is at this juncture that I will put it to you that the existing, generally available models are already capable of doing vast quantities of existing knowledge work better than qualified humans. In a recent study of month-end accounting tasks, a frontier model working alone was about fifteen times faster, and more accurate, than licensed accountants using AI. Only eighteen months earlier, the best models had scored below the accountants’ average on the same tasks, and the models in the study have since been superseded by even more capable ones. One must realise that this is the worst that the models will ever be, but even if development stopped today, the automation of most knowledge work is already feasible using only current models.
The improvements in AI capabilities have occurred so fast (largely within the past year) that most people are still completely unaware of what is now possible. Moreover, organisational change is always slow, and habits always outlast the conditions that formed them. In established companies, the prevalence of a copilot model (to the extent that the company has gotten even that far) is reinforced by the fact that the copilot is the one model of AI adoption that leaves the company’s existing hierarchies, structures and workflows intact, which is to say that it is the path of least resistance. Many companies, having equipped their employees with AI assistants, believe that they have been transformed. This, then, is the copilot fallacy.
The Human Bottleneck
Consider as an example a professional firm in which twenty juniors do the client work under a handful of managers and partners. Give each junior a copilot, and the firm has twenty faster juniors. First drafts appear faster, documents are summarised and reviewed more quickly and correspondence with clients is written for them. This is a real efficiency gain.
But every piece of work still passes through a person’s hands, at a person’s pace and within a person’s working day. In the language of the AI field, the person is still ‘in the loop’, which is to say that no piece of work is done until a person has done or approved it, with work being done in turns by human and machine together. However much of a task the machine prepares, the person must still read it, decide on it and approve it, and that sets an inherent limit on how much faster the work can go. If a human’s own portion of a task irreducibly takes ten minutes, no assistant can make the task take less time. As a result, the firm’s productive capacity can grow in only one way, which is through hiring more humans.
Another inherent drawback of the copilot model is that this limitation does not relax as AI models improve. No matter how capable a copilot becomes, whatever part of a workflow remains the task assigned to a human does not gain from advances in model capability.
It is an idea that needs getting used to, but the fact is that where AI is competent to perform a task, a person in the loop adds little but unnecessary time, and even risks forcing error. This is to say nothing of the significant difference between the relative cost and speed of human employees and agentic systems. There is, in other words, a growing collection of tasks for which a human in the loop detracts value rather than adding it, and for which automation is an inevitability.
What Automation Means
By ‘automation’ I do not mean simply taking the existing workflow and having a machine perform each of its steps. Elon Musk famously sets out a sequence for improving any process: question every requirement, delete every unnecessary step, simplify what remains, speed it up, and only then automate. The order matters because most existing workflows take their shape from the limits of the people who perform them. Work is batched into periodic cycles because people cannot attend to everything as it arrives, divided into stages and handed between people because no one person can do all of it, and reviewed in layers because people tire and make mistakes. A machine largely does not share these limits, so much of that structure has no purpose once the machine does the work. The question is therefore not how to perform each step faster, but which steps would exist at all in a workflow designed for the machine. Many of them, rather than being made faster, simply disappear.
True automation has features that place it in an entirely different category from the copilot model. I highlight some below which show why the two cannot be treated as faster and slower versions of the same concept.
The first is what factor limits output. In the copilot model, where work passes back and forth between human and machine, output is limited by the attention of the company’s people. Once the machine does the work, however, output is limited by computing power and by the capacity to verify that work, both of which can be scaled cheaply in a way that human attention cannot.
The second is time. A person attends to one task at a time, and only during working hours. A machine can carry out a hundred tasks at once, through the night and without tiring, so that work no longer waits in a queue for someone to attend to it.
The third is cost. In the copilot model, the cost of each additional task tracks a salary. With automation, it falls towards the cost of the computing and the verification that the task requires, which is typically orders of magnitude cheaper than human remuneration.
The fourth is where skill resides. In the copilot model, each person must learn separately how to get good work out of the machine, and many never will. Once the machine does the work, skills are built into the system once and apply to everything it does thereafter.
The fifth is continuous learning. Automation requires the company’s method to be made explicit, and an explicit method can be inspected and corrected. A correction made once applies to every later task of its kind, so the system improves with each error it is shown. A copilot’s help, by contrast, stays private to each user and leaves little behind by way of organisational learning.
Verification
I anticipate another objection: if a machine does the work, and a person must review every piece of work in full, little has been gained in total time saved. This, of course, is perfectly true, and it is why verification must itself be automated as far as possible.
It is instructive to consider the recent developments in software engineering practices. Many leading programmers no longer read every line of code that their AI systems write, because doing so would forfeit most of the efficiency gains. Instead, the code is run against thousands of automated tests and scanned meticulously for vulnerabilities by other AI systems during adversarial review, and a person reviews what those tests escalate. The same pattern will eventually extend to every domain in which work can be verified, which is virtually all knowledge work. Human verification then shifts from inspecting the technical minutiae of how the work was done to reviewing and validating outcomes.
Moreover, much of the verification can itself be designed into the operation of the automated system. One AI system can review the work of another, independently and at machine speed, so that first-pass review no longer waits on a human. Other tests can be built once for each type of task and applied to every instance of it, reconciling results against external sources of truth, comparing them with earlier and comparable cases, and testing them for internal consistency. The faster the review, the faster the company turns its work around, which makes the automation of verification among the most valuable things a company can implement.
The AI-Native Company
These changes describe a different kind of company. By an AI-native company, I mean one built from the outset around the machine performing its work, with people placed where judgement, accountability and relationships are required.
Consider an audit partner. An audit partner does not redo the audit, but relies on a structure of review, in which managers review the work of seniors, who review that of juniors, and the partner makes the significant judgements personally and signs off. An AI-native audit firm keeps that structure but largely replaces the layers beneath the partner with machine work and machine review. The partner’s role barely changes, while everything beneath it does.
The economics of the two kinds of company differ accordingly. The traditional company’s leverage is the number of staff each manager can supervise, and its costs rise with its headcount. The AI-native company’s leverage is the number of judgement calls each of its people can make, and its costs rise with computing and verification. The first grows by hiring. The second can serve many times as many clients with the same people, at a fraction of the price, and deliver its work in hours rather than weeks.
Above the Loop
It is no use to anyone trying to bury the implications of automation in platitudes and euphemisms. A task that is automated is no longer performed by humans, and most of the tasks that currently fill people’s working days will not survive genuine AI transformation. This is not a by-product of automation but its purpose. The copilot model currently offers the false comfort of pretending otherwise, but sticking to that model for technical work confines a company’s pace and output quality to human standards, which, in most cases, will be a losing game.
This is certainly not to say that companies will have no use for people. As the technical work moves increasingly to the machine, people move from within the loop to above it, where they set direction, decide what matters, make the calls that carry consequence, build relationships of trust with clients and answer for outcomes. Technical competence alone, once the scarce thing that many companies sold, no longer distinguishes them. To transcend the loop is to stand above it, rather than to abandon it completely. A company could, of course, use automation simply to cut costs and reduce its workforce. A visionary leader would instead leverage the people the company already has by placing them above the loop, so that together they serve a far larger client base than was possible before.
The practicalities of how a company should make that transition, and what it means for the professions in particular, I will consider in later essays on the practicalities of reinvention and on the reshaping of professional firms.
The copilot will remain tremendously useful for whatever work still requires a person to do it. But companies that mistake it for the holy grail of their ‘AI transformation’ will in time find themselves trying to compete with companies that leverage their people above the loop, rather than leaving them stuck inside it. This competition will not last long, for the odds are tremendously skewed in favour of the AI-native company. The question before every company is therefore not how much faster AI can make its people in their existing workflows, but what the company could become if its people transcended the loop entirely and abundant intelligence were unleashed. With people above it charting the course, the value-creating loop could be brought to turn at speeds which no copilot model could ever hope to match.
Reach Out
Back to Thinking