Launching account farm from scratch — this is an engineering project, not just "create several accounts". Correct sequence of steps determines whether farm will work steadily for months or burn out in first week. This checklist has passed practical verification on dozens of launches.

Block 1: Defining goal and scale

Before starting answer questions

  • For which platform are accounts being created? (Facebook, TikTok, Telegram, other)
  • What are they used for? (arbitrage, SMM, parsing, resale, other)
  • How many active accounts needed simultaneously? (10 / 50 / 200 / 1000+)
  • What budget for infrastructure? (This determines tool selection)
  • Is there already a team or is this solo project?

Calculate unit economics before start

Count cost of one account and expected income. If numbers don't match — scale or strategy is wrong. Launching without calculation = spending money on experiment without control.

Block 2: Infrastructure — mandatory minimum

Antidetect browser

  • Choose tool based on budget and scale:
  • Up to 50 profiles: Dolphin Anty Free / Octo Browser Starter
  • 50–500 profiles: Dolphin Pro / Multilogin Starter
  • 500+ profiles: Multilogin Business / AdsPower Team
  • Create test profile and check fingerprint on coveryourtracks.eff.org

Proxies

  • Choose type: mobile for Facebook/TikTok, residential for most others
  • Check that proxies not on target platform blacklist (test via test account)
  • Configure binding: one proxy = one account profile (not rotation mode)
  • Check for DNS-leak and WebRTC-leak each profile

Virtual numbers

  • Register on virtual numbers service (we recommend turbon.rent)
  • Check availability of numbers for target platform and country
  • Test getting number and SMS on test registration
  • If automation planned — check API works: number request, SMS polling
  • Replenish balance with reserve (minimum for 50–100 activations to start)

Block 3: Additional infrastructure

Mailboxes

  • Unique email per account (if required by platform)
  • Options: temp-mail services (for non-Facebook), corporate domain with catch-all (for long-term accounts)
  • Don't use Gmail/Outlook for mass registration — they block on mass creation

CRM for accounts

  • Google Sheets (up to 100 accounts): create template with fields: ID, platform, login, number, proxy, profile, status, creation date
  • Notion or Airtable (100–1000 accounts): database with filters and links
  • Custom solution or specialized tool (1000+ accounts)

Payment data

  • Unique payment methods for accounts where required (ad cabinets)
  • Virtual cards: Privacy.com, Revolut, Wise — create unique cards per account

Block 4: First accounts — test batch

Start small

  • Create first 5–10 accounts manually, strictly by SOP
  • Document each step — becomes official SOP
  • Fix actual time to create one account

Checklist for creating one account

  • New profile created in antidetect with unique fingerprint
  • Proxy attached, matching account geo
  • DNS-leak and WebRTC checked
  • Timezone matches proxy geo
  • Unique virtual number obtained via service
  • Registration done in this profile
  • SMS received and code entered
  • Basic profile data filled (avatar, description)
  • Account entered in CRM with "warmup" status

Block 5: Warmup

Regulations by platform

PlatformWarmup periodMinimum actions Facebook30 daysLikes, comments, add contacts, watch feed TikTok14 daysViews, likes, 2–3 videos, follows Instagram21 daysFollows, likes, 3–5 posts Telegram7–14 daysJoin channels, chat with bots Google Ads7 daysGmail activity, search, YouTube

Warmup automation

  • Scripts for basic actions (likes, follows) reduce operational load
  • Timing randomization — mandatory. Fixed schedule = bot detection
  • Don't exceed reasonable activity limits: better less but organic

Block 6: Scaling

Scaling transition criteria

  • Test batch (10 accounts) survived warmup without bans
  • SOP documented and reproducible
  • Unit economics confirmed by real data
  • Team trained (if not solo)

Scaling steps

  • Double batch size: 10 → 20 → 50 → 100
  • At each step: check survival rate, adjust SOP if needed
  • Automate bottlenecks (registration, warmup) before scaling further
  • Hire people after automation — not instead of it

Block 7: Operational monitoring

Daily checks

  • Account status (automated ban check)
  • Proxy balance and functionality
  • Virtual numbers service balance
  • Pool replenishment speed (new accounts created vs. lost)

Farm health metrics

  • 30-day survival rate > 80% — good result
  • Cost per live account — should decrease with scaling
  • Time per account creation — KPI for automation

Common launch mistakes

  • Start with large scale without test — lose entire budget on system error
  • Economize on proxies — datacenter proxies for Facebook = guaranteed quick ban
  • Don't document SOP — have to explain everything from scratch when hiring
  • Reuse numbers — fundamental error leading to mass bans
  • Don't calculate unit economics — work at loss without realizing it

Conclusion

Account farm launch — project with clear plan, not improvisation. Proper infrastructure from day one saves months of rework. Key element of each registration — unique virtual number. Start with reliable service: registration, balance replenishment and first activation on turbon.rent — will take 15 minutes.