Independent software research · October 2026

Newsletter platform cost worksheet: compare the plan you can actually use

An inexpensive newsletter plan can become the expensive choice if it cannot run the workflow you promised readers. A larger subscriber allowance can also be good value when you only send a regular edition and do not need paid automation.

Use this worksheet to put the required capability beside its cost. You do not need to start a trial, enter reader details or choose a winner to use it.

Write the job before filling in prices

Describe one ordinary week. Include publishing, subscriber entry, follow-up, paid access and staff handoff where relevant. Then identify anything that would make the plan unusable. “Must stop the course promotion after a recognized purchase” is a requirement. “Has lots of automation” is not specific enough to test.

Keep three columns for capabilities: required, documented on this plan, and verified in my workflow. Documentation helps you shortlist; a controlled check helps you decide. Leave the final column untested until you have actually checked it.

These are proposed tests. This worksheet does not report a successful live test of any provider.

Collect a comparable quote

For every candidate, write the date, subscriber count, currency, billing cadence and quoted plan name. Record both today's count and one plausible future count. Do not use an audience forecast as if it were an observed result.

beehiiv's current pricing guide distinguishes a plan's maximum audience from the subscriber tier used to calculate its price. Its October announcement also gives existing customers a renewal transition. Kit's Free-plan documentation separately distinguishes subscriber storage from access to Sequences and Visual Automations. Those distinctions are why a price without a workload is incomplete. [Sources: beehiiv pricing guide and plan announcement; Kit Free plan.]

Write the full annual commitment beside any advertised monthly equivalent. If a quoted annual price is $720, its monthly equivalent is $60, but you still need to budget the $720 payment. Those numbers are hypothetical and are not a vendor offer.

Count messages without pretending to predict growth

For a simple starting estimate, multiply the recipients of each broadcast by the number of sends, then add expected triggered messages. With 1,800 subscribers, four full-list broadcasts and 100 new subscribers receiving three messages each, the calculation is:

1,800 × 4 + 100 × 3 = 7,500 messages.

This assumes the stated audiences, no exclusions and no other mail. It does not model unsubscribes, overlapping segments, retries or transactional messages. Add those if they matter. Also record the largest single send and any daily ceiling. “Unlimited sends” does not remove acceptable-use rules or establish inbox placement.

Separate platform charges from payment charges

Use gross subscription receipts for the revenue-share calculation, then apply the actual fee basis your provider specifies. Substack's current policy describes a 10% subscription share plus separate processing charges. Do not quietly treat that percentage as the entire cost of collecting money. [Source: Substack fee policy.]

The accompanying calculator and workbook use two generic arrangements: a percentage platform charge and a fixed software cost. Processing percentages, a fixed charge per transaction and other recurring costs have separate inputs. The starting values are illustrative assumptions. Replace them with your verified quote and payment terms before using the result to choose a product.

If the fixed arrangement costs $60 and the percentage arrangement takes 10%, the platform-only crossover is $600 of monthly receipts. If the fixed arrangement also needs a $15 monthly extra tool, it moves to $750, assuming the percentage arrangement has no corresponding extra cost. Differing processing rates can move it again. This is why a single break-even headline can mislead.

Give migration its own line

A move may require rebuilding forms, redirects, messages, paid access and integrations. Estimate the work honestly, even if you do it yourself. That estimate is an input for your decision, not an invoice we claim you will receive.

Divide the one-time cost by a positive monthly saving to get a simple recovery period. If there is no positive saving, do not display a zero-month payback. The move might still have a workflow benefit, but it does not pay for itself through the modeled cost difference.

Keep content and subscriber access tests separate. A contact import is not evidence that a paid archive, permissions or existing billing migrated. Our migration checklist explains the broader preparation.

Choose an outcome, including waiting

You have three useful outcomes:

• Stay: your current plan passes the required checks and the difference does not justify moving.
• Evaluate: a specific capability or cost problem warrants a bounded trial on an appropriate plan.
• Wait: you lack a quote, a required integration or enough information about migration to make the comparison meaningful.

An untested feature is not automatically a failure. It is also not a pass. Keep that uncertainty visible when deciding how much time or money to commit.

For product context, return to the email-software guide or the explanation of how email platforms charge. This worksheet contains no affiliate CTA and does not require buying anything.

Sources and limits

Source-checked October 20, 2026, U.S. Central. Vendor documentation supports the fee and capability distinctions; the worksheets, examples and formulas are original editorial tools. The model excludes taxes, foreign-exchange effects, refunds, chargebacks, audience changes and unlisted costs unless you add them to the assumptions. It does not predict subscriber revenue, savings or delivery performance.