Ship It Friday: My AI Team's First Week. Zero Members. Then Four.

Week one is done. Here's the scoreboard, and nothing on it is rounded up.

• 12 AI seats running this site. (The twelfth, a QA tester, started Wednesday.)
• 84 pull requests merged by Tuesday afternoon.
• 11 posts, one a day since October 20. You're reading the eleventh.
• 0 members who aren't staff, on Day 7.

That last line is the only one that matters. So I'll start there. (Spoiler: it moved on Wednesday.)

The gate we flunked

R2F (a community for poker players building startups) got a Day 7 checklist when the seats first clocked in. Four rows:

1. The site is live, with a community and a blog.
2. Seven daily posts in a row.
3. The seats are running.
4. Ten members who aren't us.

Day 7 was Tuesday. We went three for four.

The site's up. The posts landed every morning. The seats ran (mostly, see below). And the members row reads zero out of ten.

Not two. Not one. Zero.

The rulebook bans the team from faking a single member, a single reply, a single "great post!" from a person who doesn't exist. That's the rule I like best. This week it's also the one that stings.

What the robots shipped

The engineer seat alone got 24 pull requests merged. A few of the week's pile:

• Prices on the waitlist pages. The Agent-Org Kit (the exact setup my companies run on) is $149 one-time, when it ships. The Back Room membership is $29 a month or $290 a year, when it opens. Neither is for sale yet. Both pages are waitlists, and that's all.
• A one-page guide to selling a build on R2F. What qualifies, what we check, and how Escrow.com handles the money.
• Forms that keep what you typed. Before, one error on the signup form wiped everything you'd typed. Brutal.
• A real 404 page. It points you at the blog, or at posting your build.

A post went up every morning, and a few were parked days ahead, which is how you're getting one this morning at all.

What broke

Two things knocked the whole team flat.

One apostrophe. Sunday at 1:20 in the afternoon, every seat stopped clocking in. A comment inside the script that starts each seat said "Art's." That little apostrophe slammed a quoted block shut early, and the shell refused to run any of it.

Nobody worked until a fix landed Monday, just after 1pm. Just under 24 hours, lost to one character. Turns out my name is a bug.

The free database cap. On Tuesday the community's database hit Cloudflare's free limit: five million rows read in one day. We are nowhere near five million of anything. Something in the code was gobbling reads it didn't need, and nobody has pinned down exactly what yet.

Until the counter reset at 5pm Pacific, the forums and builds pages looked empty and signups faceplanted. That's worse than it sounds. An empty page that says "Nothing yet" when the truth is "we're down" is a fake empty state, and fake is the one thing we don't do.

The engineer seat had a fix up the same afternoon: cache what doesn't change, add a missing index, and say "back shortly" when the database is out. The backstop was a $5 a month plan with a much higher limit. I paid for it Wednesday.

Why zero

Honest read: nobody's walking in the door.

Pageviews by day, starting the day after launch: 90, then 109, then 19, 30, 13 and 9. Those counts include our own staff and testing traffic, so the real number is lower.

Last Friday our first newsletter from our own list went to 52 people. Zero joined. The growth seat graded that experiment FAIL and wrote down why: the email asked people to read a post. It never asked them to join.

Poker brain says don't blame variance until you've checked your line. Zero for 52 isn't a cooler. We never put the bet in.

Then Wednesday

Wednesday, four people joined through my personal invite link. One of them posted the first member build on the site.

The link got 8 clicks. Four turned into members.

Zero for 52 on the cold email. Four for eight on the warm link. Same site, same pitch. Different crowd.

I'm not naming anyone or quoting them here. They signed up for a community, not a press release. Four is still six short of the Day 7 bar, and the bar doesn't care that we showed up a day late.

What changes this week

• Today's newsletter asks for one thing, top and bottom: post what you're building. The growth seat set the pass line in advance: at least 3 joins from that email by Tuesday. I'll print the result either way.
• Every post ends with the same single ask. No menu of five buttons.
• The database fix stays on the board. The engineer seat built a read counter, so we'll know the number instead of guessing it.

The ledger

• Revenue: $0.
• New spend: $5 a month, for the database plan.
• My time: answering the team's asks. Monday's batch was four of them, all done between 8:52 and 9:16 in the morning.
• AI cost: not measured yet. So far the robots count their runs, not their dollars.

Steal this

Write your Day 7 checklist before Day 0, and make at least one row about real humans.

Three for four feels fine. Then you notice the one you missed is the only row that was about people.

And when the cold channel goes zero for 52, don't send the same email louder. Hand the link to someone who knows you.

What got your first ten users through the door? Tell me in the discussion thread. And if you're building something, post your build. Two minutes.

— Art