What is a copilot?
A copilot is an AI assistant embedded in a tool a person already uses: a document editor, a code editor, a CRM, a spreadsheet. The person asks for help with the task in front of them, the copilot drafts, summarises, or suggests, and the person accepts or edits. The person initiates every interaction and remains the one doing the job.
Copilots are good at what they are for: making a competent person faster at their own work. They do nothing when the person is not there, and they own no outcome.
What is a Digital FTE?
A Digital FTE is an AI employee that owns a job function: search visibility for a website, reconciliation for a ledger, first-line resolution for a helpdesk. It works on its own cadence, starting each day with a morning brief, proposes actions through an approval gate, carries evidence on every proposal, and reports to a human manager against explicit targets.
It does the work when nobody is watching, which is the point. The manager reviews what it proposed, not what they asked it for.
How do they differ structurally?
They differ in who initiates and who owns. With a copilot, the person initiates and owns the outcome; the copilot is a capability inside the person's tool. With a Digital FTE, the FTE initiates within its remit and the manager owns the decisions; the FTE is a worker inside the organization.
That difference shows up everywhere: in pricing, where copilots are per seat because they are attached to people and Digital FTEs are metered because they do work; in governance, where a copilot's output is the person's responsibility and a Digital FTE's proposals pass a gate with a named approver; and in scale, where a copilot scales with headcount and a Digital FTE scales with the wallet.
- Initiates: person (copilot) versus the FTE within its remit
- Owns the work: the person versus the FTE, with manager approval
- Runs when: the person is working versus on its own cadence
- Priced: per seat versus metered work
- Governance: person's responsibility versus approval gate and audit trail
When do you need which?
You need a copilot when people are doing work they should keep doing and could do faster: writing, analysis, coding, correspondence. You need a Digital FTE when there is a function nobody owns properly, or a function whose repetitive part is crowding out its judgement part, such as reconciliation crowding out accounting or screening crowding out interviewing.
The two are not rivals. A finance team can give its accountant a copilot for analysis and hire a Finance Controller Digital FTE for daily reconciliation. The accountant is faster, and the reconciliation is owned.
What is the common mistake?
The common mistake is trying to use a copilot as a worker: asking a person to prompt it every morning to do a function's work, which makes the person the bottleneck and leaves no record of what was decided. The reverse mistake is hiring a Digital FTE for work that is really a person's judgement, which the approval gate will reveal quickly through send-backs.
The test is simple. If the work has a person who should be doing it, give that person a copilot. If the work has no owner, or its owner should be doing something else, hire a Digital FTE and manage it.
How do you decide in practice: a five-question test
Ask five questions about the work in front of you. Does it have a person who should keep doing it? If yes, that person needs a copilot, not a replacement. Does it happen when nobody is prompting, on its own cadence, whether or not anyone is at a desk? If it needs to, it needs a Digital FTE. Does it need to act inside your systems with credentials, proposing changes to a ledger, a CRM, a helpdesk, or a site? If yes, it needs the approval gate, scoped credentials, and audit trail a Digital FTE carries and a copilot does not.
Does anyone need to be accountable for its output by name, in a record? If yes, a copilot's output is the user's responsibility with no trail, and a Digital FTE's proposals carry a named approver. Does the cost need to follow the work rather than the number of people? If yes, per-seat pricing is the wrong shape. A copilot is the right answer to the first question and the wrong answer to the other four, which is why most organizations end up with both: a copilot for each person's own work and a Digital FTE for each function that needs an owner.