Use case
Independent creators and small content teams, when regularly sending newsletters to their subscriber list, need to write, send and manage the list while keeping sending cost affordable.
The old way is using newsletter platforms such as beehiiv and Mailchimp priced by subscriber tiers, paying a monthly fee for the whole list even though most no longer read it.
Tiered pricing by total subscribers makes creators keep paying for many dormant subscribers who never open, so the bill grows with list size while actual sends are far smaller.
xOcto's call
Demand is evidenced
The trend is that newsletter and marketing tools are starting to charge by actual usage rather than list size, directly hitting the old per-subscriber pricing model. Entry point could be the sending cost of small creators and content teams, with the pitch of removing dormant names from the bill; but the delivery and support boundaries of self-hosted versus hosted paths need confirming.
Reason to use it
Why users would choose it
Inference: it changes the billing basis from total subscribers to actual sends and cites being 83% cheaper than beehiiv at 4,000 subscribers, removing the step of paying for dormant names, so creators with large but low-open lists would consider it first when renewing or migrating.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: it changes the billing basis from total subscribers to actual sends and cites being 83% cheaper than beehiiv at 4,000 subscribers, removing the step of paying for dormant names, so creators with large but low-open lists would consider it first when renewing or migrating.
Entry and what to borrow
The trend is that newsletter and marketing tools are starting to charge by actual usage rather than list size, directly hitting the old per-subscriber pricing model. Entry point could be the sending cost of small creators and content teams, with the pitch of removing dormant names from the bill; but the delivery and support boundaries of self-hosted versus hosted paths need confirming.