About Lyre Leads: The Honest Data Layer for B2B Prospecting

Why Lyre Leads exists

Search for a Google Maps lead tool and you will find dozens of options that look interchangeable: a search box, an export button, and a big accuracy claim. Look closer and a pattern appears. Many are run anonymously, with no named founder and no one to hold accountable when the data is wrong. And the accuracy numbers tend to arrive from nowhere: high percentages with no test size, no method, and no date. A number without a method is not a measurement. It is a hope, priced as a fact.

That matters because scraped business data is a commodity. Anyone can pull names, phone numbers, and websites off a map. What is scarce is knowing what a given row actually claims: whether that email was found or guessed, whether that blank cell means "no" or "never checked," and whether the quality number on the pricing page was ever measured at all. Lyre Leads was built to be the accountable version of this category. Not a bigger scraper, an honest one.

What we do differently

A named verification partner

Email verification in Lyre Leads runs through MillionVerifier, a named third-party SMTP verification service. We name the partner deliberately: a verification claim you can attribute is a claim you can challenge. Every address carries its SMTP result as a label, and a catch-all result is never dressed up as verified.

Labeled provenance on every email

Every email in the product says how it was obtained. Addresses scraped from a business's own website are labeled as scraped. Decision-maker addresses that we pattern-generate from a contact's name are labeled as generated, and they are shown only when SMTP verification confirms they are deliverable. A generated email is never disguised as a found one, and an unverified guess is never shown at all.

Three-state data honesty

Every checkable field in Lyre Leads has three states: yes, no, and unknown. "We checked and the business has no online booking" and "we never checked" are different facts, and the product never conflates them. An empty cell is never allowed to quietly imply an answer.

Published definitions and published measurements

Every field we deliver is defined publicly in our data dictionary, so you can see exactly what a value means before you pay for it. And when we make a quality claim, we publish the measurement behind it on our research page. For example: in July 2026 we verified 700 scraped business emails and found that about 1 in 12 was dead. That number comes with its sample size and date attached, because without them it would be exactly the kind of claim we built this company to replace.

What we will not do

Three commitments, stated plainly. We will not publish a number we have not measured; if we have no measurement, we make the structural claim and stop there. We will not guess business emails; the primary business email on a lead comes from the company's own website, and where we pattern-generate a decision-maker address it is SMTP-verified first and labeled as generated. And we will not hide how data was obtained; provenance is a field in the product, not a support-ticket answer.

These rules cost us something. Honest labels make our coverage numbers look smaller than competitors who count guesses as finds. We think that trade is the entire point.

Who runs this

Lyre Leads is built and run by Soren Lindbo, an independent founder based in Denmark. There is no outsourced support layer: the person who wrote the enrichment pipeline is the person who answers when something looks wrong. If you have a question, found a data problem, or want to challenge any claim on this page, use the contact form. Disagreement about data quality is welcome here. It is the one conversation this product was built to have.