"567K registered, but how many are actually active?" Let's talk about that.

[Molly Bailey]

Last update I promised I'd answer the question I knew was coming. So here it is, no dodging.

The 567K number, honestly broken down

567,000+ is registered task users. That's not the number that matters, and anyone who's run a task network knows it. Honest three-layer breakdown:

• Registered users: ~568,000 (all-time signups across 209 countries)
• New signups still coming in: ~1,200–1,650 per day this past week
• Actually active (completing verified tasks daily): the number that determines real capacity — and the one most providers will never show you

A user who signed up a year ago and never came back is worthless as capacity. What matters is how many humans show up to do tasks, and that scales with how much I pay out — not with a vanity signup count.

Actual capacity — real numbers

Let me put a concrete number on it, because "we can handle any volume" is what every bot farm says. On a single order:

• 50,000 follows delivers in ~15–20 days. That's a steady ~2,500–3,500/day.
• Smaller orders (a few hundred to a few thousand) clear much faster.

That pace isn't a limitation — it is the product. Real people see the task, do it, and get paid. They don't arrive 50,000-at-once, because humans don't do anything 50,000-at-once. Any provider promising you 50k "real" follows delivered same-day is selling you a bot purge waiting to happen. The 15–20 day curve on a large order is what natural growth actually looks like, and it's the reason the numbers stick instead of getting wiped in the next platform sweep.

So: big orders are welcome. They just deliver at human speed, drip-fed naturally, which is exactly why refill tickets don't pile up afterward.

This week's delivery (Jul 1–8)

• ~56,000 verified completions in 8 days (~102k submissions — the ~27% rejection rate holds steady)
• Daily new signups holding at ~1,200–1,650
• Refill queue: still zero pending

API progress

Provider endpoints still in development. Order handling, refills, and custom orders are live internally; the Perfect Panel-compatible wrapper (services / add / status / balance / refill) is the current build focus. Native drip-feed is already how the task system works — no extra build needed, because real-user delivery is drip by nature. Once the wrapper is testable I'll open a few slots for panel owners here to run real test orders and report back, unfiltered.


Next update: first look at the retention re-checker (the drop-rate measurement system I said I'd build), plus API endpoint status.


For the panel owners reading: what delivery speed do your clients actually tolerate on large follow orders? Trying to price and pace the tiers around what real demand looks like, not guesswork.