Utobo Email lifetime deal

Choose the smallest tier that covers both people and traffic

Tier 1 provides 1 user, 3 mailboxes and 5,000 sends per month. It suits one operator with modest campaign volume. Tier 2 raises the team to 3 users and the pool to 10,000. Tier 3 gives 5 users, 25 mailboxes and 25,000 sends.

A hypothetical 2,000-recipient list receiving four campaigns needs 8,000 sends before welcome sequences or password resets. Tier 1 would be too small; Tier 2 could fit only if the remaining traffic stays inside its balance. A three-person team also needs Tier 2 even if its email volume is lower. These are workload examples, not measured usage.

The monthly B2B lead allowance is the same across all three tiers. Upgrading for more mailboxes does not increase that discovery pool. Lead discovery, stored contacts, sending and mailbox warmup should each have their own line in your budget.

Transactional email has a separate path, not reserved credits

The October 29 founder answer says transactional API/SMTP messages use an immediate sending path while sharing the same monthly pool as marketing. That distinction matters: a campaign queue should not hold up a transactional request, according to the vendor, but the account still needs sending capacity.

The provider advertises a reduced-capacity degraded mode without defining its trigger, usable rate or service guarantees. The behaviour when the monthly send allowance is exhausted remains unclear. Do not plan a critical password-reset or payment workflow on that description. Reserve headroom yourself, arrange extra capacity in advance or evaluate a dedicated transactional service whose quota and failure behaviour you can validate.

The founder says warmup does not consume the campaign-send pool. That exemption should not be stretched to normal cold-sequence emails, which do consume it. Unlimited sequences on Tier 3 describe how many sequences can exist, not unlimited sending.

Additional sending can turn a lifetime purchase into a monthly bill

In an October 31 answer about Tier 3, the founder quoted roughly $0.90 per 1,000 extra messages before the AppSumo discount, or about $0.54 after a 40% discount. On that quoted basis, 25,000 additional messages would cost approximately $13.50 per month. This is a dated founder quote, not a checkout price or guaranteed entitlement on every tier.

Confirm how extra capacity is enabled, when it is billed, whether tax applies and whether the discount covers your account. Do not assume it activates automatically when your application runs out. Paid sending remains separate from the one-time licence; compare the expected recurring bill at your actual volume rather than treating a large contact cap as free distribution.

Draper advice and autonomous email actions are different purchases

The founder distinguishes free advice chat from Draper Operator or Autopilot actions that draft, send or run campaigns. Those operational plans are separate from the AppSumo lifetime offer. A product page advertising an AI agent therefore does not establish that the purchased tier includes an autonomous campaign operator. Exact paid prices and action allowances remain unconfirmed here.

The October answer says Draper can read workspace-wide information; action permissions do not restrict that reading to one list. It also says EU-only processing is not available. A team handling several clients should settle that access requirement before enabling the assistant. This is a product-scope observation, not a compliance certification.

The reported Claude MCP connection can read and draft rather than send. Do not confuse REST access, an AI writing feature and an autonomous sending permission. Budget any external assistant separately, and obtain the exact charge for optional address verification rather than assuming lead or email credits include it.

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.