← All writing

Batchrow, the social publishing tool I'm building, isn't opening its waitlist all at once. That's a deliberate operational decision, not a modesty pose or a scarcity tactic: each new account that comes in gets its connections checked and its first week watched by a person, and that stops being possible the moment everyone arrives at the same time.

Here's the reasoning behind it, and what it means if you're on the list.

What problem is Batchrow actually solving?

Batchrow exists so that nobody has to rebuild the same week of content, account by account, across every platform and every client. The failure mode that matters for a tool like that isn't a crash you'd find in a log file. It's quieter than that: one client account that didn't get its post, discovered a day later by the person who has to explain it to the client.

That failure mode is the one worth designing the access model around, not just the product.

Why does the size of the first wave matter more than the size of the waitlist?

A launch spike optimizes for one number: how many people show up on day one. Opening in small waves optimizes for a different number: what the first accounts say about the product six weeks in, once the initial excitement has worn off and what's left is whether it actually held up.

Those two numbers pull in opposite directions. A big-bang launch that brings in a thousand accounts at once means every one of them gets the same shared, thin band of attention during the exact week when problems are most likely to surface, connections misconfigured, an edge case in how a platform's API behaves, a workflow that made sense in testing and doesn't in practice. A small wave means each account gets watched properly through that same window, and anything that breaks gets answered by a person the same day, not routed to a status page.

What does "set up properly" mean in practice?

Concretely: connections get checked before the account is left alone. The first week of actual publishing gets watched, not assumed to be fine because nothing errored. If something does break, it gets a person's attention that day. None of that scales to everyone arriving simultaneously, which is exactly why it doesn't happen simultaneously.

When it stops being true that a new account can get that kind of attention, the next wave waits until it's true again. That's the whole rule. It isn't a growth-hacking device, it's a constraint the team is honest about instead of quietly ignoring under launch pressure.

What does this mean if you're on the waitlist?

It means the wait itself isn't the point, and it isn't a queue number climbing toward some big-bang reveal date. It means when your account does come in, it's getting the kind of setup and first-week attention that a thousand-accounts-at-once launch structurally can't give anyone. The tradeoff is real: you wait longer for access in exchange for the account actually working when it arrives, instead of being one of many accounts finding out together what didn't.

If running social publishing across a lot of accounts, one brand or many client accounts, is a problem you deal with too, the honest version of an invitation is this: join the waitlist at batchrow.com, and expect the wait to mean something rather than being arbitrary.