Icypeas + Kite

Kite finds a person's work email by giving Icypeas their first name, last name, and company name or website. For one person, it runs a single email search. For a list, it starts a bulk email search that Icypeas works through in the background, and Kite checks its progress and collects the results as they finish.

Say you come back from a trade show with 200 badge scans that have names and companies but no email addresses. Kite adds each company's website where the scan is missing it, sends the list to Icypeas, and returns it with an address and Icypeas's confidence in that address beside every name it could find. The people Icypeas couldn't find stay on the list, marked as not found.

Kite checks an address you already have by sending it to Icypeas's email verification, which tests whether the mailbox exists and accepts mail. This matters most for older lists, because people change jobs and companies change domains, and every bounce makes it a little harder for your next email to reach an inbox.

When you hand Kite last year's webinar export before a re-engagement campaign, it verifies each address on it. When an address fails, Kite marks it as one to stop using and runs a fresh email search for the person at their current company.

Kite builds a new list by searching Icypeas's people database with filters for job title, company, location, skills, languages, school, and keywords. Each filter can include or exclude values, so Kite can look for marketing leaders in Germany while leaving out agencies and your current customers. Its company search works the same way with filters such as industry, location, and headcount.

Before it runs a search, Kite counts how many people or companies match. Counting costs no credits, so you see the size of the list before anyone pays for it. If you ask for heads of growth at software companies with 50 to 200 employees and the count comes back at 14,000, Kite tightens the filters with you first, using what it knows about your best customers, rather than pulling a list nobody could work through.

Kite reads a public LinkedIn profile or company page through Icypeas to fill in a row and confirm it's current. A profile gives Kite the person's name, current role, and employer. A company page gives it the company's own description of itself. Kite can read one page at a time or up to 50 in a single request.

This is how Kite checks that the person on your list still holds the job you're writing to them about. When a prospect turns out to have moved to a new company, Kite tells you and offers to look them up there, because a new role is often a good reason to get in touch.

Kite uses Icypeas to fill whichever piece of a contact record is missing. It finds a person's LinkedIn profile URL from their name and company or job title, and it finds a company's profile URL from its name or website. It can do either for a whole list at once.

It also works in reverse. Given a professional email address, Icypeas finds the LinkedIn profile behind it, one address at a time or in batches of up to 50. That's useful when a list has email addresses and nothing else, such as a newsletter signup export. Kite finds out who each person is and where they work, then decides with you which of them belong in a sales conversation.

Kite scans a company's domain with Icypeas to find its role-based addresses, the shared inboxes for teams such as sales, partnerships, or press. These matter when you need to reach a team rather than a person, for example when you're pitching a co-marketing idea to a partner and don't yet know who runs partnerships there. Kite keeps those addresses apart from your personal outreach and writes to them differently.