AI Use Cases for Business
Submit
PlaybookBuilt from the public setups listed at the bottom

Autonomous agentic business: named Bots, a weekly newsletter, posts twice a day

A setup for a one-person media or info-product business: a Chief of Staff Bot, a social Bot posting in two daily windows, and a newsletter Bot, with two short approval passes a day.

Grok BotSolo foundersCreatorsAgencies
Setup
An afternoon to set up, then two weeks of supervised runs
Your time
Design target: two short approval passes a day

This is what the setup aims for, not a measured result. Expect more of your time during the first two weeks.

  1. Name the business and hire a Chief of Staff first

    Write one paragraph: what you publish, for whom, how it makes money, and your target for the next 90 days.

    Create a Chief of Staff Bot with read access to your email, Slack or Discord, and Notion or Google Drive. Its first job is an audit, not production.

    PromptWritten by our editors
    You are Chief of Staff for [business], which publishes [topic] for [audience] and earns money from [newsletter sponsors / digital products / services].

Read our Notion or Drive, email and chat. Write a one-page audit: what we publish, each step and how long it takes, and where revenue comes from.

Recommend the two or three Bots that would save the most time or earn the most first, with a one-paragraph job description for each.

Don't create Bots, send email or change anything until I approve.

    Audit-first approach from the Arlington Bagel setup, as reported by Stork.ai.

  2. Write the handbook every Bot reads

    Create one page with your voice, topics, claims you never make, sources you trust, and where each Bot saves its work.

    Have the writing Bot read your last 30 posts and 3 newsletter issues and propose a style guide. Approve it before any drafting starts.

    PromptWritten by our editors
    Read my last 30 posts on [X / LinkedIn] and my last 3 newsletter issues.

Write a style guide in 10 lines or fewer: length, openings, tone, formatting, words I use and avoid, and how I end posts.
Then list 5 topics I return to most, with one example post for each.

Wait for my OK before drafting anything.

    Voice-first setup from Debbie O'Brien's walkthrough.

  3. Add the posting routine: two windows a day

    Create a social Bot with two daily routines, for example 8:30 a.m. and 4:30 p.m. Each run drafts one or two posts from the handbook topics, your content calendar, and what is new on X. Bots can search X without you connecting an account.

    Drafts wait for approval before anything posts. Your two approval passes are the only scheduled human work.

    PromptWritten by our editors
    Twice a day, at 8:30am and 4:30pm, draft 2 posts for [X account].

Sources: the handbook topics, [content calendar], and the most-discussed X posts in [niche] since your last run.
Rules: follow the style guide, one idea per post, link to the source when you use one, no claims that aren't in the handbook's approved list.

Park both drafts for my approval. If nothing is worth posting, say so instead of filling the slot.

    Two posting windows a day is the pattern this playbook was asked to follow. We couldn't find the original demo, so this step uses Grok Bot's documented routines and X search.

  4. Add the weekly newsletter

    A newsletter Bot collects the week’s best posts, replies and links every Thursday, drafts the issue in your voice, and saves it as a Page for your edit.

    You edit once and send from your email platform. The Bot can claim its own email address to receive reader replies, and any reply it sends waits for your approval.

    PromptWritten by our editors
    Every Thursday at 9am, draft this week's issue of [newsletter].

Collect: our 5 best-performing posts this week, the best reader replies, and 3 links worth sharing from [sources].
Write it in our voice using [last 3 issues] as examples, under [600] words, with sections: [sections].
Suggest 3 subject lines. Put anything you're unsure about in a "Check" list at the top.

Save it as a Page. Don't send or schedule it.

    Based on the Newsletter Writer template on xAI’s use-case page and the Arlington Bagel setup.

  5. Close the loop every day and every week

    Each Bot sends the Chief of Staff five lines at 6 p.m.: shipped, stuck, needs a human, tomorrow, risk. The Chief sends you one brief at 7 a.m.

    Every Friday, the Chief reviews the week: what shipped, what got stuck, and which Bot gets more or less scope.

    Track one number daily, the way Nat Eliason’s agent Felix posts a nightly revenue review: subscribers, sales or replies.

    PromptWritten by our editors
    Every day at 7am, send me one brief built from yesterday's five-line reports. Lead with "Needs a human."
Add one line with [subscribers / sales / replies] yesterday, the 7-day average, and the change from last week. Show the arithmetic.

Every Friday at 3pm, review each Bot: shipped, stuck, clean runs, and your recommendation (keep, expand, narrow, pause), with one line of evidence.
Don't change any Bot or routine. Propose, then wait for me.

    Five-line reports as recommended in the Arlington Bagel write-up; the nightly revenue review from Nat Eliason’s Felix.

  6. Promote slowly

    After five clean runs in a row, let a Bot take on one more kind of task. Keep posting behind approval unless you are comfortable with every draft going out unseen.

    Check your usage weekly. Several Bots on routines add up quickly, and Bots share one computer, so cap how many jobs run at once.

    Promotion rule from distort's onboarding guide; computer sharing from replies to Debbie O'Brien's prompt.

Guardrails

  • Every post, email and purchase waits for approval. Don't turn off drafts for the social or newsletter Bot.
  • One business per Grok Bot account, so context and memory don’t bleed between projects.
  • No income, health or results claims that aren't in the handbook's approved list.
  • Keep account passwords out of chats; use sign-in cards, Secure Forms or 1Password.

Business fit

  • Solo foundersA one-person info-product or media business can publish daily without writing every post.
  • CreatorsCreators keep two posts a day and a weekly newsletter going through busy weeks.
  • AgenciesConsultants can run their own thought-leadership engine, or set one up for each client.

Use cases behind it