How to build your AI Agent workforce

01

Who should use this

You are building a real company. You want systems and some of your time back. Another clever prompt will not clear the inbox, the calendar, the site, or the pipeline.

Start with three seats that pay for themselves: an EA for time, an SDR for revenue, and a Dev bot for shipping. Add Content or a specialist when the same work keeps stacking and you want a clean job for it. The roster later in this guide is a menu, not a day-one checklist.

02

What is a Grok Bot agent

Grok Bot is an AI teammate. It has a name, a title, a description, a memory, and a conversation that stays open. Name it something you will actually say. Title is the job. Description is the standing rules and the approval boundary.

This is the teammate view. Desktop and phone. Named jobs, a live chat, routines.

Plugins sit on your Cursor account so every agent can use them. Sites with no plugin run in a browser on a cloud computer. You take that computer over and sign in. It never sees your password and can use most software tools the way an employee would.

A General Helper has no job, so it keeps no useful memory. Never start with one General Helper. Cursor caps an account at 50 bots and group chats. You will hit a foggy helper long before 50.

03

How is an agent different from an LLM

An LLM answers a prompt. An agent has a job. That is the whole split.

Look at Grok next to GPT and Fable. The model holds. It also routes to Claude for certain tasks.

Then look at the cost. Grok 4.6 ranked first among models tested under a $5 workload budget. Intelligence per dollar is getting ridiculously high.

04

What do you get from an agent

05

How do you set this up

Setup before talk. First you give the bot a job, context, and access. Only then do you assign work.

1. 01

   Buy the seat on the web

   Open cursor.com/dashboard/billing in a browser and pick a paid Cursor plan. Grok Bot is included on Pro, Pro+, Ultra, and Teams. Higher plans hold a bigger weekly usage bucket.

   Buy it on the web so the seat sits on your Cursor account. That is the account you will sign into Grok Bot with.

2. 02

   Sign in to Grok Bot

   Sign in with the same Cursor account that owns the plan. Named jobs, a live chat, routines. Desktop and phone.

3. 03

   Create your first agent

   Open Bot actions, then Edit Profile. Name it something you will say out loud. Title is the job. Description is the standing rules and the approval boundary.

   A General Helper has no job, so it keeps no useful memory. Never start with one General Helper. Cursor caps an account at 50 bots and group chats. You will hit a foggy helper long before 50.

4. 04

   Dump your context in

   The first dump is the briefing you would give a hire. If you already wrote that briefing in Claude or ChatGPT, bring it over. Add the docs that show what good looks like.

   Then point the bot at Brand DNA in Drive and tell it to open the file. Do not summarize DNA into the description and hope. The full dump lives later in this guide, under what you feed them.

5. 05

   Connect email, calendar, Drive, CRM

   Connect plugins from the sidebar Plugins list, or the in-chat Connect card. Authorize in the browser. If it says Waiting for authorization, hit Reopen. Disabled by team admin is a Teams policy.

   Give this first bot only what the first job needs: work email, calendar, and Drive. Leave personal mail alone. The Chief of Staff cannot brief a week it cannot see. If the morning brief invents a meeting, fix the calendar plugin before you add anyone else.

   You upload the CRM. The bot reads and drafts against live records. Do not let the bot reformat a giant spreadsheet. A 4,500-row import can burn a weekly bucket and still ship a broken file.

   Least privilege is the rule. A content bot does not need the ads account. An influencer bot does not need the personal inbox.

   Never paste an API key into chat. Cursor has a secret store.

   For sites with no plugin, take over the Grok Bot computer. You sign in. It never sees the password. You type the 2FA. The session stays. One login can serve more than one bot because they share the computer.

   If the job is code, the bot stays the coordinator. The Cloud Agent rule is later in this guide.

6. 06

   One concrete first job, then Talk

   First message is one concrete job. Read tomorrow's calendar. Write a brief. Do not email anyone.

   Then hit Talk and speak the next one. Set a meeting with these three people. Ask them for times. Use my booking link. Typing at one model is the old loop.

   Setup before talk. Talking without the role, the file, and the access is just another chat window.

7. 07

   Add the next bot when ready

   Add the next bot only when the same job keeps landing on the Chief of Staff and the context is getting muddy. Name it so it feels personal. If a workflow hits you over and over, it can be a job: invoices, books, bug tickets, repeat build work.

   Sidebar Sections group bots by business task so you know who to go to.

   Hide does not pause routines. Delete only when you are sure. Shared computer files and logins are not isolated per bot.

8. 08

   Turn repeats into routines

   Recurring work becomes a routine. A weekday-morning brief. A weekly content pack. Write the routine as the job, not as a frozen recipe.

   Standing rules stay in the description. Today's task goes in Talk. How you train those repeats is its own section below.

06

Which jobs should you name first

Name each bot so it feels personal. What I named mine is not the point. If a workflow hits you over and over, it can be a job: invoices, books, bug tickets, repeat build work. Start with three. Add the rest when the Chief of Staff starts holding two brains.

07

The full roster

For each job: what it owns, day-one access, what you stay on, who it is for, skills, routines, and tools.

08

When do you add the rest

Add a bot when the same job keeps landing on the Chief of Staff and the context is getting muddy. Content, a specialist, influencers, or finance only when that loop is real.

AI Visibility is later-stage. Wait until you have a stamped story to feed it, and until customers ask ChatGPT who to hire.

Client Ops is useful the moment you have more than two customers and you are the only person who knows the state.

Coach is optional. A standing place to think that does not also hold the inbox.

09

How do you ship software

If the job is code, do not let the bot write it on the Grok Bot computer. That burns the weekly Grok Bot bucket. A Cursor Cloud Agent does the repo work on Cursor credits.

The bot stays the coordinator. It names the repo, the branch, and the full task. It launches the Cloud Agent. Then it watches and reports. Use your Cloud Agent default model unless you name one.

Put this in the description of any bot that ships software. Day one, not after it has already burned a week of local edits.

Do not write or edit product code on your Grok Bot computer. For any coding, repo, PR, test, or CI work, launch a Cursor Cloud Agent on my connected repo. Pass the full task, repo, and branch. Then monitor that agent and report back. Use my Cloud Agent default model unless I name one.

10

Which tools should you connect

This is the stack I actually run. Connect once on the Cursor account. Every bot can use those plugins. Assign per job. Give each bot only the access that job needs. Skip a tool you will not read.

Sites with no plugin take over the Grok Bot computer. The founder signs in. Never paste API keys into chat.

• G

  Google Workspace

  Gmail, Calendar, Drive. Day-one connect for the Chief of Staff.

  workspace.google.com

• B

  Breakcold

  CRM. System of record. You upload the sheet.

  breakcold.com · Login

• S

  Smartlead

  Warmup and cold send. Not the newsletter tool.

  smartlead.ai

• N

  Nitrosend

  Newsletter only. Content composes. Founder sends. CRM stays Breakcold.

  nitrosend.com · Join

• V

  Vercel

  How sites ship. Pair with GitHub.

  vercel.com

• G

  GitHub

  Source of truth for code and Issues.

  github.com

• C

  Canva

  Decks, images, and pack assets for Content.

  canva.com

• C

  Cal.com

  Meeting page. 15, 30, and 60 minute types. Block closed hours.

  cal.com

• X

  X

  Social after pack review. Content drafts. You publish.

  x.com

• O

  OpenSEO

  Cursor plugin for AI Visibility. Ask before paid credits.

  Cursor plugin

11

What do you feed them

A Brand DNA document. One file in Drive. Positioning, voice, claims you will stand behind, claims you will never make, who you write for.

Point every bot at that file. Tell them to open it. An agent that writes without DNA invents a category.

If you have no DNA yet, sit down for an hour and write:

• Who you serve, in their words
• The offer in one sentence
• Two claims you can prove with a receipt
• The words you refuse
• How you want to sound on a call with a friend

Drop the file in Drive before you create the second bot. If you want a structured version, that is what Guide IQ is for. Twelve founder inputs become the brief the agents read.

12

How do you train the repeats

Standing rules go in the description. Today's task goes in Talk. A job you do every weekday becomes a routine. Write the prompt as the job. Read tomorrow's calendar. Write a brief. Do not email anyone.

Correct it when it is wrong. If the brief invents a meeting, fix the source. Memory keeps the role. A new chat on a named bot still knows the job. A General Helper starts over every time.

13

How do you keep it human

Bots augment you. They do not replace judgment. You stay on send, spend, and the story.

Mistakes I have already paid for:

• Do not connect your whole life. Each bot gets only the access that job needs.
• They invent a meeting, a number, or a category if the source file is not open.
• They will burn the weekly bucket reformatting a giant CRM and still ship a broken import. You upload the sheet.
• A bot that sends without you can wreck a domain or a relationship. Draft. You say send.
• A bot that can spend will spend. Draft the plan. You approve the number.
• Secrets never go in chat. You take the computer for passwords and 2FA.

14

How you stop the writing from sounding like a model

A model predicts the next likely word. That is why the prose drifts toward phrases that fit every case and sound like nobody.

I keep a skill for this. Humanizer. Every writing bot gets it. Content, the newsletter, LinkedIn, pitches. Scan the catalog first. Then rewrite each tell into the plain claim underneath. Do not freestyle-edit.

Four rules, in this order.

A writing sample beats every style rule, including the em dash ban. If the person uses dashes, match that. My voice does not, so my drafts have zero.

Two things never bend. Invent nothing. And unless the sample uses them, drop the dashes.

Personality belongs on blogs, essays, and anything with a point of view. Leave it off legal, technical, and reference pages. Neutral is the human voice there.

The catalog is 33 tells. Wikipedia's Signs of AI writing page, from WikiProject AI Cleanup, is where the list comes from. The ones that show up most in founder drafts: significance language (pivotal, testament, landscape), copula dodge (serves as, boasts, features), negative parallelisms (it is not X, it is Y), the rule of three, AI vocabulary (delve, crucial, tapestry), fake-candid openers (here is the thing), and a stack of short punchlines.

The rest lives in the skill. Put the skill on the bot. Do not paste a Wikipedia page into the description.

Then run the loop. Find every tell. Rewrite. Ask two questions: what still sounds like a model, and did I add a fact that was not there. Fix those. Scan for dashes. If one remains, you are not done.

Do not gut a real receipt because it is specific. Specific is the human part. Mixed feelings stay. Uneven sentences stay. One short line is fine. A stack of them is a tell.

Put this skill on the Content bot the day you create it. Put it on any bot that writes in public.

15

How does a teammate get in

They do not sit in your sidebar. Email the bot as the primary path for partners. Give the bot a receive-only alias. It replies as their assistant. Lists, research, CRM logging. Sends still wait for you.

A Cursor Teams seat is for humans who need their own bots. They can share Drive and the CRM. They cannot inherit your Chief of Staff.

Pick one path. An alias that is a ticket. A Slack channel the bot is in. Or their own Chief of Staff pointed at the same Drive. A public share link makes a copy on their account. It does not give them your computer or your history.