惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
The Last Watchdog
The Last Watchdog
TaoSecurity Blog
TaoSecurity Blog
PCI Perspectives
PCI Perspectives
L
LINUX DO - 最新话题
H
Heimdal Security Blog
S
Security Archives - TechRepublic
www.infosecurity-magazine.com
www.infosecurity-magazine.com
T
Troy Hunt's Blog
SecWiki News
SecWiki News
S
Secure Thoughts
The Cloudflare Blog
Last Week in AI
Last Week in AI
Google DeepMind News
Google DeepMind News
Attack and Defense Labs
Attack and Defense Labs
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
量子位
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Visual Studio Blog
N
News and Events Feed by Topic
E
Exploit-DB.com RSS Feed
博客园 - Franky
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
酷 壳 – CoolShell
酷 壳 – CoolShell
Know Your Adversary
Know Your Adversary
M
MIT News - Artificial intelligence
V
V2EX
Webroot Blog
Webroot Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
Cyberwarzone
Cyberwarzone
博客园 - 【当耐特】
月光博客
月光博客
Y
Y Combinator Blog
B
Blog RSS Feed
Recent Announcements
Recent Announcements
S
Schneier on Security
H
Hacker News: Front Page
Stack Overflow Blog
Stack Overflow Blog
NISL@THU
NISL@THU
小众软件
小众软件
雷峰网
雷峰网
P
Privacy International News Feed
腾讯CDC
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
C
Cyber Attacks, Cyber Crime and Cyber Security
V
Vulnerabilities – Threatpost
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
News and Events Feed by Topic

Resend RSS Feed

6 Tips for Accessible Emails Welcoming Manoel do Amaral, our new Brand Designer Welcoming Michael Vaz, our new Customer Success Engineer Six Steps to Improve Your Sender Reputation Welcoming Tatira Andrade, our new Executive Assistant Welcoming Pedro Ivo Hudson, our new Design Engineer Welcoming Diel Duarte, our new Open source Engineer Welcoming Areia Spinner, our new Recruiter Resend Forward: A Conference about Craft React Email 6.0 Custom Tracking Domains AI Email Editor Introducing Automations Welcoming Ahmed Tolba, our new SRE Engineer Welcoming Aneil Singh, our new Founding Account Executive Welcoming Lucas Motta, our new Software Engineer Welcoming Trey Knowles, our new Founding Account Executive Welcoming Anxhela Carciu, our new SRE Engineer Introducing DMARC Analyzer Welcoming Evan Thibodeau, our new Customer Success Engineer Welcoming Derich Pacheco, our new Software Engineer Welcoming Alec Ventura, our new Data Engineer Welcoming Felipe Freitag, our new Software Engineer Welcoming Mateusz Wos, our new Software Engineer Incident report for February 15, 2026 Email automation for OpenClaw How to Create a DevTools Agent Skill Introducing Email Skills Why You Should Embrace the Promotions Tab Slater Smith, our new Customer Success Engineer Do You Need a Warmup Service? Welcoming Zá Scalon, our new Brand Designer How Replit Built Effortless Email Sending Features 1,000,000 users Top 10 new features in 2025 Welcoming Danilo Campos, our new Design Engineer How Dub Uses Webhooks to Power Features Incident report for November 18, 2025 Resend Forward 5: Wrap Up One More (AI) Thing React Email 5.0 Unsubscribe Topics New Contacts Experience Introducing Templates Inbound Emails $3M to Make Email Safer Hacktoberfest 2025 Four Ways to Hurt Your Sender Reputation Resend MCP Hackathon Welcoming Christina Martinez, our new Developer Experience Engineer How to read a DMARC report Welcoming Erin Levine, our new Chief of Staff How to Validate Form Inputs Engineering an AI App Welcoming Lucas da Costa, our new Software Engineer Welcoming Lucas Vieira, our new Software Engineer Resend acquires Briefer How Raycast Modernized their Email Sending How to Get Email Consent DMARC Policy Modes Welcoming Gabriel Miranda, our new Software Engineer Rebranding Resend The 7 Best Email Verification APIs for Developers How DMARC Applies to Subdomains Welcoming Pedro Gomes, our new Software Engineer Do You Need a Dedicated IP? The 6 best notification infrastructure services The Fixer Why Your Emails are Going to Spam Engineering Idempotency Keys Microsoft’s bulk sending requirements for 2025 Welcoming Rehan van der Merwe, our new Devops Engineer 400,000 users and beyond Welcoming Cassio Zen, our new Software Engineer Resend acquires Mergent How to warm up a new domain Welcoming Carolina Josephik, our new Software Engineer Launch Week: Behind the Scenes Welcoming Isabella Aquino, our new Software Engineer Resend Forward 4: Wrap Up React Email 4.0 Multiplayer Editor Broadcast API Multiple Teams new.email Public Launch Welcoming Anna Ward, our new Postmaster How Gumroad Migrated 100M Emails to Resend Welcoming João Melo, our new Software Engineer Welcoming Jp Valery, our new Customer Success Engineer What is AX (Agent Experience) and how to improve it Welcoming Pauline Chin, our new Customer Success Engineer Introducing new.email How we use Friction Logs to improve the product Top 10 Email Deliverability Tips Welcoming Giovana Yahiro, our new Designer Engineer What BIMI's Changes Mean for Email Top 10 new features in 2024 Design Engineering an X Component Welcoming Alexandre Cisneiros, our new Software Engineer Resend raises $18M Series A
Lessons learned from growing a 6,338 people waitlist in 7 weeks
Zeno Rocha · 2023-02-21 · via Resend RSS Feed

The first question I get from YC batch mates is: "How did you get your domain?".

The second question is: "How did you grow your waitlist?".

I'm writing this post to document what went well and what went wrong. Hopefully, this will help other founders who are launching their own waitlists or looking to find potential users.

Waitlist growth
Waitlist growth

What went well

1. Landing page

We knew that we were entering a space with many consolidated competitors, so it was crucial to show people that we were different. We did that by creating a landing page that was extremely simple but also had unique branding and smooth interactions.

Resend.com
Resend.com

Here's what worked for us:

  • Tip #1 - Show personality - Adding an animated WebGL object was super important for me. Some people might say it's a distraction, but without saying a word, it communicates that we care about the technical details. Also, the Rubik's cube is the perfect analogy to what we were doing. It's an old thing that people are familiar with, but it's displayed in a new way. The same goes for Resend. We're doing something that people are familiar with (sending emails), but we're doing it in a modern way (using React).
  • Tip #2 - Know your audience - As a developer, I absolutely love keyboard shortcuts. I couldn't live without them, and I'm sure many other developers feel the same way. Even though a landing page is not a place to add keyboard shortcuts, it was a great way to show that we care about the same things our audience cares about.
  • Tip #3 - Focus on the details - Most landing pages we visit nowadays follow the same pattern. They use a predefined template that looks like every other landing page. As you start navigating, you might find typos or broken links. I truly believe that the small details make a big difference. If you don't communicate that you care about your own website, then why should someone else care?

2. Social media posts

Back in 2009, I created an account on this new social media website called Twitter. There were a few months when I was posting every day, and there were a few months when I wasn't posting at all. I didn't have a strategy, I was just sharing whatever I was working on. After years of doing that, I built a following of 39.4k people. This came in handy when we were launching Resend.

On January 4th, 2023 at 7:11 am PT, I published the first tweet about Resend. This tweet had 999.3k views, 4,634 likes, 352 retweets, and 282 replies. I'm not a big LinkedIn user, but I did post the same content there, and it got 107,411 views, 1,378 likes, and 156 comments.

Tweet about Resend
Tweet about Resend

Here's some tactical advice I learned from this experience:

  • Tip #4 - Post a video - from all the possible content formats, video is the one that performs best nowadays. If you can't do video, then use an image. Plain text and links perform worst in my experience.
  • Tip #5 - Post early in the day - when doing a big launch, be aware of the best time to post. I chose 7 am PT because that's when people from California wake up and check their phones, it's still early on the East Coast, and people from Europe have not ended their work day yet.
  • Tip #6 - Post during the week - I also chose a weekday because people are more likely to be at work and have time to check their social media. In my opinion, Monday isn't a good day to launch because people are getting ready for the week. Friday is also not a good day because people are already thinking about the weekend. That's why we posted on Wednesday.

If you're not into social media, that's totally fine. There are many founders who don't engage on social platforms and still build incredible companies. However, if you're thinking about starting a profile, keep this in mind - the best time to start posting was yesterday, the second best time is today.

3. Build in public

After the initial launch, it's important that you keep bringing new people to the waitlist. We did that by sharing our progress publicly.

  • Tip #7 - Keep the momentum - in order to keep people from the waitlist engaged, we started sending them emails about company news and product updates. This was a great way to keep people interested in what we were doing.
  • Tip #8 - Be personal - one of the things that I learned with YC is that being vulnerable is not a demonstration of weakness. Being vulnerable shows that you're a human being too. People act like they know everything. In reality, we're all just trying to figure it out. So don't be afraid of showing the behind-the-scenes.
  • Tip #9 - Build with others - as you start to share your journey, you'll start to get more people interested in what you're doing. Some of them might want to help you. In our case, that meant other companies building integrations with our product. We also tried to respond to every single person who engaged with our content.
Email about Resend
Email about Resend

What went wrong

1. Performance testing

On the day we launched, we got several complaints about performance issues (1, 2, 3, 4, 5). We knew that people were going to sign up on mobile, but we didn't spend too much time testing the performance on real phones.

"Slowest landing page I have seen in 2023" Tweet
"Slowest landing page I have seen in 2023" Tweet

Dealing with performance issues in the middle of a launch is not fun. Small bugs can be dealt right away, but performance improvements typically require deep thinking and a lot of debugging. We ended up fixing all of them, but I wished we had done that before the launch.

2. Email address validation

When setting up the waitlist form, we wanted to have something that was easy to use and low friction. There was only a simple input field, and we didn't want to ask people to confirm their email address. Even though we had some back-end validation, people could still add fake email addresses.

Resend Request Access screen
Resend Request Access screen

In order to address this, we integrated an email validation service called Emailable to guarantee that the email addresses were real. If we had better validation from day one, we would have saved a lot of time.

3. Processing the waitlist

In the beginning, we didn't have a proper plan to process the waitlist. We found ourselves with a big list of email address and no idea how to prioritize them. What worked for us was building a quick Typeform to understand who were the best people to onboard first.

We initially required every prospect to go through a mandatory onboarding call first (Superhuman style), but we quickly realized that wouldn't scale with our current team size, so we changed it to automatically onboard certain user segments.

Resend Typeform
Resend Typeform

It's important that you qualify your leads before reaching out to them. If you don't, you'll end up wasting a lot of time with the wrong customer profile.

Conclusion

A waitlist is a great way to build a community around your product. It's also a great way to get feedback from people who are interested in what you're building.

You will never be 100% ready to launch, and that's okay. There will always be something that you can improve or fix. The best thing you can do is to launch and iterate.

If you're not launching, you're not learning.