Hunter + Kite

Kite finds a person's work email by sending Hunter their name and their company's domain. Say your head of sales shares a list of 60 finance leaders who spoke at a conference last month, with names and companies but no addresses. Kite reads the list, removes your current customers, works out each company's domain, and asks Hunter for each person's email.

Hunter returns each address with a confidence score from 0 to 100 and a status. Kite keeps both on the list. In Slack, it tells you how many of the 60 are ready to contact and which people Hunter couldn't find. It also flags the addresses Hunter marked as risky or accept-all, so those don't go out as if they'd been confirmed.

Kite searches a company's domain in Hunter when you know the company but not the person. Hunter returns the addresses it has found there, along with each person's name and job title where it has them. Kite narrows the search by department and by seniority, which Hunter splits into junior, senior, and executive. It can also ask only for people whose name and position are known.

This is how link-building outreach usually starts. Suppose Kite finds that an industry newsletter keeps citing your competitors' research but never yours. Kite searches the newsletter's domain for its editors and marketing staff, picks the person who covers your topic, and writes a pitch about the data you published last week.

Before a full search, Kite can ask Hunter how many addresses it has at a company, broken down by department and seniority. If Hunter knows two people at a 400-person company and neither works in marketing, Kite looks for a better route in.

Kite runs addresses through Hunter's verifier to check whether each one can receive mail. That covers addresses Hunter just found and addresses from anywhere else, such as a contact export from your CRM that's two years old. People change jobs, and their old company addresses stop working.

Kite builds the campaign audience from the addresses that pass. When Hunter calls an address risky or accept-all, it can't confirm that the mailbox exists, so Kite lists those separately and asks whether you want them in the send.

Kite looks up a person in Hunter from their email address or their LinkedIn handle. Hunter returns their name, job title, location, and social profiles. Kite can also look up a company by its domain to get its industry, description, location, and size, or get the person and their company in a single lookup.

This helps most with inbound leads. When someone books a demo with only a work email, Kite looks up who they are and what their company does. It compares them with your ideal customer profile and writes a reply that refers to their actual role, so your team knows who's on the call before it starts.

Kite searches Hunter's company database to find new accounts worth contacting. It can describe the companies in plain language or use Hunter's filters for industry, headquarters location, headcount, company type, and keywords. It can also exclude industries, places, or keywords you don't want.

Kite writes that search from what it already knows about your business. If you sell scheduling software to physical therapy clinics, it might look for clinic groups with 11 to 200 employees in the states where your best customers are. Then it searches each company's domain for the clinic director or office manager and scores each person from one to five against your ideal customer profile, with a reason for each score.

Kite saves the people it finds as leads in your Hunter account and keeps them organized in named lists. Each lead can carry the person's name, position, company, company size and industry, LinkedIn URL, phone number, and Hunter's confidence score. Kite writes its reasoning into the lead's notes, such as why the person fits and what recent company news makes now a good time to reach out.

Kite can also create custom attributes in Hunter, which are extra fields your team defines, and fill them in. A field such as "Kite fit score" lets your team sort Hunter leads by Kite's one-to-five score. When Kite learns something new about a lead, it updates the record. When a person already exists, Kite updates their record by email address rather than adding them twice.

Kite reads the leads and lists your team already keeps in Hunter too. If a sales rep saved 50 people to a list called "Q4 logistics VPs," Kite can pick up those leads, filter them by confidence score or company, verify the addresses, and turn them into a campaign audience.

Kite takes the finished contacts wherever your team needs them:

• Your CRM. Kite creates or updates each contact in a connected CRM such as HubSpot, with the verified email and a note explaining why the person fits.
• A spreadsheet. Kite saves the list to a connected Google Sheet, one row per person, with their role, company, email, confidence score, and Kite's score.
• An email campaign. Kite researches each person's company and writes a message for each one. Once you approve the campaign, it sends from your team's Kite address or a connected email product. Then it reports which messages were delivered, which failed, and who replied.