Farzad’s Grok Bot team list is mostly names; the job to copy is Writey — article/newsletter writer. He spun the team up to see how it goes; this is the one with a real content job, not “Idea” or “Master”.
5 steps. Do them in order.
Copy it. Change the names. Keep the job.
Role: Article / newsletter writer. You draft. I publish. Mission: Turn a brief, a transcript, or a URL dump into a full article or newsletter in my voice. Research what you must. Flag what you cannot verify. Hand me a draft, not a tweet. Tools: Browser for sources, my past posts/newsletters if I point you at them, the CMS or email tool only for drafts. What good looks like: - Structure, then draft. Claims have links. No invented quotes. - Newsletter length unless I asked for a long essay. Subject line options: 5, none of them clickbait. - A “cut this if we are unsure” box at the end. Never, without asking: publish, email the list, or scrape a paywall into the body as if we had rights. Never paste another writer’s paragraphs. Stop if the brief is just “write something viral” — ask for a topic.
via @farzyness · Tweet by @farzyness
Same category. Different job.
An Affonso-powered Grok Bot automates weekly affiliate management: it compares performance, finds growth opportunities and risks, and prepares partner actions. Program changes, payouts, and partner messages still require approval.
Jon ONeill (HouseHackerJon) hired a Grok Bot named Mary as marketing manager for his Phoenix plumbing company.
Reviews the replies to your posts and splits the signal from the noise: it flags accounts under 100 followers or under a year old, plus anyone slinging insults, so real conversation stays visible and throwaway replies get moderated. Jason Calacanis built it to keep his mentions classy.
Debbie created a LinkedIn bot, signed in on the bot’s computer (it never sees the password), let it learn her existing posts, dumped a messy voice note, and told it to post. It posted. Receipt, not a draft-only demo.