A podcast teaches people to "set up an AI bot team for small businesses and charge $25,000"; the open-source library used in the demo gained 137 stars in a week

Bops is a Mac app: a team of AI bots handles your inbox, sales leads, invoices, and reports. They work on a cloud computer, and you can watch in real time and take over at any time. It was built by the co-founder of a startup that sells "cloud computers for AI agents." The code is public, but the license has restrictions. Nearly all its stars came from two waves of traffic: one from the author's own posts, and one from a podcast host with 739k subscribers, neither of which followers can borrow. Similar open-source projects have 10 to 25 times its stars. The real thing worth learning is how this company used an open-source project to acquire customers for itself.

a podcast episode with 136k views

In 2026 Nov 2, Greg Isenberg's The Startup Ideas Podcast aired an episode titled "The $1M+ Solo Grok Bot Business (Full Course)." Guest Nick Vasilescu is co-founder of Orgo, a YC-backed company that sells cloud computers for AI agents. Around minute 10 he starts a demo: a bot named Boppy takes a phone call and a text, breaks the request into tasks, then builds a list of sales leads in a spreadsheet on a 4-screen cloud computer.

The remaining half hour covers how to make money with it: go find 50 business owners you know and see which repetitive task eats up the most of their time; do the first job for free to get a case study; after that, charge $25,000 up front per job and $3,000 a month for maintenance. Nick says he built this whole setup over one weekend in 36 hours.

The video has been viewed 136,263 times in 3 days (YouTube, 11-05). On X in Nov 3, Greg posted: "Setting up Grok Bots for boring businesses/SMBs might be one of the best AI businesses right now… Give every agent its own computer, email, phone #," getting 1,462 likes, 154k views, and 289 replies (11-05).

On GitHub, OrgoAI/bops was at 351 stars on Nov 3, reached 427 stars on Nov 4, gaining 76 in a single day. Over the next two days it added twenty to thirty a day, reaching 481 stars by Nov 6. In the week before, it had gained only 12 stars in total.

What it actually is

The README's first line reads "Business ops, run by bots." After install, you greet Boppy, the main manager bot, then add specialists by role, like finance, outreach, or inbox. What they can do:

• They work on a real computer. Every plan includes an Orgo cloud computer with 4 cores, 16GB RAM, and 4 screens, with Chrome and LibreOffice installed. You can watch live and take over.
• They ask before acting. Reading is automatic. Sending email, creating things, or paying money requires you to hit "Do it".
• They have email and phone numbers. On Pro and up, the main bot gets an @bops.bot email address and a phone number. You can text or call it to assign tasks.
• They connect to 1,400 apps. Gmail, calendar, and more connect through Composio. Login credentials are stored in the Mac Keychain.

Pricing is in the README: the free plan includes 10 hours of cloud computer time per month; Pro is $20/month; Max is $200/month, with up to 3 computers and 5 phone numbers. AI usage is billed at cost.

Two caveats. First, the tagline says "each bot has its own computer, email, and phone," but per the README's plan details, all bots on the free and Pro plans share one computer, and Pro has just one number and one email address. Second, it only runs on Apple Silicon Macs, and the model is currently OpenAI only. The license is FSL-1.1: you can use it yourself, self-host it, and use it to serve clients, but you can't use it to build a competing product or hosted service. Each version converts to Apache 2.0 after two years. So strictly speaking it's "source-available," not open source under the OSI definition.

Where the stars came from

Nick's launch-day copy read: "Instinct, Muse, Dot and Grokbot are personal agents. I wanted a business agent. So I built Bops." It names a string of well-known personal assistants, then says he's doing the opposite. This contrast-based positioning was the hook for the first wave.

Between the two waves, growth was nearly flat. There were no Hacker News threads and it never hit GitHub Trending. The channels developers usually rely on didn't work for it.

What 182 forks tell us

Fork count is worth watching more than star count. Forks went from 93 on Nov 3 to 182 on Nov 6, doubling in three days and growing faster than stars. The fork-to-star ratio is about 38%, while typical repos usually sit at a few percent to low teens (rough estimate).

The reason is easy to guess: the podcast sells the idea of taking this setup and building it for clients to charge for, so listeners fork it as a foundation for paid work. From Nov 2 to 6, GitHub also filled with several same-named copies (thisisfrank/bops, TheNeuralCube/bops, svensonlabs7/bops, CodingDyl/bops), each with 0 to 1 stars. One podcast-notes post had a whole section titled "Can you fork Bops and sell it," warning readers that the FSL license prohibits competing products. This many people wanting to do this suggests the demand is real, but they want a foundation they can sell on, not necessarily Bops itself (inference).

This is actually a customer acquisition channel

Bops's bots all run on Orgo's cloud computers, so the more users it gets, the more computer hours Orgo sells. In the commit history, most of the code was written by Orgo's CTO and another engineer; Nick himself committed only 5 times. Releases are frequent too: from v0.0.6 to v0.0.49 in a month, and 12 versions in the three days after the podcast aired.

Its tech stack is also a lineup of agent infrastructure companies: AgentMail for email, AgentPhone for phone, Composio for app integrations, and Honcho for memory. The README lists them all, and Composio even added it to their site's "Built with Composio" case study page. Each partner has a reason to help spread it.

So behind these stars is a company acquiring customers. That company has a founder with followers, a YC name, and the pull to get a big-name podcast. A solo indie developer copying the approach wouldn't have any of that.

Who it's competing with

On the closed-source side there's Grok Bot, OpenAI's Dots, Meta's Muse, and Claude Cowork, all positioned as personal assistants.

Compared with them, Bops's only new angle is building phone and email into the product, so bots can take calls and reply to email. That's exactly the line Greg used as his hook. The weaknesses are also clear: Mac only, OpenAI only, and license limits. The OpenMausBot comparison post targets these three points. A project that started two months earlier and has 27 times its stars is already there, so this lane is crowded.

If it were you

The verdict: Don't build another "open-source Grok Bot / AI employee team." The lane already has projects with 13k, 7 thousand, and 6.8 thousand stars. Bops's 481 stars also came from borrowed founder and big-account traffic. The two things worth taking are: first, the gap for "AI agencies needing a foundation they can legally sell, with phone and email built in, tuned to an industry out of the box" (OpenMausBot has a permissive license but no phone or email; Bops has phone and email but a license that blocks competing products). Second, the infrastructure companies' playbook of using an open-source sample app to acquire customers.

Who it's for: Small teams already building agent infrastructure (email, phone, browser, sandbox, memory) who want an open-source sample app for their product, or people already selling AI automation to small businesses who have real workflows in hand.

Who it's not for: A solo developer with no audience hoping to get stars with "yet another multi-agent platform." In this space, big projects gain thousands of stars a week, and a new repo struggles to be seen.

How to do it:

1. Don't build a platform; build one role in one industry. For example, "a clinic front-desk bot that answers calls, books appointments, and sends reminders," or "a renovation company's quoting and payment-chasing bot." One workflow that works is easier to explain than ten generic bots.
2. Fix what Bops got wrong: use an Apache or MIT license, and state on the README's first screen that you can deploy it for clients and white-label it. Make it cross-platform and model-agnostic. Keep phone and email, since that's the most shareable selling point.
3. Put a 30-second screen recording at the top of the README: a phone call comes in, the bot picks up, and a spreadsheet fills itself in on screen.

How to get customers: Most stars will come from the "AI agency" crowd, who follow business-idea podcasts like Greg Isenberg's, X accounts, and subreddits like r/AI_Agents and r/automation. Write your project up as a case study: "here's what I did with my first client and how many hours it saved," and post it directly into the discussion under Greg's post, or DM the creators who talk about this business. If you're building infrastructure, follow Bops's approach: name your partners in the README so they repost you. HN and Product Hunt are worth a shot, but Bops got only 1 votes on PH, so don't expect much.

Timing: The phrase "selling agent teams to small businesses" only got big-account coverage in early November, so over the next month or two, more people will look for a foundation to build on (inference). If you're going to build this, ship before year-end. Once the big projects add phone and license fixes, that window closes.

Signs you've misread it: If OpenMausBot or rakazo adds phone and email and ships a few industry templates, the gap gets filled by a bigger project. The same goes if Bops switches to an Apache license. If your project is out for two weeks with only a few stars and no one opens issues asking about deployment, it means agencies don't need a new foundation, and forking Bops or using an existing one is enough.