How many team members can I invite to Valid Email Checker?

Valid Email Checker does not put a hard cap on the number of team members you can invite to your account. There is no seat tier, no per-user price step, and no upgrade dialog that pops up once you cross a magic number. Whether you are a two-person consultancy or a 60-person marketing operation, the same Account Settings → Team page handles it the same way. The pricing model is consumption-based — you pay for credits consumed, never for the number of users on the account.

What teams actually look like in practice

From watching how real customers use VEC, three rough sizes emerge:

• Solo or 2-3 seats — freelancers and very small agencies. Often the owner plus one or two contractors who run bulk uploads now and then.
• 5-15 seats — growth, lifecycle, and email-marketing teams at small SaaS companies. Each member typically owns a specific segment or list.
• 20-50+ seats — agencies handling many client lists, or enterprise email operations with regional sub-teams. At this size, an internal team-lead workflow usually emerges where one or two operators do the heavy bulk work and everyone else does single verifications and CRM-driven cleanup.

How the no-seat-limit model works financially

Adding a team member does not move your monthly cost on its own — see does adding a team member cost extra credits. The bill is driven entirely by how many emails the team verifies against the shared credit pool. Ten members verifying 1,000 emails each pulls the same total as one member verifying 10,000. This is intentionally the opposite of per-seat SaaS pricing — we would rather see the credit usage line move and let you bring as many operators onto the account as you need.

Are there any soft limits we apply?

A few rate-limit-style guards exist on the invite endpoint, but none of them resemble a seat ceiling:

• A 5-second client-side cooldown between invite submissions to slow accidental double-clicks.
• The system rejects duplicate emails, your own email, and any email already registered as an owner account.
• If you try to invite hundreds of members at once via the comma-separated input, the browser will process them sequentially — there is no batch endpoint, so very large batches just take a minute or two to finish.

What does scale with team size

Three things grow with the number of seats: the volume of verifications running concurrently (mostly fine — our queue scales horizontally), the depth of your Credits History and Uploads & Results tables, and the security surface area. More members means more passwords, more 2FA tokens, and more potential off-boarding events when people leave. The fix for the last one is to make sure every team member enables authenticator-app 2FA on day one and to remove members immediately when they leave the org.