NUMBERS WE CAN DEFEND  //  first-party data or no number at allApply
Editorial standards

How ReplyLead sources its numbers

Updated July 2026  //  by Mark Glazer

The short answer: every number on this site is either ReplyLead's own operating data from campaigns we run, or a published figure with the source named in the sentence. One person writes the pages: Mark Glazer, ReplyLead's founder. When we cannot verify a number, the sentence ships without one.

Cold email is a channel full of unverifiable claims. This page explains who writes replylead.com, where its figures come from, what we refuse to publish, and how to get an error fixed.

Who writes this site

Every guide, benchmark and comparison page here is written by Mark Glazer, ReplyLead's founder, based in the Greater Toronto Area, with 25+ years in targeted sales, growth marketing and digital automation. His position on the channel, from a published interview: "the game has shifted from blasting volume to carefully managing reputation and making every email count." The pages on this site are that position written down and tested against live campaigns. Background is on the about page.

Where the numbers come from

First-party campaign operations. Sending ceilings, warmup windows and bounce thresholds come from infrastructure we run ourselves. The 12-month funnel on the case studies page, 1,080,000 emails and 5,028 replies producing 263 sales-qualified leads, is portal-tracked, not modelled.

The published fee table. The technology cost table in the ROI calculator is built line by line at verified list prices from each vendor, not rounded from memory.

Live verification before every send. Every list is re-verified with a live email-verification pass immediately before sending. Vendor "verified" flags are not trusted: in one of our own audits, 35 of 35 dead mailboxes behind a bounce spike traced back to leads whose vendor validation said valid.

Year-stamped figures. Numbers that age, such as reply rates and thresholds, live on the cold email benchmarks page and carry the year they were current.

What we do not do

No invented statistics. If a figure is not our own operating data or a named published source, the sentence is written without a number. External numbers name their source in the sentence, every time.

No pay-to-play rankings. Our comparison lists accept no payment for placement. One disclosure worth repeating: ReplyLead publishes those lists and appears first in them. The rest of each list is real competitors described from their own published materials, with no star ratings and no invented review counts.

Corrections

Found something wrong? Email Mark@ReplyLead.com. We check the claim against the underlying campaign data or the named source, correct the page, and restamp its visible Updated date.

Update cadence

Every guide carries an Updated line directly under its title, and the page's structured data carries the same date. The date moves only when the content does, so a stale date is a signal, not a decoration. If a year-stamped figure looks out of date, the corrections address above applies.

Common questions

Who writes ReplyLead's guides?

Mark Glazer, ReplyLead's founder, writes every page on the site. No ghostwritten content, no anonymous staff bylines.

Where do ReplyLead's statistics come from?

First-party campaign operations, portal-tracked client funnels, and a fee table built at verified list prices. Anything external names its source in the sentence.

Does ReplyLead accept payment for placement on its comparison lists?

No. ReplyLead publishes those lists and appears first in them, disclosed on each list; the remaining entries are described from their own published materials.

How do I report an error on replylead.com?

Email Mark@ReplyLead.com. The claim gets checked, the page gets corrected, and the Updated date gets restamped.

How do I know when a page was last updated?

Look for the Updated line under the title. It moves only when the content does.

Judge the numbers against the work

The case studies carry named contacts and portal-tracked results; the benchmarks page carries the thresholds we run our own infrastructure on.

Read the case studies See the benchmarks