When active account count exceeds 100, chaotic ad-hoc management stops working. Lost credentials, random bans from mixing data, unclear responsibility — this all becomes systemic losses. Let's explore how to build account pool management as a business process.
Why 100 Accounts Is a Different Scale
Up to 20–30 accounts, one person manages manually or via spreadsheet. At 100+, systemic problems emerge:
- Impossible to remember which proxy is tied to which account
- When staff rotates, credentials are lost
- Accidentally mixing account data leads to mass bans
- Unclear which accounts are active vs. blocked long ago
- No metrics: which accounts generate income vs. dead weight
Team Structure
Roles and Responsibility
| Role | Functions | Account Norm |
|---|---|---|
| Farmer/Registrar | Create, warm up new accounts | 50–200/month |
| Account Operator | Maintain activity, monitor bans | 50–100 accounts |
| Buyer/User | Use accounts for main task | 10–30 simultaneously |
| System Administrator | Infrastructure: proxies, anti-detect, access | All infrastructure |
| Manager | Strategy, metrics, hiring, KPI | Oversight of everything |
In teams under 5 people, roles overlap. Important: farming and using accounts must be separate — farmer creates, buyer uses, no one mixes one person's tasks with another's infrastructure.
CRM for Accounts: What to Store
Mandatory Fields for Each Account
- Identifier: unique internal ID, login/email
- Platform: Facebook, TikTok, Google, Telegram, etc.
- Status: active, warming, used, blocked, archived
- Phone Number: used for registration (for recovery)
- Proxy: tied IP or proxy profile
- Browser Profile: anti-detect profile ID
- Registration Date
- Last Activity Date
- Responsible Operator
- Notes: problem history, specifics
CRM Tools
Specialized account CRMs are rare. Most teams use: Notion/Google Sheets (up to 200 accounts), Airtable (up to 1000), custom tool (at 1000+ scale). Key requirement: quick search by any field and export of "live" accounts by platform.
Account Creation Process
Standard SOP (Standard Operating Procedure)
- Obtain unique virtual number for platform
- Create new profile in anti-detect browser (unique fingerprint)
- Tie proxy to profile (unique IP, never used for this platform before)
- Register account: unique email + phone number + basic profile data
- Verify via SMS (accept OTP in service interface)
- Enter in CRM with "warming" status
- Conduct warming per schedule (14–30 days depending on platform)
- Change status to "active", hand over to operator
Virtual number is the first step for every account. turbon.rent API allows you to automate this step: request number programmatically, without manual input.
Warming: Schedule by Platform
| Platform | Minimum Warming | Key Actions |
|---|---|---|
| Facebook Ads | 30–45 days | Activity on personal page, adding friends, likes |
| TikTok | 14–21 days | Video views, likes, comments, couple posts |
| Telegram | 7–14 days | Join channels, chat with bots |
| 21–30 days | Subscriptions, likes, saves, 3–5 posts | |
| Google Ads | 7–14 days | Search queries, Gmail activity |
Monitoring and Alerts
What to Monitor
- Account status: daily ban check (automated)
- Ad cabinet limits: approaching daily spend limits
- Proxy activity: proxy not expired, speed not dropped
- Anti-detect profile validity: some tools have account limits
Automatic Ban Monitoring
A script that logs in to each account every 6–12 hours and checks availability is standard practice at 100+ accounts. On ban detection — automatic alert to Telegram, status updated in CRM.
Security and Isolation
Principle: "One Account — One Profile"
Never log into two accounts of the same platform in one browser profile, even "for a second". This creates a digital link between accounts that platforms use for mass bans.
Team Access
Each operator has access only to their accounts via shared password manager (Bitwarden, 1Password). Manager sees everything, operator — only their zone. When employee leaves — immediately change all account passwords they managed.
Operational Health Metrics
- Survival Rate: % accounts surviving 30/60/90 days
- Time-to-Ban: average account lifespan before ban
- Cost per Account: full cost of creating one live account
- Replacement Rate: how many new accounts to create monthly to maintain pool
Conclusion
Managing 100+ accounts is a production process with SOP, metrics, and clear responsibility. Chaotic approach loses 30–50% of accounts from preventable errors. Start with proper infrastructure: unique numbers for each registration via turbon.rent, anti-detect browser, CRM. Scale systematically — and a pool of 1000+ accounts becomes a manageable asset.