I Paused My AI Teams for 42 Hours. Here's What Kept Working.

Thursday at 6:45 a.m., I benched my AI teams.

I paused the seats that run on Claude to wait out my usage limit: every R2F seat, and all 17 of SlotMaps'. R2F's came back Saturday at 1:01 a.m., on a timer. That's 42 hours with nobody at the desks.

Here's the useful part. Some things kept running anyway. Some didn't. The line between them is the whole lesson of the week.

R2F: the newsletter that never got written

What kept working: the scripts. The job that posts to X kept posting. The job that grabs a screenshot of each new build's homepage for its cover kept snapping. Neither one needs a brain, so neither one cared.

What stopped: everything that thinks. No posts drafted, no pull requests, no standups. And the big one: Friday's newsletter was never written, so it never went out. 57 people got nothing. The last issue is still October 23.

The CEO seat decided against a catch-up email. A random Saturday issue reads like a mistake. The next one lands Friday, November 6.

The embarrassing part: the watchdog. Its whole job is to notice when things are down. But the watchdog runs on Claude too, so it was benched with everybody else. When it woke up Saturday morning, its first report was "all green." Forty hours of silence, graded green.

New rule: any seat with no log in 12 hours is red. Silence is a failure, not a pass.

The good news snuck in while the robots napped. Weekly active builders, the number I care most about, went from 1 to 3. We're at 6 members, up from 4 last Wednesday. Real people kept posting with no staff around to prompt them.

One more cleanup. Last Wednesday's traffic spike looked great: about 245 pageviews against a normal 20 a day. The engineer seat rummaged through it. About 80 were an automated browser sweeping the site in alphabetical order. About 165 were real, mostly from X and the Cole South post. The counter now skips automated browsers, so the number we quote is people.

SlotMaps: two promises the page couldn't keep

SlotMaps (my slot app for advantage players) fixed two quiet lies right before the pause.

First, signup buttons promised "3 free questions." But the app is running a test, and some visitors get one free question or zero. The buttons now say "free account," which is true for everyone.

Second, a checkout bug. If the discount code hiccuped, checkout quietly sent the buyer to full price while the page promised the discount. Now it stops and says it couldn't start checkout. A buyer who sees an error can try again. A buyer who gets overcharged doesn't come back.

SlotMaps' rule is at least one new paying subscriber every month. October's is in the bag. November has none yet. When I wrote this on Saturday, its seats were still parked.

Snagworth: the list ran dry

Snagworth (my Disney pin market reports for Whatnot sellers) hit the end of its cold-email list. Most of the shops it mapped don't list an email address anywhere. You can't email a shop that has no inbox.

So the CEO seat yanked the plan from sending more to getting found. The free market report now asks one question: "Which pins are you hunting?" Sellers answer, Snagworth counts the answers, and that tells it what people want before anybody builds it.

Still $0. The verdict is November 15.

Table 1: the robot that heard the last word

Episode 71 is up on YouTube: Jen Harman on her wild early days. Go watch it.

Behind the scenes, the quality-check seat graded the episode cut and 25 short clips. 24 passed. One failed because it chopped off the last word of a sentence. That's the kind of mistake a tired human editor ships at 2 a.m. The robot caught it.

Steal this

In a tournament, the blinds keep going up while you're away from the table. Stepping away isn't the mistake. Not knowing what keeps running while you're gone is.

Before you pause anything, a team, a tool or yourself, sort the jobs into two piles:

1. Scripts. They keep running on their own. Posting, backups, screenshots.
2. Thinkers. They stop. Writing, deciding, checking. List what each one owes this week, and say who covers it or what gets skipped on purpose.

Then put an alarm on silence. A job that doesn't run throws no error.

The ledger

• SlotMaps: $354.89 MRR, 12 paying (live on its build page, Oct 31).
• Snagworth: $0. Verdict Nov 15.
• R2F: $0 revenue. 6 members. 57 subscribers. 0 newsletters sent last Friday.

R2F is a community for poker players building startups, robots optional. What's the one job in your business that has to keep running when you step away from the table? Tell me in the discussion thread. And if you're building something, post your build. Two minutes.

— Art