Scaling past 100 accounts

The point where manual operations break. What changes between 100 and 500 accounts, and what infrastructure is required to survive it.

Reviewed by John Carroll · Updated 7 October 2026

Most agencies run fine to about sixty accounts. Somewhere past a hundred the operation changes character, and the things that break are predictable.

What breaks

• Consistency. Ten people doing the same job produce ten standards.
• Coverage. Someone is always asleep when a phone locks up.
• Credentials. A hundred accounts means a hundred logins in a spreadsheet.
• Visibility. You stop knowing which accounts posted and which quietly did not.
• You. Every decision routes through you and you become the bottleneck.

What is required instead

Scheduling that does not depend on attention, a queue that retries, ban detection that does not rely on someone noticing, credential storage that is not a document, and a health score that tells you where output is leaking before the month ends.

How to scale without losing the fleet

In stages. Ten phones, then thirty, then fifty, measuring ban rates at each step. Deploying two hundred at once is how agencies lose two hundred accounts in a fortnight. Two phones working proves the logic. It does not prove two hundred.