Gmail Signups on a B2B Product: How to Tell Buyers From Tire-Kickers Without Guessing
You can't reliably work out who's behind a Gmail signup from the address, and you don't need to. Ask for a company or website during onboarding, watch which domains they invite teammates from, offer a reason to add a work email, and score them on product usage. Treat personal-email signups as unqualified rather than low intent, and save the "low intent" label for fake and disposable addresses.
An r/gtmengineering post put the problem simply: domain enrichment is solid for work-email signups, but a big chunk of signups come from Gmail and other personal addresses, and those come back with nothing. The poster was deprioritising them by hand. Here's a better system.
Why enrichment returns nothing
Enrichment tools look up the company that owns the email's domain. jane@acme.com maps to Acme. jane.smith@gmail.com maps to Google, which tells you nothing about Jane. Our post on business vs personal email covers the edge cases, such as ISP domains and companies running Google Workspace on their own domain. The free vs business email filter splits a signup export in one pass.
So the question isn't how to enrich Gmail. It's what other signals you have.
Who signs up with personal addresses
From the way people evaluate software, not from any dataset of ours:
- Founders and very small companies who run the business from a Gmail.
- Consultants and agencies testing a tool before recommending it to a client.
- Employees evaluating quietly, before involving IT or procurement, or at companies that block new SaaS signups from work addresses.
- Students, job seekers and the curious. Real people, not buyers.
- Fake, duplicate and trial-abuse accounts. Often disposable domains or plus-addressed variants.
Only the last group is actually low value, and it's the easiest to detect.
Signals that work
| Signal | How to collect it | What it tells you |
|---|---|---|
| Company or website field | Optional at signup, or one onboarding question | The company, from the user |
| Invited teammates' domains | Your invite flow | A teammate at acme.com makes this an Acme account |
| A work email added later | "Add your work email to share with your team" | Domain enrichment now works |
| Billing details | Checkout | Company name and country on the invoice |
| Product usage | Your analytics | Setup done, integrations connected, data imported |
| Asked for a demo or quote | Your sales form | Intent, plus usually a work address |
The second row does the most work in team products. One invite from a company address qualifies the whole account.
What to avoid
- Blocking personal emails on a free trial. You'll lose the founders and quiet evaluators. If you need a work address, ask for it at the moment it matters: inviting a team, starting a paid trial, or booking a call.
- Unmasking tools. Services that claim to find a Gmail user's employer match the address against data gathered elsewhere, and false matches route the wrong people to sales. For EU and UK users, collecting data about someone from another source means telling them about it under GDPR Article 14. Our post on whether collecting business emails is legal covers the basics.
- Scoring on the domain alone. It moves real buyers to the bottom of the queue.
A routing setup that works
- At signup: verify the address. Block invalid and disposable addresses, warn on typos, and accept personal addresses. Our disposable signup guide shows the rules.
- Split by domain type: work domains go to enrichment and normal scoring. Personal domains go to a "qualify by behaviour" track.
- On the personal track: one onboarding question (company or website), an invite prompt, and a usage score after a few days.
- Promote an account to the sales queue when it gets a company signal (invite, work email, company field, billing) or crosses a usage threshold.
- Review the personal-domain accounts that converted each month, and adjust the threshold.
Where SimpleVerifier fits
SimpleVerifier handles step 1: it marks invalid, disposable and risky addresses at signup, so fake accounts drop out before scoring. Signup protection has copy-paste recipes for common stacks, and the API docs list each field. It doesn't identify the person behind a personal address. API access comes with Pro, which is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off; API calls have their own monthly allowance. The first 100 checks are free with a Google sign-in on the verify page. See pricing.
Common questions
How do I find out who is behind a Gmail signup?
Ask them. Add an optional company or website field at signup or in onboarding, and offer a reason to add a work email later, such as inviting teammates. Domain enrichment can't help because gmail.com belongs to Google, not the user's company.
Should I block personal emails on a B2B signup form?
Usually not on a free trial. You lose real evaluators who don't want to use a work address yet. Block disposable addresses instead, and ask for a work email at the point where it matters, such as inviting a team or requesting a sales call.
Are Gmail signups lower quality for B2B?
As a group, they're harder to qualify, not necessarily worse. Score them on what they do in the product and what they tell you, not on the domain alone.
Can I look up a Gmail user's LinkedIn or employer?
Tools that claim to do this match the address against data from elsewhere, and matches are often wrong. If the person is in the EU or UK, collecting extra data about them from other sources triggers GDPR notice duties. Asking is more accurate and avoids the problem.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.