LaGrowthMachine automatically enriches and verifies professional emails. By enrichment, we mean “identifying the prospect’s contact information”.

Depending on the audience, LaGrowthMachine will automatically enrich and verify 30-60% professional emails.

How does the magic happen? Read-on!

Finding emails from imports from LinkedIn using Visit & Enrich.

Using the Visit & Enrich actions, your identity will visit the lead and extract information necessary to test emails, namely :

  1. First Name

  2. Last Name

  3. Current Company url

  4. Current Company website

Since we now know the fullname of the lead and the company he’s working for, LaGrowthMachine will then proceed to test a lot of different permutations of the firstname, lastname and company domain. For example, we’ll test :

But wait, does it mean we’re sending emails to these to test? Obviously not.

We actually ping the server to request “does this email exist within your database”. And the server will reply yes or no. Obviously, there is a catch! If it doesn't always work. It depends on the server’s configuration :

  • Catch-all Server : if the server is configured in “Catch-all”, it will literally catch everything, meaning it will always reply “yes this email exists”.

    This means that if the server is in catch-all, we won’t be able to verify the email. LaGrowthMachine will never provide an email that we haven’t been able to verify, so whenever a server is in catch-all, we will not provide the email

  • Non Catch-All Server : when the server is NOT in catch-all, it will only reply to the truth. Either “Yes it exists” or “No it doesn’t”.

    This means that whenever it’s NOT in catch-all, we will tests out dozen of permutations until it finally matches with an email existing in their data

Got it?

  1. LinkedIn Profile give us the prospect work info

  2. We ping the server - It’s NOT in Catch-All - All green to test

  3. We test dozen of different permutations until it’s the right one

DropContact estimates that 30% of servers are configured with Catch-All. So it gives room for this technique to work. Bear in mind though that the bigger the company is, the higher the probability for it to be configured in Catch-All.

So if you’re prospecting big corporates, you might end up on the low side of the enrichment spectrum.

This also means that if you’re doing ABM, you might be missing emails for a whole company. Remember, this is the whole server that is configured this way. Which means that the technic won’t work for any prospects working in the company.

Not perfect, but still great!

Finding emails from CSV Imports using Visit & Enrich.

Wait, what if I import data from my CRM, and I don’t have the Linked URL?

Fear not, we have you covered as well :

  • If your CSV contains Firstname + Lastname + CompanyName, LaGrowthMachine will automatically do a search on LinkedIn to find their LinkedIn profile.

    For more information on how we automatically find LinkedIn Profile from import, refer to this article.

  • If we find it, we loop back to the process above.

  • If we don’t, we still have enough information to give it a try. Namely we research from the companyName its domain, and do the above.

    You’re only going to be missing LinkedIn as a channel :)

LaGrowthMachine doesn’t share contact information across users

Some smart folks told us “Wait, automating for so many people, you must have a great database with people’s contact. Why not use it?”. Well, we don’t and we won’t.

Here’s why we don’t share contact information across users :

  • This is not very GDPR compliant - in everything we do, we do our best to offer a GDPR compliant approach to enriching contacts

  • Your information is proprietary, and you probably don’t want to share it. While when you’re using solutions such as Kaspr, Lusha or Prospectin, information will be shared across users, we believe your competitor shouldn’t be able to benefit from your own research.

This safe and sound approach means we have slightly lower enrichment rate than solutions that do not respect GDPR and privacy guidelines, but we believe it’s better this way.

Did this answer your question?