← all essays
SaaS · Fraud· 6 min read

Your SaaS has a signup problem: the itemised $3 bill

A hundred bot signups in fifteen minutes, ten fake users a day, a free-trial queue full of ghosts. Fake signups are not a vanity-metric problem — here is what they actually cost.

A founder posts on r/SaaS: 100+ bot signups in 15 minutes. Another: ten fake users a day, every day, since launch. A third watches their free-trial cohort fill with accounts that will never convert, because the trial abusers found them first. If you run a signup form, you have met this problem — the only question is whether you have measured it.

You should. Because a fake signup is not free just because no credit card was involved.

The itemised bill

Price out each fake signup honestly and it lands around $3, in four places:

  • Transactional email burned on a dead or disposable inbox — small per unit, brutal at bot volume
  • Support load — “my code never arrived” tickets from addresses that never existed
  • Poisoned analytics — activation rates, cohort charts and A/B tests skewed by ghosts
  • Fraud exposure — free-trial abuse, card-testing on upgrade flows, referral-program farming
Stripe quietly blocked 3.3 million abusive trial attempts. That is not a vanity metric — it is a market.

Anatomy of a fake signup

Bot traffic is lazy. The same fingerprints repeat across every product we look at:

  • Disposable domains — temp-mail services that die in an hour, and lookalikes of them
  • Mangled providers — gmial.com, outlok.com — typos no human would repeat
  • Gibberish local parts — strings with the entropy of a random generator, not a name
  • Datacenter and Tor IPs — “users” signing up from cloud servers and exit nodes
  • Plus-alias farming — one Gmail, fifty trials
  • Keyboard-walk usernames — qwerty, asdfgh — the fingerprints of a script, not a person

CAPTCHA is not a strategy

The reflex answer is a CAPTCHA. The reflex is wrong: bot operators route around the common ones, and every real user pays the friction tax — on mobile, where your signups live, the abandonment cost is well documented. Veteran founders in the threads say it plainly: the bots that matter got through reCAPTCHA years ago.

The modern answer is not a wall, it is a score. Validate the email’s structure and domain, check the phone where you collect one, look at the IP, and combine the signals into a single confidence number. That number — not a puzzle — is what you route on.

Route, don’t block

Naive blocking converts fraud-fighting into a conversion-killer. The discipline is in the thresholds: auto-approve the clearly genuine, block the clearly fake, and put only the uncertain band through a step-up — an OTP, a payment-method nudge, a human glance.

Done right, real signups get faster, not slower: the ghosts that used to clog your onboarding emails and trial queues simply stop arriving. Your activation chart starts telling the truth.