On launch day he wrote a hundred things he had seen. Pick one job you already have this week. Do not stand up a hundred bots.
You just started. You want what others already run, not a roster invented from zero.
One of the hundred actually lands: a multi-bot GTM crew, a chief that routes, or a community ops fleet.
Do not stand up a hundred bots.
Research, outbound, forecast, inbox, slides. Weekly playbooks sit on top.
Stand up a chief first. It routes to specialists. You are not the middleman.
A community ops fleet, plus weekly events and summaries. Send, spend, and CRM writes, as his post keeps saying: ask you first.
What's good: the hundred are things he saw, not a feature list. The catch: tap the whole menu at once and the roster blows up first.
I have read the 100 use cases list. Do not stand up 100 bots. This week pick ONE of these three and walk me through creating only that: 3) a multi-Bot GTM crew — research, outbound, forecast, inbox, slides — with weekly playbooks on top 4) a chief-of-staff hub that routes work to a specialist fleet, so I am not the middleman 6) a community ops fleet Ask me which of the three I already do by hand. Create one named bot for that job. I will sign into tools on your computer, not in chat. Show me a test run of one real task. Hold send, spend, and CRM writes for my approval. Save it so I can edit later. We add the next bot only after this one works.
改写自 https://x.com/ericzakariasson/status/2087258914060664902
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About