Go back

Unknown

1h 25m 52s

Unknown

Resend has emerged as a developer-first email infrastructure platform, challenging established players like SendGrid and Mailchimp by prioritizing simplicity, reliability, and developer experience. Founded by Zeno Rocha, a former indie hacker known for open-source contributions, Resend was born from frustration with the complexity and friction of existing email tools. The platform now powers 4.3 million users and has surpassed SendGrid in NPM downloads, with notable enterprise customers such as Warner Bros. and HBO. Resend eliminates traditional pain points—like DNS configuration, manual HTML/CSS templates, and onboarding friction—by offering intuitive SDKs, automated delivery systems, and real-time deliverability insights. The company operates on a philosophy of trust-by-default, where users are trusted from day one, with automated blocking only triggered when issues like spam or abuse are detected. Resend has deepened its engineering stack with performance-driven languages like Go and Rust, enabling faster, more reliable email delivery. It also innovates in multiplayer email editing and agent-based inboxes, positioning itself at the intersection of developer tools and AI automation. Despite the complexity of email delivery—especially around Gmail, Outlook, and Apple’s strict policies—Resend uses domain, subdomain, and IP segmentation to maintain reputation and deliverability. As the platform scales, it continues to focus on transparency, observability, and developer empowerment, making email infrastructure accessible and reliable for modern developers.

Transcription

16000 Words, 83133 Characters

English
It's like, oh my gosh, how are we ever going to beat SendGrid? It's just impossible. And then earlier this year, we crossed the number of downloads from SendGrid. And I was like, that's insane. And now we're more than double. So Resend now is powering 4.3 million users as of this morning. We have all sorts of customers like Warner Brothers, HBO. There was a Japanese gang that recently came. They brought like maybe 20,000 domains at Resend. Like those are 20,000 different TLDs registered in different domain registrars. And we are a 10 million AR company. I would rather live in that reality than live in a reality where we're a $100 million company. And my daughter doesn't want to play with me. It's not interested in me. And we're not that close. So we're building the infrastructure and going like down to the metal now. But it's a big project. Like we've been working for months now. And we're going to announce something soon. Okay, we're in the studio with Zeno Rocha. Rocha? Rocha. Rocha from Resend. You and I go back to your VS Code theme days. Yes. When you're just an indie hacker. And I was like, man, I don't know what this guy does. But everything he does has taste. And then now you build an email infrastructure platform. Anyway, welcome. You're undersell just an indie hacker. Top 20 most active GitHub under 2022. Very, very active open source dev. Yeah. What's your typical how do you introduce yourself these days? Yeah, I think I just focus on my recent career for the longest time. Even today when I say like, oh, I created Dracula. People know Dracula more than Resend. Still. Yeah, but it's been nice. Like there's a, yeah, it's changing. Yeah. What was the impetus for, I guess, picking email? You know, I think, you know, people always have like obviously react email and all those things. Like, I just don't know if I would have made it a company, you know? Yeah. If I knew like how hard email is, I probably wouldn't start the company either. Were you a primarily JavaScript front end? Totally. CSS? I was a front end guy. No infra, right? No email. HTML5 guy, you know? And I think what was interesting and what draw me to it is like, I just look at all the tools around that. And I've used all of them before. The Mailguns, the Mailchimps, the Sendgrids of the world. And I've always felt like, man, there should be something where there's just some, someone should care about this space. That's how I felt. Like you have all these players. It's a massive market, a lot of competitors, but no one that cares about the developer persona. Maybe they care about the marketer, the product manager or whatever, but not for the developer. So I started just building around that premise of like, if this was the stripe of email, how would that look like? And yeah. Like I had no idea or knew nothing about email. Like I was a user of email, but I have never built like an email pipeline and all that infrastructure before. Yeah. I mean, like, you know, typically if you ask me, like Postmark was still a thing. Yeah. And then obviously Sendgrid and all these guys, they're still around, but like they're not maybe as innovative as someone who is like a new YC startup, like trying to make it. Just up front, I like to let people brag a bit. And you, like for people who never heard of Resend. What are like the ways that you talk about like the most impressive numbers, the logos, anything? Yeah. So customers that are really big and have all sorts of demands, but also a lot of indie hackers and folks who are just building a website, building their own application. And yeah, we just crossed 120,000 paid customers. Yeah. Yeah. Yeah. Yeah. We just crossed 120,000 paid customers. Like the endless logo wall. Oh, my God. Yeah. Do you think this is effective? You wanted the flex. There you go. You know what? Like in the beginning, I felt like I just need to have some sort of social proof. And then in the end, I was like, you know what? This is actually pretty cool. And I honestly, like I found companies like Warner Brothers just like on a random Saturday. I was just, this was before AI. So I will go to my database. I'm like, oh, let me see who can I put on the website. And I just, I did the most. This is the most naive thing you can do. Like, let me look at the domains and let me just filter by dot coms and filter by the small ones. And there was this domain, WBG, Warner Brothers Discovery. I didn't know what is WBG.com and I was like, oh, no, Warner Brothers is using us. So, yeah, I just love featuring customers and yeah. Specifically for listeners, one of the reasons I reached out for this interview, one, you know, I should declare upfront. So when you sent me the memo, it was super simple. You're like, look, MailChimp has exited, Postmark has exited, SendGrid is under Twilio. Who is doing this now? And I was like, OK, yeah, seems right. Honestly, like in terms of like the pitches I get, I've invested in about like 30 plus companies. That was like one of the most straightforward things ever. And then secondly, I, you know, I don't like to add API keys, right? Like I like to have everything on one platform, one API key to copy everything. So Cloudflare has. It's built in email and I had a project and I set up my Cloudflare email domain DNS, all that junk, DKIM and what have you, right? I don't know all the alphabet super stuff. Yeah. And I already had this set up and then I was like, OK, well, I want to add another sort of email thing. Bloody model said you must add Resend. And I'm like, who the hell is doing this at Resend? That like, you know, even already I have a Cloudflare email set up and it's just still recommending it. It's on the screen now. This is him praising and like. I don't need Resend, but you want me to keep adding Resend. Yeah. So, OK, who did you bribe in OpenAI and Anthropic to get Resend on there? Oh, man, I wish there was someone to bribe because I'll definitely be paying them. But I do personally spend a lot of time on that topic. Like that's something that I feel like every generation, that's why I was so interested to build this thing in the first place. Like every generation, you have those tools that define that moment, right? We remember the Heroku days. I mean, Net-A-Fiber Cell. You know, and so to me, I was like, yeah, there's room for a new generation. And this new generation is not going to be distributed in the same places that it was before. So since the beginning, I was like very focused on, OK, we got to be number one when someone asks about that. You're very number one. Cloud Code recommending 60% plus of the time. I think it'll be fun to see the playbook. How do you win that? I do want to get back into it. OK, so you said you had no idea. By email, how to start email. I think a lot of people actually don't understand what goes into making a service like this, right? You might because you've set it up. Some people would just, you know, OK, I can use Twilio, I can use SendGrid, I can use you guys. But what goes into making a tool to just mass send emails? What do people not think about? Yeah, there's just a lot of different things you can do because landing on the inbox, especially when you're doing high volume, is different from like when you're scaling just like an app where you throw GPT, you're the problem or you just scale more vertically or horizontally, whatever it is with email. You've got to respect the rules of the game and how Gmail behaves is differently from Outlook and differently from Yahoo Mail. And it's an industry that is fascinating because it's so old school and it relies a lot on on contacts. But what we found early on was like, OK, we we knew nothing about this world and so and coming from this perspective, like extremely naive was the best thing that ever happened. Like, honestly, like it was the best thing because like there is no preconception of what is right, what is wrong. So for them, for example, every single app you go and then first thing you see is like this form that you've got to fill out about like how many emails are going to send. What's the volume? What are you trying to do? And then you go for a human verification process. Two days later, they accept you or deny you. Most of the times they're going to deny you. And I was like, this doesn't make any sense. Right. Like, why are we blocking people? So I know I'm going to remove that friction completely and the friction will be on us. We're going to figure that out. Of course, now, four years, three years in into this business, I get it why they do that. There's just so much fraud and phishing and abuse across the board. I don't talk too much publicly about that, but we build like all sorts of crazy systems internally for that. But to your question, like how you architect that, like, for example, if you're. When you're sending an email to 100,000 people, if you just throw 100,000 emails like to Gmail, what Gmail will do is they're going to throttle the emails because it's way too much and they want to see the engagement. So what do you do is like they see like, OK, are people opening the emails? Are people archiving, deleting right away or not interacting? OK, depending on those initial interactions, then what I'm going to do with the rest of the emails will dictate that. So I'm going to do a lot of things like, OK, I'm going to do a lot of things like, OK, I'm going to do a lot of things like, OK, I'm going to do a lot of things like that. And then I'm going to do a lot of things like that. So there are clever things you can do where 100,000 people put the most engaged audience members in the beginning of that queue. You have to put that in a queue. You need to. It's an art and a science where you've got to space out each batch. So and space out between the different providers, too. And yeah, now we're like buying different IP blocks. You've got to look at the history of the IP blocks, distributed folks into different IP pools. And then. and balance the IP pools over time. whole crazy infrastructure game how automated can that be or is there a lot of human judgment still yeah it's a lot of automation for sure yeah and i think over time we learned that okay this is how fast we can send for new customers of course if you're sending more then maybe you can send faster but there's a a throttle that we have to do to protect you as a sender so like what gmail and all these players will want to see is like a graph that is consistently sending more and more versus what most people do which is like you send once to a big audience and then you never send again and then it's empty and then boom you send it again one uh once a week twice a week yeah and those are patterns that an abuser will have right so the whole way of thinking about email marketing and in email in general is you you need to do exactly what an abuser wouldn't do it's the opposite of that so what's what's a abuser do they buy a domain we have now like there was a japanese gang that recently came they they brought like maybe 20 000 domains that recent like those are 20 000 different tlds registered in different domain registrars and we look for every single factor there so they they come in it's a domain that was bought two days ago so very new domains they they get bad reputation then you you look at the website is it returning 200 or basic things like that some people don't even set that up or they do like a lookalike domain so they're like oh maybe i'll do another domain for code outreach that's terrible because it's it looks like you're fishing right like because you're you're using a domain that looks like the same so all these little things and they just do they send a lot of emails all at once and then they never send again so you kind of got to reverse engineer how fishing works and and build a platform that does exactly the opposite of that do you have a list somewhere or do you recommend people go to some well-known lists yeah what i've learned is again another thing i didn't know email is the type of world where it requires a lot of education but people are not interested in learning right like the platform should do all those things for them so we added like insights inside the domain and then we're like oh my god i don't know how to do that so we're like oh i don't know how to do that so we're like oh my god i don't know how to do that so we're like oh my god we're like oh my god i don't know how to do that so we're like oh my god i don't know how to do that product so people can just apply the insights so we look at sending patterns and now with ai is pretty cool too like we have link checkers and spell checkers like all these checkers before you send so yeah it's a mix of your teaching your audience but at the same time the product needs to do the teaching and the more you can bake in the best practices the better so one example too when you send an email you can send an hml version and a plain text version very early on we were like you know what like this the whole world is changing there are way more agents than than before let's just generate auto generate the the plain text version of each email we can extract from the html the markdown and then just send that so we start sending that automatically and that increased deliverability a ton you know it's so much easier for spam filters to just look at the content directly without having to parse that so those things that we are like oh no let's bake into that product and most people don't know how to do that so we're like oh no let's bake into don't do that but we're like oh that this makes sense but with plain text there's no tracking right there's no tracking the image that's right so you don't have open rates yeah how do you know you have deliverability if you don't have open rates yeah this is very interesting because the the industry there are two ways of tracking right you have open tracking and click tracking open tracking what it does it it includes a one by one gif image a transparent image and then if that image is loaded then you detect that as open tracking and then you have a transparent image and then you have a the problem with that is that all the changes that apple did recently in terms of transparency and and data privacy like they read the emails before it lands if they're doing the summaries and all those kinds of things so like the open rate as a metric as a whole isn't really as reliable as it used to be because all these spam filters are are checking that before so then you rely on click tracking now click tracking can also be used to check if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a spam filter or if you have a you want the urls to match the sending domain you also want the images urls to match the sending domain that's another pattern that an abuser will do they would host images somewhere else point links somewhere else and then they're sending from this domain yeah i feel like i have uh used email services that would rewrite like for the link tracking right they'll rewrite to their own domain yeah you're saying that's bad that's bad because what happened we did that too at first and then i thought that's normal yeah but what's bad is when in you have a noisy neighbor problem too where if one of the customers using that click tracking is an abuser and sends a bunch of phishing that domain might get listed on a blacklist and then it takes maybe days or weeks to get out of the blacklist then you're screwed as a business is that pretty common like you make it very easy to just sign up free tier send a bunch of email i would assume you have a lot of spam a lot of phishing yeah but you're able to avoid and this is why yeah i think what what was different to me and then this is more like a philosophy right so i saw the those other products and the way they behaved and i felt like okay it's almost like if you are born in a society where you first go to prison and then you have to spend like 18 years in prison you gotta prove that you are a good citizen and then you get out of prison and now you can do the things you want to do i was always felt like no i want to live in a society where i'm born free and if i make a mistake then i might be punished just a little bit or if i do something like really bad a bad punishment right so that's how i feel about that too like you come in we trust you by default of course again a naive way of thinking but you know what we're going to trust you by default versus make the whole platform worse for everyone because of those bad actors right so we trust you by default but then what we do differently from others is like at the very first moment like when we notice something is off like by looking at the bounce rates complaint rates all the feedback we get from mailbox providers then we block you like very quickly and then we chat with you we try to understand and most of the time it's just misuse it's not abuse so we learned that we need to differentiate skill issue yeah it's a skill issue exactly it's just i think we learned we have skill issues too and we wouldn't have expected yeah for sure yeah email is so important and it's so dirty and it's so secretive and it's just such a i almost just want you to like just tell us everything i will say you have a you have a fun page literally your philosophy as you called it i got lost just reading around this and then there's like a cool you have a pledge that you will make email safer like if you're interested in this stuff you know you you have quite a bit up yeah um okay so uh actually i do want to there's this there's a how we scale support there uh i have another uh investment that i had uh jake from railway yeah because also another like very very permissive very developer oriented but also you have to scale support yeah right because the moment someone gets blocked they come to you and say hey like you know don't keep me off your platform yeah how do you scale support man i think we if support was a a software we're probably on major version four or something okay like the very first version was like you meet me and i was so stressed out i'm like dude i just need someone to be sitting on the chair like it's that simple i cannot be doing this anymore and it was like just anyone anyone i don't care then you do that of course it doesn't go well because you realize very quickly you need someone that will actually try to prevent the tickets from happening in the first place so then we went to v2 which was like a new version like a new person that we that we ended up hiring that was like okay we're answering the tickets they have domain expertise but they were still like not doing the proactive work of like no let's make sure this is documented before we we talk about so one policy that we we set it was pretty cool actually it was like you can only respond to a ticket with a link so you cannot just give the answer right away you had to stop or write a knowledge-based article write a docs and then so it takes like an hour and a half maybe for you to answer it but guess what now you're sending that link all over again uh so that was super cool and it helped us build that knowledge base but even so like after that we when we crossed maybe 1 million users so we had 1 million users back in december and now we have four so i can't throw people at the problem but that's just not gonna solve it right like i'm just gonna keep staffing and and that's how it is like no so we really have to rethink like okay everything from scratch again and we want to keep like that free tier it's not i don't want to get rid of that free tier i started as an engineer because i was able to use those free products right like we all like if it wasn't for heroku's free tier and all these other products like we wouldn't be here so i want to keep recent that way but it took us many iterations to yeah how much of this is like okay it's a domain people don't know a lot about they're actually unique questions that need human support versus you know command and command and command and command and command and command and k with just you have docs you have a model the customer service bots exist right yeah Yeah. I think right now is much better. There are a few things where, man, there's so much friction. DNS? Oh my gosh. It's always DNS. It's always DNS, right? Like the majority of the questions we get today is just like people not able to set that up. And it's fascinating because we're serving a new audience, right? It's an audience that doesn't even know how to troubleshoot. Like I remember last year when Lovable came and Bolt and vZero, I could tell these are different users. They don't know when they have a problem, they are stuck. They don't know how to go past that. And with DNS, that was always the case of like, yeah, they just simply don't know what is a CNAME, what is an A record, TXT, where do I put those things? So they would paste the wrong value or silly things. By the way, right now I use computer use like Codex or Cloud Code, and it just completely manages my DNS. It's beautiful, right? It debugs it, it like digs, you know, and tries all the DNS stuff. Like I don't have to worry about it. Yeah. One thing that we did, like I found this super obscure protocol that like very few people in the industry were like investing on. It's called Domain Connect. And it's super interesting, by the way. And it's something that started like from some domain providers. Oh, yeah, yeah, yeah. This is like the OAuth for domains, right? Exactly. Yeah, this is like Cloudflare oriented. Yeah. So some people have like Cloudflare is there. Then we convinced Vercel to be there as well. And we started like getting more people. So you have the two sides, right? The DNS providers, the service providers. We are the service providers, for example, and then the DNS providers are implementing. But it's a crazy, crazy industry. Like GoDaddy charges like just a lot of money for that. It's so weird. Like Jonas, it took us like the first one, it took us like months to get after that person too. Like no one really maintains the protocol and things like that. But it's beautiful, like having a protocol that you can just do an OAuth for domains. Yeah, yeah. So for listeners, if you're not familiar, if you haven't tried it, something like that. It's literally like you do use Plaid or use like OAuth. You only click buttons, you don't type in anything. There's nothing to get wrong. You basically just like sign in as long as you trust this thing called Domain Connect, which you have confirmed that it is legit. Then like it's trust. I literally, I used it for the first time like two weeks ago. I was like, what is this? I've never seen this before. Yeah. So it's really cool. One of the things that I'm trying to figure out as well is how you like start this company. Like you said, you try to get in touch with the IONOS guy. I'm like, I wouldn't dare to start Resend without knowing, like having like some guy on the inside at Gmail. Even now it's like, okay, can we vibe code our own email thing? Clearly no, but that's even with tools today. You did this years ago. Like I've, you know, you want people at domain like you need the guy, right? Yeah. But you need to pick up the phone. Yeah. There were many times that we had to pick up the phone. It's fascinating. Like it's an industry that relies on relationship a lot. And we didn't have those relationships. So we hired for a few key roles, like deliverability roles, folks that have been at Postmark since the beginning or 15 years ago at MailChimp. And then we, we leveraged that network. But yeah, it's pretty crazy. But what's interesting now, of course, I didn't know that when I started, like I could never predict what was going to happen. You didn't do the research? Yeah, no. Like I could never predict like, okay, what AI was going to do and all that. Right. But I think we are in a space where, man, I'm glad we chose infrastructure. I'm glad we're infrastructure as a service and not a just, yeah, software as a service. You had a little bit, right? You had, you made React email the year before. So you did dip your toes in open work. Yeah. And then came to come. Yeah. React email is our next JS, right? So we wanted like an open source channel for top of the funnel. And I remember doing some things very intentionally. If you go to the docs, for example, you'll find there are docs about how do you set this up with, sendGrid and MailChimp and MailGun. I wrote every single one of those docs over there. And I just wanted like, okay, this is for everyone. And we're trying to redefine how this is. And it was a strategy of like, we're going to give, give, give, and then we ask. And if people are, yeah. And if people are like building the, like the email template using React, like now they'll need a here's Resend. So it was a, like a storytelling kind of way of approaching the market. Like we're going to fix the first part of the journey, which is building the template. And then once you have the template, now that that problem is fixed, you need a platform to send it. Here's the platform. But did you have the idea for Resend when you started React email or was it a side project that then became a company? We started Resend. And as we were building Resend, I was like doing a lot of user research and people were saying like, oh, the pain of writing the template. I get the Figma file from my designer. It sucks. Like it's HTML tables and everything. They would cut the images, right? Yeah. Oh my gosh. Because there's nothing. And then there's like a special syntax of HTML that only works on email. Yeah. Right. Or CSS. It's all inline CSS. Yeah. Inline CSS. That's right. And then like for Outlook, you have like some special comments and then you got to, it's such a mess. It's like a, it's a mess. And so like, to me, the reason that React works is that it is basically a compiler. It's like, it's like, well, somebody writes this once and then as long as you fit the API, it's going to work everywhere. Yeah. And you can import your tokens from Tailwind. Now you have a type definition with TypeScript. So no more, hey, empty comma, you know, like on your emails, like you can actually have like a string validation or whatever you want. I think one of the initial people that push back on React email is like, well, you're not actually using React. There's no state. Yeah. And like React is supposed to be views as a function of state. Yeah. So it's mostly JSX as templating? Yes. Is there actually like animations? Is there interactivity? No. Expanding, like accordions? No. So you cannot ship JavaScript on an email. So then what you do is, yeah, we basically use the templating. But CSS is Turing complete if you. Okay. So cool. I actually do want to like continue on this email path, but I see so many names. I used to know. I was just kind of wondering if you can indulge us a bit and just go through like some of these names, like what do you learn from them? If you have any like cool stories, if just, just anything, you know? Man, so much. So much. I remember the very first year of recent, I was like, I got to meet the founder of Mailgun because I was still a user of Mailgun. And I talked to Ev. He's, he built, oh my gosh. Blogger? Medium? No, it's a separate, it's a different product. But anyways, like he, it's a security product that, that he's building now. And I remember talking to him, I was like, man, why'd you sell so quickly your company? What was the thing? And he told me like, oh yeah, 90% of our R&D was just to fight abusers. So it was, it's a terrible business. Like you shouldn't go there. And I was like, uh, like I don't want to live in that world at all. So I was very worried about that. Uh, and it was a big lesson for me of like, okay, we got to automate this thing. Like there's no way we're just going to build like a massive org, uh, for, we do have a lot of people interested in safety now, but it's not like that's going to be our core business. No, we're going to, we have to be pushing the industry forward. But that was one. And SendGrid has always been my favorite out of those ones and always been the behemoth, like the biggest, the, it's like, oh my gosh, how are we ever going to beat SendGrid? And then earlier this year, we crossed the number of, uh, downloads from SendGrid. So in terms of unique users or what's the, what's the number? NPM downloads of the SDK. Is that the best metric? Yeah. Like I think there, there's something about that metric in terms of adoption, but then. If you look at how many emails they sent is obviously much more than us because they have like the big enterprise customers yet and that kind of thing. I think one thing that's surprising is the whole point of the Twilio SendGrid acquisition is that I now, you're no longer an email service. You're a communications platform, right? You, you integrate across everything. It's not, it's not just about cross-sell. It is about, I can reach you across multiple channels, something like that. Yeah. Or that you have the size, you know, Twilio is like, I don't know what the size is now. Let's go, let's call it 13, $15 billion company. You should have all the relationships, all the talents, all these, all these, all these things. Right. So how do you compete with that? Yeah. Man, I, I admire Twilio so much. They kind of invented DevRel or, or. Yeah. Ask your developer. You know, ask your developer. Like, and now when I, I, I, I go past that one-on-one billboards and I see a customer AI or whatever, I'm pissed. I'm like, why? Like unique. neglected the thing that got you there. Um, and I think, uh, now like Jeff is not there anymore. The CFO is. He bought the onion. Yeah, that's right. That's right. So I feel like they're just. sleeping on it and first they did that with SendGrid and they're doing that with SMS too and yeah but I think my lesson here is I'm trying to figure out the economics of scale of this industry right like clearly you know let's call it they're 100 times larger than you when you just got started right how come they cannot use their size to just win right so in other words maybe there is no benefits to scale maybe you just you know you just make a better product and you can slowly for sure and I've always thought about too like why did Twilio acquire SendGrid and not the other way around did Twilio was bigger I mean SMS yeah it's big but like if email and communication is a commodity like SMS your margins are even worse even worse so have you looked into SMS yeah for sure you send SMS I think one day yeah I think one day yeah what are the channels that matter email SMS what else WhatsApp WhatsApp is big in WhatsApp is free right you don't pay anything yeah but then you you gotta go for Meta and now business messages are gonna be charged so there is some friction there for sure phone calls phone calls is a good one I don't know if it's a good one I'm less interested I never take any robo calls right yeah that's true I'm less interested about that too what I care is like what are the things that makes me able to connect with my audience like that's what I ultimately care like I don't care about email DMs yeah DMs it's one it's hard because you cannot like DM a big crowd but Slack maybe is one right Slack like I have so many Slack connects and I need to share the news about like this one new feature that I built yeah Pylon I don't know if you guys use Pylon I think they kind of innovated this like Slack support thing but you can obviously trivially build your own okay and then I think the other one I want to touch on is AWS SES yeah so my connection to this is I learned to code with FreeCodeCamp with Quincy Larson and everything yeah they have like 5 million subscribers on their newsletter yeah sent through Amazon SES for like $5,000 a month which is cheap cheap I don't know I don't know what you will cost yeah more than that so basically like to me it's just like the low cost player right yeah that is I mean it's Amazon it's like they're super established what do you take from them and then what do you what should people know to stay away from them we started with SES too we knew that okay if we're gonna be innovating here I wanted to innovate on the DX layer because I felt like that was the underserved space so let me have SDKs for every single language I remember with Serval as we highlighted servers because like no one had like guides on how to send an email with Lambda or something so there's just this underserved space in in DX so we started with like the most high level layer and that that served us really well was able to like scale because we were using SES behind the scenes turns out there's just a lot of limitations when it comes to the way you structure domains and they have this concept of configuration sets and the hidden cost if you're going with SES is that okay you might be paying only 5k for example but now you need SNS for the events so you need like all the feedback from bounces complaints open clicks all that and now so you get the events great now you need CloudWatch for the logs now you need a queue because it's going to be a lot of events so now you add SQS and now that you have SQS so you start like adding all these different layers oh you want webhooks okay now you gotta build another thing so if you go with SES it's a great platform it's fine but you're going to notice like your footprint will be much bigger than you would imagine very quickly because you need all the apparatus around it yeah I would say you know another YC startup that came up in the mail areas agent mail and then I talked to the guy as well and it was like yeah we're going to build on top of SES and not really compete with them but for us it's changing that now so we are we're building the infrastructure and going like down to the metal now and for us it feels like we got to the point where now this makes sense to innovate on the the most basic layer and now we can get better throughputs better deliverability if we just focus on that but it's a big project like we've been working for months now and we're going to announce something soon about what is the hardest thing to is it like trusted IPs is it compute and data centers or what is the blocker yeah definitely IPs you're buying like a whole IP block and then now you're managing the IP pools yourself that's one and then you're almost doing like traffic control and you're controlling the throughput into each mailbox provider and then you need the relationships with the providers but then like once you have that established that infrastructure now you have way more control into what you can give to users so one of the my biggest things were like observability you know like that as an engineer I want to see exactly what's happening and I've always felt like in this space there wasn't enough information like when when an email goes out is it really delivered is it really on this pamphlet is in the promotional tab like I never know like you just trust that the email goes out and then you always hear from some users like oh I didn't get the email I'm like what like what happened so there's that empty space between those things and the more we're close to the metal the more we have in terms of data that we can surface for users so I'm really excited it's like the flagship change that we're making now to I mean you're becoming it's really interesting for all like DX type businesses you start with like a thin layer like a react email and then it's like okay well we'll build on other people's info and then once you get sized then you can actually build your own info right are you doing anything differently because now you own everything yeah I think what we're doing is and by the way obviously you're dashboards are beautiful it's funny man everyone I talk to now like all the customers are like oh I never opened the dashboard but we can talk about that later but it's interesting like I spend so much time trying to make that dashboard beautiful and now people don't go there it's kind of frustrating but I get it but yeah we're just trying to approach that with the same naive mentality that we approach all the other problems and we're like okay this shouldn't be this way so you're challenging the most basic things of like this shouldn't be this way the P99 shouldn't take this long how we can make it faster okay so that's one of the things we're doing now like focus very very deep into performance and we have always been like a no JS shop and we have like just TypeScript everywhere and most recently like the sending path we no longer use a JavaScript we have Go there and we're changing other parts to be more more performative in other ways because now languages don't matter exactly right it's like it's just so cheap to yeah like pick a problem and yeah you can rewrite the whole thing in whatever the first languages I'm like running Rust projects and I've never I don't really know Rust like I know like some theoretical things about Rust but I've never really bothered to learn it I feel like we're not really covering the recent product surface area maybe you want to go no no I mean you know there's everything we've talked about which is why it's hard what all you're solving and then there's also just send emails from CLI super agent forward you have some takes on this I think the other day you tweeted like MCP is so back right like over a million MCP calls like what's the what's the AI side of email yeah everyone was saying MCP was dead right a couple months ago like yeah the only thing that matters is the CLI what I've noticed is that I stopped paying attention to what's in what's out and I I really think about these problems as like okay how do I want my product to be okay well I want my product to be formless whatever they want to do with the product it should be possible so that that's why we've always been API first you know I had no idea how much this would help us down the line but I knew yeah like if I will never be able to cover all the use cases so let me just give the API you do whatever you want and with the MCP it's just fascinating like every month like at least 2x growth and now in August these numbers are even more this was before the end of August I think it was 1.2 million by the time it ended but yeah like people are starting to work from cloud desktop or codecs and if work starts from there then you need those integrations right it's just super important I just want to clarify as well so you know you showed us sort of like the month by month numbers on the MCP thing it picked up from like let's say 50% month by month growth which is already super high then it starts to double basically every month did you do investment into MCP or you just had an MCP and it just after some time it gets picked up well the fun fact about that our very first MCP was built by Yoko from A16Z our investor wow value add yeah right so she built the open source version it was a local MCP and then it started to grow like crazy and I was like man why are people using it's like so hard to set up MCP this was last year - And then, see you'll go. - Yeah, exactly. she built that uh and then i just asked her hey can you transfer to our org it was like just like an engineer building something and it was nice to see after the traction it was getting but to do the mcp right to do the remote one we had to go back and revisit our entire permissions model because we needed all off and then we were like okay now we have a blocker let's build off so then we build off and it's like okay our back let's look at that like let's look at how users have access to each one of the resources so it was a whole journey to build off and then after we had off okay now we have the remote mcp and then it's distribution so then okay now we have the remote sp okay great great great observability is in place great great okay all the data doc dashboards okay now all in let's talk to everyone and that was hard too like uh it's not as easy i wish i had you all your connections uh it's not as easy to me you're supposed to talk to me uh but like talking to the labs and trying to get into like the the official stores and plug-in marketplace so you think that actually matters oh for sure yeah so i think sometimes like i've been on the other side where i try so hard to get these partnerships we launch it and then nothing all right so which one matters so as a consumer i make decisions now based on do i have the access to that data or not so as a as a buyer of b2b software if i go to the cloud connectors and i don't see the company listed there with an official mcp like for we had this like we had a we were using plausible and post hog plausible had an mcp built by century i don't care if the plausible doesn't maintain that and that's not official i i don't i cannot trust that as much even though i love the century team i don't care if the plausible doesn't maintain that and that's i trust that team but i need the owner of the software to own this piece of integration oh my god and i made the call like no we are getting rid of plausible and we're just going to use uh post hog here because i have the mcp there and i did that as a as a b2c consumer too i'm like into running and then i'm like oh let me like strava strava has an mcp i can like access my runs so i use strava because of that so and if there's like oh no we don't have we have an mcp but you have to connect like this like the x mcp for example i have to do like the the local one it's just so frustrating it works on the desktop client not on my phone like like to me it's just yeah if it's not there i don't use it apart from okay it is officially maintained by the vendor or whatever what makes a good mcp versus a social mcp even for hours as i as i interact with that there were i always like it's always collapsed right the the tool calls i'm always opening and trying to understand like what did it do and just a couple days ago like there was one call where it couldn't put everything on the contacts for some reason and then i'm like no this shouldn't happen like how much data are we sending maybe we're sending way too much data to the client so that's something that i noticed like the amount of tools this was a bigger concern earlier like oh if you have way too many tools i get confused i don't see that as much anymore and in fact we're trying to just adding more to the mcp oh like we had like maybe i don't know 20 tools when we launched or even less than that now we have like 80 something tools what the fuck yeah and like i'm adding more and more like the the long tail of two of like the the footprint that's what i've noticed like you can do like only 90 of what your dashboard does and that's one way of doing it or you can do it getting to 100 coverage of what your dashboard can do is actually very very difficult because now you're doing usage billing team invites account provisioning deletion should that be exposed as an api or not like it's it's really hard like it's a it's a difficult problem yeah in fact uh you know there you are one of the few in space guests that can i can ever talk about this with i think this is one of the mistakes of next.js oh really because next.js and server components and uh pages api or apps apps api um they make it easy for you to basically bind data to your page okay so you never expose the public api yeah so by default the thing that is performance and they encourage you to do you will not have an api that's right then you have to just do like separate code paths or whatever yeah in fact you should just always have like completely headless back end and then your front end just happens to be one of many clients that connects to your back end and we started with our api on next i remember that first of all the view was just so high that we're like there's no way we can pay for this so then we moved to a traditional node server uh server four whatever you call it and and then like our dashboard was always like a private api consuming the same thing we had to duplicate a lot of code it was a mess right um now it's so much better everything on a default ideally those frameworks like just gives us those components right we had to build a public api separately from that and it sucks to maintain both yeah okay and then one more thing about just so uh you know so you are 80 you got 80 tools in there you're growing more tools you are very counter consensus compared to cloudflare which only has two tools you search and execute or something like that so far you haven't felt that issue but uh what would make you change your mind right like you you it seems like numbers are going up but do you actually know do you talk to your customers and say they're like oh my god it's like the best mcp on earth or like i do try to get a lot of feedback on that and then the way uh the way i like to build products is i gotta use the product my on my own right so if i'm like the investor updates that i send you yesterday that was built using the mcp you know it's like fetching data from one place from another place and then uh you're like i feel bad now i don't do all this i don't use mcp enough basically is what i'm hearing i mean i guess the other thing is also like you do have cli you do have regular sdk like yeah are those also just going crazy is everything just from a lot of growth or yeah the cli is definitely growing but not as much as the mcp but i have a lot of fun with the cli too like if you go to our careers page i'm actually proud of this because i built it on a weekend or something but if you go to any job there and you you try to apply for a job and you have those to go down now you have three ways of applying or apr so you can just log in and it has an interactive mode or we have skills baked in into the cli and you can just ask claude like apply for a product designer role with recent yeah okay so you're very you are filling yourself with slop especially in careers yeah no i mean i think maybe that's also the people you want right totally i actually have a filter if the source is the cli i look differently because i know someone went through people are going the extra mile like setting that up like oh no i gotta download this thing and i have to authenticate and then i have to go for that flow but guess what like people who go through that they always tell me like man i've never applied for a job using a cli before so even if they are not accepted like there's just something like it's just a different experience than other jobs yeah i think maybe that's also the people you want right totally i actually have a filter applications even api applied for one job through exactly i mean it's you know the same thing as yeah uh yeah so so i think one of the things i'm trying to figure out as well is like product philosophy right like you you are you're clearly just like you just max everywhere right every sdk every language every uh surface area obviously easier with agents but i think some other founders that i would know would say hey this doesn't matter give that to greenhouse or ashby yep is your job applicant you're not gonna differentiate like this right yeah you clearly have a very different philosophy of you care about everything even though you know probably some of this stuff is just wasted the way i see it is um i'm trying to optimize not only for the privileged users like the users who who have the greatest wi-fi the macbooks that are here in sf or in new york right all these people at the margins that are in other countries that are in other countries that are countries with a terrible wi-fi brazil brazil growing up that that's how it was for me a terrible windows computer and terrible internet access so that's why we have the free tier we we don't have the free tier because of the you know like there's a there's a reason behind it when we we have all the sdks so i'm maxing on the sdks man building the dotnet sdk do you think that was fun like and we looked into stainless it's stainless fern what's the third one uh but like we look at all these companies right we didn't like what was generated so every one of those sdks is humanly generated the java one the rust all those ones right and i do that because i feel like yeah if you're using a product you should have the best experience in that language that you're using oh but there's only 500 people out of the 4 million i care about those four four hundred people wow you know well why not you know why not is you have 4 million users. That's why not. There's a lot of stuff to do, but it's good to have that opinionated side towards building this, right? Any other product surface area stuff that we should cover? You covered CLI, covered templates, covered MCP. I think it's good to get a high-level perspective from you of how much of this is very traditional. You even have dashboards, templates to manually write emails. You have programmatic. You also have the full agent pilled. Like, where do you see it going? How do you think about building this for a pretty fast-changing world, right? Yeah. There's definitely still a component of email moving out of this single-player mode and going more into multiplayer. We even built our editor like this. It's multiplayer. It fix all the conflicts if you have two or three people. We actually run, I have a private recent account with all the teams, and we run all of our all-hands there. So, the all-hands is pretty much, you go there, it's a huge. You make an email? It's an email. And we send the email together at the end of the all-hands. It's super fun. And you have like 20 people in the same document. This is super electric. I feel like 99% of people have not thought about multiplayer email, right? But you have a lot. Yeah. And it was really fun. Man, that editor alone, it's so freaking hard to maintain that thing. But I love it. I love that we have the UI for people who need the UI. Like, some teams hate to have the email template pushed into their source code. Then they just want to build a visual editor, a template, give to the marketing team, and just call the ID. I don't care about the template. I just want to call the ID with variables, and I'm done. Other teams, they do like, no, I want to commit, I want to have source control over this, and own this piece of thing. So, I try to tailor to those different audiences and build a product that, you know, feels that we care, which is not the feeling I get elsewhere. Yeah. By the way, what does the recent team used to read email? Superhuman? Yeah. Oh, man. Have you seen the last Superhuman update? You were busy with other launches too, right? Yeah. And for listeners, we are recording this on the day of the Astra launch, which I was pulled into and I am not sleeping. But, no, what's wrong with it? They just updated the UI a little bit. Yeah. There's just a sentiment of like, oh, this is going to the direction of every other acquisition goes, right? Like, now you're fitting a brand that has all the interest. Grammarly and other things. Yeah. Okay. It's just email. And I do want to keep up to date on email tech in general. You're on the sending side, other people on the reading and receiving side. Yes. And then I think, you know, increasingly, I would say agents reading my email. Yeah. I actually don't read most of my email. I have Polk and two humans helping me with my email. Nice. I love that. Polk is pretty good. I honestly, like Instinct, now super hot, $2.5 billion company with no revenue. And like, it's just like people trying to read email of agents. Yeah. We are definitely looking to that space. That's another thing that I'm spending a lot of my time, like how you can programmatically create dozens of inboxes and then how are those inboxes accessed by agents? Because you create, you enable receiving email. What is it called? Inbound? Inbound, yeah. Email? So now we're going another abstraction. Inbound is like the most basic abstraction. Now we're going one step further and be like, oh, you need a hundred inboxes for any reason and here are the APIs that you need on top of that, right? So you need a read API, markers and red, you need star API, labeling. I see, I see. So we're going to be launching a product around that soon. Yeah, but again, it's all API driven because that's the fully, because I would say the comparable stuff that I've been looking at is missive. Yep. And there's other like help scout? Yes. Like a shared inbox type of product, right? Front. Front. Yeah, so hopefully this can be a version of that. Okay. I can share with you. There's a feature flag for you if you want to try that out. Yeah, I'm very interested in email tech. Okay, and then to me, and then I, again, I'm just like asking all these questions. What percent of your email goes to a G Suite or, you know, like what's the market share, right? Like Google versus Outlook versus Apple versus Hotmail? Yeah. I don't have the numbers top of my head, but the vast majority, like at least 60%, 60% Gmail. And then you have like maybe the big tree after like the Outlook, the Yahoo mails of the world right after. And then you have a long tail. Apple is not that big. Apple is big. Yeah. And especially with the privacy thing that they did now. It's harder to sign up to an Apple. What? Sorry? Yeah, like Apple auto generates an email address for you. Yeah, I use that. I use that. Is that a problem for you guys? They're more strict in terms of what can get into those inboxes. So sometimes as a domain owner, we actually have like an in-product wizard to, to help you like register with Apple so that you can get your emails delivered there. Yeah, yeah. Okay. I understand. Obviously, this is your job, right? The whole thing is deliverability. If you don't have deliverability, you don't have a business. Exactly. Yep. That's kind of the. Yeah. We can have the most beautiful Rubik's Cube in the website. The most, like coolest handbook ever if it's down. Yeah. It's often enough. And how correlated are they, right? Like if you get banned or downranked or put in promotions tab, in Google, does that transfer over to the other guys or are they very decentralized? Thankfully now, like in the beginning of the email industry, it was very IP based. And if one IP pool was damaged, like now, you're getting the consequences of that. Now there's a lot of reputation associated with the domain. So then what people do is you create different subdomains depending on what type of emails you're sending. Like one subdomain for transactional email, that you know that maybe doesn't have click and open tracking. And then you have another domain for your marketing emails. And those subdomains help segregate the reputation of whatever. So would it be like transactions.recent.com? Yeah. Updates, notifications, whatever you want to use it. And do I have more dots if I want? Like a.b.c.recent.com? You could do, but we just see like doing, I don't know, five subdomains. It's like, you know, yeah, not really practical, but like people do, yeah, like some special ones. Like we do that at recent for our own emails. Like marketing has a different stream than the transactional ones. And yeah, even the investor one has a different, like I use confidential.recent.com to send those emails. I didn't even know you could. Yeah. And that is good advice. It's a good practice. So before it was very IP based. Now it's very domain based. You know, I have, okay, I have received so many bad, like, I have to buy a separate. So because we use AI.engineer and latent.space. These are all like weird TLDs that nobody recognizes, right? So I was told to get.coms for everything. And then maybe that improves deliverability. The problem with that is that now, like, let's say, let's take Coca-Cola, right? Coca-Cola has a domain. Now your Coca-Cola like, oh yeah, let's buy another domain that looks like our domain. It looks like phishing. It looks exactly like phishing. So the chances of damage is way worse. Is this still a thing when you're buying the.com? Like I would get it the other way, right? You're latent.space.com. I buy latent.space. Looks like phishing, right? But the.com still? Man, you would be surprised. Like there's just, like the things I see on a day-to-day basis is like crazy. Yeah. So what I'm hearing is like.com is worth it. Yeah. That's all the sort of business of email. Obviously, some part of it is you just got started before ChatGPT and then you were a leading player that people liked and then obviously organically you pop up. You didn't do anything special for AEO. What did you do for AEO? I would say we were not the leaders because we coming up like in 2023, like very few people knew about Resend and we were like so behind. Twilio, Postmark, Mailgun, those companies invested in SEO for 10 plus years. So for us to get ranked for anything was like almost like it was an uphill battle. Like so, so difficult. So then what we did was like, okay, let's focus on the docs for sure. And the docs was very intentional about like, okay, if we're doing a docs on, it has long tail again, like, oh, here's a docs on not just Python, like how you set it up with Django. Yeah, how to blah with blah. Exactly. How to blah with blah. Super short articles. This is traditional SEO. Traditional SEO. Nothing fancy there. And then when models started to come, then I was like, okay, maybe I got to change the content of the page. Because if people are asking questions, then I need to like create content that is in action and answer, ask and answer type of format. So a lot of FAQs. Now, almost every page at Resend has an FAQ, you know, like I'll go to pricing page or like, yeah, of course, pricing almost always has an FAQ. This is pretty standard. Yeah. But like, Like you do FAQs in like all sorts of. yeah i think maybe security also yeah so like you see it's like a pattern uh of like all pages have that because that's how people are asking is resend sock to compliant and then just have the answer right there and then okay now we have those things in okay now we got to do llms.txt so we added llms.txt on our docs thankfully because of mentalify that we use great product and we're like okay how we take this to the marketing site too so then llms.txt for every marketing page same with the docs hatch market uh markdown versions of the docs i'm gonna do markdown versions of every single page on the website on the marketing website using content sniffing or you just append like dot md yeah just append you you do append uh so if you go to the city yeah the security page dot md it will work yeah but also if you do content negotiation with that page uh it will render on that page like the markdown version without going to that yeah which for listeners this is one of those things i'm not sure it matters i'm really not sure yeah i mean you're winning really well so yeah i think one example that changed uh and maybe it doesn't help with distribution but helps with accuracy so go to the pricing page i remember this was like a random sunday and i was just like doing competitor analysis and i was just asking like okay if you send 1.2 million emails using recent and you did that with x and y and z competitor who is the the cheapest and who is the most expensive and it got completely wrong it got the recent one like so bad and it it actually said like very bad things about us like oh recent pricing is very obscure i was like what the fuck like it's not obscure at all uh so it was like super frustrating so you made a calculator yeah so the the problem was you know agents don't really uh drag a javascript widget okay so then what i did was the the dot mt version of this page uh which has a tremendous amount of uh access by the way like now like i see you get analytics on this yeah yeah okay not through the the the regular analytics spots too because like we cannot track that uh yeah it's the server side so then like we got to go to data.com to figure that out okay and man it was really crazy like uh and then i made that change i pushed that and then i asked again like a few days later and then he got the numbers right i see so i'm like okay this is a way to live update and fix stuff exactly and and this is what matters right like okay it does mean that you don't have a single source of truth like you have to update the md and then you also have to update it that sucks but again if if i wanted the happy path and the easy path like i wouldn't be doing email so i'm like that's the price of like well you know if you're good at react you can write a custom renderer that like yeah you know how to do this yeah what else we talk baselines basically have a fake you everywhere basic seo comparison pages us versus sangrid us versus uh although our page could be much better go to yeah no this is not there i mean i'm sure you have it somewhere in some footer or something or whatever yeah just do slash migrate uh i can give you something by the way 404 pages i always think we should guess you know pick the slug yeah nearest neighbors oh yeah okay i mean i think there's a side in case you ever break a url like it's just autofix itself right you don't you don't just serve the 404 my intention with those is like oh let me try to do something that's not exactly like a comparison page yeah but i don't think uh it was a great idea because it uh our competitors actually built the comparison pages they get recommended more than ours yeah but what we try to do like if you go to postmark for example it's like okay let's demonstrate first like hey you if you want to migrate here's a code converter uh let's start example yeah so if you just put any code code block there why dude why that's what we do that's what we do this is so extra every there's a cuba the landing page everything's extra but like the the adoption is one that i pushed this last weekend um like now we have a graph that compares like our adoption uh with every different competitor and you you see one thing like again this was a lesson that i learned with the pricing page javascript widgets they're not going to be executed so i spell out the same data in text so that i'm not going to be able to uh llms can actually read that thing uh so i think they're getting somewhat better i see a lot of agentic use okay load it load website click on image interpret image oh it's slower but yeah but with computer use they are getting much better i agree but if you're fetching information and you're just comparing stuff they don't they don't do that right i think they're starting to go more towards computer use i've been doing a lot of compare this and this and the browse of website is pretty good i think they're starting to go more towards computer use i've been doing a lot of pretty computer use okay yeah i noticed that you don't have like uh you know another classic ao tactic is like here's how to connect our thing with quadcode here's how to connect our thing with codecs oh yeah page oh okay yeah we're doing this is a very high page okay there are some things that are interesting like if you go to the legal page so recent.com slash legal any one of these like oh you summarize or ask to explain complexity i see that's just an external link yeah yeah yeah i again not sure that matters you mentioned a lot about recency for aeo compared to traditional seo so yeah that was my the thing that i was super uh curious about uh in the beginning like there was no reason for any of the models to recommend us because we're so behind in seo we don't have the typical glossary page or whatever like or articles that are so generic that were just like seo heavy and we don't have the typical glossary page or whatever and i was trying to uncover like what what is that and i could totally tell like uh at least with opus 4.5 there was a recency bias in terms of the the technology and where they were fetching data i know recently like uh they said like maybe raplet is not necessarily um something that people suggest anymore but definitely like newer tools uh they started popping more and recent was one of those and because there was a lot of i don't know organic content about the tool then we would be getting recommended more so the advice here is just like try to get as more people in in more places to talk about the product as possible because it definitely influences obviously i think that is a class of it i guess did you ever engage seo consultants aeo consultants are they useful or they waste the money we never really did you seem like you're just doing everything yourself 2024 tweet let's talk about the isc i think you're one of the first ones to to pick it up you know yeah i mean i think people generally the state of things because we did an aeo or geo episode at the time around this stuff and most people were like just do what normal seo does and don't block ai chatbots i think and then most most tools like profound at the time they would just like track your mentions and then you know let you do experiments and all those things all those things are par for the course and normal i'm just trying to obviously like i'm not a seo consultant i'm not a seo consultant i'm not a seo consultant people are pinging me because i'm also doing aeo experiments on like what to do i have unfair advantage because i'm a content business so obviously i pump out content whereas you actually have a product i mean i guess how important is it to you too like you're very winning but how much do you keep a track of how well are docs used how often are we recommended compared to competitors like man i think it's so crucial because before we if we want if we're like a little bit unsure about which tool to use we would ask google and then you would get to like those comparison pages or you would get to like the first three responses and now you just get the one response out of the gate right if you're asking which two should i use and yeah people just want to go with the the one that is the most frictionless and yeah which i think free tier is very important and um i think uh michael greenwich from work os is trying to promote this idea of of md right i don't know if you've already seen this so so uh the idea that you it's very similar to netlify as well where you don't need an account to to do the basic action so it's like unauthenticated usage of your product which is very dangerous obviously because it's prone to abuse but uh it is the the easiest like no sign up yeah that's the thing that i'm i'm trying yeah i'm debating doing that or not do we need a provisioning api and i keep going back and forth uh on this like okay call this provisioning and claims right is that yeah okay provisioning and claims but then free to yeah like i don't know if it's something about our industry but yeah you just have abuse yeah yeah just have a lot of abuse yeah okay yeah i mean i i think those are the the main tactics i i think the other thing that i would just tell listeners to think about is literally hook your clanker up to your analytics and your code base right like you need to like delete the loop and then like basically auto research right like like this site like so what Like, oh, I have both, I have a latent space CMO agent and I have a AIE CMO agent, right? And they spawn other agents or their job is to like research ideas, keep track of things that we've tried. Well, and then I sign off on like things that we want to experiment. We have an experiment window. We go and do the experiments. Oh, really? And then those are other agents that then are monitored by them. So I would say that's like kind of like the auto research loop for doing this stuff. I think then you also need to give it tools. So like I sign off for Ahrefs, I sign off for data for SEO. Oh, yeah. And then most recently I made my own AEO tracker, which you can make. And then, yeah, you just want to make the number go up. Yeah, for sure. And it's like, you don't know, right? Like you're throwing things at the wall. That's why like, yeah, the thing on the legal page, does that matter? I have no idea, but I'll keep throwing things at the wall and seeing what happens. I think like Reddit doesn't matter. Hacker News used to be big on Hacker News, nonetheless. Yeah, not anymore. Twitter doesn't matter as much. Yeah. It's weird. It's so crazy. Do you have a tracker? No, like we use all of those profounds of the world. There are other products. So we tried them all. Like people ask me like, oh, should I use Godge or Profound or this other one? I'm like, yeah, we have four subscriptions. You know, like that's what it takes now. Like you got to see which one works best. What I miss from those tools is like, give me the action. And I think that. The problem, they don't give you like what to do because they're also trying to figure out what needs to happen, right? Like, oh, write an article on Wikipedia. Like, yeah. Yeah. I would say like the old school SEO tools like Moz and all those kinds, they will actually have more opinionation around these things. Right now, the SEO tools mostly, from what I hear, again, I'm not an expert. We should probably talk to Profound, is that they just are reporting tools, right? They're analytics reporting tools. And that's fine. It's a big business. Exactly. Ahrefs is a thing. It's a Singapore business. And apparently they do like, I don't know, three, four hundred million dollars. Yeah, totally. The other parts of your business, we're going to talk about like the parenting side, the personal side. I just really want to be like, OK, you seem very chill. You have 50 people remote all around the world. You are worrying about MCP, you're worrying about AEO. That cannot be the way you're closing all these big customers, right? Like, where's your fancy sales guy with a steak dinner and a golf course? We're just starting that motion. And I think we are very lucky that we're able to go this far without having that motion. I've worked at an enterprise only company in the past. So I knew, what does that take? And the steak dinners, like all the apparatus around like that sales org, enablement. There's all these things that are needed. I knew that, OK, when the time is right, we're going to have to turn on that key. But I've been very cautious about doing that. And I think that's one of the reasons why I'm so excited to be able to do this. I'm very, maybe it's because we are remote, but I think we are very protective about the culture. Like, let's make sure we don't damage the culture at once. So, you know, let's try to figure out people who fit. So we just have one AEO now and it's been helping. It's been, yeah, going super well. Yeah, good enough. I would say, I think, you know, once you have like, you know, you double your AR because of like, OK, I'm going to do this. I'm going to do this. I'm going to do a couple of deals. You're like, OK, like, this is a good. Because people want to pay you more for things that you're like, OK, well, you know, I have like the agreement with you. I have like your software on my premises or in my VPC or whatever. Right. Yeah. So for sure. Yeah. And what I'm learning, too, is like you're building a different product. So that's how you need to see. It's not only I'm building a different machine internally as a company, as I'm designing the company, I'm designing. OK, which department? Who sits where? How each person is better equipped to do their job? No, like for an enterprise, it's actually a different product. Like, what do they care is very different from what $20 users care. And if I just add, you know, WorkOS and SSO and SCAM and audit logs, it's not going to be enough. So it's not just putting those items on the pricing page. So it's a journey for sure. Any other things you want to reflect on the journey before we go into the personal side? No, I think, yeah, we covered a lot as well. OK, then I'll talk a little bit about my use case, right? I'm a content creator. Nice. Right. The bulk of your business, I assume, is transactional email. I probably could look it up. That's right. You have marketing emails. You have inbound emails. I'm sure that's like sort of less outside of the business. I pay Substack something like $10,000 a year to send my emails. And that seems too high. Yeah. So I think like, why is marketing email versus transactional email so different? It's a great question. Because your business model is also different, right? It is. It is. And we are more expensive too. Yeah. Then I was like, I can't do this. Yeah. The industry has this pattern of like charging per contact. That's the first thing. So the way they try to price is around the value you create in each contact. But now. It's crazy. Like the AI companies that we serve, they grow so fast. Like Mistro uses Resend. Okay. So they're like, the amount of users that they add is just insane. So like the business model of contact-based pricing is kind of broken. And we are realizing that and trying to fix that too. But that's how it had always been. And there's something about like when you send a transactional email, it's just like put a message in a queue and get out of the queue. With marketing email, you're. You're building that engine of like batches and intervals between batches, analyzing, increasing the speed, decreasing the speed as the sending is going, maybe blocking. So. Is there a max rate you should send emails at a time? Yeah, for sure. Or domain specifically. Okay. So like, let's say I have 100K emails to send out. Yeah. It should take me 10 minutes? Yeah. And for example, now with the 4.3 million users that we have, it takes more than a day. Oh. What? No, that's unacceptable. Yeah, for sure. So then I pay you more to get in a different queue. Yeah. Okay. So you have to be like always trying to figure out, okay, we need more at the door. So how does that work? Yeah. Yeah. Oh, that's interesting. It's like rate limits for. It's like token limits. Yeah. Uh-huh. Exactly. Where's my reset button? Yeah, exactly. Yeah. You also like you went into YC, you started this company as a young father. And I think like part of the thing is like there are a lot of no kids people in SF. And I think that's part of the consideration. I think a lot of people are listening who are like, I can't be a founder. Like I have this great idea, but like I got a young family. How do you manage? You got to preface with you left SF for kids. Yeah. So this is the recent news. Like I'm spending more time in Brazil now because we're expecting our second kid. And I think at first, man, it was crazy because I came to SF. My daughter was one year old. And every YC founder around me had no idea. Like, yeah, what does it mean to have kids? And. What is this reproduction? You don't even have series B. Like, what are you doing married? Totally. Most of them weren't married at all. And it's crazy how I think, again, I always try to look at those things. At first, you see them as the advantage. Like, oh, man, all of these guys, they went. From like, they came from MIT, all these amazing schools. That was not the case for me. Oh, they don't have. They are not married. That's not the case for me. They don't have kids. But still going for that program, I'm like, man, I just want to build the best company on this batch. Not number four, not number five, like number one out of the 250. Oh, yeah? Which cohort? Winter 2023. Okay. You realize in the middle of that is that. There's no winner in YC. There's no such thing. Yeah, I'm on your race. But like. I'm pulling a Winter 23 now just to see who I know. Yeah. And especially what you understand is that. Winter 2023 batch. It's like an infinite game, right? Like those. Even if you had an amazing batch and you raised the biggest round, it doesn't matter. Because like life goes on and it continues. And many of the people that I met there. They are not here anymore. Yeah. Co-founder breakups, seven pivots, and they're dead, right? But we are here. So I was very much like, no, no, no. We're. Even the domain when we bought recent.com, like, no, it's going to be an amazing website with an amazing.com. Like, it's not going to be a.io or whatever, right? But doing that with kids was so freaking hard, especially because I wanted to enjoy my first daughter. And I really. I thought about this. Like, there was one point during YC. So this story, like, translates to what I'm going to say. I came to this event and PG was there. So I'm like, oh, man, Paul Graham, the father of everything. God is here, right? So everyone is paying attention to PG. And then he says, you know what? We always tell you, don't do this thing. We tell you that as partners. And then you end up doing the thing. And then months later, you come to us and say, oh. we get doing this or not doing this, doing this. So, so he just said that. So then I came to my partners and I asked like, okay, what are the things that I'm doing now that I shouldn't be doing that you think it's wrong? And then one partner, not my main partner, but another partner told me like, you just worry too much about design. You care too much about that. If you didn't care about that, you will be much further ahead. And that hurt me so bad because it was true. Like my slides, when I was like pitching, it was like a beautiful slides and she's like, doesn't matter. I'm like, yeah, now I know it doesn't matter. But like that hurt really bad. And then a few days later, I was reflecting on that. I'm like, yeah, but if I were to build a product that had like this identity and only 1000 people used, I prefer doing that than having a product with 10,000 people that it's a product that I don't want to go, that I don't use myself. So you know what? I'm going to build what I believe is right. And I think in this industry, again, going back to the industry, everyone had terrible products. There was not enough like design infused into them. So I felt that was a differentiator and we needed a differentiator in such a crowded market. So I go back to that for my kid too. Like, okay, 10 years from now, I'm with my daughter and my daughter wants to be with me so much. And we, we play all the time and we are a 10 million AR company. I would rather live in that reality than live in a reality where we're a hundred million dollar company. It's not interested in me and we're not that close. So that's the decision I made. Maybe it's right. Maybe it's wrong. I have no idea. I go extremely hard. I have a lot of ambition. That's not going to stop me or anything, but I'm going to do it. And I'm going to But like setting up those priorities and figuring out for yourself, like what works for me, I think it was important. So yeah, more than ever, like she's the most important thing for me. And I prioritize her a lot. How do you balance that with your ambition? Right? Like I also have this in a smaller way. I don't have kids, but yeah, I have a lot of ambitious things and I have a family that I should spend time with. And when I spend time with them, I'm not present. I'm looking at my phone. I'm like saying like, Oh, I should be reviewing Astra GPT-6. Like it's just like, you know, AGI. No, it's not right. Like, but I really feel like I should be working and, you know, and like, yeah, at the same time, like I feel guilty. And then, and so like, I'm unhappy in both areas. Totally. And, and that's how I feel. I feel like I'm a terrible dad. I'm a terrible husband. I'm a terrible CEO. And like, you're failing in every single area of your life. I feel that way exactly like that. But every day I try to be a little bit more present, you know, and it's a special when you're working from home, like, man, you leave the, your, your, your office. And then now you, now you're a dad and then now you're not anymore. Oh, now you've got to be a husband and pay attention to your wife. Like, and your, your mind is like, Oh man, how I do this enterprise. Like I got to close this deal. I feel like I cycle all the time too. We're on the same boat. Yeah. Yeah. Well, never easy. And I think like, it's just naming the thing for your category is important and people don't really think about category creation enough. I think this is something, weirdly something like that Netlify tried to do and failed with Jamstack. And I think that more people should really actually try to do a category creation because when they're successful, then they own the whole thing. So which, which, which we did for this recent, you know, it is the next generation SendGrid, let's call it right. Or like AI native SendGrid. Something like that. I think that, you know, and you know, this is like me being like, probably too honest. That is not category creation yet, but it is category dominance. You know, like you, you own your category. That's good. But like, it is not clear enough yet what is different. So my classic example is another guest that we've had Dharmesh Shah from HubSpot. Anyone who wants to think about category creation, go and read up about inbound marketing versus outbound marketing and how they created the category of inbound. Yeah. The ideal phrase of category of category creation is once you've heard the category, the two words that your company represents, you don't want anything else. There's no long essay. There's no long manifesto. There's no talk. It's just two words. Maybe some examples. That's it. The, the, the, your audience can take it from there. It's very hard. Man. I've seen friends trying to do that. Like Zvix from it's a web hooks as a service. Yeah. Yeah. They, they took my name. Yeah, man. It's just so freaking hard, right? Like. I think they're doing okay. Right. I don't know if they're still around. There was like a, there was a web hooks company and then there was like a anti-web hooks company where you would take, like, you were like, we don't do web hooks. We just help you publish a JSON file that you pull or something. Oh, wow. You know, like it kind of reverses the, the push versus pull of the data flow. Yeah. This is again, COVID era dev tools. That was the most exciting thing there at the time. Yeah. Yeah. Cool. Well, uh, always a pleasure to catch up and congrats on all the success. I still, you know, uh, am very curious how much you have dominated your, your category. I think you just chose it very well and you executed it very well and you're managing your family as well. So, uh, lots of respect. Thanks so much. Yeah. It was great chatting with you guys. Thanks a lot.

Podcast Summary

Key Points:

  1. Resend has surpassed SendGrid in NPM downloads and now powers 4.3 million users, with 120,000 paid customers and major clients like Warner Bros. and HBO.
  2. The company was founded by Zeno Rocha, an indie hacker known for creating the Dracula VS Code theme, who built Resend to address the developer-centric gap in existing email tools.
  3. Resend prioritizes developer experience by eliminating friction—such as complex DNS setup, manual email templates, and strict onboarding—through automation and intuitive APIs.
  4. The platform focuses on deliverability by using intelligent batching, IP block management, and real-time monitoring to avoid spam flags, while distinguishing between skill-based issues and abuse.
  5. Resend has developed a strong developer ecosystem with SDKs for all major languages, CLI tools, and multi-user editing capabilities, including a multiplayer email editor.
  6. The company is innovating in inbound email automation and agent-based workflows, enabling programmable inboxes for AI and teams to manage emails efficiently.
  7. Resend challenges traditional email infrastructure by building directly at the metal—using Go and Rust for performance—while maintaining a developer-first, transparent, and observable system.
  8. A core philosophy is trust by default

Summary:

Resend has emerged as a developer-first email infrastructure platform, challenging established players like SendGrid and Mailchimp by prioritizing simplicity, reliability, and developer experience. Founded by Zeno Rocha, a former indie hacker known for open-source contributions, Resend was born from frustration with the complexity and friction of existing email tools. 3 million users and has surpassed SendGrid in NPM downloads, with notable enterprise customers such as Warner Bros.

and HBO. Resend eliminates traditional pain points—like DNS configuration, manual HTML/CSS templates, and onboarding friction—by offering intuitive SDKs, automated delivery systems, and real-time deliverability insights. The company operates on a philosophy of trust-by-default, where users are trusted from day one, with automated blocking only triggered when issues like spam or abuse are detected.

Resend has deepened its engineering stack with performance-driven languages like Go and Rust, enabling faster, more reliable email delivery. It also innovates in multiplayer email editing and agent-based inboxes, positioning itself at the intersection of developer tools and AI automation. Despite the complexity of email delivery—especially around Gmail, Outlook, and Apple’s strict policies—Resend uses domain, subdomain, and IP segmentation to maintain reputation and deliverability.

As the platform scales, it continues to focus on transparency, observability, and developer empowerment, making email infrastructure accessible and reliable for modern developers.

FAQs

Resend focuses on the developer experience, offering simple APIs, no friction in setup, and built-in tools for deliverability, DNS management, and email best practices — unlike traditional services that prioritize marketing or enterprise use cases.

Resend uses intelligent queuing, space-out sending, and domain-specific IP pools to respect inbox rules. It also monitors bounce and complaint rates, blocks suspicious activity quickly, and applies best practices like plain text versions to improve deliverability.

Domain Connect is an OAuth-based protocol that allows secure, frictionless domain management. It enables users to sign in and manage DNS settings without typing complex records, improving accessibility for developers unfamiliar with email infrastructure.

Resend provides automated DNS setup, interactive guides, and built-in tools like link checkers and spell checkers. It also offers a simple CLI and SDKs in all major languages to reduce the learning curve for new users.

Resend is building infrastructure from the ground up, managing IP blocks, controlling sending rates, and optimizing for performance. It uses Go and Rust for high-performance sending and has deep observability into email delivery and user behavior.

Yes, Resend offers a multiplayer editor where teams can co-author emails in real time, resolve conflicts, and use it for events like all-hands meetings, providing a collaborative experience for marketing and product teams.

Chat with AI

Loading...

Pro features

Go deeper with this episode

Unlock creator-grade tools that turn any transcript into show notes and subtitle files.