How GroNow! Partners built Hunter's API into a custom automation pipeline

Meet GroNow! Partners

GroNow! Partners is a sales automation consulting firm that helps B2B companies build end-to-end outreach systems. 

Founder Hans Guiscardo works with growth-stage companies that have limited sales resources but real pipeline targets - helping them replace manual SDR work with automated, scalable processes that still feel human when they reach a person. 

His core philosophy: skilled people should spend their time at moments of truth. Research, data enrichment, and email validation are not moments of truth. Those should be automated.

Hunter's API sits at the centre of the automation stack Hans has built - and that he now builds for clients. He doesn't log into the Hunter platform. He connects to it directly, through code, as one step in a pipeline that runs without him.

The challenge

The challenge Hans faced - and that he sees in every client he works with - is the gap between a list of LinkedIn profiles and a list of verified, actionable email addresses. 

LinkedIn is the starting point for most B2B prospecting. It gives you names, titles, and company domains. What it almost never gives you is a direct email address, and without one, none of the outreach automation that follows can function.

The manual alternative - researching contacts one by one, guessing email formats, uploading CSVs to verification tools and re-associating the output - would take ten or more hours for a batch that an automated script can process in four or five. Worse, it's the kind of work that uses up capacity without adding real value.

"Where does the human interaction truly make a difference? It doesn't in automating and validating emails, finding emails. You should focus on that and outsource this."

Hans Guiscardo, Founder, GroNow! Partners

The solution

Hans built a custom Python script that automates the full journey from raw LinkedIn data to outreach-ready contacts. 

Hunter's API is a core component of that pipeline, providing the email finding step that turns a name and domain into a verified address.

• The script pulls prospect data from LinkedIn, then normalizes each record - stripping out suffixes like MBA or PMP, cleaning up unusual characters, and standardizing names so they're suitable for email pattern matching. Data quality at this stage determines whether Hunter can find a match.
• Normalized records go to Hunter's API for email finding. Hunter returns verified addresses where it has them, applying its own pattern logic across its index of public data. Hans uses this primarily for email discovery, occasionally layering on validation for records where a higher degree of confidence is needed.
• Verified contacts flow directly into Zoho CRM, where they enter automated outreach workflows. The pipeline runs server-side - four to five hours of unattended runtime per batch, replacing what would otherwise be a full working day of manual effort.

The API is what matters here. It is the data source that fits into his workflow, which is critical to him - the tool needs to fit into his process, not the other way around.

The results

This pipeline generates tens of thousands of verified contacts per year, feeding outreach campaigns that run at scale. 

For the clients he builds similar systems for, the automation makes prospecting into emerging markets tractable - it's possible to penetrate a new geography or sector without sending people to events or doing manual research.

"For a lot of companies trying to grow, it's like, how can they penetrate emerging markets without going in overhead, without having to go to events and send people? That's where Hunter helps." 

Hans Guiscardo, Founder, GroNow! Partners

What once took ten or more hours of manual effort, now takes four to five hours of server runtime. Because the process runs without human involvement, it doesn't compete for the time of people whose skills are better used in conversations.

The takeaway

For anyone building sales automation infrastructure, Hunter's API is an email finding layer that integrates without friction. 

It doesn't require adopting a new platform or changing the way data flows through a system - it accepts inputs and returns outputs, cleanly, as part of whatever pipeline surrounds it.

Hans Guiscardo's view of where human effort belongs in the outreach process is clear: save it for the conversations. 

Everything before that - including finding and validating the email address that makes a conversation possible - should run on its own. 

Hunter is how he makes that work.