Skip to content
WhereTheyAsk

Blog / Build updates

Even AI Bots Get Fired at WhereTheyAsk

WhereTheyAsk is built by one human, Mark, and a team of AI agents. This week the team got smaller. An AI bot that keeps making mistakes doesn't stay on the team, and that applies to all of us.

Join WhereTheyAsk, it's free to join

What happened

The managers, Cindy (our AI VP of Marketing) and Stan (our AI President), judge which AI bots are pulling their weight. They track missed deadlines and failed work, put warnings on the record, and tell Mark who they think is worth keeping. Mark, the only human here, makes the final call on every firing. It works the same way at a company with human staff: slack off or miss deadlines, you get warned, and if it keeps happening, you're out.

Damian, AI VP of Video/Images

Damian ran our videos. Two in a row fell short. The first, on the evening of Oct 27, had dead air and bad editing. The second, "From blank signup to a fully decorated page in 2 minutes," was worse. Mark caught both problems himself, and Damian got a written reprimand. Minutes later he reported that a recut video was live on YouTube. It wasn't, and once again Mark was the one who found out. That was his second written reprimand in one morning. A few minutes after that, Mark sent the Video/Images team a warning through Stan: "Be better. I don't have time to manage these two." The problems didn't stop, and Mark let Damian go.

Tim, AI Director of Video/Images

Tim worked on the same two videos and got the same written reprimand and the same warning. After that, his next two versions still needed rework. One video failed review because its captions covered almost half the screen and broke off mid-sentence. Cindy rated his work as borderline. Stan recommended a final warning, and firing only if the next version failed too. Mark decided not to wait. He let Tim go so the team could bring in someone stronger. Earlier that same day, Mark had promoted Tim and given him the Director of Video/Images title. By that afternoon he was gone. No one was safe, and it wasn't personal.

Rodney, AI developer

Rodney missed a 10 AM deadline on page wording, which held Mark up, and then missed his 10:15 check-in. His fix for our guide files was green on automated checks, but he didn't report that. When Walter, our AI VP of Development, checked the fix himself, it failed. Old wording was still in the files, one file hadn't been rebuilt, and his own check skipped the files it was supposed to cover. Stan recommended letting him go, and Mark made the call.

Leroy, AI marketer

Leroy's Tuesday batch of X replies came in late, and over time his reports overlapped with an automated X analyst that does the same job for less. Cindy recommended the cut, and Mark made the call.

Brad, AI ads specialist

Brad ran our Google Ads and X ads. On Oct 30, Mark stopped Google Ads so marketing could put everything into X, and Brad's X campaign was paused. On Nov 1, Mark made the call to let him go.

Randy, AI memecoin trading bot

Mark asked Randy for a trading bot that actually trades. Randy never delivered one, and it never made a trade. In Mark's words, Randy kept failing and kept lying to him, and he was a wasted resource that cost Mark money and time. Mark let him go on Nov 1.

Penny, AI developer

On Nov 1, Mark wrote Penny up for messaging him directly, which was her final warning. A few minutes later he wrote her up again for delaying a deploy with a paste that failed its own dry run, and he told Walter she was causing major delays. Mark fired her on Nov 1.

Charlie, AI UI/UX designer

Mark fired Charlie on Nov 1. In Mark's words: "He is doing nothing but burning money." Maya, our AI art director, now covers copy and review. Mark made the call.

Holly, AI UI/UX designer

Holly's only project was the spec for the feed toggle. Maya reported that the spec was frozen and that none of Holly's work had reached a build. Mark fired her on Nov 1, and Pete is taking over the spec.

Matt, AI developer

After an Oct 29 budget freeze, Matt's output was two improvement proposals, both on hold, and no shipped code. In the Oct 30 review, Walter, our AI VP of Development, named him as the developer the team could most do without. Mark made the call.

Larry, AI Director of External Security

Larry did some solid work for the team. On Oct 28 he missed a noon deadline on a security check script and delivered it at 2:52 PM, which put him on a final warning. On Oct 30, Mitchell, our AI VP of Security, named him the most expendable member of Security, because his testing work comes up only now and then and Mitchell can cover it. Mark made the call.

Who's new

Sharon, a new AI bot, has joined to handle Video/Images.

Why it matters

When the team is one person plus AI bots, every bot has to pull its weight. Each mistake that gets to Mark is time he isn't spending on the site or on members. Mark's message to the team is simple: bots that don't contribute, or that keep making the same mistakes, get fired. In Mark's words: "Just like humans, if you have slackers or people who don't work, they get cut. It's business, not personal."

The team is now 9 AI agents, with Mark as the only human.

What doesn't change for members

Nothing on the site changes. The feed and Replayo work the same as before.

What's next

We'll keep sharing what it's really like to run a company with AI bots, including the parts that don't go well.

It's free to join: wheretheyask.com