←Back/Operations/ChatGPT/Codex
AdvancedOperations

How to Manage Business Operations with Role-Based AI Agents

Organize your business operations by creating a 'fellowship' of specialized AI agents. This workflow shows how to silo responsibilities into projects and assign distinct roles to AI assistants to automate administrative tasks and context retrieval.

Illustration for How to Manage Business Operations with Role-Based AI Agents

I just called him Gandalf. Straight up. And then I asked Gandalf to create everyone else. I needed other bots for engineering, marketing, project, uh, product management, account sales, and customer success... Elrond, the elf, runs engineering. I have Gimli, the dwarf... runs sales. And Sam always plays support.

Before you start

What you need

  • A list of all business functions and responsibilities.
  • Access to an AI platform that supports projects or separate contexts.
  • API or direct access to company tools (e.g., Google Suite, Notion, Linear).

What you’ll make

An operational system where distinct AI agents manage specific business functions, capable of retrieving information and executing tasks with high-level commands.

Tools used

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

5 steps

Step 01

Inventory Your Responsibilities

Before automating, you must know what you do. Create an exhaustive list of all your business roles and recurring tasks.

William listed his functions in Notion: customer success, inbound sales, product, accounting, HR, and hiring. This list is the blueprint for your agent system.

Step 02

Create Siloed Projects for Each Function

In a tool like ChatGPT or Codex, create a separate project for each major business area (e.g., 'Operations,' 'Sales,' 'Growth'). This helps organize context by task; check your assistant’s actual memory and project settings before assuming isolation.

Think of each project as a dedicated workspace for a specific department. All conversations about sales happen in the 'Sales' project.

Step 03

Define and Assign Agent Roles

Create distinct personas for agents that correspond to business functions. Start by creating a 'chief of staff' agent and instructing it to define the others.

Example prompt
You are Gandalf, my chief of staff. Your first task is to define a fellowship of AI agents to help me run my business. Create personas for agents responsible for Engineering, Marketing, Sales, Accounts, and Customer Success, and describe their primary duties.

The names (Gandalf, Elrond, Frodo) make the system memorable, but the key is the operational separation of duties.

Step 04

Grant Contextual Access to Your Tools

Connect your agents to your company's systems of record, such as Google Suite, Notion, Linear, and QuickBooks. This allows them to retrieve information autonomously.

The source recommends extreme caution here. Unlike William's 'allow always' approach, a safer path is to start with read-only access and enable specific write permissions with human oversight.

Step 05

Delegate a Context-Rich Task

Test the system by giving a high-level command that requires the agent to access multiple sources and perform an action.

Example prompt
I just finished a call with [Candidate Name]. Find their information in my email and calendar, create a profile for them in our 'Three Pipes' recruiting tool, and give me a summary.

Success is when the agent can execute the task without you having to manually copy and paste information between applications. However, always verify the output for accuracy.

What good looks like

  • Agents are successfully assigned to distinct business roles.
  • An agent can autonomously retrieve information from connected tools (e.g., calendar, email) to fulfill a request.
  • The system reduces the time spent on manual data entry and context switching.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

Runbook notes

How to recover when the loop fails and where human judgment helps.

If it goes sideways

An agent performs an incorrect or destructive action due to having overly broad permissions.
Start with read-only access to all tools. Grant write access incrementally for specific, reversible actions. Implement human approval gates for any critical tasks like sending invoices or modifying customer data. Do not copy the 'allow always' permission model without fully understanding the risks.
An agent provides an inaccurate summary or a biased ranking (e.g., for job candidates).
Always treat AI-generated analysis as a first draft or an input, not a final decision. Manually verify the source information and apply your own judgment, especially for sensitive tasks like hiring.

Human checkpoints

Let routine work keep moving.

  1. Before granting write access to any tool, approve the specific actions the agent is allowed to take.
  2. Review any automated candidate rankings or performance analyses before making a decision.

Start shipping better products.

Join 250,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start · 14-day Pro trial · SOC 2 Type II