Jonas Mets

The through-line

Across nearly every post, Jonas Mets returns to one idea: dirty data in HubSpot is not a one-time cleanup job but a compounding, ongoing problem, and the fix has to live inside the platform itself rather than bolted on around it. He frames invalid emails and duplicate records as the two things that "compound everything downstream in HubSpot" [13], and he keeps pointing at the moment teams discover this the hard way, whether it is a sales rep searching "ACME" and getting fifty companies back [3] or a newsletter bounce rate that drops the moment a list is validated first [1]. Over time this preoccupation has widened from a single deduplication app to a broader Koalify product line, a Premier partner status with HubSpot, and, on the podcast, a more personal reflection on focus: the same instinct to stop treating problems as occasional fixes shows up in how he restructured his own work after realizing he was spread too thin [16].

On dirty data

Mets treats invalid emails and duplicates as twin, self-regenerating problems rather than isolated messes. "Invalid emails quietly wreck deliverability, reporting, and campaign performance" while "Duplicates break trust, segmentation, ownership, automation, and attribution usually all at once" [13]. He is explicit that cleanup does not stay clean: "neither one stays fixed on its own," because "the sources that created it (form fills, integrations, enrichment tools, Salesforce sync) never stop running" [13]. His conclusion, echoed from a guest but clearly his own operating view, is that "the best RevOps teams don't treat email hygiene and deduplication as occasional cleanup projects. They treat them as ongoing operational processes" [13]. He also ties this directly to trust on the sales floor: "Before duplicates break your reporting, they break your reps' trust, and once that's gone, nothing downstream works" [3], and to measurable outcomes, noting a newsletter's "0.43% bounce rate... our lowest in years" after validating the list first [1].

On staying inside HubSpot

A recurring design principle in how Mets talks about his own product is that fixes should happen without leaving the CRM. Describing the email validation app, he says it works "through a workflow action or a CRM card, and writes the result straight back to your contact properties," with "No exports. No third-party dashboard. No extra login. Everything happens without leaving HubSpot" [14]. He repeats the same framing for the app's purpose generally: "cleaner emails going in, without leaving HubSpot. That's the whole idea" [5]. Lead deduplication gets the same treatment, built to "work the same as every other object" with detection rules, bulk merge workflows, and merge rules that "decide which property values survive" [6][12].

On messy CRMs

Mets pushes back on the instinct to see every messy HubSpot portal as a failure. "A messy CRM isn't always a failure," he writes, arguing that "early on, efficiency isn't the priority, getting things done is" and "duct tape and good intentions is usually the right call" [8]. What matters, in his view, is timing: "The mess isn't the problem. Missing the moment it flips is, when the shortcut starts costing more than the fix" [8]. He extends this to how consultants should frame their work with clients: inheriting a messy system means "you've caught the company right when the duct tape finally costs more than the fix," not that you're "cleaning up someone's failure" [8].

On integration quality

Mets is skeptical of surface-level integration claims. "It integrates with HubSpot... That's the wrong question," he writes, laying out what should be asked instead: "at what level?", "which object types does it actually cover?", "how often does it update?", and "who owns the association logic" [15]. He credits integration depth, not features or price, as the real decision driver, noting that "how it actually worked under the hood mattered more than anything on the feature sheet" [15].

From the stage

On the RevOps500 Podcast, Mets discusses a personal operating mistake that doesn't appear in his written posts: taking on too many commitments at once, including client project work, building the Qualify app, and a newborn daughter, and how the year improved only after he stopped freelance project work in January and hired a full-time RevOps person to absorb those duties, freeing him to concentrate solely on building Qualify [16].

Takeaways

• Validate email lists before sending, not after; Mets saw a 0.43% bounce rate, his lowest in years, by excluding 60 invalid addresses first [1].
• Treat email hygiene and deduplication as continuous operational processes, not one-off cleanup projects, since the sources of dirty data never stop running [13].
• When evaluating a HubSpot data integration, ask about integration level, object coverage, update frequency, and who owns the association logic rather than settling for "it integrates with HubSpot" [15].
• Don't assume a messy inherited CRM signals failure; the real inflection point is when the shortcut starts costing more than fixing it [8].
• Build fixes to run inside HubSpot itself (workflow actions, CRM cards) rather than requiring exports or third-party dashboards [14].
• Cut down on parallel commitments: Mets attributes his improved focus to dropping freelance work and hiring dedicated help so he could concentrate on one product [16].