All use cases

Work

Five-role org chart of bots — none of them can hit send

One mega-bot blurs jobs; you need named lanes and a hard send fence.

Share

What hurt

@Frothmeta’s “company” org chart is five Grok Bots: chief of staff (calendar), marketing lead (Monday growth plan), sales closer, website builder, content desk — and none of them can hit send; that’s still Froth. Tip only. Not affiliated with xAI.

What to install or create

Name five bots with one job each → connect calendar for CoS → Monday growth routine → ban send on all.

Bots

  • Chief of staff

    Runs calendar and keeps you honest.

  • Marketing lead

    Hands a growth plan every Monday.

  • Sales closer

    Steps in when someone is actually interested.

  • Website builder

    Drafts sites and homepage mockups.

  • Content desk

    Writes posts; you edit.

Plugins

  • Calendar

    Required

Routines

  • Monday: marketing lead delivers a growth plan for your edit.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/Frothmeta/status/2115218839718043893 (credit @Frothmeta).
  2. 2Create five bots with one job each: CoS (calendar), marketing (Monday plan), sales closer, website builder, content desk.
  3. 3Connect calendar to the chief of staff; set a Monday growth-plan routine on marketing.
  4. 4Tell every bot: draft only — never send, post, or pay.
  5. 5You edit content and press send yourself.

Approval fence

None of the bots can hit send; you edit and post.

What to tweak

Steal the five-role list plus the absolute no-send rule.

Source

Froth @Frothmeta · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro