1
0 Comments

I worked at SendGrid at the beginning of my career. Now I'm building the email platform I kept almost building at every other startup since.

Hey IH — I'm Jarod, building Wraps.

Quick background: I started my career at SendGrid around employee 115. After that, I set up AWS SES at basically every startup I worked at. Same DKIM records, same SPF config, same bounce handling Lambda. Every time.

Meanwhile I watched companies pay Mailchimp, Customer.io, and SendGrid 10-30x what AWS charges to send the same emails. The gap always bothered me.

Wraps is a full email platform that sends through your own AWS account. Automations, workflows, templates, TypeScript SDK. You pay AWS directly for sending ($0.10/1K emails) and own your infrastructure. If you leave Wraps, your SES keeps working.

Where we're at:
- ~50 orgs signed up
- Biggest customer has 120K subscribers and 300 programmatic email workflows (something that's literally impossible on a GUI-based platform)
- Revenue: early. We charge a platform fee, sending costs go straight to AWS.
- Shipping daily

What's working: developers who already have AWS accounts and are tired of per-contact pricing. Our CLI deploys everything in about 2 minutes.

What's not working yet: getting people past the "wait, I need an AWS account?" moment. That's our biggest drop-off.

Happy to answer questions about the email infrastructure space, SES, or building dev tools.

posted toAvatar for product Wraps
Wraps