The employee has an employee.
Labor
Arbitration
Forty of Charleston AI’s 161 completed projects fit this pattern. Participants report saving about 20 hours a week. The employee has hired a personal AI to do the work.
Private practice.Public evidence.
Completed projects fitting this pattern
Average saving reported by participants
John Rector’s private tutoring observations. Project counts; self-reported time savings.
The salary still goes to the human.
At Charleston AI, we have completed 161 projects. Forty of them fit the pattern I am describing here. I am these clients’ private tutor, so I will not name names. On average, they tell me they are saving about 20 hours a week.
An employee pays for a personal AI account. They teach it the recurring parts of their job: where the information lives, what the deliverable should look like, which exceptions matter, and what must be checked before anything leaves their desk. The employer receives the work. The employee receives the salary. The AI performs a growing share of the production.
I call this labor arbitration: the employee privately deciding how much of the labor attached to their salary they will perform themselves, how much they will delegate to their own AI, and how much of the resulting time they will keep.
The attraction is straightforward. Have the AI do the work. Keep the income. Recover part of the week. Recognition for being an exceptional employee may follow, but recognition is not the prize in this arrangement. The prize is time.
These are observations from my practice, not a representative survey. Forty projects does not necessarily mean forty distinct employees, and the hours are reported by participants rather than independently measured. Within that boundary, the pattern is concrete. People are doing this now.
People are funding the other system.
Deloitte’s September 2026 research surveyed 25,000 UK workers. Among generative AI users, 17% said they personally paid for at least one tool used for work, and 31% said they used generative AI without their employer’s knowledge. The fieldwork ran from May into June. These are reports of existing behavior. Read Deloitte’s findings.
The distinction between a company’s AI and an employee’s AI is therefore already material. There can be two accounts, two histories, two sets of instructions, and two very different reasons for opening the application.
Microsoft and LinkedIn had identified the direction in 2024: 78% of surveyed AI users brought their own AI tools to work, while 52% were reluctant to admit using AI for their most important tasks. Bringing a tool does not necessarily mean paying for it, and reluctance does not prove concealment. Still, both findings predate today’s more capable agents. Read the 2024 Work Trend Index.
A personal account can become the place where the worker accumulates a working method. The useful asset is the collection of examples, instructions, corrections, and repeatable procedures around the model. “Teaching the AI” can mean building that context; it need not mean retraining the underlying model.
A personal front door to company work.
Claude on a laptop can be an operating interface for work spread across applications. Anthropic documents custom connectors on individual plans, and its connector directory includes Slack and HubSpot. The capability to bring communications and CRM context into an AI workflow is available now. Connector documentation · Current directory.
ERP access is more conditional. It requires an available integration, API, local tool, or permitted export, plus the necessary access. Buying a personal AI subscription does not unlock an employer’s systems. Anthropic even documents an enterprise setting designed to restrict connections from personal Claude accounts to supported work services. Read the account restriction documentation.
Consider an illustrative sales-operations workflow: reconcile a CRM opportunity list with an authorized ERP order export, use Slack context to explain discrepancies, prepare the weekly review, and draft the follow-up. A worker who used to move through those systems manually can instead teach an agent the sequence and inspect its results. This example describes a feasible workflow, not a verified case study of one employee.
The job’s expertise remains consequential. Someone must recognize a bad join, an obsolete order, a fabricated explanation, or a promise the company cannot keep. But the person doing that review may now be supervising work they previously performed line by line.
An illustrative model / not survey data
Two accounts.
Two objectives.
What changes when we look beneath the adoption dashboard?
Company AI
Logins. Prompts. Tokens.
Evidence that the employee is participating.
My AI
Instructions. Connected tools. Repeatable work.
A system the employee has taught to deliver.
The thesis concerns workers who separate these objectives. It does not imply that all corporate AI use is performative.
Tokenmaxxing measures the performance.
IBM describes tokenmaxxing as incentivizing employees to maximize AI token consumption, including through usage leaderboards. It also notes that the practice peaked in spring 2026 and has begun to wane. It is a documented incentive problem, not a synonym for every form of AI measurement. Read IBM’s explanation.
Once activity becomes the target, a worker can optimize activity. The company receives a reassuring signal: its AI is being used. That signal alone cannot tell management whether useful work happened, whether a personal agent did the meaningful part elsewhere, or whether automation reduced the need for further prompting.
In the pattern I see, the company’s AI serves the adoption requirement while the personal AI becomes the working system. The employee uses the official tool enough to meet the expectation and invests the serious instruction, correction, and workflow development in their own. My project experience gives that pattern a local basis; it does not tell us how common it is across the workforce.
A very effective personal automation might consume fewer tokens over time. Once the AI has written a reliable script, the script can repeat the task. A dashboard that prizes consumption may reward the noisier worker while overlooking the better system.
Twenty hours changes the relationship.
The average saving my participants report is about 20 hours per week. In a conventional 40-hour week, that is half the week. It is enough to change what a job feels like and how much of a person’s life it occupies.
These are people who sought private help, a group selected for its interest in making AI useful. Their results should not be generalized to everyone who opens a chatbot. Deloitte’s broader research reports only 70 minutes saved per week on average across the UK workforce, with most saved time used for more work for the same employer. The populations and methods differ; the figures are not directly comparable.
That distinction is central to the thesis. An occasional prompt and a taught workflow are different arrangements. One helps with a moment of work. The other can take over recurring execution across a substantial part of a role.
The employer may still receive the same deliverables, on the same schedule, at the same standard. What changes is the amount of human execution behind them. A familiar salary can now support a person who supervises an AI doing much of the work.
The company may see spare capacity. The employee may see a life returned to them. Both are looking at the same recovered hours.
Secrecy protects the arrangement.
The worker in this arrangement has little reason to announce every recovered hour. Disclosure can turn a private improvement into a higher output expectation. A task that formerly filled an afternoon can become the justification for assigning three more.
There is experimental evidence that disclosure can also affect perceived compensation. A research preprint reports ten studies in which participants reduced compensation for AI-assisted workers, including conditions that held output quality constant. The authors connect the effect to reduced credit for the worker. Those experiments do not establish what every employer will do, but they illuminate a reason to hesitate. Read the compensation research.
Job security can help explain the secrecy without being the reason the worker built the system. The immediate ambition can remain wonderfully ordinary: finish the work and have more time.
Social cover adds another layer. In Anthropic’s 2025 interview study, a fact-checker said: A colleague recently said they hate AI and I just said nothing.
The researchers found that 69% of their general professional sample mentioned stigma. That is not a finding that 69% secretly used AI. The sample was recruited through crowdworker platforms, and the study explicitly cautions against broad generalization. Read the interviews and limitations.
My stronger hypothesis is that some private users may go beyond silence and join public expressions of AI hostility. Neither the project count nor the external sources here establish how often that happens. Nor should we presume that an AI critic is secretly using it. A person can sincerely dislike AI’s social consequences while finding it useful in their own working life.
What the documented silence does show is that visible sentiment and actual practice can diverge. A room that sounds hostile to AI may contain people whose working day already depends on it.
The negotiation has already begun.
The familiar story places the employer in charge of automation. Management selects the technology, redesigns the workflow, and decides what to do with the savings. Personal AI introduces another actor capable of making those decisions first.
The employee can become the designer and supervisor of a small production system inside an existing job. Paying for that system personally can feel worthwhile because the return is measured in hours of their own life.
Personal payment does not settle ownership of work, make company information private property, or remove responsibility for what the system does. It does, however, help explain why an employee might willingly fund capability that a company assumes it controls through procurement.
For management, the useful question goes beyond whether employees are using the approved AI. Which work has already changed? Who designed the new process? What reason does that person have to reveal it? And what share of the benefit can they expect to keep?
Labor arbitration names that unsettled arrangement. The human remains on payroll. The personal AI takes on execution. The employee tries to retain the difference as time.
1 thought on “Labor Arbitration”