ChatGPT answers, unedited

For a mid-size online publication managing multiple writers and multiple paid newsletters, I’d focus less on “creator platform” features and more on multi-publication management, writer-level revenue accounting, and control over the payment split.

The practical shortlist

beehiiv explicitly supports multiple publications under one account, with up to 10 on Max and custom numbers on Enterprise. It also takes 0% of subscription revenue. Beehiiv Beehiiv

Ghost supports multiple newsletters within a publication, with the number depending on the plan, and takes no transaction fee; payments go directly through the publisher's Stripe account. Ghost Ghost

Substack allows up to 10 publications per account, but charges 10% of each paid transaction, in addition to Stripe fees. Substack Support Substack Support

For your particular model: Ghost vs. beehiiv

I'd look hardest at Ghost and beehiiv.

Choose beehiiv if growth/operations are the priority

beehiiv is particularly attractive if you're building a portfolio of newsletters. You can put multiple publications under an account, create multiple paid tiers, and use Stripe for payments. Beehiiv Beehiiv

For example, you could have:

• Publication A — Writer 1
• Publication B — Writer 2
• Publication C — Writer 3
• Publication D — Editorial newsletter
• Publication E — Premium research product

The important caveat is your writer revenue split. If your business model is:

Writer gets 70% of their newsletter revenue; publication keeps 30%

beehiiv's 0% platform subscription fee doesn't automatically mean it will perform all of the accounting/payout mechanics for you. You may need to maintain the revenue ledger and handle writer payouts separately.

Choose Ghost if revenue ownership and customization are the priority

Ghost is compelling for a publisher because the subscription money goes through your own Stripe account, rather than through a platform-controlled payment pool. Ghost itself takes no transaction commission. Ghost Ghost

That makes a structure like this relatively straightforward:

Subscriber pays $15 → your Stripe account receives payment → your accounting system allocates 70% to Writer A / 30% to Publisher.

Ghost also supports multiple membership tiers and multiple newsletters, which gives you considerable control over the product structure. Ghost Ghost

If you're essentially building a small media company rather than a collection of independent creator accounts, that's an important distinction.

One option I'd consider separately: Stripe Connect

If by “revenue split options” you mean you want the platform itself to automatically split subscription revenue between your company and individual writers, I'd investigate a custom Stripe Connect architecture rather than trying to force a newsletter platform to do it.

Stripe Connect explicitly supports platforms/marketplaces where the platform can control pricing and collect fees from connected accounts. Stripe

That gives you much more flexibility to implement arrangements such as:

• Writer A: 80/20
• Writer B: 70/30
• Established writers: 90/10
• Publication-owned newsletters: 100% publisher
• Joint newsletter: 50/50
• Different splits for subscriptions vs. sponsorships

You'd then use Ghost or beehiiv primarily for publishing/email, while Stripe/your own accounting layer handles the economics.

My decision framework

For your business, I'd structure the evaluation this way:

If you want the fastest launch: beehiiv
If you want maximum publishing/brand ownership: Ghost
If writers are essentially independent creators: Substack
If writer-specific revenue splits are central to the business: Ghost/beehiiv + a proper Stripe/accounting layer, or a custom Stripe Connect setup.

One particularly important question is whether you mean “multiple newsletters under our company account” or “multiple writers where each writer automatically receives their contractual percentage of every subscription.” Those lead to somewhat different platform choices.

If you're essentially building a small media company rather than a collection of independent creator accounts, that's an important distinction.

One option I'd consider separately: Stripe Connect

If by “revenue split options” you mean you want the platform itself to automatically split subscription revenue between your company and individual writers, I'd investigate a custom Stripe Connect architecture rather than trying to force a newsletter platform to do it.

Stripe Connect explicitly supports platforms/marketplaces where the platform can control pricing and collect fees from connected accounts.

That gives you much more flexibility to implement arrangements such as:

For a mid-size online publication running multiple paid newsletters with different writers and revenue-sharing arrangements, I’d focus less on the headline subscription fee and more on multi-publication support, ownership of subscriber data, team/workflow features, and whether you can control the money split yourself.

Based on the current 2026 offerings, beehiiv and Ghost are the two I’d investigate first, with Substack and Patreon serving rather different models.

1. beehiiv — probably the closest match

beehiiv is particularly interesting for your model.

Its current Max plan supports up to 10 publications, while Scale supports 3. Paid subscriptions have 0% platform revenue share, with Stripe processing fees still applying. It also supports multiple paid tiers, tier-specific content access, monthly/annual/pay-what-you-wish pricing, and team functionality. Beehiiv Beehiiv Beehiiv

That combination makes it well suited to something like:

• Publication newsletter — 40% publisher / 60% writer
• Politics newsletter — 50% / 50%
• Culture newsletter — 30% / 70%
• Premium specialist newsletter — negotiated split

The important caveat is that beehiiv's native subscription system doesn't appear to be designed primarily around automatically distributing each subscription payment among multiple internal writers. You'd likely want to use your own accounting/payment workflow for the writer splits rather than expect the platform to function as a multi-party royalty system.

beehiiv.com

2. Ghost — strongest if you want to own the infrastructure

Ghost takes 0% transaction fees on paid subscriptions; you connect your own Stripe account and the subscription revenue goes directly through it. Its Publisher plan is currently $29/month billed annually and includes paid subscriptions and team/staff functionality. Ghost Ghost

That's attractive for a publication because you're not giving 5–10% of every subscription to the newsletter platform as you scale.

Ghost is also particularly appealing if these newsletters are part of a broader publication website, rather than independent creator businesses.

The downside is that you'll probably need to build more of the publisher-specific accounting layer yourself. Ghost is excellent membership/publishing infrastructure; it isn't really a full "we have 20 writers and automatically split each writer's subscription revenue" system.

ghost.org

3. Substack — easiest for writers, less attractive for your business model

Substack is extremely straightforward for individual writers. Paid subscriptions support monthly, annual and founding-member plans, but Substack currently takes 10% of each paid transaction, in addition to payment processing. Substack Support Substack Support

For your situation, that becomes significant.

For example, if your newsletters collectively generate $1 million/year in subscriptions, a 10% platform cut represents $100,000/year before payment-processing costs.

More importantly, Substack's mental model is essentially writer → publication → subscribers, whereas you're describing publisher → multiple writers → multiple publications → shared revenue.

That's a materially different organizational model.

substack.com

4. Patreon — useful if the product is really membership

Patreon supports multiple membership tiers and digital products, but new creators are generally on its 10% platform-fee plan, plus payment processing and potentially other fees. Patreon Help Center Patreon Help Center

I'd consider Patreon if your newsletters are really membership communities with perks, Discord access, bonus content, video, etc.

I wouldn't make it my first choice for a conventional editorial publication with multiple newsletter brands.

support.patreon.com

The bigger issue: revenue splitting

This is the part I'd pay the most attention to.

If your business model is:

Reader pays $10 → platform takes payment → publisher and writer automatically receive predetermined percentages

then you're not merely looking for a newsletter platform. You're looking for a multi-party payments/royalty system.

I'd architect it as:

Newsletter platform
→ subscriber management + email + paywall + analytics

Stripe
→ payment processing

Your publisher ledger
→ determines Writer A gets 60%, Publication gets 40%, etc.

Automated payouts/accounting
→ sends each writer their share monthly

That gives you much more flexibility than trying to make the newsletter platform itself handle your entire royalty structure.

What I'd shortlist for your publication

If I were evaluating this for your business, I'd run a serious pilot with:

1. beehiiv — particularly attractive if you expect many distinct newsletters and want built-in growth/monetization tooling. Its 0% paid-subscription take rate is compelling at scale. Beehiiv
2. Ghost — particularly attractive if your newsletters are fundamentally extensions of one publication and you want maximum control over your website, memberships, Stripe account, and customer relationship. Ghost Ghost
3. Substack — benchmark it for writer adoption and reader experience, but model the economics carefully because of the 10% transaction fee. Substack Support

For your specific use case, I'd lean toward beehiiv if "many newsletters + growth" is the priority, and Ghost if "publisher-owned ecosystem + maximum control" is the priority.

The one thing I'd validate in a sales/demo call before signing anything is whether you can have one organization manage multiple publications while maintaining separate Stripe/payment flows, writer-level analytics, subscriber ownership, and automated revenue attribution. That's likely to matter considerably more than the advertised platform fee.

Ghost is also particularly appealing if these newsletters are part of a broader publication website, rather than independent creator businesses.

The downside is that you'll probably need to build more of the publisher-specific accounting layer yourself. Ghost is excellent membership/publishing infrastructure; it isn't really a full "we have 20 writers and automatically split each writer's subscription revenue" system.

ghost.org

3. Substack — easiest for writers, less attractive for your business model

Substack is extremely straightforward for individual writers. Paid subscriptions support monthly, annual and founding-member plans, but Substack currently takes 10% of each paid transaction, in addition to payment processing. Substack Support Substack Support

For your situation, that becomes significant.

For example, if your newsletters collectively generate $1 million/year in subscriptions, a 10% platform cut represents $100,000/year before payment-processing costs.

More importantly, Substack's mental model is essentially writer → publication → subscribers, whereas you're describing publisher → multiple writers → multiple publications → shared revenue.

That's a materially different organizational model.

substack.com

4. Patreon — useful if the product is really membership

Patreon supports multiple membership tiers and digital products, but new creators are generally on its 10% platform-fee plan, plus payment processing and potentially other fees. support.patreon.com support.patreon.com

I'd consider Patreon if your newsletters are really membership communities with perks, Discord access, bonus content, video, etc.

I wouldn't make it my first choice for a conventional editorial publication with multiple newsletter brands.

support.patreon.com

The bigger issue: revenue splitting

This is the part I'd pay the most attention to.

If your business model is:

Reader pays $10 → platform takes payment → publisher and writer automatically receive predetermined percentages

then you're not merely looking for a newsletter platform. You're looking for a multi-party payments/royalty system.

I'd architect it as:

Newsletter platform
→ subscriber management + email + paywall + analytics

Stripe
→ payment processing

Your publisher ledger
→ determines Writer A gets 60%, Publication gets 40%, etc.

Automated payouts/accounting
→ sends each writer their share monthly

That gives you much more flexibility than trying to make the newsletter platform itself handle your entire royalty structure.

What I'd shortlist for your publication

If I were evaluating this for your business, I'd run a serious pilot with:

For a mid-size online publication running multiple paid newsletters written by different writers, I’d shortlist beehiiv, Kit, and Substack—but I’d put beehiiv first for your use case.

My ranking

Why I'd choose beehiiv: it explicitly supports multiple publications, and its current pricing says paid subscription revenue has 0% platform take; you pay Stripe's standard processing fee instead. Its Max plan supports up to 10 publications per account. Beehiiv

That matters a lot when you're taking, say, 20% of a writer's subscription revenue. On Substack, you'd first lose 10% to the platform, then have to decide whether your writer's percentage is calculated before or after that fee. Substack does support up to 10 publications under one account, but its 10% transaction fee makes the economics less attractive for a publisher operating at scale. Substack Support Substack Support

The important wrinkle: revenue splits

If by "revenue split options" you mean something like:

Writer gets 70%, publication gets 30%, with the ability to change that to 50/50 for another newsletter

That's the feature I'd investigate before committing.

beehiiv is excellent at the subscription/publishing economics, but you shouldn't assume that "0% platform fee" means it automatically handles arbitrary writer-by-writer revenue splits and payouts the way a marketplace platform would. You may need to maintain the split/accounting layer yourselves.

Kit is interesting because it's more explicitly built around individual creators and monetization. It supports paid newsletters with monthly, quarterly and annual subscriptions and currently advertises a 0.6% fee plus payment processing for paid subscriptions. Kit It also has a Creator Network and paid recommendations, which could be useful if your writers cross-promote one another. Kit Kit Help Center

What I'd build for your publication

I'd lean toward:

beehiiv + your own writer revenue ledger/payout system

For example:

• Publication A: writer 70% / publisher 30%
• Publication B: writer 60% / publisher 40%
• Publication C: staff writer 100% salary, publisher retains subscription revenue
• Guest writer: 50/50
• Sponsorship revenue: separate split from subscription revenue
• Bundled subscription: allocate revenue according to an agreed formula

This gives you considerably more flexibility than making the newsletter platform itself the authority on your business relationship with writers.

beehiiv's subscription business is also substantial enough that I'd take its ecosystem seriously: it reports $19M in paid-subscription revenue in 2025, up 138% year over year, with $35M projected for 2026. Beehiiv

When I'd pick Substack instead

I'd choose Substack if your strategy is essentially:

"Each writer is an independent creator; give them the easiest possible way to build their own paid audience."

Its network/discovery effects and extremely simple writer experience are compelling. But for a publication company managing a portfolio of newsletters and taking a contractual share of their revenue, the 10% platform fee and less publisher-oriented architecture make it less appealing. Substack Support

Bottom line

For your specific business: beehiiv > Kit > Substack.

But there's one question that could change the recommendation substantially: Do you need the platform itself to automatically calculate and pay each writer their negotiated percentage, or are you comfortable having your publication collect all subscription revenue and pay writers monthly?

If you need automatic writer-level splits/payouts, I can research the current 2026 options specifically for multi-author publishers/marketplaces and compare beehiiv, Kit, Ghost, Stripe Connect, Memberful, and custom setups—including actual fees and payout mechanics.

For a mid-size online publication launching paid newsletters with multiple writers, I would generally not choose the same platform a solo creator would choose. Your priorities are different: you likely need multiple publications, writer-level revenue attribution, editorial control, analytics, subscriber ownership, and scalable economics.

My shortlist:

TierGauge OwnLetter## My recommendation for your situation

1. Best overall: beehiiv

For a mid-size publication launching several paid newsletters from different writers, this is probably the strongest fit.

Why:

• You can run multiple newsletters under one publishing operation.
• Better suited to growth teams than individual creators.
• Supports monetization beyond subscriptions (ads, referrals, sponsorship models).
• Avoids giving away a percentage of every subscription dollar as you scale. Beehiiv Sasanova

A possible structure:

• Publication owns the platform account.
• Each writer has a newsletter brand/page.
• Revenue dashboards track each newsletter.
• Writer compensation is handled internally: - fixed contributor fee, or
• percentage of net revenue, or
• tiered bonuses based on paid subscribers.

2. Best if your brand and ownership matter most: Ghost

Choose this if you want the newsletters to feel like an extension of your publication website.

Strengths:

• Strong control over branding and subscriber relationship.
• Memberships and newsletters are built in.
• No platform percentage on subscription revenue. Fieldwork

Tradeoff:

• It is more of a publishing platform/CMS than a newsletter growth machine.
• You may need more operational work.

3. Use Substack only if writer autonomy/discovery is the priority

Substack is excellent when each writer is effectively a standalone creator. Its recommendation network can help writers grow, but the economics become less attractive when you have a portfolio of successful newsletters because the 10% revenue share grows forever. TierGauge Publishing House

Example:

• 10 newsletters
• $10,000/month total paid revenue
• Substack fee ≈ $1,000/month before payment processing

At larger scale, that becomes meaningful.

Revenue split models I’d consider

The platform does not need to handle your writer split. Most publications handle this internally.

Common approaches:

Model A: Publisher-owned

• Publication keeps 100% subscription revenue.
• Writers receive salary, bonuses, or contributor fees.
• Best for building a long-term media company.

Model B: Writer incentive split

Example:

• 70% publication / 30% writer of newsletter net revenue
• Higher split after subscriber milestones

Example:

• First 1,000 paid subscribers: 20%
• 1,000–5,000: 30%
• 5,000+: 40%

Model C: Hybrid

• Base compensation + performance share.
• Usually best for established journalists because it rewards growth without making writers carry all business risk.

A stack I would consider

For a mid-size publication:

• Newsletter platform: beehiiv or Ghost
• Payments: Stripe
• CRM/data: your own subscriber database
• Analytics: first-party dashboards + attribution tracking
• Internal writer dashboard: revenue and subscriber reporting

Bottom line

• Launching 5–50 paid newsletters and treating them as a business: choose beehiiv.
• Building a premium publication brand with memberships: choose Ghost.
• Letting star writers operate almost independently: consider Substack.
• Avoid making Substack your core infrastructure if you expect meaningful paid revenue across many writers.

For a mid-size publisher, I’d lean beehiiv first, Ghost second. gatilab.com Sasanova

For a mid-size publication with multiple writers and multiple paid newsletters, I’d put beehiiv first, Ghost second, and Substack third.

My pick: beehiiv

For your specific model, beehiiv is probably the best fit. Its Scale/Max plans support paid subscriptions with 0% platform revenue share, so you're primarily paying the software subscription plus Stripe processing. It also supports multiple paid tiers and paywalled content. Beehiiv Beehiiv

The particularly relevant part for you is Max, which currently supports up to 10 publications, unlimited team seats, and group subscriptions. Beehiiv

That gives you a structure like:

• Publication → Newsletter A → Writer A
• Publication → Newsletter B → Writer B
• Publication → Newsletter C → Writer C
• Central publisher account → subscriptions, analytics, billing
• Your company → collects subscription revenue
• Writers → receive an agreed percentage

The important caveat: beehiiv's 0% fee doesn't itself solve writer revenue sharing. If you want, for example, Writer A gets 70%, publication gets 30%, you'll likely want to implement that as your internal accounting/payout system, rather than expecting the newsletter platform to automatically split every subscription transaction among writers.

Ghost is the strongest alternative

ghost.org is attractive if your publication wants maximum ownership and control. Ghost explicitly charges no payment/revenue fee and connects subscriptions directly to your Stripe account. Ghost

Ghost is unusually well suited to a publication because its current Business tier supports unlimited newsletters and premium tiers, while Publisher supports three newsletters. Ghost

I'd choose Ghost over beehiiv if your priority is:

• Your publication's website/CMS being the center of everything
• Strong editorial control
• Custom design and infrastructure
• Owning the reader relationship and billing
• Less dependence on a creator-oriented platform

I wouldn't choose Substack for this model

substack.com is extremely easy for writers, and it now allows up to 10 publications per account. Substack Support But it takes 10% of every paid transaction, on top of Stripe fees. Substack Support

That becomes painful when you're operating at publication scale.

For example, at $1 million/year in paid subscriptions, a 10% platform fee is roughly $100,000/year before payment processing. With beehiiv or Ghost, that platform-level percentage is $0, although you still have payment-processing costs and software costs.

The bigger question: how you want to split money

I'd separate platform economics from writer compensation.

A good model could be:

Reader pays $100 → payment processing → publication keeps 30% → writer receives 70%

Or, if the publication is providing substantial editing, marketing, sales, audience, and infrastructure:

Reader pays $100 → payment processing → publication keeps 50% → writer receives 50%

I'd also consider newsletter-specific P&Ls, so a writer can see:

• Gross subscription revenue
• Refunds/chargebacks
• Payment processing
• Advertising/sponsorship revenue
• Publication's share
• Writer's share
• Net payout

Bottom line: For a mid-size publisher launching a portfolio of paid writer-led newsletters, I'd start with beehiiv Max unless you have a strong reason to make your CMS/site infrastructure the primary product, in which case I'd seriously consider Ghost Business. I would use Substack mainly if the priority were giving individual writers maximum simplicity rather than building a publisher-controlled multi-newsletter business. Beehiiv Ghost Substack Support

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), subscriber count, and your desired writer/publisher split, I can model the economics of beehiiv vs. Ghost vs. Substack at $100k/$500k/$1M+ annual subscription revenue.

A good model could be:

Reader pays $100 → payment processing → publication keeps 30% → writer receives 70%

Or, if the publication is providing substantial editing, marketing, sales, audience, and infrastructure:

Reader pays $100 → payment processing → publication keeps 50% → writer receives 50%

I'd also consider newsletter-specific P&Ls, so a writer can see:

• Gross subscription revenue
• Refunds/chargebacks
• Payment processing
• Advertising/sponsorship revenue
• Publication's share
• Writer's share
• Net payout

Bottom line: For a mid-size publisher launching a portfolio of paid writer-led newsletters, I'd start with beehiiv Max unless you have a strong reason to make your CMS/site infrastructure the primary product, in which case I'd seriously consider Ghost Business. I would use Substack mainly if the priority were giving individual writers maximum simplicity rather than building a publisher-controlled multi-newsletter business.

For a mid-size online publication running multiple writers/newsletters, I’d pick beehiiv over Substack or Kit.

My ranking

beehiiv is particularly compelling because its current plans explicitly support multiple publications: up to 3 on Scale, 10 on Max, and a custom number on Enterprise. More importantly, beehiiv says it takes 0% of paid subscription revenue, leaving Stripe's processing fees as the transaction cost. Beehiiv Beehiiv

Why I'd choose beehiiv for your publication

The key distinction is that you're not really looking for a "newsletter platform." You're looking for a multi-publication monetization infrastructure.

I'd structure it roughly like:

• Publication owns the beehiiv account/workspace.
• Each writer gets their own publication/newsletter.
• Readers subscribe to individual newsletters.
• Revenue flows into the publication's payment infrastructure.
• You calculate each writer's contractual share after agreed expenses/fees.
• You can have different economics for different writers—for example, 60/40 for staff writers, 70/30 for independent contributors, or different splits based on subscriber acquisition.
• The publication retains control over branding, audience data, cross-promotion and sponsorships.

beehiiv's 0% subscription take makes those economics substantially easier to model than Substack's 10% cut. Beehiiv Substack Support

There's also a meaningful growth advantage: beehiiv has a recommendation network, advertising infrastructure, digital products, automations and other publisher-oriented monetization tools. Its own 2026 report says paid-subscription revenue on the platform reached $19M in 2025. Beehiiv

Where Kit fits

kit.com is worth considering if your writers are effectively independent creators operating inside your ecosystem.

Kit supports paid newsletters and recurring subscriptions, and its current pricing lists a 0.6% platform fee on digital products/subscriptions in addition to payment processing. It also has a sophisticated Creator Network and paid recommendations system. Kit Kit Help Center

That makes Kit interesting if your business model is heavily about creator growth, referrals and marketing automation rather than managing a portfolio of editorial publications.

Where I would not choose Substack

substack.com is fantastic when the model is:

"One writer → one newsletter → writer owns the business."

That's less aligned with:

"One publisher → 10–20 writers → multiple paid publications → publisher/writer revenue sharing."

Substack currently takes 10% of each paid transaction, on top of Stripe fees. Substack Support

So if you're doing, say, $1M/year in paid subscriptions, that 10% platform cut is potentially $100K/year before payment processing. With beehiiv's 0% platform take, you have considerably more room to design your writer compensation model.

One important caveat

I'd separate "platform revenue split" from "writer revenue split."

beehiiv's 0% take doesn't mean it natively becomes a full-fledged Substack-for-publishers with automated contributor royalties. You may need to build the accounting/payout layer yourself—or integrate your payment/accounting stack—if you want sophisticated rules such as:

Writer gets 70% of net subscription revenue attributable to their newsletter; publisher gets 30%; sponsorship revenue split 50/50; cross-sold subscribers allocated proportionally.

If that exact automated royalty/accounting functionality is your primary requirement, I'd evaluate the platforms differently.

Bottom line: beehiiv is my first choice for your situation, especially if you're planning 5–10+ paid newsletters and want the publication—not each individual writer—to control the commercial infrastructure. I'd choose Kit if creator marketing/growth is more important than publisher architecture, and Substack if each writer is essentially an independent business.

For a mid-size online publication managing multiple writers and multiple paid newsletters, I’d put beehiiv first, with Ghost as the strongest alternative if you want more publishing/ownership control.

My pick: beehiiv

For your use case, beehiiv is probably the best fit.

Its big advantage is that you're not forced into a 10% revenue share with the platform. beehiiv currently charges 0% on paid subscription revenue, leaving Stripe's processing fees as the primary transaction cost. Its Scale plan supports up to 3 publications, while Max supports up to 10 publications. Beehiiv Beehiiv

That matters considerably once you have several writers.

For example, suppose you have:

• 8 newsletters
• 8 writers
• $20,000/month in subscription revenue
• Writer contracts giving authors 50% of the revenue from their newsletter

You could collect the $20k centrally, calculate each writer's contractual share, and pay them through your accounting/payroll system. beehiiv doesn't take another 10% just because you're splitting the economics internally.

The important caveat: beehiiv isn't really a writer-revenue-accounting platform. I'd treat the newsletter platform and your writer compensation system as two separate layers.

Ghost is the other serious contender

Ghost is particularly attractive if your publication wants to own the infrastructure and have more control over the publishing experience. Ghost also takes 0% of subscription revenue, charging a fixed hosting fee instead. Ghost

I'd choose Ghost over beehiiv if your priority is:

• publication-owned website + CMS
• maximum control over your publishing stack
• less dependence on a newsletter-specific SaaS ecosystem
• willingness to build/maintain more of the operational tooling yourself

Why I wouldn't choose Substack for this

Substack is excellent for individual writers, but I'd be hesitant to make it the foundation of a multi-writer publication.

Substack currently takes 10% of every paid transaction, on top of Stripe fees. Substack Support

That becomes expensive surprisingly quickly. At $20,000/month in paid subscriptions, that's $2,000/month—or $24,000/year—before payment processing.

It also isn't designed around the sort of "publication owns the newsletter, writer gets X%, editor gets Y%, company retains Z%" organizational model you're describing.

Kit is interesting, but I'd rank it fourth

Kit has unusually good creator monetization and referral infrastructure. Paid newsletters are supported, and its Creator Network lets newsletters earn money from paid recommendations. Kit Kit Help Center

But its paid-subscription economics are currently 3.5% + $0.30 per transaction, with payment processing included in that fee. Kit

Kit is therefore compelling if your writers are essentially independent creators under your umbrella. For a centralized editorial operation with numerous publications, I think beehiiv's multi-publication setup is cleaner.

The bigger question: how you want to split revenue

I'd actually make this decision based on your desired writer compensation model.

If you want:

Publication owns everything → writers receive contractual percentages

beehiiv + Stripe + your own royalty/accounting system

If you want:

Each writer essentially operates their own business → publication takes a management/platform percentage

Kit or Substack can make more sense, depending on how independent the writers are.

If you want:

One company-owned membership → readers pay once and receive several newsletters

I'd look beyond the standard "newsletter platform" model and design a central subscription/membership layer. That's a materially different architecture and could be much better for a publication with multiple verticals.

For your situation, my shortlist would be: #1 beehiiv, #2 Ghost, #3 Kit, #4 Substack.

If you tell me roughly how many newsletters/writers you expect, total subscribers, average paid price, and whether writers should get a percentage of their newsletter revenue or the publication's overall revenue, I can model the economics of each platform and show you the cheapest/best structure.

For a mid-size publication running multiple writers/newsletters, I’d put beehiiv first, with Ghost as the strongest alternative if you want more ownership/control. Substack is attractive for individual writers, but less attractive for a publication that wants to control the economics and revenue splits.

My ranking

🥇 Best overall: beehiiv

For your situation, beehiiv has the strongest combination of multi-publication support, paid subscriptions, analytics, growth tools, and economics.

Its current Max plan supports up to 10 publications per account, while Enterprise offers custom publication limits. The Scale plan includes teams and paid subscriptions; Max adds unlimited team seats and the 10-publication allowance. Beehiiv

The big advantage is economics: beehiiv currently charges 0% platform revenue share on paid subscriptions; you pay the normal Stripe processing fees instead. Beehiiv Beehiiv

That matters enormously when you're paying writers.

For example, suppose a newsletter generates $100,000/year:

• Substack: roughly $10,000 platform fee
• beehiiv: $0 platform revenue share
• You could therefore establish your own writer split—say 70/30, 80/20, or a more complicated arrangement—and have the publication retain the remainder.

beehiiv also has strong native monetization beyond subscriptions—advertising, sponsorships, recommendations, digital products, etc. Beehiiv

One caveat: beehiiv's 0% take doesn't mean it is itself a sophisticated marketplace for automatically splitting subscription proceeds among your writers. If automated per-transaction writer payouts are a core requirement, I'd look at the architecture below.

🥈 Ghost: best if ownership/control is paramount

Ghost is compelling if your publication wants to behave more like a media company with its own publishing infrastructure.

Ghost takes no percentage of subscription revenue and connects directly to your Stripe account. Ghost

The tradeoff is that Ghost is less oriented toward the newsletter-growth ecosystem than beehiiv. You get more control, but potentially more operational work.

I'd choose Ghost if your priorities are:

• owning the publication infrastructure
• owning the customer relationship
• avoiding a percentage-of-revenue platform
• having a highly customized publication/site
• potentially integrating your own writer-payment system

🥉 Substack: easiest writer experience, weaker economics for you

Substack is excellent if you're essentially giving each writer their own independent business.

It supports multiple publications under one account. Substack Support And its network is a genuine advantage: Substack says it has 5 million+ paid subscriptions, with more than half of new subscribers coming through its network. Substack

But the fundamental problem for a publisher is the 10% cut. Writers keep 90% before payment processing fees. Substack Substack

So if you're building a company that wants to say:

"We own the newsletter business, recruit the writers, sell subscriptions, and give writers X% of the resulting revenue"

Substack isn't as natural a fit.

The important distinction: platform vs. revenue-split infrastructure

If by "revenue split options" you mean something like:

Reader pays $10 → publication automatically receives $3 → writer automatically receives $7

then I'd actually consider beehiiv + Stripe Connect rather than choosing a newsletter platform based solely on its native payout functionality.

Stripe Connect is specifically designed for platforms and marketplaces that need to split a payment between multiple parties, take a platform fee, route funds, and control payout timing. Stripe Stripe

That gives you the ability to design your own economics:

Example

• Reader pays: $100
• Payment processing: ~$3.20
• Writer: 70% of net = ~$67.76
• Publication: 30% of net = ~$29.04

Or:

• Writer gets 80%
• Publication gets 20%
• Publication gets 100% of sponsorship revenue
• Writer gets a separate percentage of subscription revenue
• Bonus pool based on subscriber growth/retention

That's much closer to what I'd expect a mid-size publication to need.

What I'd build

For your particular model, I'd shortlist:

Option A — simplest:
beehiiv + your own writer compensation agreements

Best if you can handle writer accounting internally.

Option B — scalable:
beehiiv + Stripe Connect

Best if you want automated, auditable writer payouts and potentially dozens of writers/newsletters.

Option C — maximum control:
Ghost + Stripe Connect

Best if your publication wants its own branded membership infrastructure rather than being heavily dependent on a newsletter platform.

My recommendation

Start with beehiiv if you want to launch quickly. Its current multi-publication/team capabilities and 0% subscription take are unusually well aligned with a publisher running several paid newsletters. Beehiiv

But design the writer economics independently of the newsletter platform. If you expect this to become a meaningful multi-writer business, make Stripe Connect—or an equivalent payment architecture—the layer responsible for the actual revenue split.

That way, you're not locked into a platform's definition of how a "writer" gets paid.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), your expected paid subscribers, and whether the publication or individual writers will own the subscriber relationship, I can give you a concrete beehiiv vs Ghost vs Substack architecture and recommended 70/30/80/20 revenue model.

For a mid-size online publication launching multiple paid newsletters written by different writers, I’d shortlist Ghost, beehiiv, and Substack—but they fit very different business models.

My recommendation: Ghost

Ghost is the best fit if the publication—not individual writers—should own the subscription business.

Why Ghost stands out: it connects subscriptions directly to your own Stripe account and takes 0% of paid revenue; Ghost says you retain ownership of your member/customer data as well. Ghost Developer Docs Ghost

That makes it particularly attractive if your model is something like:

Reader pays $10 → Stripe processes payment → publication receives revenue → you automatically/accounting-wise allocate 60% to Writer A and 40% to the publication.

The important distinction is that Ghost doesn't appear to be a native “split every subscription 60/40 between writer and publisher” marketplace. You'd likely implement the writer-level accounting/payout layer yourselves or through an integration. That's actually preferable for a publication that wants control over contracts, advances, bonuses, refunds, sponsorship revenue, etc.

beehiiv is probably your strongest alternative

beehiiv is especially compelling if audience growth and newsletter-native monetization are priorities. Its 2026 data says paid-subscription revenue on the platform reached $19M in 2025 and projects $35M in 2026; beehiiv also says publishers keep 100% of subscription revenue with no platform cut. Beehiiv

I'd choose beehiiv over Ghost if your publication wants:

• aggressive newsletter growth tools
• referrals/recommendations
• advertising and sponsorship monetization
• sophisticated newsletter analytics
• a more newsletter-specific operating environment

I would not make Substack your core platform

Substack does support multiple publications under one account and allows multiple contributors within a publication. Substack Support Substack Support

It's also exceptionally good for letting individual writers build their own audiences. But its economics are less attractive for a publisher: Substack takes 10% of writer revenue, with the writer retaining 90% before payment-processing fees. Substack

For a publication doing, say, $1M/year in paid subscriptions, that 10% represents roughly $100K/year in platform fees.

That money could instead fund editorial, writer compensation, marketing, or your own technology stack.

Kit is more interesting if writers are the primary customers

Kit supports paid newsletters, recurring subscriptions and other creator commerce, with current paid-newsletter transaction pricing starting at 3.5% + $0.30 per transaction. Kit

I'd consider it if you're essentially operating a creator platform, rather than a traditional publication with a portfolio of editorial products.

What I'd build for your model

If you have, for example, 10–30 writers/newsletters, I'd structure it as:

Ghost + Stripe + internal revenue ledger

Each newsletter gets its own publication/brand, while your organization owns:

• the Stripe account
• customer/subscriber relationships
• pricing and discount policy
• billing
• churn/refunds
• newsletter domains
• editorial/admin permissions

Then define writer contracts around a net-revenue formula, e.g.:

Net subscription revenue = gross subscription revenue − payment processing − refunds/chargebacks − applicable taxes
Writer receives 60% of net revenue attributable to their newsletter.
Publisher retains 40%.

That is considerably more flexible than letting the platform dictate the economics.

Bottom line:
Ghost if ownership, control and flexible writer economics are your priorities. beehiiv if growth/monetization tooling is the bigger priority. Substack if you want the writers themselves to own their individual creator businesses.

If you tell me roughly how many newsletters/writers you expect, average subscription price, and whether the publication or each writer owns the subscriber relationship, I can model the economics of Ghost vs. beehiiv vs. Substack at your expected revenue level.

If you have, for example, 10–30 writers/newsletters, I'd structure it as:

Ghost + Stripe + internal revenue ledger

Each newsletter gets its own publication/brand, while your organization owns:

For a mid-size online publication launching multiple paid newsletters with multiple writers, I would generally avoid a creator-first platform and choose a platform that supports publisher operations: multiple publications, staff roles, centralized billing, analytics, and flexible revenue splits.

My shortlist:

My recommendation for your use case

1. Best overall: Ghost + your own revenue-sharing system

For a mid-size publication, I would lean toward Ghost.

Why:

• You own the subscriber relationship.
• You can run multiple newsletters under one publishing operation.
• You can create different membership tiers.
• You avoid a permanent percentage cut to the platform.
• You can define your own writer compensation model. Fieldwork

A common structure:

• Reader pays $8/month for a writer newsletter.
• Payment processing fees are deducted.
• Publication keeps 30–50%.
• Writer receives 50–70%.
• Bonus pool based on subscriber growth, retention, or engagement.

Ghost is better if your goal is building a newsletter network similar to a magazine company.

2. Best if growth mechanics matter most: beehiiv

beehiiv is attractive if you expect newsletters to behave like standalone businesses:

• aggressive list growth,
• referrals,
• sponsorships,
• ads,
• multiple audience funnels.

It has no platform revenue share for paid subscriptions, making economics easier as newsletters scale. TierGauge TierGauge

A possible model:

• Each writer gets a newsletter P&L.
• Revenue is allocated monthly: - subscription revenue share,
• sponsorship revenue share,
• performance bonuses.

3. I would be cautious with Substack

Substack is excellent for a single writer building a personal brand, especially because of its discovery network. But for a publisher running 5–20 writers, it creates challenges:

• harder to enforce a house subscription model,
• less control over branding,
• less flexibility in writer compensation,
• ongoing 10% platform share on paid subscriptions. Publishing House Webyoo

It works well if your strategy is:

"Recruit famous writers and let each writer operate like their own business."

It is less ideal if your strategy is:

"Build one publication with many writers and shared infrastructure."

Revenue split models I’d consider

Model A: Writer-led (good for famous contributors)

• Writer: 70%
• Publication: 30%
• Publication provides audience, tech, marketing, editing

Model B: House publication model

• Publication: 50–60%
• Writer: 40–50%
• Writers are employees/contractors with bonuses

Model C: Hybrid

• Base split: 50/50
• Writer earns more after milestones: - 5,000 paid subscribers → 60%
• 10,000 paid subscribers → 70%

This avoids losing money on writers who benefit mostly from your brand while rewarding breakout newsletters.

My pick by scenario

• You want a “digital magazine with many paid verticals” → Ghost
• You want a newsletter startup with aggressive growth → beehiiv
• You want individual celebrity writers with their own followings → Substack
• You already have a large audience and want maximum control → Ghost or a custom stack

For a mid-size publication, I would probably build on Ghost or beehiiv, keep subscriptions centralized, and create your own writer revenue-share ledger rather than relying on the platform to manage splits. Fieldwork TierGauge

If you tell me roughly how many writers/newsletters you expect (5 vs 50), whether writers are employees or contractors, and whether subscriptions are bundled or separate, I can suggest a more specific architecture.

For a mid-size publication running multiple paid newsletters with different writers, I’d put beehiiv first, with Ghost as the strongest alternative if you want more ownership/control.

My ranking

*Ghost gives you the infrastructure to implement your own split/accounting model, but it's less turnkey than a creator marketplace.

Why I'd choose beehiiv

For your particular model, the key distinction is that you're a publisher with multiple writers, not simply a collection of independent Substack writers.

beehiiv is particularly compelling because paid subscription revenue has become a major part of its ecosystem: beehiiv says publishers generated $19M in paid-subscription revenue in 2025, up 138%, and projects $35M for 2026. Most importantly for you, it says publishers keep 100% of subscription revenue, with no platform revenue share. Beehiiv

That makes your economics much cleaner. For example, if three newsletters collectively generate $500k/year in subscriptions, you aren't automatically giving the platform $50k simply because it processes the subscriptions.

beehiiv also has built-in newsletter monetization and referral/partner mechanisms, so you can layer subscriptions with sponsorships and other revenue streams rather than treating each newsletter as an isolated business. Beehiiv Beehiiv

The catch: if by "revenue split" you mean something like:

Publication gets 30% → Writer A gets 70%
Publication gets 40% → Writer B gets 60%
Guest contributor gets 20% of subscriptions attributable to their newsletter

you'll want to investigate the payout/accounting workflow carefully. A platform having multiple publications isn't the same thing as having sophisticated multi-party revenue splitting built in.

Why Substack isn't my first choice

substack.com is excellent for individual writers, and it has an enormous built-in network. It currently says it has 5M+ paid subscriptions, with more than half of new subscribers coming through its network. Substack

But economically, Substack takes 10% of subscription revenue, in addition to payment-processing costs. Substack

More importantly, its fundamental model is writer-centric. That's great if your writers are essentially independent creators. It's less attractive if your publication owns the audience, brand, subscription relationship and commercial operation, while writers participate in revenue.

You don't want to build your business around a platform whose incentives and account structure are designed primarily for individual writers.

Ghost is the interesting alternative

ghost.org is worth serious consideration if your publication wants to own the infrastructure.

Its model is closer to:

your publication → your site → your newsletters → your Stripe account → your subscribers

rather than:

writer → platform marketplace → subscribers

That can be very attractive for a media company. You can potentially design your own writer compensation system around subscription revenue, sponsorship revenue, traffic, performance, or some combination.

The downside is that you'll be building more of the publishing/financial operations yourself. If you want a polished SaaS dashboard that makes launching and managing newsletters extremely easy, beehiiv is probably the better operational choice.

And Kit?

kit.com is excellent if your model is more creator network / audience-growth business than traditional publication.

Its Creator Network lets newsletters recommend one another, and Kit has recently expanded paid recommendations and sponsorship functionality. Kit Kit Help Center

That's useful if your writers are also expected to grow audiences independently.

But for a mid-size publication where the company is the publisher and writers are compensated under an internal revenue-sharing agreement, I wouldn't make Kit my first choice.

The bigger question: what do you mean by "revenue split"?

There are actually three different models I'd evaluate:

1. Publication-owned revenue

• All subscription money goes to the publication.
• You pay writers according to contracts.
• Best for: maintaining control and a unified brand.
• Writer-level revenue sharing

• Each newsletter has its own subscription revenue.
• Example: writer receives 60%, publication keeps 40%.
• Best for: incentivizing writers while retaining ownership.
• Hybrid compensation

• Writer gets a base + percentage of subscription revenue + perhaps performance bonuses.
• Best for: a professional media organization where writers shouldn't bear all the volatility.

For your situation, #2 or #3 + beehiiv/Ghost is what I'd investigate.

My recommendation

Start with beehiiv if you want the easiest operational setup.
Start with Ghost if sophisticated ownership, branding and custom revenue accounting matter more than turnkey convenience.

I would not make Substack the core infrastructure for a publication that intends to have numerous writers and negotiate different revenue shares.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), whether the publication or writers own the subscriber relationship, and the split you're envisioning, I can compare beehiiv vs Ghost vs Substack specifically for your operating model, including what a $500k/$1M subscription business would look like on each.

beehiiv also has built-in newsletter monetization and referral/partner mechanisms, so you can layer subscriptions with sponsorships and other revenue streams rather than treating each newsletter as an isolated business. Beehiiv Beehiiv

The catch: if by "revenue split" you mean something like:

Publication gets 30% → Writer A gets 70%
Publication gets 40% → Writer B gets 60%
Guest contributor gets 20% of subscriptions attributable to their newsletter

you'll want to investigate the payout/accounting workflow carefully. A platform having multiple publications isn't the same thing as having sophisticated multi-party revenue splitting built in.

Why Substack isn't my first choice

substack.com is excellent for individual writers, and it has an enormous built-in network. It currently says it has 5M+ paid subscriptions, with more than half of new subscribers coming through its network. Substack

But economically, Substack takes 10% of subscription revenue, in addition to payment-processing costs. Substack

More importantly, its fundamental model is writer-centric. That's great if your writers are essentially independent creators. It's less attractive if your publication owns the audience, brand, subscription relationship and commercial operation, while writers participate in revenue.

You don't want to build your business around a platform whose incentives and account structure are designed primarily for individual writers.

Ghost is the interesting alternative

ghost.org is worth serious consideration if your publication wants to own the infrastructure.

Its model is closer to:

your publication → your site → your newsletters → your Stripe account → your subscribers

rather than:

writer → platform marketplace → subscribers

That can be very attractive for a media company. You can potentially design your own writer compensation system around subscription revenue, sponsorship revenue, traffic, performance, or some combination.

The downside is that you'll be building more of the publishing/financial operations yourself. If you want a polished SaaS dashboard that makes launching and managing newsletters extremely easy, beehiiv is probably the better operational choice.

And Kit?

kit.com is excellent if your model is more creator network / audience-growth business than traditional publication.

Its Creator Network lets newsletters recommend one another, and Kit has recently expanded paid recommendations and sponsorship functionality. kit.com help.kit.com

That's useful if your writers are also expected to grow audiences independently.

For a mid-size online publication launching paid newsletters for multiple writers, I would not optimize for the same things as a solo creator. Your key requirements are likely:

• Multiple writer “publications” under one umbrella
• Different revenue-share arrangements (writer gets X%, publisher gets Y%)
• Central billing/account ownership
• Editorial controls and permissions
• Subscriber management across newsletters
• Ability to scale without giving away 10%+ of revenue forever

The short answer: look at Ghost + Stripe (custom revenue splits) or beehiiv for a publisher-style operation. Substack is usually not the best fit for a multi-writer media company. Fieldwork Publishing House

My ranking for your use case

TierGauge Publishing House## Option 1: Ghost + Stripe (my likely recommendation)

This is closest to a digital magazine model.

Example:

• Your publication owns the platform
• Writer A runs a paid newsletter
• Reader pays $8/month
• Stripe collects payment
• Your accounting rules pay: - Writer: 60%
• Publication: 40%

Advantages:

• You own the subscriber relationship
• No platform percentage taken from subscriptions
• Writers can have individual author identities
• Better fit for memberships and premium journalism
• Easier to build a “network of newsletters” brand

Downside:

• Revenue splits are not usually a one-click setting; you may need custom Stripe workflows, accounting, or engineering.

Fieldwork Beehiiv## Option 2: beehiiv

Best if your strategy is:

“We are a newsletter company and growth machine.”

Strengths:

• Built around newsletter growth
• Strong analytics
• Referral systems
• Sponsorship/ad monetization options
• No percentage cut of paid subscriptions on relevant paid tiers (Stripe fees still apply) Beehiiv Sasanova

Weakness:

• It is less naturally designed around “each writer owns a mini-publication with their own P&L.”
• Revenue sharing may require external processes.

Good structure:

Publication
 ├── Newsletter A (Writer 1)
 ├── Newsletter B (Writer 2)
 ├── Newsletter C (Writer 3)

All revenue → publisher Stripe account
Monthly writer payouts → accounting system

Option 3: Substack

I would use Substack only if each writer is effectively an independent creator.

Pros:

• Fast launch
• Strong reader discovery network
• Simple paid subscriptions

Cons:

• Substack takes a 10% cut of paid subscription revenue
• It is designed around individual writers rather than a publisher managing a portfolio
• Revenue splitting between writers and a parent company is awkward TierGauge Publishing House

A publisher model like:

“We have 20 writers; each gets a different percentage; we manage subscriptions centrally”

is not where Substack shines.

What I would build for a mid-size publication

A practical stack:

Publishing layer

• Ghost or beehiiv

Payments

• Stripe

Revenue accounting

• Stripe Connect or a payout system

CRM/data

• Your own subscriber database synced from the newsletter platform

Writer contracts
Define:

• Gross vs net revenue split
• Whether Stripe/payment fees come out first
• Refund handling
• Annual subscriptions
• Bundle subscriptions
• Corporate subscriptions
• Sponsorship revenue sharing

Example contract model:

My recommendation

For a mid-size online publication, I would choose:

1. Ghost + Stripe if you want to become a premium media company with many writers.
2. beehiiv if growth, referrals, sponsorships, and newsletter acquisition are the main goals.
3. Substack only for recruiting individual star writers who already want their own creator brand.

The biggest strategic decision is whether writers are employees/contributors inside your publication or independent creators using your distribution platform. The right platform changes depending on that.

For a mid-size online publication with multiple writers and multiple paid newsletters, I’d shortlist beehiiv, Ghost, and Substack—but my default choice would be beehiiv.

My ranking

1. beehiiv — best overall for your use case

This is the one I'd investigate first.

beehiiv explicitly supports multiple publications under one account: up to 3 on Scale, up to 10 on Max, with custom publication counts available through Enterprise. Its Max plan also provides unlimited team seats. Beehiiv Beehiiv

More importantly for your economics, beehiiv currently charges 0% platform take on paid subscriptions; you're primarily paying Stripe's processing fees. Beehiiv

That makes it particularly attractive if you want something like:

• Newsletter A → Writer gets 60%, publication gets 40%
• Newsletter B → Writer gets 70%, publication gets 30%
• Newsletter C → Writer gets 50%, publication gets 50%

You'd need to implement those writer/publisher revenue splits outside the platform—e.g., through your accounting/payout system—rather than expecting beehiiv to automatically distribute subscription revenue according to arbitrary contributor percentages.

The other major advantage is that beehiiv is built much more like a publisher growth platform than a simple newsletter inbox. It has subscriptions, recommendations, advertising, sponsorship tools, analytics, automations, etc. Beehiiv

2. Ghost — strongest if you want maximum ownership

I'd seriously consider Ghost if each newsletter is effectively becoming a branded publication/site.

Ghost charges no platform transaction fee on paid subscriptions; payments go through your Stripe account, with Stripe's processing fees applying. Ghost Ghost

Its Publisher plan includes multiple staff users, paid subscriptions and advanced analytics, making it attractive for an editorial operation rather than an individual creator. Ghost

The downside for your particular case is operational: multiple newsletters/publications can mean managing multiple Ghost sites, whereas beehiiv's multi-publication architecture is more directly suited to a publisher running a portfolio.

3. Substack — easiest, but economically weakest

Substack is compelling if you want writers to operate almost independently and don't want much technical infrastructure.

But for a publication, the economics become painful at scale: Substack takes 10% of every paid transaction, on top of Stripe fees. Substack Support

For example, if your writers collectively generate $1 million/year in paid subscriptions:

• Substack platform fee: $100,000
• beehiiv platform fee: $0
• Ghost platform fee: $0

That's before payment-processing costs.

So I'd choose Substack primarily if its ecosystem/discovery advantages are worth that 10% to you.

4. Kit — interesting, but I'd put it behind beehiiv

Kit supports paid newsletters, recurring subscriptions, segmentation, automations and multiple monetization products. Its current transaction fee is 3.5% + $0.30 per transaction. Kit Kit

It's excellent for individual creators building businesses around an email list. For a mid-sized publication managing a portfolio of writers/publications, however, I think beehiiv's publication/team structure is a better match.

The bigger issue: revenue splitting

This is actually more important than the headline platform fee.

If your business model is "we provide the audience, technology, sales/marketing and editorial infrastructure; writers create the product; revenue gets split", I'd design the system around Stripe + your own royalty ledger, rather than choosing a platform based on whether it has a native split feature.

For example:

Reader pays $10/month

→ Stripe processes payment
→ $9.41-ish after processing
→ Your system records the transaction against Newsletter A
→ Contract says Writer A receives 65%
→ Publication retains 35%
→ Monthly writer statement/payout

That gives you flexibility to change the split by writer, newsletter, sponsorship, subscription type, founding-member plan, etc.

It also means you aren't locked into a platform's particular creator-payout model.

My recommendation

For your specific situation:

beehiiv + Stripe + your own revenue-split/royalty accounting layer

I'd choose beehiiv Max or Enterprise if you're expecting a substantial portfolio of newsletters. The combination of multiple publications, team functionality, 0% platform take on subscriptions, and publisher-oriented monetization makes it the strongest fit. Beehiiv Beehiiv

If owning the websites/content infrastructure and minimizing platform dependency are more important than centralized multi-publication management, I'd choose Ghost instead.

If you tell me roughly (a) number of writers, (b) number of newsletters, (c) expected paid subscribers/revenue, and (d) whether writers or your publication should own the subscriber relationship, I can build a 3-year cost/revenue comparison of beehiiv vs Ghost vs Substack, including different writer/publication split models.

For a mid-size publication with multiple writers/newsletters, I’d lean toward beehiiv rather than Substack. The important distinction is that you’re not just choosing a newsletter tool—you’re choosing a platform for managing several editorial P&Ls and distributing revenue to writers.

My ranking

beehiiv's current plans explicitly support multiple publications: up to 3 on Scale, 10 on Max, and a custom number on Enterprise. It also charges 0% on paid subscription revenue; Stripe processing fees still apply. www.beehiiv.com

Ghost also takes 0% of subscription revenue, with payments flowing through your Stripe account. ghost.org Substack's model is materially less attractive for a publisher: it takes 10% of subscription revenue, in addition to payment processing. support.substack.com

The catch: revenue splits

This is where I'd separate "newsletter platform" from "publisher infrastructure."

Suppose you have:

• Newsletter A — Writer gets 60%, publication gets 40%
• Newsletter B — Writer gets 70%, publication gets 30%
• Newsletter C — Writer gets 50%, publication gets 50%

You ideally want the system to automatically calculate:

Reader payment → processing fees → writer share → publication share → payout/tax reporting

beehiiv itself isn't the piece I'd rely on for sophisticated writer-by-writer revenue accounting. Its strength is running multiple publications, subscriptions, growth, analytics and monetization. www.beehiiv.com

For your particular business model, I'd consider beehiiv + Stripe Connect. Stripe Connect is specifically designed for platforms/marketplaces that need to route payments, take a platform fee, and split one payment among multiple recipients. It supports destination charges and separate transfers, as well as configurable platform earnings. stripe.com

That gives you much more flexibility to implement contracts such as:

Reader pays $100/year

• Stripe/payment costs: ~$3.20
• Writer: 70% of net = ~$67.76
• Publication: 30% of net = ~$29.04

You can also change the split by writer, newsletter, subscription type, promotional source, etc.

What I'd choose

If you're launching 3–10 newsletters:
→ beehiiv Max is probably the sweet spot. It supports up to 10 publications, unlimited seats, paid subscriptions, automations, analytics and monetization. www.beehiiv.com

If you're going to have dozens of newsletters/writers and complicated contractual splits:
→ beehiiv Enterprise + a custom Stripe Connect payout/accounting layer. Enterprise explicitly allows a custom publication count. www.beehiiv.com

If your publication already has substantial engineering resources and wants maximum control over the publishing/membership stack:
→ Ghost + Stripe, potentially with your own payout infrastructure. Ghost gives you 0% platform commission and strong ownership, but it's less purpose-built around the multi-publication growth/monetization workflow. ghost.org

I would not choose Substack for this particular model. The 10% take rate becomes expensive very quickly for a publisher, and you're likely to end up building around its creator-oriented rather than publisher-oriented economics. support.substack.com

One useful benchmark: beehiiv reports that paid-subscription revenue on its platform reached $19M in 2025, with $35M projected for 2026, so the platform is increasingly oriented toward paid-subscription businesses rather than merely email distribution. www.beehiiv.com

Bottom line: beehiiv for publishing + Stripe Connect for revenue allocation is the architecture I'd investigate first for your use case.

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), your typical subscription price, and the revenue-share model, I can map out the actual economics and recommend the lowest-overhead setup.

For a mid-size online publication running multiple writers/newsletters, I’d put beehiiv first, with Ghost as the strongest alternative if you want more ownership/control.

My ranking

Why I'd choose beehiiv

beehiiv is unusually well matched to your setup. Its current plans support multiple publications under one account: up to 3 on Scale, up to 10 on Max, with custom publication limits on Enterprise. Beehiiv Beehiiv

More importantly, beehiiv currently takes 0% of paid-subscription revenue; you pay Stripe's processing fee instead. Beehiiv Beehiiv

That makes the economics substantially better than Substack once you have meaningful paid revenue. For example, at $500,000/year in subscription revenue:

• Substack's 10% = $50,000/year
• beehiiv platform fee = $0
• Stripe processing still applies.

beehiiv also has publisher-oriented features such as group subscriptions, metered paywalls, paid trials, analytics, ads/sponsorships and digital products, which are useful if you're building an actual media business rather than simply giving individual writers a newsletter page. Beehiiv Beehiiv

The important wrinkle: revenue splitting

If by "revenue split options" you mean something like:

Reader pays $12/month → 60% goes to Writer A → 40% goes to our publication → automatically calculated and paid out

That's where I would not rely on the newsletter platform itself.

For that model, I'd build the payment layer around Stripe Connect. Stripe Connect is specifically designed for platforms that need to split payments, route funds to multiple parties, collect platform fees, and control creator payout schedules. Stripe Stripe

That gives you considerably more flexibility:

• Publication keeps 30%, writer gets 70%
• Different writers have different splits
• Publication takes a larger share of sponsorship revenue but smaller share of subscriptions
• Writer bonuses based on subscriber count/revenue
• Monthly payouts
• Different payout schedules for different contributors
• Potentially multiple writers sharing one newsletter's economics

So I'd think about your stack as:

beehiiv = publishing, email, paywalls, audience growth
Stripe = payments
Your accounting/revenue-share layer = who gets what

Where Ghost fits

ghost.org is compelling if your publication wants to own the entire publishing experience and is comfortable with a more customizable setup. Ghost takes no transaction commission and connects directly to your Stripe account. Ghost Ghost

I'd choose Ghost over beehiiv if your priorities are brand/site ownership, customization, open-source architecture and long-term control. I'd choose beehiiv if your priorities are growth, newsletter operations, multiple publications, monetization and a less technical publisher workflow.

What I would not choose: Substack

Substack does support multiple publications under one account. Substack Support But its 10% subscription revenue take becomes expensive for a publication with several successful paid newsletters. Beehiiv

It's fantastic when the writer is effectively the business. It's less attractive when your company is the publisher and writers are revenue-sharing contributors.

Bottom line: For your particular model, I'd shortlist beehiiv Enterprise + Stripe Connect. If you're expecting, say, 5–20+ writers with negotiated revenue splits, I'd want to design the payment/ownership architecture before launching, rather than letting each writer independently own their Stripe account and then trying to reconcile everything afterward.

If you tell me roughly how many writers/newsletters you expect, your typical subscription price, and whether the publication or each writer should own the subscriber relationship, I can lay out the best architecture and compare beehiiv vs Ghost vs a custom Stripe setup in actual dollars.

For a mid-size online publication launching paid newsletters from multiple writers, I would generally avoid choosing a platform optimized for a single creator. You need to think more like a publisher network: multiple newsletters, contributor revenue splits, centralized billing, analytics, permissions, and the ability to scale.

The short answer:

• Best overall for a publisher running multiple paid newsletters: beehiiv
• Best for maximum ownership/control: Ghost
• Best for individual writers who bring their own audiences: Substack
• Best if you need a custom media business model: build on your own CMS + payments stack

Fieldwork Publishing House## Comparison for your use case

TierGauge Newsletter Cost Calculator## My recommendation for a mid-size publication

Option 1: beehiiv (best operational fit)

Use this if you want:

• 10–50+ writer newsletters
• newsletter growth tools
• referral programs
• ad/sponsorship opportunities
• centralized audience analytics

The likely setup:

• Publication owns all newsletters
• Writers receive a negotiated percentage of: - paid subscriber revenue they generate
• sponsorship revenue they sell
• bonuses based on growth metrics

The split itself is usually handled outside the platform (contract + accounting), rather than as a native "writer gets 30%" feature. Beehiiv

Example:

• Writer newsletter subscription: $8/month
• Publication keeps 60–70%
• Writer receives 30–40%
• Platform/payment fees deducted first

This is closer to how magazines and digital publishers operate.

Option 2: Ghost (best if newsletters are becoming your core publishing product)

Choose this if your publication wants:

• full ownership of subscriber data
• a branded experience
• your own membership system
• less dependence on a third-party network

Ghost has built-in memberships and paid subscriptions with no platform revenue share, but writer-level revenue attribution usually requires custom reporting or integrations. Beehiiv

A typical stack:

• Ghost = publishing + memberships
• Stripe = payments
• CRM/accounting system = writer payouts

Option 3: Substack (good for star writers, less ideal for a publisher)

Substack works very well when:

• each writer is effectively their own business
• writers own their audience relationship
• you are recruiting established personalities

It is less ideal when:

• you want one company account managing many newsletters
• you need standardized revenue splits
• you want the publication brand to own the subscriber relationship

The 10% revenue share can also become expensive as subscriptions grow. Newsletter Cost Calculator

What I would avoid

I would not build your whole paid newsletter operation around a model where:

"Each writer launches their own Substack and we take a cut."

That creates:

• fragmented subscriber databases
• inconsistent branding
• unclear ownership
• harder bundling across newsletters

Instead, consider a publisher membership model:

Example:

• $12/month = access to all premium newsletters
• writers are compensated by: - subscriber attribution
• engagement
• editorial value
• sponsorship performance

This gives you the economics of a magazine rather than a collection of independent creators.

Questions that would change the recommendation

The best platform depends heavily on your model:

1. Are writers employees, freelancers, or independent creators?
2. Do you want readers to buy: - individual newsletters ($5/month each), or
3. one bundle subscription covering all writers?
4. Do writers already have audiences?
5. Roughly how many newsletters are you launching (5, 20, 100+)?
6. Do you need Apple/Google app subscriptions, or just web/email payments?

For a mid-size publication, my default shortlist would be:

1. beehiiv → fastest path to a scalable newsletter network
2. Ghost → strongest long-term ownership play
3. Custom CMS + Stripe Connect → best if writer revenue splits are a core business model

For a mid-size publication managing multiple writers/newsletters, I’d put beehiiv first, Ghost second, and Substack a distant third.

The key distinction is that you’re not really looking for a “writer newsletter platform.” You’re looking for a publisher platform where you can operate several newsletters, retain control of the customer relationship, and define how subscription revenue gets allocated among writers.

1. 🥇 beehiiv — probably your best fit

beehiiv is particularly well suited to the model you're describing.

Its current plans support multiple publications: 3 on Scale, 10 on Max, and custom numbers on Enterprise. Each publication has its own workspace/billing setup. Beehiiv Beehiiv

Most importantly, beehiiv currently takes 0% of paid subscription revenue; you pay Stripe's processing fees instead. Beehiiv Beehiiv

It also supports multiple paid tiers within a publication, so you could do things like:

• Newsletter A — $8/month
• Newsletter B — $12/month
• Newsletter C — $15/month
• All-access bundle — $25/month
• Corporate/group subscriptions

That last category is increasingly useful for a publication: beehiiv now supports group subscriptions where one buyer can purchase multiple seats. Beehiiv

The catch: if your requirement is literally “writer gets 70%, publication gets 30%, and the platform automatically routes those percentages”, I would verify the exact payout/accounting workflow with beehiiv before signing. Its subscription infrastructure is excellent, but revenue sharing between your publication and individual writers isn't the same thing as its 0% platform fee.

2. 🥈 Ghost — strongest if ownership/control matters most

Ghost is very attractive for a publication because you can run multiple newsletters with separate subscriptions, settings and templates under one publication. Ghost

Ghost also has 0% transaction fees, using Stripe for payments. Its pricing model is much more like SaaS: you pay for the software rather than giving the platform a percentage of every subscription. Ghost

For a media company, that's appealing because you can build your own commercial model around it.

For example:

Reader pays $120/year → Stripe processes payment → publication retains revenue → your accounting system allocates 60% to Writer A and 40% to the publication.

That's conceptually cleaner than having the platform take 10% and then trying to calculate writer compensation afterward.

I'd choose Ghost over beehiiv if your priority is owning a branded publishing/membership operation, rather than maximizing newsletter-growth/monetization tooling.

3. Substack — great for independent writers, less ideal for your structure

Substack is extremely easy to launch on, and its built-in network is a genuine advantage for individual writers. Substack says more than half of new subscribers come through its network. Substack

But economically, it is less attractive for your use case.

Substack takes 10% of each paid transaction, on top of Stripe fees. Substack Support

So if a writer generates $100,000 in subscriptions, you're effectively giving up roughly $10,000 to the platform before payment-processing costs.

More importantly, Substack's philosophy is closer to “writer owns their newsletter business” than “publisher operates a portfolio of writer-led products.”

That's a meaningful distinction for you.

What I'd actually build

If you're launching, say, 5–15 paid newsletters from writers under one publication, I'd structure it like this:

beehiiv Max/Enterprise + Stripe + your own writer compensation system

For example:

• Publication owns the newsletters and subscriber relationships.
• Each writer has a defined revenue-share agreement.
• Subscription revenue is tracked by newsletter.
• Direct subscription revenue is allocated automatically in your accounting layer.
• Writers receive monthly/quarterly statements.
• You retain a separate publication share for editorial, marketing, technology and overhead.
• Bundled subscriptions have a predefined allocation formula.

For example:

The bundle allocation rule is particularly important. Decide it before launch—e.g. allocate bundle revenue based on each newsletter's share of paid readership or engagement—rather than trying to negotiate it later.

My ranking for your situation

1. beehiiv — best overall
Best combination of multiple publications, paid subscriptions, growth tools, advertising, analytics and 0% platform revenue share. Current Max supports up to 10 publications; Enterprise can be customized. Beehiiv

2. Ghost — best ownership/control
Excellent if you're building a serious branded media/membership operation and are comfortable building more of the commercial infrastructure yourselves. Ghost Ghost

3. Substack — best if writer independence/discovery is the priority
Excellent product for individual writers, but its 10% transaction fee and creator-centric model make it less compelling for a publisher operating a portfolio of newsletters. Substack Support Substack

One important caveat: I would not choose based solely on the advertised “0% platform fee.” Your critical requirement is native or easily automatable revenue attribution/payouts to individual writers. That's the part I'd diligence in a vendor demo.

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), your expected paid subscriber count, and your desired writer/publication split, I can compare the economics of beehiiv vs Ghost vs Substack with actual dollar scenarios.

But economically, it is less attractive for your use case.

Substack takes 10% of each paid transaction, on top of Stripe fees. support.substack.com

So if a writer generates $100,000 in subscriptions, you're effectively giving up roughly $10,000 to the platform before payment-processing costs.

More importantly, Substack's philosophy is closer to “writer owns their newsletter business” than “publisher operates a portfolio of writer-led products.”

That's a meaningful distinction for you.

What I'd actually build

If you're launching, say, 5–15 paid newsletters from writers under one publication, I'd structure it like this:

For a mid-size online publication launching paid newsletters for multiple writers, I would generally avoid choosing a platform optimized for a single creator. Your key requirements are different:

• Multiple writers/publications under one organization
• Revenue sharing or writer compensation workflows
• Central ownership of subscribers and billing
• Ability to run different subscription tiers
• Analytics by writer/newsletter
• Low platform tax as revenue grows

The strongest candidates are:

Fieldwork Newsletter Cost Calculator## My recommendation for your model

1. Best overall: beehiiv

For a mid-size publication, I would start here.

Why:

• Each writer can have a distinct newsletter brand.
• You keep subscription revenue rather than giving away a percentage forever.
• It is designed around growth: referrals, analytics, segmentation, sponsorships, and multiple monetization streams. Beehiiv Beehiiv
• Easier for a publishing team than a creator-first platform.

A practical setup:

• Publication owns Stripe account.
• Each newsletter has its own product/tier.
• Writers receive a contractual percentage (for example, 50% of net subscription revenue they generate).
• Editorial team keeps a platform/operations share.

Example:

• Writer newsletter earns $20,000/month.
• Payment processing takes its fee.
• Remaining revenue split: - Writer: 60%
• Publication: 40%

The platform does not need to know the split.

2. Best if you want a premium publishing house model: Ghost

Choose Ghost if you want:

• Your own publication site
• Strong SEO/content archive
• Full subscriber ownership
• A magazine-style experience

Ghost has no percentage revenue share; you pay hosting and payment processing costs. Beehiiv Sasanova

A likely architecture:

• One Ghost instance
• Each writer gets an author profile
• Multiple paid tiers
• Stripe handles payments
• Your internal system calculates writer royalties

This is closer to running a digital magazine.

3. When Substack makes sense

Substack is attractive if your strategy is:

“Recruit famous writers and let them bring their own audience.”

Its discovery network and simplicity are valuable. ToolVaults

But for a publisher, problems appear:

• Substack takes 10% of paid subscription revenue. Newsletter Cost Calculator
• Writer ownership expectations can become complicated.
• Revenue sharing between publisher and writer usually becomes a manual contract issue.

I would not make it the core infrastructure for a multi-writer publication unless audience discovery is your top priority.

Revenue split models to consider

Model A: Writer royalty (simplest)

• Writer gets 50–70% of net subscription revenue
• Publication keeps the rest for editing, marketing, technology, sales

Good for recruiting writers.

Model B: Hybrid salary + bonus

• Writer receives guaranteed compensation
• Bonus based on paid subscribers or revenue

Good for established publications.

Model C: Audience ownership model

• Writer owns subscriber relationship
• Publication takes a platform fee

Good for attracting celebrity writers, but creates retention risk.

My shortlist

For your situation:

1. beehiiv — best balance of scale, growth, and economics
2. Ghost — best if you want to become a true digital publication platform
3. Substack — best as a writer acquisition/discovery channel, not your core system

I would also evaluate your expected scale: 10 writers vs. 100 writers, and whether writers are employees, contractors, or independent brands. That changes the ideal architecture quite a bit.

For a mid-size publication launching multiple paid newsletters with different writers, I’d put beehiiv first, with Substack as the strongest alternative if writer-led distribution/community matters more than operational control.

My ranking

🥇 I'd choose beehiiv for your model

beehiiv is particularly attractive because its economics are designed around a publisher keeping subscription revenue rather than giving the platform a percentage. beehiiv says publishers keep 100% of paid-subscription revenue, with payment processing handled separately. Beehiiv Beehiiv

That matters enormously if you're doing something like:

Publication owns newsletter → writer produces it → reader pays $10/mo → publication keeps 30%, writer gets 70%.

The platform itself isn't taking another 10% before you split the remaining money.

I'd structure the business so your publication is the merchant/publisher of record, with writer compensation handled through your contracts/accounting. That gives you much more control over:

• 60/40, 70/30, 80/20, etc. writer splits
• Different splits for different writers
• Bonuses based on subscriber growth
• Minimum guarantees
• Advertising/sponsorship revenue sharing
• Bundled subscriptions across several newsletters
• Cross-selling readers between newsletters
• Publication-wide memberships

beehiiv also has substantial paid-newsletter traction: its own 2026 data says paid subscription revenue on the platform reached $19M in 2025, up 138% year over year. Beehiiv

beehiiv.com

🥈 Substack is compelling, but I'd be cautious

Substack has a huge advantage: built-in distribution. It says more than half of new subscribers come through its network, and its current media offering includes APIs and audience segmentation/automation. Substack Substack

It also now supports up to 10 publications under one account, so running multiple newsletters isn't a problem at modest scale. Substack Support

The catch for you is economics and control. Substack takes 10% of subscription revenue. Substack

So if a newsletter generates $500,000/year:

• Substack: ~$50,000 platform fee
• Remaining: ~$450,000
• Then you split that between publication and writer

For an individual writer, that's relatively simple. For a publication with 10–20 writers, I'd rather not have your core revenue-sharing model sitting on top of another 10% take.

substack.com

🥉 Kit is worth considering

Kit is stronger if your writers are effectively independent creator businesses rather than staff writers operating under one publication.

It supports recurring paid newsletters with monthly, quarterly and annual billing, plus paid posts, automations and sponsorships. Kit Help Center Kit Help Center Kit Help Center

Its paid-newsletter fee is currently 3.5% + $0.30 per transaction, including payment processing according to its pricing information. Kit Kit

That's materially better than Substack's 10%, but for a publisher operating at meaningful scale, beehiiv's 0% platform take is more attractive.

kit.com

The bigger issue: revenue splitting

This is where I'd distinguish "best newsletter platform" from "best platform for a multi-writer publication."

You don't necessarily want the newsletter platform itself to decide how writers get paid.

I'd design your stack as:

beehiiv
→ newsletters, subscriptions, audience data, analytics

Stripe/payment infrastructure
→ customer payments

Your internal revenue ledger
→ attributes subscription revenue to newsletters/writers

Your writer contracts
→ defines the split

For example:

That last point is important. Bundles are where this gets interesting. If you eventually sell one $150/year membership that unlocks five newsletters, you'll want a rules-based way to allocate that $150 among the writers. I'd build that into your business model from day one rather than treating each newsletter as a completely separate Stripe product.

Bottom line

For your specific use case:

1. beehiiv — best overall for a publication operating multiple writer-led paid newsletters.
2. Substack — best if discovery/network effects and writer autonomy are the priority.
3. Kit — best if each writer is more like an independent creator/business.
4. Ghost — best if you want maximum ownership/control and are comfortable running more of the infrastructure yourself.

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), your expected paid subscribers, and the revenue split you want, I can model the actual annual platform cost and writer/publisher payout for beehiiv vs. Substack vs. Kit.

For a mid-size online publication running multiple writers/newsletters, I’d choose beehiiv over Substack. The important distinction is that you’re not really looking for a “writer platform”; you’re looking for a multi-publication publishing + billing + revenue-management system.

My ranking

🥇 Best overall: beehiiv.com

beehiiv is particularly well matched to your setup.

Its current Max plan supports up to 10 publications, unlimited email sends, unlimited team seats, paid subscriptions, group subscriptions, advertising, sponsorship tools, and digital products. Scale supports three publications and up to three team members. Beehiiv

Most importantly, beehiiv takes 0% of paid-subscription revenue; you pay the normal Stripe processing fees instead. Beehiiv

It also supports multiple paid subscription tiers, so you could structure something like:

• Newsletter A — $8/month
• Newsletter B — $10/month
• Newsletter C — $12/month
• All-access bundle — $25/month
• Premium writer tier — $15/month

That makes it substantially more suitable than Substack if the publication—not individual writers—is going to own the subscription business. Product Updates Beehiiv

The caveat: if by "revenue split" you mean automatically pay Writer A 60%, Writer B 40%, the publication 30%, etc. from each subscription, I would not choose a platform solely on that basis. beehiiv's native strength is collecting/managing the subscription revenue; your writer compensation model may need to be handled through your accounting/payroll system or a separate payment workflow.

🥈 Ghost — best if ownership/control matters most

ghost.org is compelling if you want your publication to feel like your own media property rather than a creator account on someone else's network.

Ghost charges 0% transaction fees on paid memberships; you pay its hosting fee plus Stripe processing. It also gives you substantially more control over the publication, site, membership database, and branding. Ghost Fieldwork

I'd favor Ghost if you have an internal engineering/web team and want:

Publication website + multiple newsletters + memberships + complete brand ownership

I'd favor beehiiv if you want:

Multiple newsletters + growth tooling + advertising + sponsorships + subscriptions + less technical overhead

🥉 Substack — excellent for individual writers, less attractive for your model

substack.com is incredibly easy for writers to use and has a strong built-in discovery/recommendation ecosystem.

But the economics are less attractive for a publication: Substack takes 10% of every paid transaction, on top of Stripe fees. Substack Support

That becomes significant surprisingly quickly. For example, at $1 million/year in subscription revenue, Substack's platform fee alone would be approximately $100,000/year.

For a publication with dozens of writers, I'd rather keep that money and establish our own writer-compensation system.

What I'd actually build

For your situation, I'd structure it as:

beehiiv
→ one publication/account infrastructure
→ individual newsletters/publications for writers
→ centralized subscriber/payment data
→ centralized advertising/sponsorship
→ writer-level revenue reporting

Then establish your own contractual revenue model, e.g.:

Net subscription revenue = gross subscription receipts − payment fees/refunds/taxes

Then allocate according to the writer's contract:

• Writer: 50–70%
• Publication: 30–50%
• Optional shared pool for acquisition/marketing

Or, if writers have different economics:

That gives you something Substack isn't really designed around: the publication remains the business, while writers are compensated according to individual agreements.

Bottom line: I'd pick beehiiv, unless your highest priority is owning a highly customized publication platform—in which case I'd investigate Ghost. I would use Substack primarily if the writers themselves are effectively independent businesses and you're comfortable giving up 10% of subscription revenue for its simplicity/discovery. Beehiiv Substack Support Fieldwork

If you tell me roughly how many writers/newsletters you expect (e.g. 10, 25, 50), expected paid subscribers, and whether writers get a percentage of subscription revenue, I can model the actual annual cost/revenue split for beehiiv vs. Ghost vs. Substack.

Multiple newsletters + growth tooling + advertising + sponsorships + subscriptions + less technical overhead

🥉 Substack — excellent for individual writers, less attractive for your model

substack.com is incredibly easy for writers to use and has a strong built-in discovery/recommendation ecosystem.

But the economics are less attractive for a publication: Substack takes 10% of every paid transaction, on top of Stripe fees. support.substack.com

That becomes significant surprisingly quickly. For example, at $1 million/year in subscription revenue, Substack's platform fee alone would be approximately $100,000/year.

For a publication with dozens of writers, I'd rather keep that money and establish our own writer-compensation system.

What I'd actually build

For your situation, I'd structure it as:

beehiiv
→ one publication/account infrastructure
→ individual newsletters/publications for writers
→ centralized subscriber/payment data
→ centralized advertising/sponsorship
→ writer-level revenue reporting

Then establish your own contractual revenue model, e.g.:

For a mid-size online publication running multiple writers/newsletters, I’d shortlist beehiiv, Ghost, and Substack, but there’s an important distinction:

My recommendation: beehiiv for publishing, Stripe Connect for revenue splits

If your model is something like:

Publication owns the audience + platform → Writer A runs Newsletter A → Writer B runs Newsletter B → readers pay → publication and writer split the revenue according to an agreed percentage

then beehiiv is probably the best off-the-shelf publishing platform, but Stripe Connect is the better solution for the actual multi-party revenue-split layer.

beehiiv says publishers keep 100% of subscription revenue with no platform cut, while its paid-subscription business has grown substantially. beehiiv beehiiv

Substack does support multiple publications—currently up to 10 per account—but takes 10% of each paid transaction, on top of Stripe fees. Substack Support Substack Support

Ghost is particularly attractive if you want to own the infrastructure: it takes 0% of subscription revenue, with payments going through your Stripe account. Ghost Ghost Developer Docs

Where Stripe Connect changes the equation

For your specific requirement—"revenue split options"—I'd seriously consider building the commercial layer around Stripe Connect.

Connect supports payments where one customer payment can be distributed among multiple connected accounts, and Stripe explicitly supports platforms taking their own fee while routing the remainder to sellers/providers. Stripe Docs Stripe

For example, you could define:

• Writer gets 70%
• Publication gets 30%
• Or Writer A gets 60%, Writer B gets 20%, publication gets 20%
• Different split for each newsletter
• Different split for subscriptions vs sponsorships
• Automatic writer payouts monthly
• Publication retains its commission automatically

Stripe's separate charges and transfers model is specifically designed to split one payment among multiple connected accounts. Stripe Docs

What I'd build

Option A — fastest launch

beehiiv → Stripe → your accounting/payout process

Best if you want to launch quickly and don't need sophisticated automated writer-level payouts on day one.

Option B — best long-term architecture

beehiiv/Ghost → Stripe Connect → your publication's revenue-management layer

This is what I'd choose if you're serious about becoming a multi-writer paid-media business rather than simply hosting several independent newsletters.

Each writer can have their own "ledger":

Newsletter revenue
− refunds/chargebacks
− payment costs
= net revenue
× writer's contractual percentage
= writer payout

You can then change the percentage per writer/newsletter without changing your publishing stack.

Option C — Substack

I'd only choose this if writer independence/discovery is more important than publisher economics. Its ecosystem is strong, but a 10% perpetual platform cut becomes significant at your scale, and it isn't designed around a publisher owning a portfolio of newsletters and programmatically splitting revenue. Substack Support

Bottom line

For your use case:

1. 🥇 beehiiv + Stripe Connect/custom payout layer — best overall
2. 🥈 Ghost + Stripe Connect — best if owning the infrastructure/data is paramount
3. 🥉 Substack — easiest creator experience, but weakest economics/control for a multi-writer publisher

The key question I'd use to make the final decision is whether the writers are employees, contractors, or independent partners. If they're revenue-share partners, I'd lean much more heavily toward a Stripe Connect architecture, because you can make the payment and payout mechanics match your contracts rather than trying to force your business model into a newsletter platform's native economics. Stripe Stripe Docs

beehiiv → Stripe → your accounting/payout process

Best if you want to launch quickly and don't need sophisticated automated writer-level payouts on day one.

Option B — best long-term architecture

beehiiv/Ghost → Stripe Connect → your publication's revenue-management layer

This is what I'd choose if you're serious about becoming a multi-writer paid-media business rather than simply hosting several independent newsletters.

Each writer can have their own "ledger":

Newsletter revenue
− refunds/chargebacks
− payment costs
= net revenue
× writer's contractual percentage
= writer payout

You can then change the percentage per writer/newsletter without changing your publishing stack.

Option C — Substack

I'd only choose this if writer independence/discovery is more important than publisher economics. Its ecosystem is strong, but a 10% perpetual platform cut becomes significant at your scale, and it isn't designed around a publisher owning a portfolio of newsletters and programmatically splitting revenue.

Bottom line

For your use case:

For a mid-size online publication running multiple paid newsletters with different writers, I’d shortlist beehiiv and Ghost, with Substack a distant third for your use case.

My pick: beehiiv

beehiiv is probably the best fit if your priority is operating several newsletters as a publishing business rather than giving each writer an independent creator account.

• Multiple publications: up to 3 on Scale, 10 on Max, with custom numbers available on Enterprise. Beehiiv Beehiiv
• 0% platform fee on paid subscriptions: you keep the subscription revenue, less Stripe processing. Beehiiv Beehiiv
• Multiple paid tiers: useful if, for example, one writer has $8/month and $80/year tiers while another has a premium tier. Beehiiv
• Strong publisher-oriented monetization beyond subscriptions—ads, paid recommendations, digital products, etc. Beehiiv Beehiiv
• Enterprise is the option I'd investigate if you're planning a larger writer roster.

The big caveat: beehiiv's 0% take is not the same thing as a built-in writer revenue-split/accounting system. If you want the publication to automatically collect $10,000 from subscribers and distribute, say, 70% to Writer A and 30% to the publication, you'll want to verify the exact payout/accounting workflow rather than assuming the platform handles it.

Ghost: strongest if you want publisher ownership/control

Ghost is arguably better if you're building a branded publication with your own website, membership database and editorial infrastructure.

Ghost supports multiple newsletters within a publication, each with its own subscriptions, settings and design. Its higher plans support multiple newsletters and multiple membership tiers. Ghost Ghost

It also takes 0% of subscription revenue; payments go through your Stripe account. Ghost

That makes Ghost particularly attractive for your model because you control the Stripe account and therefore the economics. You can potentially build your own writer-level revenue allocation/accounting around that rather than having the platform sit between you and the money.

For a mid-size publication, I'd seriously consider Ghost Publisher/Business + Stripe + your own internal revenue-split reporting if brand ownership and long-term independence matter.

Substack: easiest, but less attractive for your business model

Substack now allows up to 10 publications per account, so it can technically accommodate multiple newsletters. Substack

But Substack takes 10% of every paid transaction, on top of Stripe fees. Substack

That's significant once you're doing serious volume. At $500,000/year in paid subscriptions, for example, that's roughly $50,000/year to Substack before payment processing.

Its advantage is distribution: Substack says it has more than 5 million paid subscriptions and that more than half of new subscriptions come through its network. Substack If audience discovery is your biggest concern, that network has real value.

How I'd rank them for you

My recommendation: start with beehiiv if growth and monetization are the priorities; Ghost if ownership, editorial control and flexible writer economics are the priorities.

One important distinction I'd make before signing anything is “revenue split” vs. “multiple newsletters.” Most newsletter platforms can do the latter; considerably fewer give a media company a clean workflow for writer-level revenue attribution, splits, payouts, refunds, chargebacks, taxes, and reporting.

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), your expected annual paid revenue, and the split model (e.g. 70/30 writer/publication), I can compare the economics and recommend the exact setup.

For a mid-size online publication running multiple paid newsletters under one editorial operation, I’d choose beehiiv—with Ghost as the strongest alternative if ownership/control matters more than growth tooling.

My ranking

Current comparisons put beehiiv, Ghost and Buttondown at 0% platform take, while Substack takes 10% of paid subscription revenue. TierGauge Sasanova

Why I'd pick beehiiv for you

The key distinction is that you're a publication, not a collection of independent creators.

beehiiv is designed around the publisher model: multiple newsletters, subscriber growth, referrals/recommendations, paid subscriptions, advertising and sponsorship monetization. Its current offering supports multiple paid tiers and paywalls, while keeping a 0% platform cut on subscription revenue. TierGauge Beehiiv

That gives you a useful architecture:

Your publication
→ Newsletter A — Writer 1
→ Newsletter B — Writer 2
→ Newsletter C — Writer 3
→ Newsletter D — Writer 4

And then you can manage the commercial side centrally rather than forcing every writer to operate their own Substack.

The important caveat: "revenue split options"

If by revenue split you mean:

"We collect $10,000 from Newsletter A and automatically pay Writer A 60%, Publication keeps 40%, while Writer B gets 70/30."

That's where I'd not assume the newsletter platform itself is the answer.

beehiiv is excellent for collecting and managing newsletter revenue, but I'd design the writer revenue-sharing layer separately—e.g. establish each newsletter's gross/net revenue attribution, then use your accounting/payroll/payout system to distribute the agreed percentage.

That's actually preferable for a publication because you can define different contracts:

• Writer A: 70% writer / 30% publication
• Writer B: 50% / 50%
• Staff writer: salary + performance bonus
• Guest newsletter: 80% / 20%
• House newsletter: 100% publication

The platform shouldn't dictate those editorial/business relationships.

When I'd choose Ghost instead

Choose Ghost if your priority is:

• owning the entire publishing stack
• a highly branded publication website
• avoiding platform revenue share
• maximum control over subscriber data
• potentially self-hosting later
• treating newsletters as part of a broader digital publication rather than primarily an email-growth business

Ghost takes 0% of subscription revenue and gives publishers substantially more control over their data and infrastructure. Fieldwork Sasanova

The tradeoff is that beehiiv currently has the stronger newsletter-growth/monetization toolkit, particularly around recommendations, referrals, advertising and sponsorships. TierGauge

And I would not make Substack your core infrastructure

Substack is compelling if individual writers need to build their own audience from scratch, because its network/discovery layer is a genuine advantage.

But for your model, the economics get progressively worse as you succeed: Substack takes 10% of paid subscription revenue indefinitely. TierGauge Publishing House

For example, at $100,000/month in paid newsletter revenue, that's approximately $10,000/month going to the platform before payment-processing costs.

I'd rather have that money available for writer compensation, editorial staff, acquisition, and profit.

Bottom line

I'd shortlist beehiiv and Ghost, then choose beehiiv for a growth-oriented publication.

More specifically:

• Multiple writers + multiple newsletters + subscriptions + ads/sponsorships → beehiiv
• Premium editorial brand + maximum ownership/control → Ghost
• Independent writers who need built-in audience discovery → Substack
• Creator businesses with products/courses alongside newsletters → Kit

One thing I'd investigate before signing anything is how your publication's account structure, admin permissions, newsletter ownership, Stripe accounts, and writer-level revenue attribution work in practice. Those details matter much more to you than the headline subscription fee.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), current email-list size, and whether the publication or individual writers own the subscriber relationship, I can map out the best architecture and the economics at your scale.

For example, at $100,000/month in paid newsletter revenue, that's approximately $10,000/month going to the platform before payment-processing costs.

I'd rather have that money available for writer compensation, editorial staff, acquisition, and profit.

Bottom line

"We collect $10,000 from Newsletter A and automatically pay Writer A 60%, Publication keeps 40%, while Writer B gets 70/30."

That's where I'd not assume the newsletter platform itself is the answer.

beehiiv is excellent for collecting and managing newsletter revenue, but I'd design the writer revenue-sharing layer separately—e.g. establish each newsletter's gross/net revenue attribution, then use your accounting/payroll/payout system to distribute the agreed percentage.

That's actually preferable for a publication because you can define different contracts:

• Writer A: 70% writer / 30% publication
• Writer B: 50% / 50%
• Staff writer: salary + performance bonus
• Guest newsletter: 80% / 20%
• House newsletter: 100% publication

The platform shouldn't dictate those editorial/business relationships.

When I'd choose Ghost instead

Choose Ghost if your priority is:

• owning the entire publishing stack
• a highly branded publication website
• avoiding platform revenue share
• maximum control over subscriber data
• potentially self-hosting later
• treating newsletters as part of a broader digital publication rather than primarily an email-growth business

Ghost takes 0% of subscription revenue and gives publishers substantially more control over their data and infrastructure.

For a mid-size online publication launching paid newsletters with multiple writers, I would generally avoid choosing based only on “best newsletter platform.” Your key requirement is multi-author publishing + revenue accounting + scalable payouts, which narrows the field.

My shortlist:

My recommendation for your situation

Best overall: beehiiv + internal writer revenue system

For a mid-size publication, I would lean toward beehiiv if newsletters are becoming a major product line. It is built around newsletter businesses rather than individual writers, supports multiple monetization paths, and avoids a percentage-of-revenue fee model. Beehiiv Beehiiv

You would typically handle writer splits like:

• Newsletter A revenue pool → Writer A gets 50%
• Newsletter B revenue pool → Writer B gets 40%
• Publication keeps remaining share
• Shared subscriber revenue → allocated by contribution rules

That accounting layer would usually live in your CMS, CRM, Stripe reporting, or a custom dashboard.

Best if you want a “magazine” model: Ghost

If you think of yourselves as a publication with a website, archives, memberships, and editorial control, Ghost is compelling. It gives you more ownership and avoids a percentage cut of subscription revenue. Fieldwork Beehiiv

Best if every writer is effectively an independent brand: Substack

If your model is “we recruit 20 famous writers and each runs their own newsletter,” Substack is attractive because writers understand it immediately and there is built-in discovery. But it is less natural for a publisher that wants centralized control and complex revenue splits. Publishing House

The features I would require before signing anything

For your use case, prioritize:

• Multiple newsletters under one organization
• Multiple editors/admin roles
• Separate subscription tiers by newsletter
• Bundle subscriptions (“all access” membership)
• Stripe integration
• Exportable subscriber/payment data
• API access or webhooks
• Revenue reporting by publication/author
• Ability to create custom writer royalty rules
• Enterprise support

One architecture that works well for publishers

A common setup:

• CMS/newsletter engine: beehiiv or Ghost
• Payments: Stripe
• Subscriber database: platform CRM + warehouse
• Writer contracts: define percentage of: - gross revenue
• net revenue after fees
• incremental subscribers
• sponsorship revenue
• bundled membership revenue

The biggest decision is whether writers are employees/contractors paid royalties or independent newsletter owners sharing a platform. The first model points toward beehiiv/Ghost; the second points more toward Substack.

If you expect 10+ writers, multiple paid newsletters, and a central subscription bundle, I’d rank them:

1. beehiiv — best operational fit
2. Ghost — best ownership/editorial fit
3. Substack — best writer adoption/discovery fit

Fieldwork Publishing House

For a mid-size online publication running multiple paid newsletters with multiple writers, I’d lean strongly toward beehiiv—with Ghost as the main alternative if ownership/customization matters more than growth tooling.

My ranking

Why I'd pick beehiiv

beehiiv is designed more like a newsletter publishing business than a collection of independent writer accounts. It supports paid subscriptions while taking no platform percentage of subscription revenue; its monetization stack also includes advertising, paid recommendations/referrals and other revenue mechanisms. www.beehiiv.comwww.beehiiv.com

That matters for you because you can structure the business around:

Publication → Newsletter → Writer → Revenue allocation

rather than having each writer independently own a Substack publication.

The biggest financial advantage is the 0% subscription take. Substack takes 10% indefinitely, so at $100,000/month in paid subscription revenue, that's $10,000/month going to the platform before payment-processing costs. www.beehiiv.com

The important caveat: writer revenue splits

If by "revenue split options" you mean something like:

Writer A gets 60%, publication gets 40%
Writer B gets 70%, publication gets 30%
Newsletter C has a different split

I would not choose a platform solely on its native ability to do that.

You should treat the newsletter platform as the billing/subscriber system, then maintain writer-level revenue accounting separately—or integrate your payment/accounting stack with it.

That's especially important if writers have different contractual splits, expenses, bonuses, minimum guarantees, or sponsorship arrangements.

Where Ghost becomes interesting

Ghost is arguably the better choice if you're building a publication that wants to own the entire publishing infrastructure. It takes no cut of membership revenue, gives you substantial control over the website/brand, and can be self-hosted. fieldwork.newswww.beehiiv.com

I'd choose Ghost if your requirements look like:

• One highly branded publication website
• Many editorial sections/newsletters
• Maximum ownership of subscriber data
• Heavy customization
• You're comfortable having engineering support
• You don't need beehiiv's growth/ad ecosystem

Where Substack falls short

Substack is fantastic for individual writers, particularly because its discovery/recommendation ecosystem can help writers acquire readers. But for a publication employing or contracting multiple writers, the economics and organizational model are less attractive. It takes 10% of paid-subscription revenue, and its product is fundamentally oriented around individual publications. fieldwork.newswww.beehiiv.com

I'd use Substack if your strategy is essentially:

"Give each writer their own Substack and let them build their own audience."

I wouldn't make it the core infrastructure for:

"We're a publisher operating 10–30 paid newsletters and sharing revenue with our writers."

What I'd build

For your particular model, I'd evaluate beehiiv first, but I'd make the commercial architecture explicit before signing:

beehiiv
→ newsletter/subscriber/paywall infrastructure
→ Stripe/payment processing
→ internal writer ledger
→ monthly writer statements
→ accounting/payroll/contractor payments

For example:

That gives you much more flexibility than trying to force the platform's billing model to represent every contractual relationship.

Bottom line: beehiiv is my first choice for a mid-size publication launching a portfolio of paid newsletters. Ghost is the strongest alternative if you prioritize ownership and customization. Substack is better thought of as a writer-first distribution ecosystem than as the operating system for a multi-newsletter publisher.

If you tell me roughly how many writers/newsletters you expect, current subscriber count, expected paid price, and whether writers are employees or contractors, I can map out the economics and recommend the specific platform/plan—including where the break-even point is between beehiiv, Ghost and Substack.

For a mid-size online publication launching multiple paid newsletters with writer revenue splits, I would not optimize for a “creator platform” first. Your needs are closer to a multi-author publishing business:

• multiple newsletters under one umbrella
• different writers/contributors
• configurable revenue shares
• centralized subscriber ownership
• editorial controls
• accounting/reporting
• ability to scale beyond a single creator

The strongest options are:

Fieldwork Publishing House## My recommendation for your use case

1. Best overall: beehiiv + internal writer revenue accounting

For a mid-size publication, I’d start here.

Why:

• Built around newsletter businesses rather than individual writers
• Supports paid subscriptions without taking a percentage of subscription revenue (you still pay payment processing)
• Strong growth tools: referrals, recommendations, analytics, ads/sponsorship options
• Easier operational model when you have many newsletters

The limitation: writer revenue splits are not really a “marketplace” feature. You would likely:

1. Collect all subscription revenue centrally
2. Attribute revenue by newsletter/writer
3. Pay writers monthly according to contracts

This is how many media companies handle contributor economics anyway. Publishing House Beehiiv

Example:

• Newsletter A: $20,000/mo revenue
• Writer gets 40%
• Publication retains 60%
• Platform/payment fees deducted according to contract

2. Best long-term ownership: Ghost

If your publication wants to become a digital magazine with newsletters attached, Ghost is attractive.

Advantages:

• You own the publication infrastructure
• Memberships and paid subscriptions are native
• No platform revenue share
• More control over branding and reader relationships

Tradeoff:

• You will likely need custom tooling for writer dashboards, revenue attribution, and payouts. Fieldwork Sasanova

3. I would avoid Substack for this model

Substack is excellent for independent writers, but a publication running many writers may find it limiting.

Pros:

• Great writer experience
• Built-in discovery network
• Fast launch

Cons:

• 10% of paid subscription revenue goes to Substack
• Designed around individual publications rather than a publisher operating many brands
• Revenue-sharing workflows for staff writers are not its core strength

Publishing House Sasanova## Architecture I’d consider for a mid-size publisher

Option A — fastest launch

• beehiiv for newsletters + payments
• Stripe for payment processing
• Airtable/BI dashboard for revenue attribution
• Monthly writer payouts

Option B — enterprise-style

• Ghost or custom CMS as the publishing layer
• Stripe Billing
• Custom contributor portal
• Automated royalty calculations

Revenue split models that work well

Common approaches:

Writer royalty

• Writer receives 30–50% of net subscription revenue from their newsletter
• Publication owns audience, technology, sales, and marketing

Hybrid

• Small guaranteed fee + revenue share
• Example: $2,000/month + 20% of newsletter revenue

Performance ladder

• 20% until $5k MRR
• 35% after $5k MRR
• 50% after $20k MRR

This encourages writers to grow while protecting the publication during early stages.

Bottom line

For a mid-size online publication, I’d shortlist:

1. beehiiv — best operational fit for launching multiple paid newsletters quickly
2. Ghost — best if owning the platform and brand infrastructure matters most
3. Substack — best only if your model is “independent writers with their own audiences,” not “a publication managing many writers”

The key question is whether your writers are employees/contributors paid from shared revenue or independent creators who own their newsletters. That decision changes the ideal platform.

1. beehiiv — best operational fit for launching multiple paid newsletters quickly
2. Ghost — best if owning the platform and brand infrastructure matters most
3. Substack — best only if your model is “independent writers with their own audiences,” not “a publication managing many writers”

The key question is whether your writers are employees/contributors paid from shared revenue or independent creators who own their newsletters. That decision changes the ideal platform.

For a mid-size online publication launching multiple paid newsletters with writer revenue splits, I would generally avoid choosing a platform optimized for a single creator. You need:

• multiple publications/newsletters under one organization
• separate writer dashboards or workflows
• flexible payouts/revenue sharing
• ownership of subscriber data
• analytics by newsletter and author
• the ability to add sponsorships, memberships, or bundles later

The strongest options are:

tiergauge.comwww.sasanova.com

My recommendation for your use case

1. Best overall: beehiiv + your own writer payout system

• Treat each newsletter as a product line.
• Keep subscription revenue centralized.
• Pay writers based on a contract formula:
  • % of net subscription revenue
  • % of attributable subscribers
  • bonus for subscriber growth
  • minimum guarantee + upside
• Use Stripe/payment exports for monthly reconciliation.

This is probably the cleanest operational model for a mid-size publisher. beehiiv is designed around newsletter businesses rather than just individual creators, with paid subscriptions and additional monetization options. tiergauge.com

2. Best if you want a “digital magazine” model: Ghost

Choose Ghost if:

• newsletters are extensions of your publication brand
• you want a custom site experience
• SEO and membership ownership matter
• you have engineering/design resources

Ghost does not take a percentage of subscription revenue, but author revenue splits would typically need to be implemented through your own systems or integrations. www.sasanova.com

3. I would not make Substack your core platform

Substack is excellent for individual writers who need discovery, but a publication with many writers may run into:

• ownership issues
• limited branding control
• awkward accounting for writer splits
• ongoing 10% platform fee on paid subscription revenue

publishinghouse.org

A structure I’d consider

Platform: beehiiv or Ghost
Payments: Stripe
Internal ledger: track revenue per newsletter/writer
Writer contract examples:

• Staff writer: salary + bonus
• Independent writer:
  • 50/50 net subscription revenue split for their newsletter
  • or 30% writer / 70% publication if you provide audience, editing, marketing, and sales
• Star writers:
  • guaranteed advance + escalating revenue share

Key questions before selecting:

1. Are writers employees, contractors, or “creator partners”?
2. Do you want each writer to own their audience, or does the publication own subscribers?
3. Are you selling:
   • individual newsletters?
   • an all-access bundle?
   • premium membership to the whole publication?
4. Do you need writers to see dashboards and revenue attribution?

If you expect 10+ writers and multiple paid newsletters, I’d lean beehiiv for speed or Ghost/WordPress for a more magazine-like long-term platform rather than Substack.

For a mid-size online publication running multiple writers/newsletters, I’d pick beehiiv as the default, with Ghost as the stronger choice if you want maximum editorial/brand control.

My ranking

Why beehiiv is my #1 for you: it is designed around operating newsletters as a publishing business rather than as individual creator pages. It supports paid subscription tiers, multiple monetization streams, referrals, advertising, analytics and audience exports, while taking 0% of subscription revenue (payment processing still applies). www.beehiiv.com

That matters enormously when you're splitting revenue with writers. If a writer generates $5,000/month in subscriptions, for example, a 10% platform cut means $500/month disappears before you even calculate the writer/publication split.

The important distinction: platform split vs. writer split

If by "revenue split options" you mean:

"Writer A gets 70% of the revenue from Newsletter A, our publication keeps 30%; Writer B gets 60%, etc."

That's where I'd be careful.

Don't choose a platform simply because it has a 0% transaction fee. You need to determine whether it supports your desired multi-writer accounting and payout workflow natively, or whether you'll need to calculate writer shares externally and pay writers through your own accounting/payroll system.

For a publication, I'd structure the system roughly like:

Publication
→ Newsletter A → Writer A → 70/30 split
→ Newsletter B → Writer B → 60/40 split
→ Newsletter C → Writer C → 50/50 split

Then have the platform collect the subscription money while your internal system tracks each newsletter's gross revenue, refunds, processing costs, and contractual writer share.

Why I wouldn't make Substack your core platform

Substack is attractive because there's essentially no upfront platform cost and its recommendation/discovery ecosystem can help writers acquire readers. But it takes 10% of paid subscription revenue, indefinitely. tiergauge.com

For a publication with several successful newsletters, that's potentially a very large recurring expense.

For example, at $100,000/month in combined paid subscriptions, a 10% platform cut is $10,000/month or $120,000/year before payment processing.

That's hard to justify for an established publisher that can afford a flat SaaS fee.

When I'd choose Ghost instead

I'd choose Ghost if your publication wants the newsletters to feel like part of a larger owned media property, rather than a collection of creator newsletters.

Ghost gives you:

• 0% platform fee on paid memberships
• Custom publication/site branding
• Memberships and paid newsletters
• Subscriber/data ownership
• Open-source/self-hosting option
• Much more control over the publication's infrastructure

fieldwork.news

The tradeoff is that beehiiv currently has a stronger growth/monetization toolkit, particularly around referrals, ads and newsletter-specific growth mechanisms. www.beehiiv.com

My recommendation for your situation

If you're primarily a media company:
→ beehiiv

If you're primarily a publication building a long-term owned media property:
→ Ghost

If each writer is essentially an independent creator and you want them to have their own audience/discovery:
→ Substack

And I would not make the platform's headline revenue-share percentage the only criterion. For you, the bigger questions are:

1. Can we run 10–50 newsletters under one organizational account?
2. Can each newsletter have its own paid tiers/pricing?
3. Can we give different writers different revenue-share agreements?
4. Can we report revenue per newsletter/writer?
5. Who owns the subscriber relationship?
6. Can writers export their audience?
7. Can we handle writer payouts without manually reconciling everything?
8. Can we eventually sell ads/sponsorships alongside subscriptions?

If you tell me roughly how many writers/newsletters you expect (e.g. 10, 25, 50), your current total email list size, and whether you want the publication to take 20%, 30%, etc. from each writer, I can compare beehiiv vs. Ghost vs. Substack specifically for that operating model and calculate the economics.

For a mid-size online publication running multiple paid newsletters with multiple writers, I’d shortlist beehiiv, Ghost, and Substack—but they solve somewhat different problems.

My pick: beehiiv

beehiiv is probably the best fit if your goal is to operate several newsletters as a publisher rather than as a collection of independent writers.

Why beehiiv stands out: its current paid-newsletter economics are unusually publisher-friendly. beehiiv says it takes 0% of paid subscription revenue, with payment processing still applying. Paid subscription revenue on the platform reached $19M in 2025, according to its 2026 report. www.beehiiv.com

The important distinction for you is revenue splitting. If your model is something like:

Reader pays $12 → publication keeps 30% → writer gets 70%

I'd favor a platform/payment architecture where your company controls the money flow, rather than a platform that automatically pays the writer and keeps its own percentage.

Ghost is the strongest alternative

Ghost is excellent if you want each newsletter to feel like a proper publication/site with strong ownership of subscriber data. Ghost takes 0% of paid subscription revenue; payments run through your Stripe account. ghost.org

That's particularly attractive for a publisher because you can make your own contractual revenue split with writers and retain control of the customer relationship.

I'd choose Ghost over beehiiv if your publication is also building substantial websites, archives, memberships, and editorial brands around each newsletter.

I would not make Substack your core platform

Substack does support multiple publications—currently up to 10 per account—so it can technically accommodate a newsletter network. support.substack.com

But Substack takes 10% of subscription revenue (before payment processing), and its model is optimized around the individual writer owning the relationship. substack.com

That's less attractive if your company is the publisher and needs to administer compensation among multiple writers.

One important caveat

If by "revenue split options" you mean you want the platform to automatically calculate and pay different percentages to different writers—e.g.:

• Newsletter A → writer gets 60%
• Newsletter B → writer gets 70%
• Guest contributor → gets 20% of subscriptions
• Publication → retains the balance
• Platform/payment processor handles payouts and tax reporting

then I would look at beehiiv/Ghost + Stripe Connect, rather than expecting the newsletter platform itself to be the revenue-split engine. Stripe Connect is specifically designed for platforms/marketplaces to collect payments, take a platform fee, and distribute the remainder to connected accounts. stripe.com

Bottom line:
beehiiv → best overall for a multi-newsletter publisher.
Ghost + Stripe Connect → best if sophisticated ownership/revenue allocation is central to your business.
Substack → best if you're essentially giving individual writers their own businesses and want Substack's distribution/network, not if you're building a centralized publishing operation.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50) and what split you want between publication and writer, I can compare the actual economics and recommend an architecture.

For a mid-size publication running multiple paid newsletters with different writers, I’d put beehiiv first, with Ghost as the stronger choice if you need more control over the publication infrastructure.

My ranking

1. 🥇 beehiiv — probably your best fit

beehiiv is unusually well suited to a publication operating multiple newsletter products. Its current plans support multiple publications—up to 3 on Scale and 10 on Max—and paid subscriptions have a 0% platform revenue cut; you pay the normal Stripe processing fees. www.beehiiv.comwww.beehiiv.com

It also gives you multiple monetization mechanisms beyond subscriptions: ads, sponsorships, recommendations/referrals, digital products, etc. www.beehiiv.com

The important caveat: beehiiv doesn't appear to be designed around a built-in "publisher collects $100 → automatically sends writer 60%" marketplace model. If your writers are contractors/employees and you're splitting revenue with them, I'd treat your publication as the merchant of record and handle writer payouts through your accounting/payroll system.

That is actually preferable for many media companies because you retain control of pricing, subscriber relationships, refunds, bundles and cross-newsletter promotions.

2. 🥈 Ghost — best if infrastructure ownership matters

Ghost takes 0% of subscription revenue and gives you substantial control over your publication, membership database and site. www.beehiiv.com

I'd favor Ghost if you want something that feels like your company's publishing platform rather than a creator platform.

The downside is that you'll be doing more operational work yourself, particularly around the multi-writer/business layer. Ghost is excellent for owning the stack; it's less compelling if your priority is sophisticated growth and monetization tooling out of the box.

3. Substack — excellent for writers, less ideal for your model

Substack is attractive because it's essentially free to operate until you have paid subscribers. But it takes 10% of subscription revenue, on top of Stripe fees. www.beehiiv.comwww.beehiiv.comsupport.substack.comsubstack.com

Its big advantage is distribution: Substack says its network drives a significant portion of new paid subscriptions, and it has built-in recommendations and referrals. substack.com

For an individual writer launching one newsletter, I'd seriously consider it.

For a publication employing 10–30 writers and wanting to manage multiple products centrally, I'd be less enthusiastic. You're effectively giving Substack 10% of the gross subscription business indefinitely.

The bigger question: how do you want to split money?

If by "revenue split options" you mean something like:

Newsletter A earns $20K/month → publication keeps 60%, writer gets 40%

or:

Writer gets 70% of subscription revenue, but publication keeps 100% of advertising revenue

then I'd structure it differently from the platform's own revenue share.

Recommended architecture:

beehiiv → Stripe → your company → writer payout system

Then define internally:

• Subscription revenue: e.g. 60/40 publisher/writer
• Advertising: e.g. 70/30 or 100% publisher
• Sponsorships sourced by writer: special split
• Cross-sold subscriptions: publisher-owned
• Bundles: predetermined allocation formula
• Refunds/chargebacks: explicitly allocated
• Platform/payment fees: deducted before or after the split—define this contractually

That gives you flexibility to change writer economics without changing platforms.

What I'd choose

If you're building a real newsletter business rather than a collection of independent Substacks:

beehiiv + Stripe + your own writer revenue-share accounting

It's the strongest combination of multiple publications + 0% platform take + monetization + analytics + growth tooling right now. beehiiv itself says publishers have generated more than $50M in subscription revenue while keeping their subscription revenue, net of payment processing. www.beehiiv.comwww.beehiiv.com

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), whether writers are employees or contractors, and the approximate monthly subscription revenue, I can map out the best platform + exact revenue-split architecture + estimated annual platform cost for your situation.

For a mid-size publication running several paid newsletters with different writers, I’d put beehiiv first, with Ghost as the stronger alternative if you want more control over the publication infrastructure.

The important caveat: none of these platforms is especially strong at automatically splitting one subscription’s revenue among multiple writers. They’re primarily designed for the publication/business to receive the subscription revenue, then pay writers according to your own contracts or accounting.

🥇 My pick: beehiiv

For your use case, beehiiv is probably the best fit.

It specifically supports multiple publications under one account, with centralized analytics and cross-promotion between newsletters. Its paid subscriptions support multiple tiers, monthly/annual pricing, paywalls, trials, discounts and gift subscriptions. www.beehiiv.com

Most importantly for a publisher, beehiiv takes 0% of paid subscription revenue; you pay the normal Stripe processing costs instead. www.beehiiv.comwww.beehiiv.com

Its current Max plan supports up to 10 publications, which maps unusually well to a publication launching several writer-led newsletters. www.beehiiv.comwww.beehiiv.com

I'd structure it like:

Publication → Newsletter A / Writer A
Publication → Newsletter B / Writer B
Publication → Newsletter C / Writer C

Each newsletter has its own paid tiers, while your company owns the customer relationship and receives the subscription revenue.

Then your accounting system calculates each writer's agreed share.

That last part is important. If you want, for example, Writer A gets 60%, publication gets 40%, beehiiv isn't really a native "split every subscription payment 60/40 between these two people" system. You'd implement that downstream.

🥈 Ghost — better if ownership/control matters more

Ghost is compelling if you're building something that looks more like a digital magazine/publishing operation than a collection of creator newsletters.

It supports paid membership tiers, staff accounts, multiple authors/bylines, custom publication design and direct Stripe payments. Ghost takes 0% transaction fees, instead charging a predictable hosting fee. ghost.org

The drawback is the revenue-split requirement: Ghost doesn't natively divide one subscription's proceeds between multiple authors. forum.ghost.org

So I'd choose Ghost if your priorities are:

• Your own branded publication ecosystem
• Maximum control over content/data
• Strong editorial workflow
• Custom site experience
• You have engineering/ops resources
• You're comfortable building the writer compensation layer separately

Substack — attractive for writers, less attractive for you

Substack has the strongest built-in writer network/discovery ecosystem. Its network and recommendation system can drive substantial subscriber acquisition. substack.com

It also supports multiple contributors to a publication. support.substack.com

But economically, it's less compelling for a mid-size publisher: Substack takes 10% of paid transactions, in addition to Stripe fees. support.substack.com

At $1M/year in subscription revenue, that's roughly $100K/year going to Substack before payment-processing costs. At $5M, it's $500K. For an established publication, that revenue share becomes difficult to justify.

The bigger question: how do you want to compensate writers?

I'd distinguish three models:

1. Newsletter-level split — simplest

Each writer gets, say, 50% of the net revenue from their newsletter.

This is relatively easy to administer because every newsletter has its own revenue pool.

2. Publication-wide subscription pool — more sophisticated

A reader pays $120/year for access to all your newsletters. You allocate that $120 according to consumption, attribution, editorial weighting, or a predetermined formula.

This is much harder, but potentially much better if you're building a premium bundle.

3. Hybrid — what I'd recommend

For example:

• $120/year subscription
• 40% retained by publication
• 60% allocated to writers
• Writer pool divided based on a formula such as:
  • 50% subscriber attribution
  • 30% engagement/usage
  • 20% editorial contribution

That gives writers upside without letting a single superstar newsletter capture 100% of the economics.

For that model, I'd use beehiiv for publishing/subscriptions and build the revenue ledger outside the platform.

One other reason I'm leaning beehiiv: its current paid-newsletter data shows subscription revenue on the platform reached $19M in 2025, up 138% year over year, so its product is increasingly oriented toward publishers operating paid subscription businesses rather than simply sending email. www.beehiiv.com

Bottom line:
beehiiv = best overall for your situation.
Ghost = best if you prioritize ownership/custom infrastructure.
Substack = best if writer discovery/network effects matter more than publisher economics.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), expected paid subscribers, and whether subscriptions will be individual or one bundle, I can model the economics of beehiiv vs. Ghost vs. Substack—including what the writers and publication would actually take home at $500K/$1M/$5M in annual subscription revenue.

For a mid-size online publication managing multiple writers/newsletters, I’d put beehiiv first, with Ghost as the stronger choice if you want maximum ownership/control. I would not make Substack the core infrastructure if revenue-sharing with writers is important.

1. 🥇 beehiiv — my pick for your use case

beehiiv is particularly well suited to a publication operating several newsletters under one business. Its current Max plan supports up to 10 publications, unlimited team seats, paid subscriptions, and 0% platform take-rate on subscription revenue. Enterprise offers custom publication limits. www.beehiiv.com

The important distinction for you is that beehiiv doesn't appear to provide a native "writer gets X%, publication gets Y%" settlement system. Instead, the publication receives the subscription revenue and you establish your own writer compensation/accounting.

That can actually be preferable: you can define contracts such as:

• Writer A: 70% of net subscription revenue
• Writer B: 50% of revenue attributable to their newsletter
• Staff writer: salary + performance bonus
• Guest contributor: fixed fee
• Publication: retains 30–50% for editing, sales, technology, marketing, etc.

beehiiv's 0% platform fee means you're not giving another 10% away before calculating those splits. www.beehiiv.com

2. 🥈 Ghost — best if brand/control matters more

Ghost is compelling for a publication because it supports multiple newsletters, separate audiences, paid memberships, premium tiers, staff roles, custom domains, and full data ownership. Its Business plan supports up to 10 newsletters and 15 staff users; Custom offers unlimited newsletters/staff. Ghost takes 0% of subscription revenue, with Stripe processing fees still applying. ghost.org

The downside is that it's more of a publishing infrastructure platform than a growth-oriented newsletter business platform. You'd likely need more of your own systems for sophisticated revenue attribution, writer accounting, and growth.

3. Substack — easiest, but weakest fit for your business model

Substack is excellent if the individual writer is effectively the business. It's extremely easy to launch and has a built-in reader/discovery ecosystem.

But financially, Substack takes 10% of every paid transaction, on top of Stripe fees. www.beehiiv.comghost.orgsupport.substack.com

For a publication with several successful newsletters, that becomes meaningful. For example, at $500,000/year in subscription revenue, a 10% platform fee is $50,000/year before payment processing.

More importantly, Substack isn't really designed around your likely organizational model of:

Publication → newsletter brand → writer → revenue allocation

It's designed more around:

Writer/publication → subscribers → writer

What I'd actually build

If you're launching, say, 5–10 paid newsletters, I'd use:

beehiiv + Stripe + your own revenue ledger/contract system

Structure each newsletter as its own publication/product, while keeping the parent publication responsible for:

1. Subscriber acquisition
2. Pricing and promotions
3. Payment processing
4. Writer contracts
5. Revenue attribution
6. Monthly writer payouts
7. Central analytics

I'd define the split against net subscription revenue, rather than gross revenue. For example:

Gross subscription revenue
− Stripe/payment fees
− refunds/chargebacks
= Net subscription revenue
→ writer % / publication %

That avoids disputes over whether payment processing costs come out of the writer's share or the publisher's.

Bottom line:
beehiiv is the best fit if you're trying to build a portfolio of paid newsletters as a business. Ghost is my alternative if your priority is owning a highly branded publishing operation and subscriber infrastructure. Substack makes the most sense if each writer is essentially operating independently and you value its built-in network more than margin.

One caveat: none of these is a complete writer-revenue-accounting platform. If "automatically split every subscription among the publication and individual writer" is a hard requirement, I'd evaluate the payment/accounting layer separately rather than choosing solely on newsletter features.

For a mid-size online publication managing multiple writers/newsletters, I’d put beehiiv first, Ghost second, and Substack third.

The key distinction is that you’re not really choosing a “writer newsletter platform.” You’re choosing a publisher operating system: multiple publications, multiple contributors, centralized billing, and a way to split subscription revenue with writers.

1. 🥇 beehiiv — best overall

For a publication launching several paid newsletters under one company, beehiiv is probably the strongest starting point.

It is explicitly designed around publishers and supports multiple monetization streams, including paid subscriptions, advertising, referrals/Boosts and sponsorships. Most importantly, it doesn't take a percentage of subscription revenue; you pay the platform fee and payment-processing fees instead. www.beehiiv.comtiergauge.com

That becomes important very quickly. If your writers collectively generate $100,000/month in paid subscriptions, a 10% platform cut would be $10,000/month. A flat SaaS fee is much more attractive at that scale.

The catch: beehiiv isn't really a built-in "publisher collects $X and automatically pays Writer A 70%, Writer B 80%, etc." system. I'd treat writer revenue sharing as an accounting/payout layer you control, rather than assuming the newsletter platform handles it.

That isn't necessarily bad for a publication—you may actually want the company to own the customer relationship and pay writers according to contracts.

2. 🥈 Ghost — best if ownership and customization matter most

Ghost is particularly attractive if you want the newsletters to feel like your publication's infrastructure, rather than individual creators living inside somebody else's ecosystem.

It has paid memberships/newsletters, 0% platform revenue share, data export, custom domains and an open-source/self-hostable option. fieldwork.news

The downside is that Ghost is less turnkey for the growth/monetization machinery around newsletters. Compared with beehiiv, you'll likely be assembling more of your own referral, advertising and revenue-reporting stack.

I'd choose Ghost if your priorities are:

• Your brand/domain is paramount
• You want maximum data ownership
• You have technical resources
• You expect the publication to become a substantial media property
• You don't mind building some infrastructure around it

3. 🥉 Substack — excellent for writers, less ideal for your business

Substack is fantastic if your model is:

"Give each writer a publication and let them build their own audience."

It's less compelling if your model is:

"We're a media company with 10–30 writers, multiple newsletters, centralized subscriptions, and contractual revenue splits."

The biggest issue is economics: Substack takes 10% of paid subscription revenue indefinitely, in addition to payment processing. tiergauge.com

Its discovery/recommendation network is a genuine advantage, particularly when writers don't already have audiences. But you're effectively paying Substack a permanent commission for that ecosystem.

For a publication with an established audience, I'd generally rather own the economics.

The bigger issue: revenue sharing

This is where I'd change the evaluation criteria.

You should distinguish between:

A. Platform revenue share
How much does the software company take?

and

B. Writer revenue share
How much of your subscription revenue does each writer receive?

Those are completely different.

For example, suppose you have:

• 8 newsletters
• 40,000 combined paid subscribers
• $12 average monthly subscription
• $480,000/month gross subscription revenue

You might have contracts such as:

• Writer A → 60%
• Writer B → 70%
• Writer C → 50%
• House newsletter → 100% company
• Bonus pool → 5% above revenue targets

In that scenario, your platform shouldn't be deciding the split. Your publication should own the subscription revenue and calculate writer compensation from it.

I'd therefore look for a stack where:

Reader → Stripe/payment processor → your company → platform + writer accounting → writer payout

rather than:

Reader → platform → platform takes its cut → platform decides/distributes creator money

That distinction becomes extremely important once you have dozens of writers.

My recommendation

If you're launching now: beehiiv + your own writer-revenue accounting.

I'd structure it approximately like this:

beehiiv
→ newsletters, email delivery, subscriptions, analytics, growth, ads

Stripe
→ payment processing

Your publication
→ owns customer relationship + subscription revenue

Internal revenue ledger
→ tracks revenue by newsletter/writer

Payroll/contractor payout system
→ pays each writer according to their contract

That gives you the flexibility to say:

"Writer gets 70% of net subscription revenue attributable to Newsletter X."

without having to find a newsletter platform whose creator-payout model happens to match your contracts.

One caveat: verify beehiiv's current multi-publication/team and account structure against your exact number of newsletters and staff before signing, because those limits and plan features can change. Current 2026 comparisons consistently put beehiiv in the strongest position for publisher-oriented, multi-revenue newsletter operations. www.beehiiv.comtiergauge.com

If you tell me roughly how many writers/newsletters you expect (e.g. 5, 20, 50), your expected paid subscribers, and the writer split you have in mind, I can model the actual annual cost and writer payouts for beehiiv vs Ghost vs Substack at your scale.

For a mid-size online publication launching several paid newsletters for different writers, I’d shortlist beehiiv, Ghost, and Substack—but for your specific requirement of multiple newsletters + flexible revenue splits, I’d put beehiiv first.

1. beehiiv — best overall for your use case

This is the one I'd investigate first.

beehiiv explicitly supports multiple publications: 3 on Scale, 10 on Max, and a custom number on Enterprise. Each publication has its own subscriber list, settings, domain and analytics. www.beehiiv.comwww.beehiiv.comwww.beehiiv.com

The big economic advantage is that beehiiv currently takes 0% of paid subscription revenue; you pay the normal Stripe processing fee instead. www.beehiiv.comwww.beehiiv.comwww.beehiiv.com

That matters considerably when you're paying writers. For example, if a newsletter generates $20,000/month:

• Substack: $2,000 platform cut
• beehiiv: $0 platform cut
• You can therefore establish your own writer/publication split without first giving 10% to the platform.

The catch: beehiiv isn't really a native "we collect $X and automatically split 70% to writer A / 30% to publisher" system. I'd structure the commercial relationship so your company owns the publication/payment account and then calculates writer royalties internally.

That's actually preferable for a media company because you retain control over editorial ownership, accounting, contracts, and cross-newsletter revenue.

2. Ghost — best if you want a true publisher-owned platform

Ghost is particularly attractive if your publication wants maximum ownership and customization.

Ghost charges 0% of subscription revenue and connects directly to your Stripe account. ghost.org

Its model is essentially:

publisher pays Ghost a predictable software/hosting fee → publisher keeps subscription revenue.

That's a very good model for an established publication because your economics don't deteriorate as paid subscriptions grow.

I'd favor Ghost over beehiiv if your priorities are:

• sophisticated editorial publishing
• maximum control over your site/brand
• your publication owning the customer relationship
• custom integrations
• building a larger media operation rather than primarily a newsletter-growth business

The downside is that multi-publication management and growth tooling aren't as turnkey as beehiiv, so I'd want to map your proposed newsletter architecture before choosing it.

3. Substack — easiest for individual writers, less attractive for your business model

Substack is extremely easy to launch on and has the strongest built-in writer ecosystem.

It now allows up to 10 publications under one account, so it can technically accommodate your multiple-newsletter strategy. support.substack.com

But economically, Substack takes 10% of paid subscription revenue, plus payment-processing fees. support.substack.comsubstack.com

More importantly for you, Substack isn't designed around a publisher saying:

"Writer gets 60%, publication gets 40%, and our finance team reconciles everything."

A publication can have multiple contributors, but the payment/account structure is much more centralized. faq.substack.com

So I'd use Substack if writer autonomy and built-in distribution were the overriding priorities—not if you're building a coordinated multi-writer paid-newsletter business.

The revenue model I'd recommend

For a mid-size publisher, I'd avoid making the platform responsible for writer compensation.

Instead:

Reader → your publication/payment account → platform → publisher accounting → writer

Then define a contractual split such as:

• 70/30 writer/publisher for writer-originated subscriptions
• 50/50 for subscriptions generated primarily by the publication's brand/distribution
• 70/30 publisher/writer for sponsorship revenue sold by your central sales team
• bonuses for subscriber acquisition/retention

Or, even cleaner:

Writer receives 50% of net subscription revenue attributable to their newsletter.

"Net" should be precisely defined—e.g. after refunds, chargebacks, payment processing and taxes, but before your platform/software overhead.

That gives you a scalable accounting model across 5, 10, or 20 newsletters.

My ranking for you

🥇 beehiiv — best combination of multi-publication management, growth tools, 0% subscription take, and publisher-friendly economics. Its Max plan supports 10 publications and Enterprise can go beyond that. www.beehiiv.comwww.beehiiv.comghost.orgfaq.substack.comwww.beehiiv.com

🥈 Ghost — best if ownership/control and a sophisticated publication site matter more than newsletter-growth tooling. 0% revenue share is particularly attractive at scale. ghost.org

🥉 Substack — best for tapping into the existing writer/subscriber ecosystem, but the 10% cut and less publisher-oriented financial structure make it less compelling for your model. substack.com

One important caveat: if by "revenue split options" you mean automatic Stripe-level splitting of each subscription payment between your company and the individual writer, rather than simply having a platform that lets you calculate royalties, that's a different requirement. I'd evaluate the payment architecture separately before committing.

If you tell me roughly how many newsletters/writers you expect (e.g. 5 vs. 25), expected paid subscribers, and whether writers are employees or independent contractors, I can give you a much more concrete recommendation—including the likely monthly platform cost and a sample 70/30 economics model.

For a mid-size online publication launching paid newsletters from multiple writers, I would generally avoid a creator-first platform and choose a platform that supports publisher operations, multiple publications, revenue ownership, and writer compensation workflows.

The short answer:

Best overall fit: beehiiv
Best for ownership/control: Ghost
Best for individual star writers with built-in discovery: Substack

fieldwork.newstiergauge.com

Recommended ranking for your use case

tiergauge.com

Why I’d lean beehiiv for a mid-size publisher

A likely structure for you:

• Writer A launches Newsletter A
• Writer B launches Newsletter B
• Subscribers pay monthly/yearly
• Publication keeps a platform fee or management fee
• Writers receive a percentage of net revenue

beehiiv fits this model because it is designed more like a newsletter business platform:

• multiple newsletters/publications
• subscriber analytics
• growth tools
• referrals/recommendations
• paid subscriptions without a platform percentage cut (beyond payment processing) tiergauge.com

Your revenue split could be managed as:

Example

• Subscriber revenue: $10/month
• Payment processing deducted
• Publication keeps 30%
• Writer receives 70%

or:

Tiered model

• First 1,000 paid subscribers: writer gets 80%
• 1,000–10,000: writer gets 70%
• Publication-sponsored newsletters: 50/50

The platform usually does not need to calculate this automatically; many publishers handle writer royalties in their accounting system.

When Ghost may be better

Choose Ghost if your publication wants to become a destination media brand, where newsletters are part of a broader site:

• main website
• articles
• memberships
• archives
• SEO
• paid content

Ghost has a stronger ownership philosophy because it is open source and avoids ongoing revenue sharing. fieldwork.newstiergauge.com

A typical setup:

• Ghost manages memberships and payments
• Stripe processes subscriptions
• Your finance system calculates writer royalties

This is attractive if you expect millions in annual subscription revenue and want maximum control.

Why I would be cautious with Substack

Substack is excellent for a single influential writer, especially when discovery through its network matters. But for a publisher running many writers:

Potential issues:

• the 10% revenue share becomes expensive at scale
• writer relationships can become tied to Substack identities
• less publisher-style control over monetization rules tiergauge.com

Example:

• 10,000 paid subscribers
• $10/month subscription
• $100,000/month gross revenue

A 10% platform share would be $10,000/month before payment processing.

Questions I would answer before choosing

The platform decision changes depending on these:

1. Are writers employees, contractors, or independent brands?
   • Employees → Ghost/beehiiv with internal royalty accounting
   • Independent creators → consider a marketplace-style approach

2. Will each writer own their subscriber relationship?
   • Yes → favor Ghost or beehiiv
   • No → centralized publication model works better

3. Do you want one subscription unlocking all newsletters?
   • Example: "The Publication Premium Pass" gives access to 20 writers
   • This favors Ghost/custom membership architecture

4. Do you need revenue sharing automated inside the platform?
   • If yes, you may need a more custom stack rather than a pure newsletter platform.

My recommendation for a mid-size publication

Start with beehiiv + Stripe + a clear writer royalty agreement.

Use:

• beehiiv for newsletter operations
• Stripe for payments
• your accounting system for writer payouts
• your CMS for editorial workflow

Move toward Ghost/custom infrastructure if paid memberships become a major business line.

The biggest mistake for a publisher is optimizing for the writer who launches the first newsletter rather than the operating model you will need when you have 25–100 writers.

For a mid-size publication launching several paid newsletters written by different writers, I’d choose beehiiv—with Ghost as the strongest alternative if you want maximum ownership/control.

My ranking

1. beehiiv — my pick

beehiiv is unusually well suited to a publication operating a portfolio of newsletters. Its current plans support multiple publications under one workspace: up to 3 on Launch/Scale, 10 on Max, and custom numbers on Enterprise. Each publication has its own subscribers, settings and analytics. www.beehiiv.comwww.beehiiv.com

It also has proper team roles and publication-level permissions, so you can give a writer access to their newsletter without giving them access to your entire operation. Contributors can be restricted to content creation, while members/admins can have broader access. www.beehiiv.com

Most importantly for your economics, beehiiv doesn't take a percentage of paid-subscription revenue; you pay the platform subscription and payment-processing fees rather than surrendering a growing share of subscription revenue. www.beehiiv.com

The catch: beehiiv's native permissions are primarily about access, not sophisticated writer-by-writer revenue accounting. If your business model is, say:

Newsletter A → writer gets 50% of net subscription revenue
Newsletter B → writer gets 30%
Newsletter C → staff writer gets salary + bonus

I'd treat the revenue split as an internal accounting/payroll process, rather than expecting beehiiv to automatically calculate and pay each writer their contractual percentage.

That distinction is important.

2. Ghost — strongest if you're building a true publishing business

Ghost also takes 0% of subscription revenue and connects directly to your Stripe account. You own the billing relationship and subscriber data. ghost.org

I'd favor Ghost over beehiiv if your publication wants:

• a highly customized editorial site
• maximum control over branding and content
• ownership/self-hosting as a strategic priority
• subscriptions integrated tightly with your main publication
• the ability to build custom revenue/accounting infrastructure

The downside is that Ghost is more of a publishing platform you can customize than an out-of-the-box multi-newsletter growth operation. beehiiv has stronger built-in growth/monetization tooling and multi-publication workflows. www.beehiiv.com

3. Substack — attractive for individual writers, less so for your company

Substack now allows up to 10 publications under one account, so the old objection that it couldn't handle multiple newsletters isn't really valid anymore. support.substack.com

But it takes 10% of paid subscription revenue, indefinitely, in addition to payment processing. tiergauge.com

That's a significant disadvantage for a publisher. At $1M in annual paid-subscription revenue across your newsletters, a 10% platform cut is $100,000/year before processing costs.

Its big advantage is the Substack network/discovery ecosystem. If you're essentially recruiting independent writers and want each of them to build an audience inside Substack, that network can be valuable.

The key question: what do you mean by "revenue split"?

There are actually two very different models:

A. Platform revenue share
The platform takes a percentage of subscription revenue.

→ Avoid this for a mid-size publisher. beehiiv/Ghost's 0% model is much better.

B. Publisher ↔ writer revenue share
Your company collects subscription revenue and then distributes an agreed percentage to the writer.

→ This is the model I'd design your operation around.

For example:

Reader pays $10/month → Stripe → your publication → accounting → writer payout

You could establish a standard contract such as:

• 50/50 of net subscription revenue for independent writers
• 70/30 publisher/writer for writers receiving substantial editorial/marketing support
• fixed compensation + performance bonus for staff writers
• separate terms for advertising/sponsorship revenue

I'd explicitly define whether "net" means after payment processing only, or after refunds, taxes, platform costs, promotions, etc. That becomes very important once you have multiple newsletters.

Bottom line

I'd start with beehiiv Enterprise/Max for your situation. Its multi-publication architecture, publication-specific permissions, centralized management and 0% subscription take are a very good match for a mid-size publisher running several paid writer-led products. www.beehiiv.comwww.beehiiv.com

I'd choose Ghost instead if your primary objective is building a highly controlled, publication-owned subscription business and you're comfortable investing more in technical infrastructure.

I would choose Substack only if access to its writer/discovery network is sufficiently valuable to justify giving up 10% of subscription revenue.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50) and whether writers get a percentage of subscription revenue, I can map out the best beehiiv vs. Ghost architecture and payout workflow for your publication.

For a mid-size publication running multiple paid newsletters by different writers, I’d choose beehiiv, with one important caveat: beehiiv is excellent for portfolio management and monetization, but you’ll likely need to handle writer revenue splits in your own accounting/payroll layer rather than expecting the platform to automatically split subscription proceeds among writers.

My ranking

🥇 beehiiv — my pick

beehiiv is unusually well suited to a publication operating a portfolio of newsletters. Its current plans support up to 3 publications on Launch/Scale, 10 on Max, and custom numbers on Enterprise. Each publication has its own subscriber list, settings, domains and analytics, while the publications can live within the same account/workspace. www.beehiiv.com

More importantly, paid subscriptions have a 0% beehiiv platform revenue cut; you pay normal Stripe processing instead. It also supports multiple paid tiers, paid trials, group subscriptions, advertising, sponsorships, referrals and other monetization mechanisms. www.beehiiv.com

That makes it much more attractive than Substack once your newsletters generate meaningful revenue.

Example: if a newsletter generates $20,000/month in paid subscriptions:

• Substack platform fee: $2,000/month
• beehiiv platform fee: $0
• You still have payment-processing costs either way.

At $20K/month, that's roughly $24K/year in platform fees avoided.

The revenue-split issue

This is the part I'd investigate carefully before signing anything.

If your model is:

Publication owns the newsletter → writer receives 60% → publication keeps 40%

or:

Writer receives 70% of subscription revenue → publication keeps 30% → certain costs deducted first

beehiiv doesn't appear to be primarily designed as a native multi-writer royalty/payout system. Its strength is managing the publications and collecting the revenue, not automatically calculating and paying each writer their contractual share.

I'd therefore structure it as:

beehiiv → Stripe/company account → internal revenue ledger → monthly writer payouts

You can make the accounting sophisticated enough to support different deals:

• Writer A: 70% of net subscription revenue
• Writer B: 50/50
• Writer C: $5 per paid subscriber
• Writer D: 60% until $10K/month, then 70%
• Publication-wide sponsorship revenue: 50% writer / 50% publisher
• Ad revenue: separate split
• Bundle subscribers: allocated according to a predefined formula

That gives you considerably more flexibility than letting the newsletter platform dictate the economics.

🥈 Ghost — compelling if ownership matters more

Ghost is my second choice, particularly if you're building the newsletters as long-term publication properties rather than primarily growth/monetization machines.

Ghost takes 0% of paid-subscription revenue and connects payments directly to your Stripe account. Its Publisher/Business plans also provide staff accounts and collaboration features. ghost.org

The downside for your specific use case is that multi-publication portfolio management and growth monetization aren't as central to Ghost as they are to beehiiv. I'd favor Ghost if you have a strong technical/editorial team and want maximum control over your sites, data and infrastructure.

🥉 Substack — great for writers, less attractive for your business model

Substack remains excellent if your goal is:

"Give a writer a newsletter and let them independently build an audience."

Its big advantage is discovery through the Substack network, recommendations, Notes and app. But the economics are less appealing for a publisher: Substack charges 10% of paid subscription transactions, on top of Stripe's processing/billing fees. support.substack.com

For a publication with several successful newsletters, that 10% becomes a very substantial recurring cost.

I'd choose Substack only if its built-in writer discovery/community is expected to materially outperform the alternatives for your particular writers.

What I'd do in your position

Use beehiiv Enterprise if you're planning a serious portfolio.

Your architecture could look like:

Publication
→ beehiiv workspace
→ Newsletter A
→ Newsletter B
→ Newsletter C
→ Newsletter D
→ shared subscriber/analytics infrastructure
→ Stripe/company payments
→ internal revenue-allocation system
→ monthly writer payouts

And negotiate writer contracts around net revenue, rather than asking the platform to determine the split.

For example:

Net subscription revenue = gross subscription receipts − payment processing − refunds/chargebacks − applicable taxes

Then each writer's contract specifies their percentage of that number.

That is much cleaner than saying "the writer gets 70% of whatever beehiiv pays us."

Bottom line: beehiiv is the best fit for your described model. Its combination of multiple publications, 0% subscription take, portfolio-level management and broader monetization is much closer to a publisher operating system than Substack. www.beehiiv.com

If you expect 10+ newsletters, complex writer royalty formulas, or writers to have their own independent financial accounts, I'd specifically evaluate beehiiv Enterprise plus a separate payout/accounting layer rather than choosing a platform based solely on newsletter features.

For a mid-size online publication with multiple writers/newsletters, I’d shortlist beehiiv, Ghost, and Substack, but my default choice would be beehiiv.

My recommendation: beehiiv

For your particular model, beehiiv has the strongest fit. It explicitly supports multiple publications in one account: up to 3 on Launch/Scale, 10 on Max, and a custom number on Enterprise. Each publication can maintain its own subscribers, settings and content. Its Enterprise product is specifically aimed at media companies running portfolios of newsletters, with shared templates, permissions, analytics and unified management. www.beehiiv.com

The big financial advantage is that beehiiv currently says publishers keep 100% of paid-subscription revenue, rather than giving the platform a percentage. Its 2026 data also shows paid-subscription revenue on the platform reached $19M in 2025. www.beehiiv.com

The catch: beehiiv isn't really a writer-by-writer royalty accounting system. If your business model is:

Writer A gets 70% → publication gets 30%
Writer B gets 50% → publication gets 50%
Newsletter C has a different split for sponsorships

I'd treat beehiiv as the publishing/subscription infrastructure, and build the revenue ledger/payout workflow around Stripe/accounting rather than expecting the newsletter platform to handle arbitrary contributor splits.

Ghost is the strongest alternative

Ghost is particularly attractive if you're more of an editorial organization than a newsletter-growth operation.

Ghost supports multiple newsletters with independently configurable subscriptions/designs. Its current Publisher plan includes 3 staff users and Business includes 15; higher plans support unlimited staff. It takes 0% of subscription revenue, with the platform charging a fixed hosting fee instead. ghost.org

That's compelling if you want a publication-owned site and don't want to become dependent on a platform's audience/discovery ecosystem.

Why I wouldn't make Substack the default

Substack is probably the easiest writer experience and has a substantial built-in discovery network. It also supports multiple publications under one account. support.substack.comsubstack.com

But the economics are less attractive at your scale: Substack takes 10% of subscription revenue, in addition to payment-processing costs. support.substack.comsubstack.com

For a publication doing, say, $1M/year in paid subscriptions, that's roughly $100K/year going to the platform before payment processing. That's a meaningful amount to sacrifice if you're already bringing the audience.

The bigger question: how do you want to split revenue?

I'd separate platform selection from writer compensation.

For a publication with multiple writers, I'd structure it roughly like:

Reader → Stripe/payment processor → publication revenue account → accounting ledger → writer payout

Then define per-newsletter rules such as:

• 70/30 writer/publication for newsletters where the writer owns most of the editorial value
• 50/50 where the publication supplies audience, editing, marketing and infrastructure
• salary/flat fee + bonus for staff writers
• Separate splits for subscription vs. sponsorship revenue
• A clear treatment of refunds, chargebacks, payment fees, discounts, taxes and annual subscriptions

That gives you much more flexibility than locking your compensation model into a newsletter platform.

Bottom line:
beehiiv Enterprise if you want a scalable portfolio of paid newsletters with strong growth/monetization tooling. Ghost Business/Custom if editorial ownership, site control and membership infrastructure matter more. Substack if writer autonomy and built-in discovery are worth paying the 10% platform tax.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50), expected paid subscribers, and your intended writer/publication split, I can compare the three on actual annual costs and recommend the best architecture.

For a mid-size publication launching several paid newsletters with multiple writers, I’d put beehiiv first, but with an important caveat: if by “revenue split” you mean automatically paying each writer a negotiated percentage of the subscription revenue they generate, none of the mainstream newsletter platforms is especially elegant at that natively.

My ranking

🥇 I'd choose beehiiv

beehiiv is particularly well suited to your situation because you can run multiple publications from one account/workspace, with up to 10 on Max and custom quantities on Enterprise. www.beehiiv.com

More importantly, its paid-subscription economics are attractive at publication scale: beehiiv says publishers keep 100% of subscription revenue, with payment processing handled through Stripe. www.beehiiv.comwww.beehiiv.com

It also gives you substantially more of a media-business monetization stack than just a paywall—subscriptions, advertising, sponsorships, and its recommendation/Boost ecosystem. Paid newsletter revenue on beehiiv reached $19M in 2025, according to its 2026 report. www.beehiiv.com

The catch: the money from paid subscriptions goes to the connected Stripe account, rather than beehiiv natively saying “Writer A gets 35%, publication gets 65%.” www.beehiiv.comwww.beehiiv.com

So I'd structure it as:

Reader pays $10 → Stripe receives it → publication accounts for payment costs/refunds → writer gets agreed percentage → publication retains the remainder.

You can automate the accounting/payout layer separately if needed.

🥈 Ghost is worth serious consideration

If you're building something closer to a digital magazine/media company than a collection of creator newsletters, Ghost may actually be the better long-term infrastructure.

Ghost supports multiple newsletters within a publication, including separate audiences/segments. docs.ghost.org It takes 0% transaction fees on memberships and connects directly to your Stripe account. ghost.org

The downside is that Ghost doesn't solve your writer compensation problem either. You'd need to build your own reporting and payout process.

🥉 Substack is less attractive for your model

Substack now supports multiple publications—up to 10 per account—and multiple newsletters/sections within a publication, so technically it can handle a multi-newsletter operation. support.substack.com

But the economics are worse for an established publisher: Substack keeps 10% of subscription revenue, before payment processing. substack.com

And its product is fundamentally optimized around independent writers, rather than a publication hiring/commissioning a roster of writers and allocating revenue among them.

What I'd actually build

For your model, I'd separate publishing from writer compensation:

beehiiv + Stripe + internal revenue ledger/payout system

For each newsletter, define something like:

• Writer gets 50% of net subscription revenue attributable to that newsletter
• Publication gets 50%
• Or writer gets 30% of gross, publication gets 70%
• Editors can have fixed fees or a percentage
• Sponsorship revenue can have a separate split
• Cross-publication/shared subscribers get a predefined allocation rule

That's much more flexible than forcing your compensation model into the newsletter platform.

One important distinction: if you want the platform itself to handle arbitrary revenue splits and payouts to writers—e.g. automatically calculate 70/30, issue tax forms, onboard writers, and pay them—you should evaluate the payment infrastructure as carefully as the newsletter CMS. That's where Stripe Connect or a similar marketplace/payment layer becomes relevant.

Bottom line:
beehiiv = best overall for your publication.
Ghost = best if ownership, 0% platform fees, and long-term publishing infrastructure matter most.
Substack = best if you're essentially giving individual writers their own businesses, not operating a centralized publication.

If you tell me roughly how many newsletters/writers you expect (e.g. 5, 20, 50) and whether each writer gets a percentage of subscriptions, sponsorships, or both, I can map out the best platform + payout architecture and the economics at your expected revenue level.