Back to Blog

Account sharing vs multi-accounting: which is costing you?

Account sharing hides revenue and multi-accounting burns cash. How to tell which one is costing you, and why fixing one can cost you the other.

9,400 accounts is the number in your last deck, and your co-founder has just asked if it's real: "Investor call at 2. They want to know how many real people use this. We keep saying 9,400 accounts. Is that true? Also, paid usage is up 38% since June and seats haven't moved. Are people sharing logins?"

You start typing and delete it. You know the users table has 9,400 rows. You don't know how many humans that is, and you can't say whether your 1,150 paid licenses are 1,150 people or closer to 1,400. Account sharing vs multi-accounting sounds like a question about definitions until the answer is due in front of an investor at 2.

So you pull the numbers. This is a made-up scenario, so swap in your own. You charge $40 a seat, and a free account costs you $1.20 a month at full use.

Multi-accounting is one person with many accounts:

  • 60 people × 30 free accounts = 1,800 accounts
  • 1,800 × $1.20 = $2,160 a month
  • $2,160 × 12 = $25,920 a year, already spent

Account sharing is many people on one account:

  • 120 seats × 2 extra people = 240 people not paying
  • 240 × $40 = $9,600 a month, if every one of them would pay
  • Say one in three would: 80 × $40 = $3,200 a month, or $38,400 a year

Together that's $64,320 a year, more than a month of runway if you spend $60,000 a month. And the number you've been repeating is wrong in both directions. Those 1,800 accounts are 60 people, so 9,400 accounts is really 7,660. Add the 240 people hiding behind shared logins and you get 7,900. The figure in your last deck was 1,500 too high, about 16%, and you set a hiring plan by it.

You act on both. An email asks shared accounts to add their colleagues, and a new rule allows one free account per IP address.

An agency of five has shared one $40 login for a year. They get your email and do what it says. The second person to sign up from their office sees an error saying an account already exists on this network. Nobody writes to you. Three days later that seat cancels, and the reason field is blank.

They were about to be $200 a month (5 × $40). Over 24 months that's $4,800, and it won't appear on any report. Each repeat account your rule stops saves $1.20 a month, so one lost team equals 4,000 account-months of repeat use ($4,800 ÷ $1.20).

Now say that happens to two teams a month. By month 12 it's 24 teams and $4,800 a month gone (24 × $200). Added up across the year, you've lost $31,200 ($400 × 78, the sum of months 1 to 12). A rule that stopped every one of the 1,800 accounts would've saved $25,920.

Monthly revenue effect at month 12, illustrative010002000300040005000Shared loginsExtra accountsBlocked teamsUS dollars a month
Monthly revenue effect at month 12,illustrative020004000SharedloginsExtraaccountsBlockedteamsUS dollars a month

Those three bars are different kinds of loss: revenue you didn't earn, cash you spent and revenue you drove away. The chart ignores ordinary churn. At 2 p.m. you still owe an investor a number, and by the end of the week you have to choose between tightening up and paying for 1,800 accounts. You can't see which one is bigger.

Account sharing vs multi-accounting: the difference

Account sharing is several people behind one account. Multi-accounting is one person behind several accounts. They run in opposite directions, and they cost you in different ways.

Account sharingMulti-accounting
What you loseRevenue you never earnedCash you already spent
What it looks likeA quiet, loyal customerSignup growth
Usual causeA seat costs more than occasional use is worthA free benefit is worth collecting again
What fixes itPricing, seats and easy invitesLimits per person on each benefit
Seats paid vs accounts used, illustrativeIdle seatsMulti-accountingAccount sharingRoom to expandFew seats paidMany seats paidFewer accounts than peopleMore accounts than people30 free accounts40 seats, 28 people5 people, 1 login30 seats, 45 people
Seats paid vs accounts used,illustrativeIdle seatsMulti-accountingAccountsharingRoom toexpandFew seats paidMany seats paidFeweraccounts thanpeopleMore accountsthan people30 free accounts40 seats, 28 people5 people, 1 login30 seats, 45 people

The obvious fix is one rule: one person, one account. It gives two groups opposite instructions. You want sharers to create more accounts and everyone else to create fewer. A team that stops sharing does it by signing up several people from one office in one afternoon, and that trips a simple duplicate rule. The person running 30 accounts, meanwhile, passes it as 30 new users. That's why blocking duplicates without hurting real users is harder than the rule makes it look.

How to tell which one is costing you

Account sharing shows up on the paid side. Paid usage climbs while the seat count stays flat. One login has several sessions open at once, all day. Support gets tickets about forwarded two-factor codes, or about someone changing the shared password.

Multi-accounting shows up on the free side. Free spend grows faster than new paying customers. Plenty of free accounts use the whole allowance and never come back. Your email column also holds the same mailbox written different ways: Gmail ignores dots, so jane.doe@gmail.com and janedoe@gmail.com are one inbox, and mail to jane+anything@gmail.com lands there too. That's simply how aliases work.

One number tells you most of it:

free cost per new customer=free plan spend in a monthnew paying customers that month\text{free cost per new customer} = \frac{\text{free plan spend in a month}}{\text{new paying customers that month}}

Say you spend $6,000 on the free plan and win 40 customers. That's $150 each. Without the 1,800 accounts it's $3,840, or $96 each, so they add $54 to every customer you win ($2,160 ÷ 40). You can work out your own cost per free user the same way.

If both are happening, start with the free side. It's cash leaving every month, and the sharing revenue will still be there next quarter. Get your free limits fair first, so the people you invite to add seats don't run into them.

How to fix account sharing without losing the account

Most sharing is a pricing signal. Someone who opens your app twice a month won't pay $40 for that, so they borrow a login.

  • Make adding a person cheap and easy. A low-priced occasional seat catches people who were only avoiding $40. It misses heavy shared use, and some full seats will trade down.
  • Limit active sessions per login. This catches simultaneous use. It misses people who take turns, and it hits the customer on a laptop and a phone.
  • Charge for usage instead of seats. Sharing stops mattering, and that 38% rise would've been billed. Revenue gets harder to forecast.

Decide where free limits should sit before you change what a seat includes.

The basic fixes for multi-accounting, and how they break

Each of these catches something real. Read the fourth column with that agency in mind.

Basic fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny second real inboxPeople whose code lands in spamDeliverability work
Disposable-domain blocksKnown throwaway servicesNew domains and ordinary mailboxesPeople using privacy forwardingA list someone updates forever
Gmail dot and plus rulesOne inbox written several waysA second real mailboxPeople who sort their mail with plus addressesUpkeep as mail services change
CAPTCHASimple scriptsPeople signing up by handPeople using screen readersFees and lost signups
Phone or card requiredCasual second accountsAnyone with another number or cardPeople without a reliable mobile numberA charge per text, fewer signups
One per IP addressRepeats on one connectionAny other networkOffices, campuses and householdsExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listStaff on company VPNsAnother list to maintain
Rate limitsBursts from one account30 accounts under the limitReal users in a busy hourTuning per endpoint
Usage capsOne account overrunningEach new account's fresh capAnyone at the capDeciding when your product stops
Manual reviewWhat a person can spotAnything spread out slowlyWhoever looks odd to a tired reviewerHours every month

At one minute per account, reviewing 1,800 accounts takes 30 hours.

Stack these and your form asks for a verified email, a puzzle, a phone number and a card, and five people at an agency have to get through it one at a time. Every row also asks about the signup, while the money moves later, when a free benefit goes out.

Write down what one person gets and what one seat covers, in a plain one account per person policy.

Decide each free benefit when it's claimed, and keep a record of who received it.

Give anyone you turn away a way to reach you. What you say to them decides whether a real customer writes back.

Then ask shared accounts to add people. Their signups now meet rules that were written for them.

Your records can tell you an account had the benefit. They can't tell you whether a new account is the same person or a colleague at the next desk.

Stop rebuilding the part that keeps breaking

You don't have to build your own abuse prevention system. AbuseZero was made for the multi-accounting half of this post. Creating a fresh account isn't enough to erase previous activity. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. The alias rules and domain lists in that table? It checks mailbox aliases, disposable domains and mail routing. Where a one-per-IP rule stops, it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Signals are read together, never one at a time. AbuseZero puts 140,000+ signals through multi-layer AI risk analysis, which detects linked claims and flags abuse that single checks miss. There's also a proprietary algorithm, with AI that checks the claim again.

Your server makes one API call when someone claims a free benefit and gets a clear allow or deny, under rules you control. Observe mode shows you what would be denied before anyone is blocked, so you can read those would-be denials before any team meets one. Seats and logins stay in your app. The quickstart protects your first benefit.

Frequently asked questions

What's the difference between account sharing and multi-accounting?

Account sharing is several people using one account. Multi-accounting is one person using several accounts, usually to claim a free benefit more often than you meant to give it.

Is account sharing always a problem?

No. A couple on a low-priced plan may never have paid for two seats. Act on it when paid usage keeps rising and seats don't.

Which should I fix first?

Usually multi-accounting, because it costs cash every month. Sharing responds better to pricing than to blocks, and it can wait a quarter.

Protect free benefits and keep the teams

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.