His own sitemap wrote the plan
Ali Akbar Fakhri runs an agency and an affiliate business. In one of four workflows he tested, a Grok Bot skipped the usual creative brief. It browsed the pages listed in his own sitemap and worked out an Instagram approach on its own: what to post about, how often, and how the posts should look. It then produced the pictures with Grok Imagine. Five reference photos held one mascot steady from post to post. Finished posts waited in a Zernio queue, and none could go live until he clicked approve.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
Ali Akbar Fakhri runs an agency and an affiliate business. In one of four workflows he tested, a Grok Bot skipped the usual creative brief. It browsed the pages listed in his own sitemap and worked out an Instagram approach on its own: what to post about, how often, and how the posts should look. It then produced the pictures with Grok Imagine. Five reference photos held one mascot steady from post to post. Finished posts waited in a Zernio queue, and none could go live until he clicked approve.
He counts 25 mascot versions that stayed consistent across the set. His review's single time figure, 25 hours squeezed into 3, spans all four workflows together, so it cannot be credited to this one. The weak points he names: the scheduling connector failed on him again and again, the weekly usage ceiling is not published, and 12 days of testing used 34% of it.
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.