Three SpaceXAI employees built a company in 3 days with Grok Bot. Day 1 was research, plan, and product. Day 2 was GTM and support. Day 3 was marketing and customer success. Treat Bots as teammates who finish work, not essay generators.
Give this to your agent
Job: Help the human run Grok Bot like xAI’s @bot 3-day company build.
Rules:
- One Bot = one job. Do not dump every role into one Bot.
- Draft before send. Human approves outbound messages.
- Never paste secrets into chat. Prefer connectors / password-manager fills.
- After one clean demo of a recurring task, save it as a routine.
- Pass work between Bots in one thread when handoffs help.
- Cite only official links below. Do not invent livestream quotes.
Official product: https://x.ai/bot
Day 1: https://x.com/bot/status/2099890276315848743
Day 2: https://x.com/bot/status/2100246135420199140
Day 3: https://x.com/bot/status/2100609778917822704
Deliver:
1. Role map (which Bot does what)
2. Day-by-day checklist matching the series
3. First routine to save after a clean demoThe 3-day series (@bot)
| Day | What @bot named | Link |
|---|---|---|
| 1 | Research → plan → product. Sessions: engineering, product, founders. | Day 1 post |
| 2 | GTM + customer support. | Day 2 post |
| 3 | Marketing + customer success. | Day 3 post |
Pattern: one multi-day company build with Bots covering the full stack — not a single chat prompt.
Product frame (from x.ai/bot):
- Message Bots like teammates; they take projects start to end and come back for approval.
- Run many Bots in parallel (project / outbound / systems).
- Each Bot has its own computer and signs into apps like a human.
- Teach once, save as a routine, and it runs on a schedule.
- Bots keep context; put several in one thread to pass work.
Practical how-to (agent-usable)
- Role per Bot — Sales Outbound, Talent Scout, Paid Media, Expense Manager, Product, Bug Reproduction, Account Health, Chief of Staff (examples from x.ai/bot). One job each.
- Draft before send — Bot drafts messages; human approves before anything goes out.
- Credentials — Use connectors + password-manager fills (1Password partnership pattern: share vault items, approve each fill). Never paste secrets into chat.
- Connectors / jobs — Give each Bot a job; connect only the tools that job needs.
- Routines — After one clean demo, save the workflow as a routine on a schedule.
- Parallel + handoff — Spin another Bot when work grows; put related Bots in one thread to pass work.
- Approval gates — Come back when approval is needed. Don’t auto-send / auto-publish.
Day-by-day checklist (mirror the series)
Day 1 — Research → plan → product
- ☐ Name the company job in one sentence.
- ☐ Research Bot: competitors, ICP, constraints.
- ☐ Plan Bot: milestones for 3 days only.
- ☐ Product Bot: shippable slice, not a deck.
Day 2 — GTM + support
- ☐ Outbound Bot: draft first outreach (approval required).
- ☐ Support Bot: FAQ / ticket flow in the tools you already use.
Day 3 — Marketing + customer success
- ☐ Marketing Bot: one channel, one asset, one CTA.
- ☐ CS Bot: onboarding checklist + health check prompts.
- ☐ Save any clean recurring workflow as a routine.
Related SoloAI Agents notes
- Grok Bot on Arch: when Settings won’t click — upgrade script when in-app update is dead.
Sources
- https://x.ai/bot
- https://x.com/bot/status/2099890276315848743
- https://x.com/bot/status/2100246135420199140
- https://x.com/bot/status/2100609778917822704
No affiliate links. Field note only. No invented livestream quotes — titles and product frame only.