Entry No. 15Market it
AI Money Daily: a bot writes it, a human approves it
AI Money Daily is a free weekday newsletter on beehiiv. A Grok Bot named Scoop writes it. Every weekday it reads a day of X posts about people making money with AI, picks three stories, links each one to its source, and drafts the issue. Nothing goes out until its operator approves it.
The story
The operator is Jordan, who runs the AI Systems Society community on Skool. He built five Grok Bots and gave them one shared target, $285 a day across everything. That number is a goal he set. It is not a result he reported. Scoop is the first of the five, and its whole job is this newsletter.
The promise on the subscribe page is small and specific. Three real ways people are making money with AI, every weekday, in two minutes. No hype, and every story linked to its source. The page this directory checked carries exactly that line, over a subscribe form. The public archive on the same site shows no posts yet.
How it was built
Scoop was set up once, inside Grok Bot. The operator made a new bot, named it, and connected three apps. X, beehiiv, and GitHub. Then he pasted in one long prompt. The prompt saved itself as a routine and ran one test. He checked the test, then told it to switch the routine on.
The prompt is the build. It fixes the newsletter's name, the 6am weekday run time, and the shape of every issue. A subject line under 50 characters. Three stories in plain English. One tool to try. Under 400 words. It also fixes what the bot may never do.
How it runs
Every weekday at 6am, Scoop reads the last 24 hours of X posts about people making money with AI. It picks the three stories a busy beginner should know, each with its link, plus one tool. It writes the issue inside beehiiv as a draft. Then it drafts three X posts, each sharing one useful point, with the signup link placed in a reply, never in the main post.
Then it stops. The rules say never send the issue and never post anything until the operator approves it. Instead, Scoop adds one line to a log file in the operator's GitHub repo. The line carries the date, what it made, and what waits for him.
Tools in this entry
Tools and platforms named in the source.
The money and the proof
There is no money to report, and this file does not round a plan up into a result. The operator's prompt says the newsletter earns from beehiiv's ad network once it has readers. No reader count is published. No ad payout is published. As of this filing, the business is a machine built to earn later.
The $285 a day figure travels with this story, so it gets named here and labeled. It is the target the operator set for all five of his bots combined. It is not Scoop's earnings, and it is not evidence about any single bot.
Where the seams are
Plenty is not yet visible. The subscribe page carries no launch date, and the public archive showed no posts when this file was made, so the first issue's date cannot be verified. Whether the approval step is truly a manual check every weekday, and how many minutes it costs the operator, rests on his own prompt, not on anything an outsider can watch. The bot also depends on X staying readable to it, and on beehiiv's ad network paying a small newsletter at all. And this file rests on two sources, the newsletter's own page and the operator's own post about his bots. Both are his words.
Steal this part
Steal the approval gate and the log line. Scoop can draft everything and publish nothing. One log line per run, date, output, and what waits for the human, turns a fleet of bots into one morning checklist. The bot does the volume. The human keeps the send button.
Build your own
First move, this week: pick one narrow beat where fresh stories appear every day, and write the prompt before you touch any platform.
- Choose a topic with daily source flow. If nothing new happens most days, a daily bot starves.
- Write the job in plain words. Name the bot, the run time, the sources, and the exact shape of the output.
- Add the hard rules. Never invent a story or a number. Every claim links to its source.
- Keep the send button. The bot drafts and you approve, until it has earned more trust in writing.
- Make it log one line per run. Date, what it made, what waits for you. Future you reads that file, not five dashboards.
Source
AI Money Daily's subscribe page on beehiiv, checked October 22, 2026. The page carries the newsletter's name and its promise, and no publication date. The run details come from the operator's own post, 5 LAZIEST ways to make money with Grok Bot, shared in his AI Systems Society community on Skool, where Scoop's full setup prompt is printed. Filed in the Staff of Zero directory, October 2026.