beehiiv Revenue: Company Run Rate vs Newsletter Earnings
Separate beehiiv’s company run rate from publisher subscription earnings and forecasts, then investigate the business model behind real newsletter cases.
The clearest company figure in the sources reviewed is $32 million in annualized revenue, disclosed by beehiiv cofounder Tyler Denk in a post dated November 19, 2025. It is a historical run-rate statement, not verified full-year 2025 revenue, current 2026 revenue, or the earnings of newsletters using the platform.
That last distinction is especially important here. beehiiv also publishes large figures about money earned by its users. Mixing the two creates a bigger headline and a less useful answer. A founder considering email software and a creator considering a paid newsletter are investigating different businesses.
Contents
What does the company revenue figure mean?
Preserve the phrase “annualized revenue” from the founder’s fourth-year retrospective. Do not silently upgrade it to subscription ARR or a completed-year accounting result.
The post’s opening reports $32 million annualized revenue, 110 employees, and more than three billion emails sent per month. The revenue figure is a company disclosure, not a set of audited accounts reviewed by ProvenStartups.
A useful evidence ledger therefore starts with these boundaries:
| Question | What the reviewed evidence supports |
|---|---|
| What company amount was disclosed? | $32M annualized revenue |
| Where and when? | Founder retrospective dated November 19, 2025 |
| Is it current October 2026 revenue? | Not established by that dated statement |
| Is all of it recurring subscription revenue? | Not established by the opening statement |
| Does it disclose company profit? | No profit figure established here |
The article also contains an internal year inconsistency in its campaign narrative. We use the explicit opening disclosure and displayed publication date, rather than reconstructing a precise campaign timeline from that section. A primary source is still something to read critically.
Which amounts belong to newsletter publishers?
Publisher earnings describe money made by businesses using beehiiv. They are not automatically revenue earned by beehiiv, and they are not a forecast for a new newsletter.
The January 2026 State of Newsletters report says paid subscriptions generated $19 million in 2025 versus $8 million in 2024. These are publisher-side subscription figures reported by the platform.
The June 2026 paid-newsletter report repeats the $19 million result and projects $35 million for 2026. A projection remains a projection until a later source establishes the completed result.
| Figure | Recipient or scope | Time basis |
|---|---|---|
| $32M annualized revenue | beehiiv company | Historical operating pace |
| $19M paid subscriptions | Publishers using beehiiv | Reported 2025 total |
| $35M paid subscriptions | Publishers using beehiiv | Projected 2026 total |
Keep these in separate rows. Adding them would mix company income, customer income, and different periods. Subtracting one from another would be equally uninformative without a consistent revenue definition and a documented flow of funds.
Which calculations can you safely make?
You can check arithmetic while keeping the underlying labels intact. You cannot use arithmetic to fill missing definitions.
Dividing $32 million by twelve produces approximately $2.67 million per month. That is a monthly equivalent of the published annualized figure. It is not a separately reported MRR number, and we do not label it one.
For the publisher subscription totals, the calculation is ($19M − $8M) ÷ $8M = 137.5%. That is consistent with the rounded 138% growth stated in the platform’s report. It still says nothing about the median publisher’s growth or the company’s profit.
A hypothetical example shows why. Suppose one large publisher grows from $900,000 to $1.9 million while ten small publishers each remain at $10,000. The group total doubles from $1 million to $2 million, but ten of eleven businesses did not grow. These are invented numbers illustrating aggregation, not beehiiv observations.
Before applying any platform benchmark to your plan, inspect who was included, what period was measured, and whether inactive or unsuccessful participants were excluded. A total and a typical outcome are different answers.
Are you building a platform or a publication?
Choose the payer and delivered outcome before choosing a revenue comparison. Software infrastructure, reader-funded publishing, and a service around publishing have different constraints.
| Model | Who pays? | Work that must continue |
|---|---|---|
| Email software platform | Publishers or organizations | Delivery, account management, product reliability |
| Paid publication | Readers | Useful, repeated editorial output |
| Newsletter-supported product business | Buyers of the publisher’s product | Product fulfillment plus audience development |
| Publishing service | Clients | A defined service outcome and ongoing support |
The Ghost revenue ledger makes a similar separation between platform run rate and publisher earnings. That is a comparison of financial scope, not a tested recommendation to buy one platform instead of another.
A founder may reasonably decide that operating an entire email platform is too broad, then investigate a narrow workflow used by publishers. But the existence of a large platform does not validate every extension or service around it. You still need a reachable buyer with a recurring problem and a credible reason to pay.
What do real newsletter cases add?
Individual cases reveal how money actually enters a business. They are useful when their evidence grade and limits remain visible.
The Tim Stoddard project record links to a founder interview reporting about $86,000 over five months from selling his own product through a newsletter with roughly 15,000 subscribers. That is period sales associated with a product business, not $86,000 MRR and not revenue from paid newsletter subscriptions.
This does not establish that he uses beehiiv, and we do not make that claim. The case belongs here because it illustrates a different money mechanism that a reader researching “newsletter revenue” might otherwise overlook.
The Kit record provides a software-side contrast. The interview host introduces its financial headline, so the record retains a creator-reported classification. Its discussion of serving creators and helping with migrations is more useful for defining the customer task than for forecasting a new entrant’s revenue.
Read the source behind each case before copying the model. Record whether the buyer pays for software access, ongoing information, a separate product, or work performed by a person. Then list the costs and responsibilities omitted from the headline.
How should you use the evidence before building?
Turn the research into a bounded decision, not a motivational revenue target. The right next step depends on the business you intend to operate.
If you want to build software, identify one repeated publishing task and observe how a real operator completes it. If you want to publish, identify a reader decision your work can improve repeatedly. If you want to sell a service, specify the deliverable and the capacity required to maintain it.
Use this five-line research note:
- 1.Business and payer: name the entity receiving the money.
- 2.Metric and period: record exactly what was disclosed.
- 3.Evidence: link the original source and identify who made the claim.
- 4.Missing inputs: list delivery cost, acquisition cost, and retention information you still need.
- 5.Next observation: choose one customer action that would support or weaken the idea.
Our newsletter revenue examples extend the case comparison. The SaaS gross-margin worksheet helps investigate the costs behind software revenue, while the customer exit interview guide addresses what to learn when a recurring customer leaves.
None of those steps needs a guessed current beehiiv valuation or an invented profit number. Better evidence about your buyer is more valuable than extra precision in somebody else’s headline.
Frequently asked questions
Is beehiiv’s $32 million figure ARR?
The reviewed founder post calls it annualized revenue. Without a clearer definition of its recurring components, this guide preserves that wording rather than relabeling it subscription ARR.
Is the $19 million figure beehiiv company revenue?
No. The cited platform reports describe paid subscription revenue earned by publishers during 2025. That is a different scope from company revenue.
Did paid newsletters already earn $35 million in 2026?
The June 2026 source presents $35 million as a projection. This guide does not treat it as a completed result.
How profitable is beehiiv?
The reviewed disclosures do not establish a company profit figure or margin. Revenue, annualized pace, publisher earnings, and profit should remain separate.