How OFM agencies run Instagram farms
There are three operating models in use, and they differ by one thing: how much a human has to be present.
One, VAs on phones. Still the most common. Each VA runs a batch of accounts by hand. Works to about sixty accounts, then management becomes the job. Two, remote control tools. Phones mirrored onto one computer so an operator drives many at once. Faster per operator, same headcount per unit of output. Three, automated device fleets. Phones execute jobs on a schedule with nobody watching. Output scales with phones rather than people.
The three models, compared on what matters
| VAs by hand | Remote control | Automated fleet | |
|---|---|---|---|
| Accounts per person | 15 to 30 | 40 to 80 | Whole fleet |
| Works overnight | Only with shift cover | No | Yes |
| Account creation | By hand, slow | By hand, faster | Unattended |
| Warming | Usually skipped | Usually skipped | Automatic per account |
| Ban replacement | Days per slot | Days per slot | Hours, automatic |
| Credential exposure | Every VA holds them | Every operator holds them | Encrypted, access logged |
| Doubling output | Double the people | Double the people | Add phones |
What a typical farm looks like inside an agency
The shape most agencies converge on, regardless of which model they run:
- Three accounts per phone. More is possible and raises ban risk, because accounts on a device are visibly linked to each other.
- Around three posts a day per account. Enough output to matter, still within the range a heavy human user occupies.
- Phones grouped by creator. It maps onto how the agency already works, and makes scoping manager access trivial.
- A warm up window of five to seven days before an account carries any link.
- Separate network identity per phone or per small group, because a single office connection links every account behind it.
The numbers at each stage
| Accounts | Phones at 3 per | Posts per day | People, manual | People, fleet |
|---|---|---|---|---|
| 60 | 20 | 180 | 2 to 4 | 1 |
| 150 | 50 | 450 | 5 to 10 | 1 |
| 300 | 100 | 900 | 10 to 20 plus a manager | 1 |
| 600 | 200 | 1,800 | Rarely attempted | 1 to 2 |
Where agencies actually lose output
Not where they expect. The three leaks, in order of size:
- Dead slots after bans. On a manual setup a banned account stays unreplaced for three to seven days while somebody notices and rebuilds. Across a steady ban rate that is a large share of total capacity, permanently offline.
- Skipped warming. Accounts pushed into production early die early, so the agency pays the creation cost repeatedly for accounts that never produced.
- Silent failures. Without per job logging, accounts that quietly stopped posting are discovered at the end of the month rather than the same hour.
What separates agencies that scale from ones that stall
Three things, and none of them are tactics.
They instrument before they grow. Ban events recorded against the phone, the network group, the account age and the warm up it received. Within weeks a pattern appears, and it is almost always concentrated in one proxy group or one batch of accounts created the same way. Agencies without this guess, and guessing at scale is expensive.
They solve content supply first. A fleet is a distribution machine. Nine hundred posts a day needs nine hundred pieces of content, and the agencies that stall are usually the ones that built capacity they could not feed.
They ramp in stages. Ten phones, then thirty, then fifty, measuring ban rate at each step. Two phones working proves the automation logic and proves nothing about two hundred, which adds concurrency, heat, queueing and detection at scale.
Build it, or have it built
Agencies that build in house usually get one phone driving within a week and then spend six months on everything between ten phones working and two hundred working. That is the real project: account creation that survives verification repeatedly, warming that varies genuinely, a queue with retries and circuit breakers, ban detection, encrypted credentials and enough observability to find the phone losing you accounts.
TIDE is that system, already built. Hosted by us, or licensed and installed on your own hardware so your agency owns it.
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