Three SpaceXAI employees built a company with AI bots in three days the hard part was management, not prompts

Grok Bot Galaxy was a public experiment, streamed live. @mattyp, @poteto and @roshan_s started with no product, no code and no team. Instead of people they hired Grok Bot – SpaceXAI's AI agents, each with its own cloud computer

- Day 1 – the first idea: software for chefs who run pop-up restaurants in San Francisco – ticketing, venues, staff
- Day 2 – pivot. A real-world event needs city permits, and permits take longer than three days. The team switched to a game
- Day 3 – Thursday Arena is live: a free browser game where teams of bots fight each other automatically. We played it, it works

The workshops spent little time on how to write prompts. They read like a manager's handbook:

- Proof before trust. @lingxi's bot cleans up the codebase at 3am every night. Its changes go in without human review only if it attaches proof: screenshots for interface changes, speed measurements for performance ones
- Stop conditions. @SimonLackowskii's sales bots build a list of 50 potential customers a day, flag 5 to contact now and schedule the rest. Once a deal moves forward in Salesforce, the automated outreach emails stop
- Probation. @davidgan's customer support bot starts by only reading requests, then writes draft replies for a human to check, and answers customers directly last. His own cost estimate: $1-2 per complex request, ~$0.20 for a simple one
- Headcount discipline. Before adding another bot, ask whether a scheduled task for an existing one would do. If you check on every bot yourself, you become a manager with too many reports
- Access breaks before the work does. The bots got stuck on expired logins and files nobody had permission to open, not on the tasks themselves

The takeaway: AI agents can already do the work. The bottleneck is no longer the prompt – it's how you manage them

Before you launch a bot, decide three things:
- What it can access
- What counts as proof the job is done
- When it must stop

Then widen its permissions step by step, like a new hire on probation

Full day 3 recording in the quoted post: