SendFox
- The 300,000-send pool never resets or stacks; campaigns and automations share it.
- When the pool is exhausted, sending pauses; Pro is the continuation option.
- New subscriptions use Pro. Existing Empire subscribers may retain their previous terms.
Estimate the pool in recipient-messages, not campaigns
One newsletter delivered to 1,000 recipients uses 1,000 sends. A four-message welcome sequence for 100 new subscribers adds 400. The current help page says newsletters, automation and transactional email all draw from the same cumulative balance. Unused capacity does not reset next month.
For a hypothetical list of 2,000 receiving four campaigns each month, broadcasts require 8,000 sends monthly. Add 500 automation messages and the workload becomes 8,500. Divide the currently recorded lifetime allowance by that workload to estimate how long it lasts, then allow for list growth and special campaigns. This is a planning calculation, not a measured account result.
The contact limit is separate. A list can fit the stored-contact cap while sending often enough to exhaust its pool quickly. Conversely, a larger address book cannot be imported simply because substantial sending capacity remains. Budget both constraints before migrating an established audience.
The lifetime plan and Pro solve different requirements
The current direct pricing page starts Pro at $19 per month for 5,000 contacts and 100,000 monthly sends. Its quoted entry annual price is $190. These are subscription prices, separate from the lifetime tiers, and may change. Larger lists move to other Pro levels.
Pro removes the SendFox footer and adds functions such as full HTML editing, paid newsletters and team access. Existing Empire subscribers may retain their purchased arrangement, but an old $10 Empire reference should not be used as a current new-buyer quote. If branding removal is mandatory, evaluate the recurring Pro cost from the beginning.
External domain registration, list cleaning and payment-processing costs for a paid newsletter are separate. An email tool’s deliverability wording is not a guarantee that every message reaches the main inbox. Sender reputation and the provider’s acceptable-use policies still matter.
See all SendFox tier guidance
Utobo Email
- No reserved transactional-send quota.
- Draper draft/send/autopilot actions need a separate paid plan.
- Brand separation does not create independent limits or billing.
Decide whether the delivery events fit your application
The founder describes signed webhooks with message IDs and recipient information for delivered and bounced messages, along with other engagement events. Rejected and deferred messages are not separate event types in the answer. If your application needs those intermediate states, a generic webhook checkmark is insufficient.
Idempotency keys are described as valid for 24 hours. Reusing a key with the same payload returns the same send ID; a changed payload produces a conflict. Temporary failures are described as retrying with backoff over several hours, but no precise attempt count or deadline was established. Keep your own event and retry logic consistent with those documented limits rather than assuming immediate success.
See all Utobo Email tier guidance
