Tonight, the team. Every night stands on its own.
How you do anything is how you do everything.

AI ExchangeBuilding Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.
SRE, Support, Growth, GTM, Chief of staff.
Read, draft, ask first, never.
Every bot knows which human to ping.
Every Never is missing access
Support drafts, a human sends
Kill switch in five minutes
claudeWhich job eats most of your week?
youSupport email. Then the Monday numbers.
claudeWho approves a reply before it goes out?
✓ OPS-TEAM.md: 5 bots, 5 channels, 1 owner each
Interview me, then write OPS-TEAM.md: roster, connections, permissions, escalation, audit trail, kill switches and Done when. Wait for my review.
docs.x.ai/grok-bot/bots
Never means
not connected.
Alerts, email, PostHog, the FAQ. Read-only keys.
Replies, reports, triage notes. A human sends.
Refunds, bans, deploys. The access isn't there.
Write the Ask first rules for each bot, and next to every Never, the missing access that enforces it. Mark anything that's only a rule.
docs.x.ai/grok-bot/approvals-security-and-privacy
One thread per item, so the work is visible.
What it read, drafted and is waiting on.
Personal bots post as you. Tag every post.
The daily standup and every follow-up.
Write the Slack plan: one channel per bot plus #ops, every action posted in a thread, every post tagged with the bot's name.
docs.x.ai/grok-bot/chat-and-collaboration
support@ · "My dinners won't load since Tuesday"
claude[Support] Lookup: 2 errors Tuesday, 0 dinners since. FAQ 4 fits.
claudeReply drafted in Gmail. Flagged to SRE as a possible bug.
youEdited one line. Sent.
Write FAQ.md with a hand-to-a-human rule for each answer, then a Support brief: read support@ mail, look the user up, draft in Gmail, ask before sending.
docs.x.ai/grok-bot/skills-routines-and-automations
✓ GET /api/ops/lookup · bearer token · email in a header
✓ POST 405 · wrong token 401 · unknown email 404 · 6 fields
✓ bot.user_lookup row in admin_audit_log
claudeRotate the token in Vercel and every lookup stops.
A GET-only lookup behind a bearer token, email in a header: six fields, rate limited, every call in the audit log, and one env var to switch it off.
docs.x.ai/grok-bot/computer-and-apps
[Support] [Bug] 3 users: Find dinners times out
claude[SRE] /api/health ok. Matches the Sentry spike since 8c1e2f4.
claudeTriage and a Claude Code prompt drafted. Approve to post?
youApproved. Rolling back myself.
Support posts [Bug] in its channel, the SRE bot picks it up and replies only in that thread, and write the escalation map: who pings which human, and how fast.
docs.x.ai/grok-bot/chat-and-collaboration
Monday 8:00 AM · weekly growth report
claude[Growth] Activation 58%, down from 63%. Biggest leak: signup to first dinners.
claudeIdea: show three starter ingredients. Metric: activation.
youGood. I'll run it through Claude Code.
A Monday routine that reads PostHog in read-only mode, posts the five stages and the biggest leak, and drafts one experiment idea.
posthog.com/docs/model-context-protocol/faq
3:00 PM · 2 email replies · 1 mention on X
claude[GTM] @weeknightmeals tried it. Stage: Trying it. Draft asks if they'd share.
→ Gmail draft saved · note added in Twenty
youStage approved. Sending it myself.
Twice a day: read replies and mentions, note them in Twenty with a narrow key, suggest the stage, draft the answer. It sends nothing.
docs.twenty.com/developers/extend/mcp
8:30 AM · daily standup
claude[Chief of staff] SRE: 1 alert, resolved. Support: 4 drafts waiting.
claudeFollow-ups: @cofounder approve 4 replies. @founder stage for 1 creator.
✓ 2 Granola calls filed under Meetings in Notion
The primary bot posts a daily standup with drafts waiting and owners, files Granola notes in Notion, and asks before assigning work.
docs.x.ai/grok-bot/bots
bot:support · bot.user_lookup · 37 this week
claudeSupport: 31 drafts, 28 sent as written, 3 edited.
claudeKill switch drill: all routines paused, token revoked, 3m 40s.
✓ ops/REVIEW.md · one change per brief
An audit script, a Friday review checklist per bot, kill switches in the runbook, and a timed drill to switch the whole team off.
Twelve nights: company, research, MVP, feature, presence, GTM, growth, workflows, security, monitoring, admin, ops team. Next: Founder Weekend, and the Discord.
An Arizona AI hackathon. Teams of 1-4.
See the hackathon ↗