--- title: "From BYOD to BYOA: The New Workplace Shift Nobody’s Naming Yet" date: 2026-04-03 author: Matt url: https://www.mattwarren.co/2026/04/bring-your-own-agent/ --- # From BYOD to BYOA: The New Workplace Shift Nobody’s Naming Yet Work has been offloading its infrastructure onto workers for years. First the commute. Then the device. Then the office. Now the next shift is starting to emerge: bring your own agent. Ten years ago, bring your own device was a workplace trend. Employers increasingly expected people to have their own phone, their own laptop, and their own hardware wrapped into the company’s workflow. Then remote work pushed the idea further. For a lot of people, it effectively became bring your own office. Your internet. Your desk. Your extra monitor. Your spare bedroom. Your heat. Your coffee. The company still got the output, but more of the working environment moved onto the employee. If you go back even further, you can find older versions of the same pattern. In some industries, even getting to work used to be part of the system. Over time that became your car, your gas, your commute, your problem. That is why bring your own AI matters. Not because it is a catchy acronym, but because it fits a long-running pattern: productive assets keep moving outward from the company and into the hands of the worker. And unlike a laptop or a phone, an agent stack is not just a tool. It is accumulated capability. ## This is more than “use ChatGPT at work” A lot of people still think AI adoption means opening a chatbot and asking it a few questions. That is the beginner version. The real edge starts when someone builds a private operating system around their work: - prompt libraries refined over months - little scripts that clean data, generate reports, or move work between tools - retrieval systems and notes that give the model better context - review workflows for checking accuracy, tone, and quality - persistent agents that can wake up, monitor things, and keep moving - multi-agent setups where different models play different roles That stack compounds. I’ve written before about [how I use AI to write and publish blog posts](https://www.mattwarren.co/2026/01/how-i-use-ai-to-write-and-publish-blog-posts/) and about [building AI-operable systems instead of isolated prompts](https://www.mattwarren.co/2026/01/claude-code-first-development-building-ai-operable-systems/). The same pattern keeps showing up: the value is rarely in one prompt. The value is in the system around it. When somebody builds that system on their own time, on their own machine, with their own habits and history baked into it, they are not just bringing labor to a company anymore. They are bringing infrastructure. ## The moat is not the model. It is the context. This is where bring your own agent gets much more interesting than bring your own software. Software licenses are easy to understand. A company can buy a seat and hand it to anyone. An agent stack is different because the most valuable part is often personal. The memory lives in your account. The prompt files live in your folders. The judgment about how to scope a task, which tools to call, what good output looks like, and how to audit the result lives in a thousand small decisions you have already made. Even the context itself becomes an asset. A personal AI system gets better when it has access to your notes, your past work, your frameworks, your examples, your definitions of quality, and the patterns you have trained yourself to follow. That is part of why I built [a personal knowledge base over everything I’ve made](https://www.mattwarren.co/2026/01/building-a-personal-knowledge-base-how-i-created-a-semantic-search-engine-over-everything-ive-ever-made/). The context is not a side detail. It is the advantage. That creates a strange boundary. If an employee becomes dramatically more productive because of a personal agent stack, how much of that should transfer to the employer? Should the company expect access to the whole system? The prompt library? The memory? The scripts? The evaluation harnesses? The accumulated context? That is not a normal software procurement question. It starts to look more like asking someone to show up with their own miniature company attached. ## In software, this is already happening The clearest example is coding. A growing number of AI-assisted developers are no longer staring at code in the old way all day. They are orchestrating systems that can: - write code - explain code - edit code across multiple files - run tests and interpret failures - audit for security, style, and performance - generate documentation - compare different implementation paths - review each other and challenge each other I’ve written about [persistent agents needing a heartbeat](https://www.mattwarren.co/2026/02/lets-talk-about-the-open-claw-in-the-room/) and about [adversarial agents improving the quality of creative and analytical work](https://www.mattwarren.co/2026/02/adversarial-agents/). Once you start using these systems seriously, it stops feeling like one person with one tool and starts feeling like one person directing a small team. That matters. Because when a company hires that person, it is not only hiring judgment and taste. It is hiring the ability to mobilize an entire stack of capability on demand. And this is not going to stay inside software. Marketing teams will bring campaign-generation systems. Salespeople will bring prospecting and follow-up agents. Operators will bring reporting workflows. Researchers will bring literature-review agents. Writers will bring editorial pipelines. Scientists will bring experiment design and analysis harnesses. Whatever the domain is, the pattern is the same. The worker who knows how to build and run agents does not arrive alone. ## Better systems create an awkward compensation problem From the worker’s side, this is obviously powerful. If one person can produce the output of five or ten people because they have better systems, that is a real hiring advantage. It creates independence. It creates negotiating power. It changes what one person can realistically promise to deliver. But from the employer’s side, it creates a compensation problem. If an employee brings 10x output but gets paid on a normal salary band, most of that upside is captured by the company. And in many cases the worker is paying part of the bill. They may be covering model subscriptions. They may be covering API costs. They may have spent hundreds of hours building the prompts, scripts, notes, and workflows that make the system useful. They may even be floating the cost for a while and getting reimbursed later, imperfectly, or not at all. That is what makes BYOA different from an ordinary productivity tip. What looks like a simple efficiency story is also a story about ownership. Who paid to build the system? Who owns the context? Who keeps the prompts? Who captures the gains? ## BYOA fits freelancing better than salaried work This is why I think bring your own agent will push more people toward freelancing, consulting, and one-person businesses. If your real moat is a personal stack of AI systems, then selling outcomes starts to make more sense than selling hours. A freelancer can say: here is the result, here is the speed, here is the quality, and here is the price. That framing fits AI-powered work much better than a salary band does. It also gives the worker a cleaner way to protect the asset. Instead of donating their entire operating system into an employer’s workflow, they can keep the system private and sell the output. They can price in the tooling costs. They can improve the stack over time and keep more of the upside for themselves. This does not mean normal jobs disappear overnight. But it does mean the center of gravity shifts. If companies are trying to hire fewer people and get more output from each one, and if high-performing workers are building private agent systems that dramatically raise what they can do, the natural meeting point is not always full-time employment. Often it is some form of entrepreneurial freelancing. That may end up being one of the most important second-order effects of AI at work. ## Companies should get ahead of this now Most businesses are still treating AI adoption like a tooling question. Should we buy seats? Which model should we use? What policy should we write? Those questions matter, but they are not the whole thing. The deeper questions are organizational: - What should be company-owned versus worker-owned? - Are employees expected to use personal agent stacks? - If so, who pays for them? - If someone builds a workflow that makes them radically more productive, how should that show up in compensation? - Should critical workflows live in personal accounts and private folders at all? - What happens when the most productive person on the team leaves with the entire system in their backpack? Those questions are going to get louder. Because BYOA is not just a work habit. It is a form of capital formation at the edge of the company. The employee is accumulating productive assets outside the business, then deciding how much of that power to rent back in. ## The shift nobody is naming yet Bring your own device felt normal. Then bring your own office started to feel normal. Bring your own agent sounds strange today, but probably not for long. The people who will create outsized value over the next few years will not just be good at AI. They will know how to build agents, manage context, collect tools, define evaluation loops, and orchestrate systems that keep getting better. In other words, they will have built a private factory for thought work. That is an amazing opportunity for workers. It is also a warning sign. Because if people are expected to show up with their own devices, their own office, and now their own agent infrastructure, the obvious next question is this: Why rent all of that capability to an employer at a discount? The real question is not whether people will bring their own agents to work. It is who pays for them, who owns them, and who captures the upside when they do.