Newsletter platform pricing is rarely one monthly number. A plan can change with subscriber count, contacts, sends, seats, features, paid revenue, and add-ons. Switching adds one-time work and launch risk that a pricing table does not show.
A useful comparison therefore models the next 24 months. It separates verified fees from estimates and unknowns so a missing quote cannot silently become zero.
The seven cost lines to include
Start with the provider's official pricing page and record only what is verifiable. If a live selector or sales quote is required, write UNKNOWN and obtain the quote before committing.
- Base plan fees across 24 months.
- Subscriber or contact-tier increases as the list grows.
- Monthly send limits, overages, or frequency-related upgrades.
- Seats, permissions, and team-plan requirements.
- Add-ons for automations, SMS, websites, analytics, or transactional email.
- Percentage fees on paid subscriptions or commerce revenue.
- Migration labor, specialist help, and launch monitoring: estimate separately, never silently add an invented allowance.
Model growth month by month when fees are variable
For subscriber-based plans, calculate the projected list for each billing period rather than applying today's tier for two years. For percentage-based fees, apply the published percentage to projected paid revenue for each month.
Example: Substack publishes a 10% platform fee on paid transactions. If paid revenue averages $1,000 per month, the directional platform share is $100 per month or $2,400 over 24 months, before Stripe fees. If revenue grows, the amount grows with it.
Price the migration separately
Migration cost is not just list export and import. It can include template rebuilding, forms, landing pages, domain authentication, tags, segments, automations, integrations, archived content, team training, and parallel monitoring.
Keep this estimate separate from the platform subscription. A switch may have better long-term economics but still be wrong this quarter because the launch window is unsafe.
Run three scenarios instead of one forecast
Use a conservative scenario, a base scenario, and a growth scenario. Change only the variables that genuinely affect pricing: list growth, paid revenue, sending rhythm, users, and required features.
If one platform wins all three scenarios, the cost result is stable. If the winner changes with a small assumption, mark the decision unstable and get a live quote before switching.
Cost is an input—not the whole recommendation
The cheapest platform can be expensive if it creates weekly manual work, blocks a revenue model, or forces another migration. The highest-fit platform can also be wasteful if its strongest features remain unused.
Evaluate cost beside eligibility, job fit, evidence confidence, and switching burden. Do not combine everything into one opaque score.
Frequently asked questions
What is included in newsletter platform total cost?
Include plan fees, subscriber or contact growth, send limits, seats, add-ons, revenue-share fees, payment processing where relevant, and migration work.
How should I treat a price that requires a live quote?
Mark it unknown and request the quote. Never treat missing pricing as free, and do not compare a verified number with an invented estimate as though confidence were equal.
Should migration cost stop me from switching?
Not automatically. It should raise the improvement threshold. Switch when the recurring benefit is material enough to repay the migration cost and risk within an acceptable period.
Primary sources
Product details and prices can change. These sources were checked on September 13, 2026.
StackOZ uses published product information and transparent model assumptions. It does not claim hands-on testing of every platform, plan, or migration path.