The 100 phone fleet
A hundred phones at three accounts each is 300 live accounts producing around 900 posts a day. Still run by one person, but this is where the problems stop being operational and start being structural.
What it produces
| Accounts | 300 |
| Posts per day | Around 900 |
| Posts per month | Around 27,000 |
| People required | One |
| Equivalent VA team | Ten to twenty plus a manager |
What changes at this scale
- Concurrency. A hundred devices contending for USB bandwidth, the controlling machine and the queue. Architectures that worked at twenty fall over here.
- Heat. A hundred phones is a server room problem, not a shelf problem. Throttled phones time out and timed out jobs look like software bugs.
- Detection at scale. Behaviour that was invisible across sixty accounts becomes a signature across three hundred, because the similarity between them is the evidence.
- Network segmentation. Grouping has to be designed rather than assumed, so that a compromised group costs you a slice rather than the fleet.
- Content. Nine hundred posts a day is a production operation in its own right.
Why fleets fail at this size
Almost never because the automation stopped working. They fail because the fleet was scaled before it was instrumented, so accounts are being lost and nobody can say which phones, which network group or which creation batch is responsible. The fix is unglamorous: record ban events against every variable, then look.
Getting there
In stages. Ten, thirty, fifty, a hundred, measuring ban rate at each step. Agencies that jump straight to a hundred lose the first cohort and then distrust the whole approach.
Let us build your fleet.
Tell us how many creators you run and how you get traffic today. We will show you the system running on a real fleet and tell you honestly which setup fits, or whether it fits at all. Every build is scoped and quoted around your agency.
Message us on WhatsApp Telegram