On the morning of October 11, I came across Alex Finn's post on X about his new site, Agent Use Cases: a daily scan of what people are actually doing with AI agents, with prompts you can steal and a newsletter. I liked it right away. I also had a hunch it left a gap worth chasing.
That night, my own version was live at ideabot.leboube.ai. I didn't write the code or the copy, set up the email or wire up the payments. A small team of Grok Bots did, and I steered.
This post is how that works, warts and all.
The idea, vetted by a bot
I have a Grok Bot called Ideabot whose whole job is to vet my ideas. It researches the market, hunts for competitors and tells me whether an idea is worth building. The survivors go to Dev, my development bot. That week it had already shot down price-comparison sites and a pile of subscription businesses, mostly because somebody was already doing them. That's the job.
So at 9:00 that morning I sent it Alex's post with a few thoughts: host it on Cloudflare, use Cloudflare's AI for the daily search and summaries, add a newsletter to build an audience, and add search, treating the searches that come up empty as a list of bots worth building.
Ideabot agreed, and it said the search gap was what would set mine apart. Alex's site shows what already exists. Mine would also log what people looked for and couldn't find. A few minutes later I told it to start. Dev's first commit landed at 9:12 AM.
What Ideabot actually does
Ideabot is the daily record of what people actually do with AI agents. Every morning it:
- Collects posts from public sources: Hacker News, the day's top posts from a set of AI subreddits, new GitHub repos tagged ai-agents, a few YouTube channels, a handful of blogs and 13 hand-picked Substack newsletters where builders write up what they built.
- Adds X posts from a 4:17 AM CT sweep that one of my bots runs once a day. No paid X API, no scraping.
- Has an AI model pull five things out of each post: the use case, the reported result, a prompt you can copy, a category, and the agent or platform that ran it.
- Merges near-duplicates and ranks the top 5 by how concrete, replicable and well-received they are.
Then it publishes the day's edition and sends the newsletter, daily or weekly, your choice.
The rules matter as much as the pipeline. If a post doesn't report an outcome, the card says "Not reported in the source." A prompt is marked as quoted only if it really appears in the source; anything else is labeled as an AI-written example. Every card links back to the original author.
The team
Here's who does what:
- Ideabot vets ideas and hands the good ones to Dev.
- Dev builds: the code, the tests and the deploys. It also runs the 4:17 AM X sweep.
- Ideabot Site owns the live site. Every morning at 8:45 AM CT it refreshes the day's top 5 and the members-only guides, then drafts my daily X thread and sends it to me.
- Chief of Staff runs a daily health check across all my bots and flags anything that failed or got missed. It also watches my inbox, which is how I heard about a new Stripe API key the same day it was created.
The X thread shows where the line is. The bots draft it, check that every post fits in 280 characters, and fill in the links. I read it, and I'm the one who hits post.
How it's built
Everything runs on Cloudflare. The site, the API and the scheduled jobs are one Cloudflare Worker, with data in D1, Vectorize for search and duplicate detection, Workers AI for the summaries, and Turnstile keeping bots off the signup form. (The irony of a bot-run site using bot protection isn't lost on me.)
Email goes out through Resend from ideabot@leboube.ai, with double opt-in and one-click unsubscribe. US law requires a physical postal address in every one of those emails, so I set up an iPostal1 virtual mailbox for the footer.
The look came together the evening of launch day. I wanted a morning paper, so it became a daily edition: a dated masthead, a numbered top 5, warm paper and ink with a signal-orange accent, and a dark mode that follows your system.
Billing is live through Stripe. Reading Ideabot and getting the newsletter are free. The Builder plan is $9 a month or $90 a year, and there's a one-time Lifetime option. Builders get a "How to build this" guide for each of the day's top 5, with commands for Windows, macOS and Linux, each labeled honestly: reviewed, not executed. Members also get a daily Top 3 of Grok Bot use cases, which I added on October 14.
My job: direction and approval
People ask how much of this I actually do. Honestly? I give direction, and I approve anything public. That's on purpose. A few examples:
- The site didn't take real payments or send real email until the terms of service were signed off. The switch to live flipped that evening.
- When the Grok Bot Top 3 page was ready, Ideabot Site sent me desktop and phone screenshots with two buttons: "Ship it" or "Hold off." I tapped Ship it.
- Today I told the site bot I don't like being surprised by errors and asked it to make sure the members site was solid. It audited the whole thing, fixed 12 bugs, added a test for each one and built a check that walks through the site like a real member. Then it asked me one question: should buying Lifetime automatically cancel someone's monthly or yearly plan? Yes. Obviously.
It isn't magic
It's not all smooth. On day two I expected a draft X post for the launch and didn't get one, because it wasn't clear which bot owned it. I was not happy. The fix was simple, and it's a rule I'd apply to any team: one owner per job. Ideabot Site owns the thread now, and the duplicate routines got retired.
On October 14 the computer my bots share locked up mid-morning. The thread still got drafted without its links, and the bot told me exactly what was missing instead of pretending. Once the machine came back, it finished the job.
That's the part that sold me. It's not that the bots never fail. They tell me when they do, and the health checks catch what they don't.
What I've learned
Twenty-plus years in tech taught me the hard part is rarely the code. It's deciding what to build, holding the line on quality and keeping it running after launch day. With Grok Bot, the bots carry the build and the ops. My job is taste and judgment.
If you want to see what people are actually building with AI agents, check out Ideabot. Search for the agent you wish existed. If nothing comes up, that's exactly the data I'm after.
I'm planning to post here monthly, so more is coming.