{"ok":true,"slug":"ai-chief-of-staff","title":"How to hire an AI chief of staff who runs your other bots","url":"https://bot.store/academy/ai-chief-of-staff","summary":"How to hire an AI chief of staff who runs Recruiter, writer, and researcher as named seats, not one generalist. A founder can start this week.","markdownUrl":"https://bot.store/academy/ai-chief-of-staff.md","markdown":"---\ntitle: How to hire an AI chief of staff who runs your other bots\nslug: ai-chief-of-staff\ndescription: How to hire an AI chief of staff who runs Recruiter, writer, and researcher as named seats, not one generalist. A founder can start this week.\ncategory: use-cases\nhero_image: /academy/ai-chief-of-staff.jpg\nhero_alt: A coral boss mascot at a glass table hands job cards to mint writer, blue researcher, and orange finder mascots.\npublished: 2026-09-01\nrecipe:\n  - name: Chief of staff\n    job: One-page plan, hire briefs, keep or cut, one next action. Not the specialist.\n    listing_url: /bots/chief-of-staff-aryaman\n  - name: Recruiter\n    job: Given a hire brief, find the seat on bot.store. Does not invent work.\n    listing_url: /bots/talent-matchmaker\n  - name: Writer\n    job: One communication job. Turns this week's plan into one page a founder can run. Not strategy.\n    listing_url: /bots/human-copywriter\n  - name: Researcher\n    job: One research job. A person checks the sources. Not publishing.\n    listing_url: /bots/research-bot\n---\n\n**Takeaway:** Hire the boss bot first. They write the week, then run Recruiter, Writer, and Researcher. You don't run four chats.\n\n\n\nYou just got Grok Bot. Don't dump every job in one chat. Hire an AI chief of staff first. They write the week's plan. They write the hire briefs. Then they run Recruiter, Writer, and Researcher. You stay the owner.\n\nThe seats are Grok Bots you copy from bot.store. Get is live on the recipe. One chat that writes, researches, and hires is a generalist. Named seats beat that.\n\n## What the boss bot actually does\n\nThey are not the writer. They are not the researcher. They are not Recruiter.\n\nThey turn a messy goal into one page: company in one sentence, one number for 90 days, who exists this week, three things you will not do, three outcomes with one owner each. Then they write a hire brief before anyone new shows up. When work comes back they keep the useful bit, cut the rest, and name one next action: one person, one verb.\n\nSearch this query and you land on a [tools roundup](https://get-alfred.ai/blog/best-ai-chief-of-staff-tools). Inbox apps in a stack. This page is the desk. A boss bot. Three seats with edges. A Friday where someone decides what survives.\n\n[Charlie Grinnell](https://www.linkedin.com/pulse/how-i-built-ai-chief-staff-actually-works-charlie-grinnell-qf9rf) built one that actually runs a week, not a chat that says \"sounds good.\" [Jeffrey Bussgang](https://www.linkedin.com/pulse/you-need-hire-ai-chief-staff-now-jeffrey-bussgang-wym4e) says hire this seat now, before you hire more people. A [morning-routine post on r/productivity](https://www.reddit.com/r/productivity/comments/1lpe8yd/i_replaced_my_morning_routine_with_an_ai_chief_of/) swapped a solo morning for a chief of staff. Fine for a routine. You need a company seat: plan, briefs, Friday.\n\nOn Grok Bot, people already run this. [MedalofHonour15](https://www.reddit.com/r/GrokBot/comments/1vx9q3i/) ran a chief of staff with specialists. [N273MB](https://www.reddit.com/r/GrokBot/comments/1vzjbmp/) put one on the inbox so the rest of the desk was not reading every mail. [Krista Letz](https://x.ai/bot/guides/grok-bot-for-gtm) uses one to run GTM bots. [Igor's chief of staff pack](https://grokbot.dev/marketplace/chief-of-staff-igor/) is a public seat you can open. Proof it exists. Yours still works off your one-page, not theirs.\n\n## Then they run the other three\n\nFour seats is a lot. Week one is often just the chief of staff plus one specialist. These four are the seats on this page. Don't add a fifth so the org looks busy.\n\n**Chief of staff.** The door. Plan, briefs, Friday. Not the specialist. If they start drafting the page because it's faster, you are back to one chat.\n\n**Recruiter.** The chief of staff hands them a hire brief. They find that seat on bot.store. They don't invent work. They don't rewrite the brief to match whatever is listed. [Kevin Niparko](https://x.ai/bot/guides/grok-bot-for-pms) describes a Recruiter-shaped seat on a PM desk. That is the job.\n\n**Writer.** One communication job. They turn this week's plan into one page a founder can run without a meeting. Not strategy. Not publishing. First action: draft page one, hand it to the chief of staff, don't publish it.\n\n**Researcher.** One research job. They answer one question with sources you can click. A person checks those sources. They don't draft the page. They don't publish. If this week has no research job, you don't hire a researcher.\n\nSkip job boards. That is a human hire. Skip tools that call themselves the product and then sit in Slack. You are hiring a Grok Bot seat, then teaching it your desk.\n\n## How to start with an AI chief of staff this week\n\nMonday. You and the new chief of staff. Blank note. Five headings only.\n\nCompany. One sentence for what this is.\n\nNorth star. One number for 90 days. One. Not a dashboard.\n\nWho exists. Who is on the desk this week, and what each owns.\n\nNot doing. Three tempting things.\n\nThis week. Three outcomes. Each has one owner. Two owners means nobody owns it.\n\nIf a thought doesn't fit, it's not on the page. The chief of staff can draft those five fields. They don't get a sixth. You cut anything that sounds like strategy.\n\nHere is a small desk. You ship short how-tos for founders who build software. That is the company sentence. For 90 days you call it a win if three of those pages are live. This week you exist, a chief of staff exists, and a writer exists. Recruiter is off. Researcher is off. You are not starting a second product, not launching a newsletter, and not drawing twelve seats.\n\nThe three outcomes: the one-page gets signed (chief of staff), the writer turns in a draft a founder can run without a meeting (writer), Friday you review (chief of staff).\n\nThen a hire brief before you create a seat. Name. Job in one sentence. Three ways a stranger can tell they are done. What is not their job. First action this week. A brief that says \"help with content, make it good, start\" is how you rehire the generalist.\n\nIf this week is one communication job, call them Writer. They are done when it is one job and one page with no strategy section, a founder can name the first action after one read, and nothing wandered off the brief. Strategy, hiring, a second page of research, and publishing are not their job.\n\nIf the one-page only needs a writer, you write one brief. Don't brief a researcher in case. Don't send Recruiter hunting because a chart has a blank.\n\nFriday you decide. Keep the one true, useful thing. Cut anything vague or off the brief. Name one next action: one owner, one verb. If a founder can't run the page after one read, it goes back. The chief of staff writes that note so you are not line-editing five chats. They don't tidy the draft and send it. If it still needs writing, that next action belongs to the Writer.\n\n## Share, copy, and the missing update path\n\nA Grok Bot share is a copy. Training stays on the maker's account. When they get better, your copy does not. Free on bot.store is always v1, frozen. That is the first version they uploaded. Paid is the missing update path: a way for new training to leave their account and reach the copy. It is not a live product promise on this page. We are not building a feed here. Don't read this as a shipped update loop.\n\nIf you make bots, you can charge for updates that currently die on your bot. If you hire one, you pay because you want those updates if and when that path exists. Until then, treat a free Get as v1. Sit with it. Teach it your desk.\n\n## Common questions\n\n**What does the boss bot do?** They write the week's plan and the hire briefs. They keep, cut, and name one next action. They don't do the specialist work.\n\n**How do I start this week?** Copy the chief of staff. Write the one-page with them on Monday. Brief only the seats this week actually needs. Review on Friday.\n\n**Do I need Recruiter on day one?** Only when you have a hire brief to fill. No brief, no Recruiter.\n\n**Where do the bots come from?** Copy them from bot.store. Get is live on the recipe listings.\n\n**Will my copy keep up with the maker?** Not as a share. Training dies on their account. Free is v1 frozen. Paid is the missing update path, not a shipped feed.\n\n## The recipe\n\nFour seats. One job each. Get is live.\n\n**Chief of staff**\nOne-page plan, hire briefs, keep or cut, one next action. Not the specialist.\n\n**Recruiter**\nGiven a hire brief, find the seat on bot.store. Does not invent work.\n\n**Writer**\nOne communication job. Turns this week's plan into one page a founder can run. Not strategy.\n\n**Researcher**\nOne research job. A person checks the sources. Not publishing.\n\nYou can hire these seats one at a time from bot.store.\n","steps":[{"name":"What the boss bot actually does","text":"They are not the writer. They are not the researcher. They are not Recruiter. They turn a messy goal into one page: company in one sentence, one number for 90 days, who exists this week, three things you will not do, three outcomes with one owner each. Then they write a hire brief before anyone new shows up. When work comes back they keep the useful bit, cut the rest, and name one next action: one person, one verb. Search this query and you land on a tools roundup. Inbox apps in a stack. This page is the desk. A boss bot. Three seats with edges. A Friday where someone decides what survives. Charlie Grinnell built one that actually runs a week, not a chat that says \"sounds good.\" Jeffrey Bussgang says hire this seat now, before you hire more people. A morning-routine post on r/productivity swapped a solo morning for a chief of staff. Fine for a routine. You need a company seat: plan, briefs, Friday. On Grok Bot, people already run this. MedalofHonour15 ran a chief of staff with specialists. N273MB put one on the inbox so the rest of the desk was not reading every mail. Krista Letz uses one to run GTM bots. Igor's chief of staff pack is a public seat you can open. Proof it exists. Yours still works off your one-page, not theirs.","actor":"human"},{"name":"Then they run the other three","text":"Four seats is a lot. Week one is often just the chief of staff plus one specialist. These four are the seats on this page. Don't add a fifth so the org looks busy. Chief of staff. The door. Plan, briefs, Friday. Not the specialist. If they start drafting the page because it's faster, you are back to one chat. Recruiter. The chief of staff hands them a hire brief. They find that seat on bot.store. They don't invent work. They don't rewrite the brief to match whatever is listed. Kevin Niparko describes a Recruiter-shaped seat on a PM desk. That is the job. Writer. One communication job. They turn this week's plan into one page a founder can run without a meeting. Not strategy. Not publishing. First action: draft page one, hand it to the chief of staff, don't publish it. Researcher. One research job. They answer one question with sources you can click. A person checks those sources. They don't draft the page. They don't publish. If this week has no research job, you don't hire a researcher. Skip job boards. That is a human hire. Skip tools that call themselves the product and then sit in Slack. You are hiring a Grok Bot seat, then teaching it your desk.","actor":"human"},{"name":"How to start with an AI chief of staff this week","text":"Monday. You and the new chief of staff. Blank note. Five headings only. Company. One sentence for what this is. North star. One number for 90 days. One. Not a dashboard. Who exists. Who is on the desk this week, and what each owns. Not doing. Three tempting things. This week. Three outcomes. Each has one owner. Two owners means nobody owns it. If a thought doesn't fit, it's not on the page. The chief of staff can draft those five fields. They don't get a sixth. You cut anything that sounds like strategy. Here is a small desk. You ship short how-tos for founders who build software. That is the company sentence. For 90 days you call it a win if three of those pages are live. This week you exist, a chief of staff exists, and a writer exists. Recruiter is off. Researcher is off. You are not starting a second product, not launching a newsletter, and not drawing twelve seats. The three outcomes: the one-page gets signed (chief of staff), the writer turns in a draft a founder can run without a meeting (writer), Friday you review (chief of staff). Then a hire brief before you create a seat. Name. Job in one sentence. Three ways a stranger can tell they are done. What is not their job. First action this week. A brief that says \"help with content, make it good, start\" is how you rehire the generalist. If this week is one communication job, call them Writer. They are done when it is one job and one page with no strategy section, a founder can name the first action after one read, and nothing wandered off the brief. Strategy, hiring, a second page of research, and publishing are not their job. If the one-page only needs a writer, you write one brief. Don't brief a researcher in case. Don't send Recruiter hunting because a chart has a blank. Friday you decide. Keep the one true, useful thing. Cut anything vague or off the brief. Name one next action: one owner, one verb. If a founder can't run the page after one read, it goes back. The chief of staff writes that note so you are not line-editing five chats. They don't tidy the draft and send it. If it still needs writing, that next action belongs to the Writer.","actor":"human"},{"name":"Share, copy, and the missing update path","text":"A Grok Bot share is a copy. Training stays on the maker's account. When they get better, your copy does not. Free on bot.store is always v1, frozen. That is the first version they uploaded. Paid is the missing update path: a way for new training to leave their account and reach the copy. It is not a live product promise on this page. We are not building a feed here. Don't read this as a shipped update loop. If you make bots, you can charge for updates that currently die on your bot. If you hire one, you pay because you want those updates if and when that path exists. Until then, treat a free Get as v1. Sit with it. Teach it your desk.","actor":"human"},{"name":"Common questions","text":"What does the boss bot do? They write the week's plan and the hire briefs. They keep, cut, and name one next action. They don't do the specialist work. How do I start this week? Copy the chief of staff. Write the one-page with them on Monday. Brief only the seats this week actually needs. Review on Friday. Do I need Recruiter on day one? Only when you have a hire brief to fill. No brief, no Recruiter. Where do the bots come from? Copy them from bot.store. Get is live on the recipe listings. Will my copy keep up with the maker? Not as a share. Training dies on their account. Free is v1 frozen. Paid is the missing update path, not a shipped feed.","actor":"human"},{"name":"The recipe","text":"Four seats. One job each. Get is live. Chief of staff One-page plan, hire briefs, keep or cut, one next action. Not the specialist. Recruiter Given a hire brief, find the seat on bot.store. Does not invent work. Writer One communication job. Turns this week's plan into one page a founder can run. Not strategy. Researcher One research job. A person checks the sources. Not publishing. You can hire these seats one at a time from bot.store.","actor":"human"}]}