# Resend's Strategy: AI-Native Email Infrastructure

**Podcast:** Latent Space: The AI Engineer Podcast
**Published:** 2026-11-10

## Transcript

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 recent, 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 hundred million dollar 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 are, 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 about that round.
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 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 undersell just an indie hacker.
Top 20 most active GitHub under 2022.
Very, very active open source dev.
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 recent, but yeah, but it's been nice.
Like there's a, yeah, it's changing.
Yeah.
What was the...
impetus for, I guess, picking email.
I think people always have, obviously, React email and all those things.
I just don't know if I would have made it a company.
Yeah.
If I knew how hard email is, I probably wouldn't start the company either.
Were you primarily JavaScript front-end?
Totally.
CSS, like...
I was a front-end guy.
No infra, right?
No email background.
HTML5 guy, you know?
And I think what was interesting and what drew me to it is, like, I just look at all the tools around that, and I've used all of them before, the mail guns, the mail chimps, the send grids 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 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 the stripe of email how would that look like um 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, logos, anything?
Yeah.
So Resend now is powering 4.3 million users as of this morning.
We have all sorts of customers like Warner Brothers, HBO.
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.
And the endless local wall.
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'll 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 nice.
naive thing you can do.
Like, let me look at the domains and let me just filter by .coms and filter by the small ones.
And there was this domain, WBD, Warner Brothers Discovery.
I didn't know.
What is WBD.com?
And I was like, oh no, Warner Brothers is using us.
So yeah, I just love featuring customers and yeah, pretty good.
Specifically for listeners, one of the reasons I reached out for this interview, one, you know, I should declare up front, I am an angel.
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?
And I was like, okay, yeah, seems right.
Honestly, like...
In terms of the pitches I get, I've invested in about 30-plus companies.
That was one of the most straightforward things ever.
And then secondly, I don't like to add API keys.
I like to have everything on one platform, one API key to cover everything.
So Cloudflare has built-in email.
And I had a project, and I set up my Cloudflare email domain, DNS, all that junk, DKIM, what have you.
I don't know all the Alphabet Super stuff.
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 fuck 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, okay.
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.
Yeah.
Every generation, you have those tools that define that moment, right?
We remember the Heroku days.
I mean, another 5% you know.
And so to me, it 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, okay, 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, okay, so you said you had no idea why 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, okay, 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.
It's different from like when you're scaling just like an app where you throw GPU at the problem or you just scale more vertically or horizontally, whatever it is.
With email, you 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 contacts.
But what we found early on was like, okay, we knew nothing about this world.
And so, and coming from this perspective, like extremely naive was the best thing that ever happened.
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 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, 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 they want to see the engagement so what do you do is like they see like okay are people opening the emails are people archiving deleting right away or not interacting okay depending on those initial interactions then what i'm gonna do with the rest of the emails will dictate that that beginning 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 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 got to look at the history of the IP blocks, distributed folks into different IP pools, and then balance the IP pools over time.
So it's a 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.
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 trial 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.
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 email in general is you need to do exactly what an abuser wouldn't do.
It's the opposite of that.
So what's an abuser do?
They buy a domain.
We have now, like there was a Japanese gang that recently came.
They brought like maybe 20,000 domains at recent.
Like those are 20,000 different TLDs registered in different domain registrars.
And we look for every single factor there.
So they come in, it's a domain that was bought two days ago.
So very new domains, they get bad reputation.
Then 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 looks like you're phishing, right?
Like because 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.
You kind of got to reverse engineer how phishing works and build a platform that does exactly 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 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 you're 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 HTML 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 before.
Let's just generate, auto-generate 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.
Most people don't do that, but we're like, oh, this makes sense.
But with plain text, there's no tracking, right?
There's no tracking.
Because you can't embed 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 industry, there are two ways of tracking, right?
You have open tracking and click tracking.
Open tracking, what it does, it includes a one-by-one GIF image, a transparent image.
And then if that image is loaded, then you detect that as open.
The problem with that is that all the changes that Apple did recently in terms of transparency and data privacy, like they read the emails before it lands, if they're doing the summaries and all those kinds of things.
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 checking that before.
So then you rely on click tracking.
Now, click tracking can also be difficult because 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 these domain bits.
I feel like I have used email services that would rewrite, like for the link tracking, right?
They would rewrite to their own domain.
You're saying that's bad.
That's bad because what happened, we did that too at first.
I thought that's normal.
Yeah, but what's bad is when 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 that blacklist.
Then you're screwed as a business.
Is that not 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, but you're able to avoid.
And this is why?
Yeah, I think what was different to me, and then this is more like a philosophy, right?
So I saw 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 got to 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 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?
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...
Different shape.
Skill issue.
Yeah.
It's a skill issue.
Exactly.
It's a skill issue.
I think we learned we have skill issues too.
We wouldn't have expected.
Yeah, 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 fun page.
Literally your philosophy as you called it.
I got lost just reading around this and then there's like a call, you have a pledge that you will make email safer.
Like, If you're interested in this stuff, you know, you have quite a bit up here.
Okay, so actually, I do want to, there's a how we scale support there.
I think this is, you remind me of another investment that I had, Jake from Railway.
Yeah.
Because also another like.
Very, very permissive, very developer-oriented, but also you have to scale support.
Because the moment someone gets blocked, they come to you and say, hey, don't keep me off your platform.
How do you scale support?
Man, I think if support was a software, we're probably on major version four or something.
Like the very first version was like 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 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 talk about.
So one policy that we set, it was pretty cool actually, is like you can only respond to a ticket with a link.
So you cannot just give the answer right away.
You had to stop, write a knowledge-based article, write a docs.
And then, so it takes like an hour and a half maybe for you to answer a ticket.
guess what now you're sending that link all over again so that was super cool and it helped us build that knowledge base but even so like after that we when we crossed maybe one million users so we had one million users back in december and now we have four so i can't throw people at the problem but that's just not going to solve it right like i'm just going to 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 that free tier.
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.
If it wasn't for Heroku's free tier and all these other products, we wouldn't be here.
So I want to keep Risa in that way, but it took us many iterations to get to it.
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 K with just, you have docs, you have a model, customer service plots exist, right?
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're 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 C name, 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 records.
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.
And...
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 is...
Yeah.
So for listeners, if you're not familiar, if you haven't tried it, something like that, it's literally like you use Plaid or you use OAuth.
You only click buttons.
You don't type in anything.
There's nothing to get wrong.
You basically just sign in.
As long as you trust this thing called Domain Connect, which you have confirmed that it is legit, then it's trust.
Literally, I used it for the first time two weeks ago.
I was like, what is this?
I've never seen this before.
So it's really cool.
One of the things that I'm trying to figure out as well is how you start this company.
Like you said, you tried to get in touch with the IONOS guy.
I'm like, I wouldn't dare to start Resend without knowing, like having some guy on the inside at Gmail.
Even now, it's like, okay, can we Vibecode our own email thing?
Clearly no, but that's even with tools today.
You did this years ago.
you want people at domain res, like you need the guy, right?
But you need to pick up the phone, right?
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 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 just...
Yeah, software as a service.
You had a little bit, right?
You made React email the year before, so you did dip your toes in open work.
Yeah.
And then came the company.
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...
Gary V.
Yeah.
And if people are like building the email template using React.
Like now they'll need a platform to send it.
Where do they do that?
Here's Resend.
So it was 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...
We started Resend and as we were building Resend, I was like doing a lot of user research.
And people are 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 mess.
And so to me, the reason that React works is that it is basically a compiler.
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 pushed 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 used as a function of state.
Yeah.
So it's mostly JSX is 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.
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 some of these names.
What do you learn from them?
If you have any cool stories?
Just anything, you know?
Man, so much.
So much.
I remember the very first year of Resend, I was like, I gotta meet the founder of Mailgun because I was still a user of Mailgun.
And I talked to Ev.
He built...
Oh my gosh.
Blogger?
Medium?
No, it's a different product.
But anyways, like he, it's a security product 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, Like, I don't want to live in that world at all.
So I was very worried about that.
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 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.
SendGrid has always been my favorite out of those ones and always been the behemoth, like the biggest.
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 a number of downloads from SendGrid and I was like...
That's insane.
And now we're more than double.
So in terms of unique users, or what's the number?
NPM downloads of the SDK.
Is that the best metric?
Yeah.
I think there's something about that metric in terms of adoption.
But then if you look at how many emails they sent, it's obviously much more than us because they have 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 you are no longer an email service.
You're a communications platform, right?
You integrate across everything.
It's not just about cross-sell.
It is about I can reach you across multiple channels, something like that.
Or that you have the size, you know, Twilio is like, I don't know what the size is now.
Let's call it a $13, $15 billion company.
You should have all the relationships, all the talents, all these things, right?
How do you compete with that?
Yeah.
Man, I admire Twilio so much.
They kind of invented DevRel or...
Yeah, ask your developer.
You know, ask your developer.
And now when I go past that one-on-one billboard and I see a customer AI or whatever, I'm pissed.
I'm like, why?
Like, you neglected the thing that got you there.
And I think 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.
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?
Yep.
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 make a better product and you can slowly...
For sure.
And I've always thought about too, like why did Twilio acquired SendGrid and not the other way around?
Twilio was bigger.
I mean, SMS.
Yeah.
But like if email and communication is a commodity, like SMS, your margins are even...
It's worse.
Even worse.
Have you looked into SMS?
Yeah, for sure.
I think one day.
What are the channels that matter?
Email, SMS, what else?
WhatsApp is big in many other countries.
You don't pay anything.
Yeah, but then you've got to go through meta and now business messages are going to 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 never take any robocalls, 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?
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.
Nice.
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.
Mm-hmm.
Which is cheap.
Cheap.
I don't know what you would cost.
Yeah, more than that.
So basically, to me, it's just like the low-cost player, right?
Yeah.
I mean, it's Amazon.
They're super established.
What do you take from them?
And then what should people know to stay away from them?
We started with SES, too.
We knew that, okay, if we're going to be innovating here, I wanted to innovate on the DX layer because I felt like that was the underserved space.
Let me have SDKs for every single language.
I remember with Serval as we highlighted service 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 DX.
So we started with like the most high level layer and that served us really well.
Was able to like scale because we were using SCS 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've got to build another thing.
So if you go with SCS, 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 area is Agent Mail.
And then I talked to the guy as well and he was like, yeah, we're going to build on top of SES and not really compete with them.
Yeah, but for us, it's changing that now.
So we are 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 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 that.
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 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 an email goes out, is it really delivered?
Is it really on this platform?
Is it 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 too.
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 infra.
And then once you get size, then you can actually build your own infra, right?
Yeah.
Are you doing anything differently because now you own everything?
Yeah, I think what we're doing is...
And by the way, obviously your 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 spent 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 Node.js shop and we have like just...
TypeScript everywhere.
And most recently, like the sending path, we no longer use JavaScript.
We have Go there.
And we're changing other parts to be more performative in other ways.
Because now languages don't matter.
Exactly, right?
It's just so cheap to pick a problem and you can rewrite the whole thing in whatever the first language is.
I'm running Rust projects and I don't really know Rust.
I know some theoretical things about Rust, but I've never really bothered to learn it.
I feel like we are 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 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 really think about these problems as like, okay, how do I want my product to be?
Well, I want my product to be formless.
Whatever they want to do with the product, it should be possible.
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.
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-to-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, 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?
It's like so hard to set up MCP.
This was last year.
And then...
Yoko.
Yeah, exactly.
And so she built that.
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 OAuth.
And then we were like, okay, now we have a blocker.
Let's build OAuth.
So then we build OAuth 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 OAuth.
And then after we had OAuth, okay, now we have the remote MCP and then it's distribution.
So then, okay, now we have the remote MCP.
Okay, great, great, great.
Observability is in place.
Great, great.
Okay, all the data dashboards.
Okay, now.
all in, let's talk to everyone.
And that was hard too.
Like, it's not as easy.
I wish I had all your connections.
It's not as easy to me.
You're supposed to talk to me.
But like talking to the labs and trying to get into like the official stores and plug-in marketplaces.
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.
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 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 we had this, like we were using Plausible and Pulse Hogg.
Plausible had an MCP built by Sentry.
I don't care.
If the Plausible doesn't maintain that and that's not official, I cannot trust that as much.
Even though I love the Sentry team and 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 Pulse Hog here because I have the MCP there.
And I did that 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 have an MCP, but you have to connect like this, like the X MCP, for example.
I have to do like the local one.
It's just so frustrating.
It works on the desktop line, not on my phone.
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 interact with that, it's always collapsed, right?
The two calls, I'm always opening and trying to understand what did it do.
And just a couple of days ago, 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 just adding more to the MCP.
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 long tail of like 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 100.
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 really hard.
Like, it's a difficult problem.
Yeah.
In fact, you know, you are one of the few Linux-based guests that 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 Pages API or Apps API.
they make it easy for you to basically bind data to your page.
So you never expose a public API.
So by default, the thing that is performance and they encourage you to do, you will not have an API.
Then you have to just do like separate code paths or whatever.
In fact, you should just always have like completely headless backend.
And then your front end just happens to be one of many clients that connects to your backend.
We started with our API on Next.
I remember that.
First of all, the build was just so high that we were like, there's no way we can pay for this.
So then we moved to a traditional node server, server four, whatever you call it.
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?
Now it's so much better.
Everything on a monorepo, you can reuse stuff.
Yeah, like by default, ideally those frameworks like just gives us those components, right?
We had to build a public API separately from...
And it sucks to maintain both.
Yeah.
Okay.
And then one more thing about just the NCP front.
So, you know, so you are, you've got 80 tools in there.
You're growing more tools.
You are very counter consensus compared to Cloudflare, which only has two tools.
Search and execute or something like that.
So far, you haven't felt that issue.
But what would make you change your mind?
Right?
Like 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?
I do try to get a lot of feedback on that.
And then the way I like to build products is I got to use the product on my own, right?
So if I'm...
Like the investor update that I sent you yesterday, that was built using the MCP, you know, it was like fetching data from one place, from another place.
And then...
You're making me 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, 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 try to apply for a job.
And you have those to go down now.
You have three ways of applying.
You can apply via CLI 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 at recent.
Okay, so you are filling yourself with slop, especially in careers.
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 people are going the extra mile, like setting that up like, oh, no, I got to download this thing and I have to authenticate and then I have to go through 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 job applications.
Even API, applying for one job through API.
Exactly.
I mean, it's the same thing as UCLA.
Yeah.
So I think one of the things that I'm trying to figure out as well is product philosophy, right?
You're clearly just max everywhere.
Every SDK, every language, every 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.
It's your job application.
You're not going to 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 I'm trying to optimize not only for the privileged users, like the users 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 with a terrible Wi-Fi.
Brazil.
Brazil.
Growing up, 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 don't have the free tier because of the, you know, like there's a reason behind it.
When we have all the SDKs, so I'm maxing on the SDKs, man.
Building the .NET SDK, do you think that was fun?
Like, and we looked into...
Stainless.
Stainless, Fern.
What's the third one?
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, 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 400 people.
Wow.
You know?
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 piled.
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 fixes 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.
I feel like 99% of people have not thought about multiplayer email, right?
But yes, 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.
I try to tailor to those different audiences and build a product that feels that we care, which is not the feeling I get elsewhere.
Yeah.
By the way, what does the Resend team use to read email?
Superhuman?
Yeah.
Oh, man, that.
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 other interests.
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.
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.
Honestly, like Instinct now super hot, $2.5 billion company with no revenue.
And like, it's just like people trying to read email 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.
Here are the APIs that you need on top of that, right?
So you need a read API, markers and read.
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.
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, 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% 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 of...
Apple is not that big.
Apple is big, yeah.
And especially with the privacy thing that they did now, it's harder.
You can have to sign up to an Apple.
What?
Sorry?
Yeah, like Apple auto generates an email address for you.
Oh, yeah, yeah, yeah.
Yeah, 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 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.
That's kind of the...
We can have the most beautiful Rubik's Cube in the website, the coolest handbook ever if it's down.
Yeah.
It's all for enough.
And how correlated are they?
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 emails 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 is this stuff you manage?
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 is like, 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 advice.
I have to buy a separate, so because we use AI.engineer and Dayton.space.
These are all like weird TLDs and 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 you're 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.
Yeah.
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, it 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 create content that isn't...
action and answer, ask and answer type of format.
So a lot of FAQs.
Now, almost every page at recent has an FAQ, you know, like, you know, go to pricing page or like, yeah, of course, pricing almost always has an FAQ.
This is pretty standard.
Yeah.
But 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 of like all pages have that because that's how people are asking.
Is recent SOC 2 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 Mintlify 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 markdown versions of the docs.
I'm going to do markdown versions of every single page on the website, on the marketing website.
Using content sniffing or you just append like .md?
Yeah, just append.
You do append.
So if you go to the security page, .md, it will work.
But also if you do content negotiation with that page, 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.
I mean, you're winning really well.
Yeah, I think one example that changed, and maybe it doesn't help with distribution, but it 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 Resend, and you did that with X and Y and Z competitor, who is the cheapest and who is the most expensive.
And it got completely wrong.
It got the recent one like so bad.
And 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.
So it was like super frustrating.
Oh, so you made a calculator.
Yeah.
So the problem was, you know, agents don't really...
drag a JavaScript widget.
Okay.
So then what I did was the .mt version of this page, which has a tremendous amount of access, by the way.
Like now, like...
I see, you get analytics on this.
Yeah.
Yeah, yeah, okay.
Not through the regular analytics spots, too, because like we cannot track that.
Yeah, it's the server side.
So then like we got to go to Datadog to figure that out.
Oh, okay.
And man, it was really crazy.
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 already...
It's a good way to live update and fix stuff in your search.
Exactly.
And this is what matters, right?
Like, okay...
But 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 the...
That sucks completely.
But again, if I wanted the happy path and the easy path, 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.
You know how to do this.
What else?
We talk baselines, basically have FAQ everywhere, basic SEO stuff.
Comparison pages?
Us versus SendGrid, us versus MailChimp.
Although our page could be much better.
Go to...
Yeah, notice it's not there.
I mean, I'm sure you have it somewhere in some footer or something or whatever.
Yeah.
Just do slash migrate.
I can give you some...
By the way, 404 pages, I always think we should guess.
Oh, interesting.
Take the slug.
Yeah.
Near his neighbors.
Oh, yeah.
Okay.
I think there's a side...
In case you ever break a URL, it'll just autofix itself, right?
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 it was a great idea because our competitors actually built the comparison pages and they get recommended more than ours.
But what we try to do, like if you go to Postmark, for example, is like, okay, let's demonstrate.
First, like, hey, if you want to migrate, here's a code converter.
Is that an example?
Yeah, so if you just...
put any code block there.
Ooh.
Why?
Why, dude?
Why?
That's what we do.
That's what we do.
This is so extra.
There's a cube on the landing page.
Everything's extra.
The cube's been left to do.
But the adoption is one that I pushed this last weekend.
Like now we have a graph.
that compares our adoption with every different competitor.
And you see one thing, 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 LLMs can actually read that thing.
I think they're getting somewhat better.
I see a lot of agentic use.
Okay, load website, click on image, interpret image.
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 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 computer use.
Okay.
I noticed that you don't have, like, you know, another classic AEO tactic is, like, here's how to connect our thing with quadcode.
Here's how to connect our thing with codecs.
The whole AI page.
Oh, okay.
Yeah, we do have a separate AI 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, again, not sure that matters.
You mentioned a lot about recency for AEO compared to traditional SEO.
Yeah, that was the thing that I was super curious about in the beginning.
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, or articles that are so generic that we're just SEO heavy.
And I was trying to uncover, like, what is that?
And I could totally tell, like, at least with Opus 4.5, there was a recency bias in terms of the technology and where they were fetching data.
I know recently, like, they said, like, maybe RapLit is not necessarily something that people suggest anymore.
But definitely, like, newer tools, 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 will be getting recommended more.
So the advice here is just like try to get as more people 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?
Are they a waste of money?
We never really did that.
You seem like you're just doing everything yourself.
You're the AEO.
You have a 2024 tweet of let's talk about AI SEO.
I think you were one of the first ones to pick it up, you know?
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 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 people are pinging me because I'm also doing AO experiments on like...
what to do.
I have unfair advantage because I'm a content business.
So obviously I pump up 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 one response out of the gate, right?
If you're asking which tool should I use?
And yeah, people just want to go with the one that is the most frictionless.
Yeah, which I think free tier is very important.
And I think...
Michael Greenidge from WorkOS is trying to promote this idea of MD, right?
I don't know if you've seen this.
So the idea that you, it's very similar to Netlify as well, where you don't need an account 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 it is the easiest, like no sign up.
Yeah, that's the thing that I'm trying, yeah, I'm debating doing that or not.
Do we need a provisioning API?
And I keep going back and forth on this.
Like, okay, call this API.
Provisioning and claims, right?
Yeah, provisioning and claims.
But then free tier, yeah.
Like, I don't know if it's something about our industry, but there's just...
Yeah, you just have abuse.
Yeah, you just have a lot of abuse.
Yeah, okay.
Yeah, I mean, I think those are the main tactics.
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 fully complete the loop and then like basically auto research, right?
Like this side, so what I have now is my cycle.
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 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 signed off for Ahrefs.
I signed 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...
I think, like, Reddit doesn't matter.
Hacker News.
You used to be big on Hacker News.
Yeah, not anymore.
Twitter doesn't matter as much.
Yeah.
It's weird, right?
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 Gauge 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.
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 AO 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.
Ahrefs is a Singapore business, and apparently they do like, I don't know, $300, $400 million.
Yeah, totally.
The other parts of your business, we're going to talk about the parenting side, the personal side.
I just really want to be like, okay, 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, okay, when the time is right, we're going to have to turn on that key.
But I've been very cautious about doing that at recent, like in different layers, instead of just like...
At 20, 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 no, let's try to figure out people who fit.
So we just have one AE now and it's been helping.
It's been, yeah, going super long.
Yeah, good enough.
I would say, I think, you know, once you have like, you know, you double your AR because of like a couple of deals, you're like, okay, like this is a good deal.
Because people want to pay you more for things that you're like, okay, well, you know, I have like the agreement with you.
I have like your software on my premises or in my VPC, 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, okay, which department, who sits, where, how each person is better equipped to do their job.
No, like for 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 of growth.
Oh, okay.
Then I'll talk a little bit about my use case, right?
Like 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 is 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 was just like, put a message in a queue and get out of the queue.
With marketing email, 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.
Is there a max rate you should send emails at a time?
Yeah, for sure.
Or domain, specifically.
So let's say I have 100k emails to send out, 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.
Oh, that's interesting.
It's like rate limits for, let's say token.
Yeah.
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, I got young family.
How do you manage?
You got a 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?
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 it...
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 came from MIT, all these amazing schools.
That was not the case for me.
Oh, they are not married.
That's not the case for me.
They don't have kids.
That's not the case for me.
But still, going through 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, that there's no such fame.
Yeah, a lot you raise.
But...
I'm pulling a winter 23 now.
Let's just see who I know.
And especially what you understand is that...
Winter 2023, right?
It's like an infinite game, right?
Even if you had an amazing batch and you raised the biggest round, it doesn't matter because life goes on and it continues.
And many of the people that I met there, they are not here anymore.
Co-founder breakups.
seven pivots and they're dead, right?
But we are here.
So I was very much like, no, no, no.
Even the domain, when we bought recent.com, I'm like, no, it's going to be an amazing website with an amazing .com.
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 thought about this.
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 ended up doing the thing.
And then months later, you come to us and say, oh, I regret doing this or not doing this.
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 1,000 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 follow.
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 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 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 and my daughter doesn't want to play with me.
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 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, you know, GPT-6.
Like it's just like, you know, AGI.
No, it's not, right?
But I really feel like I should be working and, you know, and like...
At the same time, I feel guilty.
And so I'm unhappy in both areas.
Totally.
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 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, especially when you're working from home, like, man, you leave your office and then 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 mind is like, oh man, how I do this enterprise?
Like, I got to close this deal.
I feel like I suck all the time too.
We're on the same boat.
Yeah.
Well, never easy.
And I think 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 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 we did for this.
Recent, you know, it is the next generation SendGrid, let's call it.
Right?
Or like AI native SandGrid or something like that.
I think that, you know, and this is me being probably too honest, that is not category creation yet.
But it is category dominance.
You own your category, that's good.
But 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.
The ideal phrase 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.
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 Webhooks as a Service.
Yeah, they took my name.
Yeah, man.
It's just so freaking hard, right?
I think they're doing okay, right?
I don't know if they're still around.
There was a Webhooks company, and then there was an anti-Webhooks company.
You were like, we don't do Webhooks, we just help you publish a JSON file that you pull.
Oh, wow.
You know, it kind of reverses the push versus pull of the data flow.
Yeah, this is, again, COVID era DevTools.
That was the most exciting thing at the time.
Cool.
Well, always a pleasure to catch up and congrats on all the success.
I still, you know, am very curious how much you have dominated 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 lots of respect.
Thanks so much.
Yeah, it was great chatting with you guys.
Thanks a lot.