Zhivko Todorov
ALL CASE STUDIES

CASE 130 · ZEPHYR · 2024

TWILIO → SESSNSTRANSACTIONAL MESSAGINGCOST

Twilio for SMS, SES for email, both for less.

An on-demand services platform was using Twilio for both SMS and transactional email at $24,400/month. Half of that was email — a use case Twilio happens to support but isn’t especially cheap at. We kept Twilio for SMS (where they’re strong) and moved email to SES.

INDUSTRY

On-demand services

DOMAIN

MIGRATION

DELIVERED

2024

STACK

AMAZON SES·TWILIO (KEPT FOR SMS)·SNS (BACKUP NOTIFICATIONS)·PINPOINT (TARGETING)·EVENTBRIDGE

RESULTS

What changed, by the numbers.

MESSAGING BILL

−42%

$24.4K → $14.2K / MONTH

EMAIL DELIVERABILITY

99.4%

NEW BASELINE

SMS LEFT WITH TWILIO

CORRECTLY

BEST-IN-CLASS

TEMPLATES MIGRATED

47

PRESERVED IN PINPOINT

HOW IT WENT

The "Twilio for everything" decision had been about consolidation: one vendor, one API, one bill. The bill turned out to be the issue. For SMS, Twilio remained the best answer; for email, SES at a tenth of the cost was a better fit at the company’s scale.

We moved transactional email — order confirmations, password resets, receipts — to SES, with Pinpoint holding the templates and audience segmentation that had been in Twilio. SNS handled the backup-notification path. SMS stayed on Twilio.

Bill dropped 42% net. Email deliverability stayed at the previous baseline (99.4% to inbox at large providers). The team kept the abstraction layer for messaging so future channel changes are configuration, not code.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →