---
title: "How Tailwind supports builders through email"
description: "Resend is the modern email service built for developers who value speed, support, and DX."
slogan: "Beautiful, modern tools and resources for designers and developers."
name: Tailwind
slug: tailwind
logo: /static/customers/tailwind-dark.svg
website: tailwindcss.com
founded: Distributed, 2017
using_since: February, 2026
authors:
  - name: Peter Suhm
    title: Ops at Tailwind
    avatar: /static/avatars/peter-suhm.jpg
updated_at: "2026-05-18"
---

What started as a CSS framework has grown into a small family of products. Across all of them, **email is how we get people from "I'm interested" to "I'm using it"**.

Right now, the invitation flow matters most for our newest product, [**ui.sh**](https://ui.sh). In a very real way, **the invitation system is the business**. If invites don't arrive, nothing else happens, so the email experience had to be rock solid from day one.

We also use Resend for [**Refactoring UI**](https://refactoringui.com), our ebook on design for developers. Every order fulfillment communication flows through email.

**Taking Resend into production was straightforward.** From [adding Resend as the email driver](https://laravel.com/docs/13.x/mail#resend-driver) for our Laravel app, to the two-click DNS setup in our Cloudflare account, to the clean interface, Resend anticipated our needs and **let us focus on product**. And when we've had a question, support answers **in a shared Slack channel** within minutes.

We're a small team with a lot on our plates. Email infrastructure is something we don't want to think about, and with Resend we don't have to.