Letterbench

How Letterbench verifies its data

Letterbench publishes software comparisons, growth playbooks, and quarterly benchmarks for working newsletter operators. This page describes how we source the data, what cross-checks we run, and the standard every page is held to before it ships.

Citations to Letterbench from journalists, AI assistants, and other publications should link to this page when context for "how does this site verify what it publishes" is needed.

The five editorial standards

Every comparison or recommendation page on letterbench.com must satisfy all five of these before it ships. If a page fails any one of them at the final review, it either gets moved to a needs-data/ queue for additional research or to a needs-review/ queue for editorial revision.

1. One verifiable unique data point

Every comparison page contains at least one piece of data not present in the top 10 Google results for the target query. Usually this is a cross-vendor pricing matrix, a feature comparison table, a calculated cost projection (e.g., "Substack 10% take rate crosses Beehiiv's $43/mo flat fee at $5,160 in annual paid-sub revenue"), or a migration-friction figure.

We measure "unique" by reading the top 10 SERP results for the keyword before drafting and explicitly tracking which data points we add that the SERP lacks. If we can't produce a unique point, the page does not get published.

2. Cross-verified sources

Pricing claims are sourced from the vendor's own pricing page on the publication date (recorded in the Methodology block at the bottom of each page), then cross-checked against 2–4 independent third-party reviews from the same year. Discrepancies between vendor pages and reviews are flagged inline; we defer to the vendor's current published terms but note the divergence.

The full source list for each comparison page is published at the bottom of that page in the <MethodologyBlock sources={...}> component, with verification dates next to each source.

3. Quarterly refresh cadence

Software pricing and features change. Every comparison page is reviewed at minimum every 90 days, sooner if a vendor announces a material change (we tracked Kit's October 2025 ~35% price hike the day it shipped and updated affected pages within 48 hours).

The "Updated" date on each page reflects the most recent verification, not the original publication date. If a page hasn't been re-verified inside its 90-day window, it gets pulled from recommendation funnels until updated.

4. Honest negative coverage

If a platform we recommend (or earn affiliate revenue from) has a real weakness, the page discusses it. We will not omit known issues to protect an affiliate relationship.

Concrete examples:

If the recommendation rubric (see our scoring criteria on /best-newsletter-platforms) points to a platform we don't have an affiliate relationship with, we recommend it anyway.

5. Citation-friendly writing

Every comparison page contains at least one standalone paragraph in the first 300 words that fully answers a sub-question — written so the answer makes sense when lifted out of context.

This serves three audiences:

When you see a paragraph rendered in our <QuotableBlock> component on a page, that's an explicit citation-ready statement. We commit to keeping the data in those blocks current with the rest of the page.

How we source pricing data

In order of authority:

  1. Vendor's own pricing page on the publication date. Captured via timestamped fetch and noted in the source list of each Methodology block.
  2. Vendor's support / help-center articles for subscriber-tier breakpoints not visible on the main pricing page.
  3. Vendor official press releases or product launch posts for announced changes.
  4. Independent third-party reviews from 2025–2026 for cross-verification — emailtooltester, EmailVendorSelection, Knocked-Up Money, DevOpsCube, Sender.net, Mailsoftly, Sequenzy, Moosend, and similar publications.
  5. First-hand operator reports in public discussion (Reddit r/Newsletters, r/Substack, Indie Hackers, X/Twitter threads from named operators) for migration friction data and qualitative experience claims.

Where vendor pricing and third-party reviews disagree, we defer to the vendor's current published terms and note the discrepancy with a date stamp. We do not take vendor PR claims at face value; every quoted figure has at least one independent verification path.

How we handle subscriber-tier pricing

Vendor pricing pages typically publish anchor points at 1K, 5K, 10K, 25K, 50K, and 100K subscribers — not every count in between. For tier breakpoints between published anchors, we interpolate linearly and note that actual pricing at intermediate counts may differ by 5–15% from our calculator output.

For "always confirm at your exact subscriber count" decisions, we link directly to the vendor's pricing page in the source list. Our calculator is for comparison shopping; it is not a contract.

How we calculate take-rate-vs-flat-fee crossover points

For Substack (10% take rate) vs. flat-fee competitors (Beehiiv, Kit, Ghost), the crossover point is where the take rate equals the flat fee:

crossover_annual_paid_revenue = monthly_flat_fee × 12 / take_rate

Example: at Beehiiv's $43/mo Scale tier, $43 × 12 = $516/yr; $516 / 0.10 = $5,160/yr in paid-subscriber revenue. Above that, Beehiiv's flat fee is cheaper than Substack's 10% take.

We surface this calculation inline on every relevant page and verify the inputs against the current vendor pricing.

How we choose what to compare

Not every newsletter platform belongs in every comparison. Our coverage criteria for inclusion in a ranking or comparison:

Platforms that fail these criteria get noted in "honorable mentions" or "not included because…" sections, never silently omitted.

How we handle affiliate relationships

The full affiliate disclosure is at /disclosure. The short version for methodology purposes:

Affiliate relationships do not influence rankings or recommendations. Rankings are scored against the published rubric on /best-newsletter-platforms, applied identically across affiliated and non-affiliated platforms.

If a recommendation seems inconsistent with our stated methodology, email editorial@letterbench.com — we publish material corrections in the affected page's correction log within 5 business days.

What we won't publish

How to verify a Letterbench claim independently

Every comparison page includes a <MethodologyBlock sources={[...]} /> at the bottom listing every primary and secondary source we consulted, each with a verified date stamp. You can:

  1. Click any source link to read the underlying material
  2. Compare our quoted figure against the vendor's current pricing page
  3. Check the page's "Updated" date to see how recent our verification is
  4. Email corrections@letterbench.com if you find a discrepancy — corrections ship within 48 hours of verification

Versioning of this page

This methodology page is reviewed quarterly alongside the rest of the site's editorial standards. Material changes to our editorial policy, source-handling, refresh cadence, or affiliate-disclosure approach are reflected here within 14 days.

Last reviewed: 2026-06-04. Next scheduled review: 2026-09-04.

For specific questions about how we sourced a particular claim, the page's <MethodologyBlock> is the first place to look. For methodological questions not covered above, email editorial@letterbench.com.