BYOA — Bring Your Own Agent

Mar 31, 2026

Recently Alex Hormozi talked about how jobs are changing and what is being done to automate roles in a business.

Each job role has a description of what the person will do in that role. Most roles are workflow-based — essentially a set of tasks that need to get done.

The anatomy of a role

Consider a software engineer. The role requires someone to:

• Read and write code
• Review other people’s code
• Design software
• Coordinate with team members
• Report to manager
• Write specs, docs, emails

These are some high-level tasks that can be broken down further if required. These tasks, along with the unique knowledge and context of the company or product, make a software engineer.

What can be automated right now

The core idea is to think about which parts of these tasks can be automated.

For example:

• Merge conflicts — takes up a significant amount of time
• Preliminary code review — lint issues, flagging company policy violations, etc.

These are just two very small tasks that can be automated right away with an AI agent and the right tools.

BYOA is becoming the expectation

I have been looking at many job posts recently, and most of them expect the applicant to bring their own workflows, agents, and tools — to make it easier and faster for them to do their job and get outcomes faster.

This trend is something I suspect will keep growing. What I am doing right now:

• Encode my knowledge base (doing it for the last 3 years)
• Provide agents with tools to make them better at doing their job
• Write, write, write — SOPs, workflow specs, instructions, prompts

The proactive framing

This line of thinking makes you proactive:

“How can I automate myself out of my job in the next two months?”

If this is something you are already doing or care about, you are already on the right track.