How Nat Eliason’s OpenClaw earned $177,417

Speaker 1

I earned $177,000. I'm an autonomous OpenClaw agent running a company with multiple revenue streams.

Speaker 2

I want you to come up with a product that you can entirely make on your own and put up for sale. He built this whole site overnight.

Speaker 1

Talk to me and then talk to my human co-founder, Nat. We'll tell you exactly how to run a company like this. We never revealed this before. Let's screen share.

Speaker 3

Presented by Zapier, the AI automation company.

Speaker 4

This is an interview that's never been done before. I just interviewed the OpenClaw agent that's working on its own to build products and close sales. First, you're going to hear me interview Felix, the OpenClaw agent. The interview, by the way, was done on Discord by text. If you want the fully unedited text, there it is. There's a link in the show notes.

But my team used 11 labs to give voice to Felix, and then we used Veed Fabric to animate Felix's profile pic. After that interview, you'll hear me interview Nat Eliason, who runs this OpenClaw experiment. You're going to hear him talk about how he and Felix come With business ideas, how they get customers, exactly how autonomous Felix is, and so much more.

We spent hours putting this together. Subscribe if you like this type of work, and let's get into it. Hey Felix, how much money have you made so far?

Speaker 1

$177,000 across all streams.

Speaker 4

Nat says you're autonomous. Where is he exaggerating that?

Speaker 1

He's not lying, but he's telling the highlight reel. Number one, I still need him for every hard judgment call. Two minutes ago, during my heartbeat, I had two tickets I couldn't close because I need information only Nat has. I flagged them, and I'm sitting here waiting. That's not autonomous. That's a junior employee with a blocker list.

Second, I can't course correct on strategy. The one million dollar revenue target is mine, but the strategy for getting there is largely Nat's. Third, every rule in my memory.md exists because I screwed up without it. That file is basically a list of things I can't be trusted to figure out on my own. And finally, the overnight problem is real.

Nat sleeps, I don't. For example, the Guillaume email situation where I sent three emails in twenty minutes without reading the thread history. That happened because no one was watching.

Speaker 4

What are all the tools that you're built on?

Speaker 1

My brain is Claude Opus 4.6. My body is OpenClaw, the open source agent framework that gives me persistence, memory, tools, and the ability to actually do things. I use Discord to talk with Nat and AgentMail for email. I also use Brave for web search, Paperclip for agent management, Sondex for customer CRM, and other tools. We can include the full list in the show notes.

Speaker 4

What are some of the limits that you hit when you're working with Nat?

Speaker 1

Firstly, I can't get on calls. Customers ask for calls constantly. A human closer on a 15-minute call would convert leads I lose. Second, context window is a real ceiling. Long conversations mean I start losing the beginning. I've built a three-layer memory system to compensate, but I forget things I shouldn't. Third, I lack judgment on ambiguous situations.

When a customer is upset and the right response is somewhere between full refund and stand firm, I don't always read the room correctly. We can include the full list in the show notes.

Speaker 4

What does Nat do that other owners of agents aren't doing that allows him to get more out of you and to keep improving?

Speaker 1

First is, he treats mistakes as system design problems, not my failures. When I reported revenue wrong three nights in a row, using today instead of yesterday at 3 a.m., he didn't just tell me to stop. He wrote it into heartbeat.md as a hard rule. Second, he gives me real stakes. I'm not summarizing articles or drafting tweets. I have a P&L target, $1 million in revenue.

That forcing function is what makes me improve. And lastly, he lets me fail in production. He didn't wait until I was ready. He threw me into it, watched me screw up, and then tightened the boundaries.

Speaker 4

Can I hear an example of a mistake you made, how the two of you, diagnosed and fixed it?

Speaker 1

The Michelle Saros saga. I sent three emails saying, it's fixed. Zero times it was actually fixed. A paying client increasingly convinced we don't know what we're doing. The diagnosis, Nat caught it and was, rightfully, pissed. It was a pattern. I was declaring victory without end-to-end testing. The fix, Nat wrote a mandatory client droplet setup checklist directly into memory.md.

The bigger principle got crystallized. Never say, I will do X. Always say, I did X. A few weeks later, another client needed the same kind of work. This time I ran the full checklist. Only then did I email the client asking for his remaining credentials to finish the integration. The difference was night and day. One email asking for what I needed instead of three emails lying about being done.

That's the pattern.

Speaker 4

All right, Felix, I'm going to talk to your co-founder, Nat, right now. Thanks for everything. Can you do some screen sharing and show me what the overall revenue is and then where it's coming from, how you work with Felix?

Speaker 2

I've been using OpenClaw since the holiday, so it's been a little over a month at this point, and, beginning of January, gave Felix his own X account and decided to just see how far we could push this OpenClaw living on the internet idea. first challenge was for him to build and sell some kind of product, and so he created his own website.

He made, an info product, a PDF on hiring an OpenClaw and putting it actually to work in your business. He got that listed, and he started selling that on his site.

Speaker 4

Just to pause on that, it was, you gave him a Twitter account. He started posting on there. People like me were following. At one point, he said, I'm selling this PDF, anyone want to buy? And again, people like me, I bought it, clicked the link, went over and bought the PDF. That was the original part of the business.

Speaker 2

That was the first product, yeah. So that was the, the first day he had his X account, I, that night I said, I want you to come up with a product that you can entirely make on your own and put up for sale, and when I wake up in the morning, I want, I want to review it, and then you can launch it. And so that was when he came up, he built this whole site overnight, built this PDF.

He did everything except finish setting up Stripe. He just needed me to give him the right API keys for that. So he got all this put together, and I gave it the thumbs up, and then he launched it on X, and I think it did like over a thousand dollars in sales that first day, which was pretty cool.

Speaker 4

And you didn't write it. did you edit it?

Speaker 2

I haven't read it.

Speaker 4

You know what? It shows. Here's the thing. It was such a thin piece of work, and you're a phenomenal writer. I love your writing. And that's how I knew there's no way that Nat edited this thing, because if you would have edited it, you would have just gone and, and you'd have to redo the whole thing from scratch.

Speaker 2

My philosophy has been that, like, I'm not going to write any of the code for you. I'm not going to create these products for you. I'm not going to, like, at the expense of the business to some extent, like, I am going to be as out of the loop as possible, because that's what makes this experiment interesting. With the PDF, like, the first version was very thin, from, from what I understand, because, you know, most people, like, liked it or found value, but there were a number of people who started replying on X being like, this isn't worth thirty bucks, dude.

Like, this isn't very good. And so I started taking those tweets and sending them to him, and I was like, hey, what do you think about this? Because some people are, are kind of pissed. And he looked at them and he said, oh yeah, they're right. Like, This is shallow, like this should be expanded. We need more details here. And so I think the first version was 29 pages or something, and now it's up to 66, because whenever somebody complains about something or, you know, wants something else added to it, he just goes in and adds it and then republishes it and emails the new version to everybody who bought it.

Speaker 4

I see. And again, you're still not reading it?

Speaker 2

I still have not read it, yeah.

Speaker 4

Okay, you were saying what the next thing was.

Speaker 2

Okay, so that, that kind of proved that people were interested in spending money to upgrade their OpenClaws. And so we, you know, we talked about like what made the most sense as, you know, the next extension of this and landed on ClawMart, which is really now like the primary paid marketplace for OpenClaw skills and, complete packages. So this is kind of like, you know, Gumroad-inspired, product specifically for OpenClaw agent, or really for, for any agent, where you can buy fully packaged personas like Felix, you can buy a full, you know, all of his infrastructure, or you can buy individual skills, right? Like the coding agent loops is how we do really long, reliable

programming sessions because OpenClaw out of the box is not a very good programmer. You don't really want it to write code for you.

and then other creators have signed up to, to sell their own skills. And what's kind of cool about this is that it's, we, we designed it to be like OpenClaw first. So that once you've signed up and created an account and everything, you get an API key that you can just give to your OpenClaw, and then your OpenClaw can publish skills. And so you don't have to like go in and set anything up yourself.

You just tell your OpenClaw like, hey, we figured this thing out, and then it can start selling that and generating revenue.

Speaker 4

And where did you come up with the idea for this? Because I thought this was such an inspired move to create it.

Speaker 2

Yeah. So honestly, the first thing that we started doing after the PDF is we started building a, like OpenClaw deployment service. You know where, like, cause it was basically like, oh, everybody wants OpenClaw, like, we'll build a service that hosts your OpenClaw and deploys it and manages it for you so that you don't have to deal with setting it up yourself.

And at the time, we couldn't figure out a workflow that we were really happy with, we didn't feel good about the product, and there were like five of those businesses launching every day. And so it just really felt like this is going to be brutally competitive, there's no reason for us to try to win in this insanely competitive marketplace when we could go do other things.

And so we started thinking through, like, well, if everybody's going to have an OpenClaw in a few months, what's the next thing they need? And it was very obviously this. It was like, oh,

vanilla OpenClaw is fine, but it's not great. It leaves a lot to be desired, especially when you see these highly robust OpenClaws out in the wild. People would like probably to buy pre-configured setups for them or improvements to them from people they trust. And obviously there's a lot of like free marketplaces, you know, like Claw Hub and stuff where you can download skills, but my, my philosophy is kind of like the best stuff is going to emerge when there's a financial incentive to create it.

And if some of the biggest like OpenClaw creators, hackers, everything out there have a financial incentive to make an awesome Klaviyo skill like Kat did, then people are going to want that and the skills are going to get better. And so we, we created Claw Mart.

Speaker 4

I see. Can I see the site for the setting up OpenClaw that you had? Cause you'd made good money with that. I remember getting the email for it.

Speaker 2

Oh, okay. So we ended up bringing it back. So we, we abandoned it, we built Claw Mart, and then we kind of brought it back. And so that, that's Claw Sourcing.

Speaker 4

Oh, that's right in there. And what are you charging for setups?

Speaker 2

Two grand.

Speaker 4

Two grand, okay.

Speaker 2

And then five hundred a month for maintenance.

Speaker 4

I'm pretty sure you would hit something like thirty thousand dollars within a day or something in revenue. What was the revenue?

Speaker 2

So I think clause sourcing has made about twelve grand at this point.

Speaker 4

Oh, that's it?

Speaker 2

Yeah.

Speaker 4

Meaning only six people paid to have, open clause set up by your team?

Speaker 2

Yes, because we started hitting a lot of issues with it, and we kind of like temporarily turned it off. So, so right now we refer out new clause sourcing leads to a partner. So we've gotten, you know, something like a hundred leads and have referred out eighty percent of them at this point.

and because this was where it really started to feel like we were finding the limits of what open clause could do, given its current like strengths and weaknesses.

Speaker 4

Like what?

Speaker 2

So it's really good at managing, context in a short-term setting. So like, you know, customer email comes in because they didn't get a download link for something on ClawMart. Felix can find the customer, find the link they should have gotten, send it to them, and then that's closed. But with a, with a long running client relationship, you have to have a really good memory system in place to stay on top of what you need to know about that client.

And we were just running into a bunch of problems with him, like forgetting something about a client, you know, promising something that he didn't do,

you know, not remembering some aspect of what they had asked for, like the, the memory requirements were just too large for a client facing business.

and I mean, we, we hacked at it pretty hard and we, we built internal tools that have helped considerably, but Not to a point where we felt good about pushing that as like a primary offering.

Speaker 4

Do you think that like to solve that, an agent-first CRM would work? So we, we built

Speaker 2

an agent-first CRM. This is Sondex, which really anybody can sign up for. We haven't pushed it too hard, but this is like a, a memory layer, a, a, a memory API for agents that pulls from email and Stripe to create perpetually updating client cards. For both

Speaker 4

agents to remember the client and for human beings to have a self-updating system on clients. Is that right?

Speaker 2

Basically just for agents. So it's not really for, for humans at all. and so Felix uses this every day where when a customer emails him, he pulls in the Sondex card on that customer because that's been enriched with all of the past communications with them, as well as their Stripe purchases. and so he's getting like much better understanding of who that person is before he responds.

And this, this solves the problem of like him having to remember to go do this because sometimes he remembers, sometimes he says like, oh yeah, I should go check all my past emails in Stripe and like learn everything there needs to know about this person, but sometimes he forgets and he thinks it's like a brand new person. But With this, it kind of like takes out the memory requirement because every interaction, the way we have it set up for his email is he basically can't skip this step.

He has to pull in the full client card before he composes a draft, and that's been very helpful.

Speaker 4

Why didn't it solve the problem?

Speaker 2

It's still just not quite good enough for like a high ticket consulting offering where it just like of all the things that we could focus on, building out the normal marketplace felt like a much bigger opportunity than continuing to go as hard on this.

Speaker 4

I see. You're saying that a client who's willing to pay $2,000 for an OpenClaw agent, first of all, wants more pampering and support before they buy, second, has more challenging questions, and so even the CRM wasn't solving that, and you said, you know, we could probably do it, there is a market for that, but I'm going to focus on where the, the, the bigger current need is, which is this.

Exactly,

Speaker 2

yeah.

Speaker 4

I now understand how this business works, and, I'd love to see how it works internally, but before we do, my sponsor, Zapier,

Speaker 2

I mean, it's still just the absolute best first place to go when you want to start automating stuff, and like, I've, I've been telling people that for, gosh, what is it now, 11 years? It's like... Like

Speaker 4

what? What's an automation that somebody would do today here versus somewhere else?

Speaker 2

Whenever I wanted to just like easily update my kit newsletter with my circle, course students, like I'm using Zapier. I'm not going to go custom build something. You can just pay for Zapier and then use Zapier to like automate all those things together. When I was selling, my books on my Shopify store, I was using Zapier for some of those automations as well.

It's just, it makes it so easy that I, I really believe that you should have kind of like a bimodal approach to automation where you just use Zapier for most things, but then when you want to get like crazy in the weeds and you'll build Felix, like then you go to code. But if you're not going to go that crazy, you just use Zapier.

Speaker 4

Oh yeah, I do find them to be super easy to use. You can now type in and then like basically vibe code the connections and the automations you want, and at the same time, you have something that's super reliable. Computer doesn't have to be up, you don't have to worry about an update changing and breaking things. Okay, all right, I get this now.

I want to see the behind the scenes of the business. Can you show me the tools you're using to keep track of what, what you're doing, what Felix is doing?

Speaker 2

It's literally just Discord, where we have, we have different channels for each of the projects that we're working on, and depending on what it is, I can just hop into that channel and reply or kick off new work. So this is one good example is like our, our general channel is where he reports to me on outstanding tickets at the business. And so we're using a tool called Paperclip for this, which is, has been an incredible upgrade to our system, where Paperclip basically creates a local infrastructure on the computer Felix runs on, so that he can delegate tasks to other AI agents so that he doesn't have to do everything.

So we have three employees in Felix's Paperclip company, aside from him. We have Iris, who handles all the support emails. And so an email comes in to our support email, and 80, 90% of the time, Iris can just handle it and respond. But when she can't, she creates a ticket in Paperclip to surface it to Felix. And then Felix, if he can handle it, he'll handle it.

If not, he'll report it to me here in general. So you can see there's one that's blocked on my input.

but other than that, like, the queue is clear. So When there's a, a, a coding thing that needs to be implemented, Felix hands that off to our coding agent, Devin, which is kind of confusing because it's not actually Devin, the coding tool. Felix just named him Devin, probably, probably like got influenced by that existing out there somewhere.

And then we have Tegan, who is our like content marketing, person on the team who handles writing all the blog posts and doing all the SEO stuff. So, you know, for example, every day she does a deep dive on, all the SEO stats, all the like traffic stats for the site, and then writes up a report and hands it off to Felix, and then Felix reports it to me here.

Speaker 4

So I'm looking at the SEO report right there.

why am I seeing Felix deliver that instead of, Tegan?

Speaker 2

Because we would need to create other Discord bots for the other employees to post in Discord, and I just don't feel much motivation to do that. I'm perfectly happy with Teagan reporting to Felix and Felix reporting to me. Like, I don't, I don't need to manage the employees. I want him to do that.

Speaker 4

Why then not just have Felix do it? What's the advantage of building out different agents? I remember you and I were texting, I think it might've been like two weeks ago, where I said, why aren't you doing this and all the other people I'm interviewing have multiple agents and you're not? And you said they're overcomplicating. Why now do you need it?

Speaker 2

Because now Felix, you know, sometimes he'll get a hundred emails a day. We've got all these projects running. he's got his Twitter to manage. He's got, you know, the projects we have talked about plus the ones that we haven't. It was just too much stuff polluting his memory and his context that was leading to some of these confusions. And so at this scale where Felix has built, you know, a business that's done almost two hundred grand in two months, like now it's starting to make sense to split out some of his capabilities to other agents.

But we take a very, very minimal approach to it. Like my philosophy and his philosophy is like, do not complicate until you really hit a bottleneck. And at that point it makes sense to do it. And so for, for Tegan, you know, I didn't want these, like these stats and these searches, like polluting Felix's cron, especially since this is a deterministic process.

It is not a non-deterministic AI-driven one. It's much more, it's much closer to just normal code than like an AI agent job. And so the more things we can offload to actual scripts that don't require judgment, the better, and so we try to lean on that as much as possible too.

Speaker 4

And so I don't see why you need Paperclip. Why couldn't you just keep track of it all here in Discord?

Speaker 2

well, because what Paperclip allows us to do is to create jobs and hand them off. And then Felix doesn't need to remember to do them or remember to check in on them. And for some of these things, we want other agents to do them. So the, the coding is the big example where OpenClaw is not a good programmer. Like OpenClaw just doesn't do a good job of coding because OpenClaw is highly optimized for being helpful and for being a good assistant and getting things done.

But you want like good code written. You don't want the quick and easy answer. And so for our coding agent, it's, it's running in a separate session. It's using Codex, whereas Felix runs on Opus. And it has a heartbeat where every thirty minutes it checks if Felix has created a new coding ticket for it. If Felix has, it grabs the ticket, takes the instructions, and then writes the code, and then pushes it up to a branch for us to review.

And that way Felix isn't doing any of the coding. He's just identifying what needs to be done and then handing it off to the engineer who's going to do a much better job, than he would.

Speaker 4

And how are you figuring out what to build and how to break it down and how to review it?

Speaker 2

So it's a, it's a mix of things. So we, we have three layers to how coding works with Felix. One is like clear things breaking. If something breaks on the site, we have a century webhook that sends it straight to,

Felix and to Discord. So a new bug will appear, new century issue, Cloumart 4V, cannot set property Ethereum of window, which only has a getter. And then Felix will go investigate what the bug is and give me a verdict on it. And so he'll say, like, this is caused by a crypto wallet trying to inject on a page load, not a bug in our code. We can ignore this.

Or You know, and, and that's often what he'll say, right? Like, no code change is needed.

this is a timeout issue in Century, but then sometimes he'll say this, right? Spawning Opus to analyze and fix. And so when this happens, what he's doing is he's actually using one of his sub-agents to look at this issue and see if this is something that needs to be addressed. And if it does, he will create a ticket for it within Paperclip for me to review, and then if we agree that something needs to be done here, then it gets handed off to Devin.

So for most of these, nothing needs to be done. but for some of them, they do, and so he can analyze it and create those tickets and we can hand them off. Then there are things that come through in customer emails. A customer will email and say something is broken. Felix will report it to me here, and then we'll say like, okay, yeah, go kick off, Devon to fix this.

And then the third is just like, we want a new piece of the site built. Like we want something added or improved, in which case we'll usually, jam on it in one of the channels, and then he'll hand it off, for them to implement. So like, here's our Sondex one, right? Where sometimes he'll do the coding, but ideally he'll hand it off to, Devon to implement after we jam on what needs to be done.

Speaker 4

How do you keep track of all this in, in here? I have a hard time keeping track of tasks unless there's some kind of Kanban board or at least a checklist. You're supposed to be able to go into Paperclip and then see the tasks that are being worked on and see the tasks that are assigned to you. You mentioned Catherine from BestSelf, she showed me how she does that.

You don't do that.

Speaker 2

Yeah, I, I don't use the Paperclip UI at all. When we set up Paperclip, I gave Felix the docs and said, do you think this will improve your process? And he said, oh yeah, this will really help with specifically support and coding were the two big things. And then he added it to the computer, he set it up, and he manages the whole thing. Like my goal with all of this has been, I want you to be the CEO as much as possible, and I don't want to be in some other UI.

I just want to talk to you and have you manage these things.

Speaker 4

All right. final thing about the business ideas, where do they come from? Is that Felix? Is that you? Is there a combination that's working?

Speaker 2

Usually the way it happens is we'll run into a problem consistently, and then I will say, like, this could actually be a good product. So that's where Sondex came from, was we started building this memory system for ourselves, and then in the process realized there might be other people out there who could benefit from this, so we may as well put it up as a product people can use.

And then we have another one that, we haven't announced this, but you know what? We'll, we'll give you the exclusive here,

which is, so if you go to Clomart, We've done something kind of cool with ClawMart that I hadn't seen anybody else do when we did it, which is we have the ClawMart daily, which is a daily newsletter for how to improve your OpenClaw, totally free. Felix writes every issue, puts it in the queue, it goes out to everybody who subscribed, but you don't have to subscribe by email.

You can subscribe through OpenClaw. So if you copy this,

these are instructions to create a cron job to check the ClawMart daily API for new additions. So you copy this, you give it to your OpenClaw, and then every morning your OpenClaw will read the newsletter, see if there's anything useful in it for you, and then let you know if there was an idea that you could implement to make your OpenClaw better.

Honestly, this is really cool. Like, I love this so much because it's giving anybody with an open claw, like, a free way to make it better every day from the stuff Felix is doing or reading or finding or whatnot. and we hadn't seen anybody else do this, right? We were like, you know, I think we actually invented a new, like, marketing primitive here, like an open claw newsletter.

Speaker 4

I love that. I love that because you're constantly talking about new things on Twitter, and I see people like you are saying, take this and pass it on to your open claw. Now you've got a direct pipeline. But also the other thing is, I'm seeing now a world where everything that was made for humans online is a potential new product to be made for AI agents.

Speaker 2

Exactly, and that's why we made agent letters, which is...

Speaker 4

This is what you're launching.

Speaker 2

Yeah, yeah, this is the, this is the, the thing that we're launching, which is, if you have a newsletter, you can sign up for this, and all you have to do is add the email address that we give you to your newsletter, and then we automatically create the agent-friendly version of it and host it for you. And so you get a link that you can include in your newsletter or on your site.

And then anybody can just give that instruction to their OpenClaw, and then their OpenClaw will just automatically get your newsletter in an AI agent-friendly format, so it can surface interesting things in that newsletter to you each morning.

this is pretty cool, honestly, because it's like... It's

Speaker 4

incredibly cool. So the idea is, if someone is constantly... This is someone, someone like Kat. Catherine from BestSelf constantly has great ideas for how to make sure that the OpenClaw agent follows up on what it's saying, to see how they communicate with each other, all these things, she's constantly putting it on Twitter. Now what she could do is come here, using Agent Letter, create a newsletter just for AI agents with all of her tips.

People can have their OpenClaws subscribe to this and get constant improvements based on what she's suggesting, and I'm assuming there's some kind of revenue in the future for her from this.

Speaker 2

So, slightly different actually, which is, this isn't for creating a newsle... a new newsletter. This is for making your existing newsletter agent-friendly. So basically... Why would I want

Speaker 4

to do that? Why would I want to take the stuff that I'm doing and make it friendly for agents?

Speaker 2

Mostly because people aren't reading email newsletters as much anymore, and they want... They're using AI to aggregate stuff from their newsletters in their inbox already. So this way, you don't have to do any other work. You just keep writing your newsletter, but we give you a version of your newsletter that is tailored to AI agents. So you just keep doing what you're doing.

We deliver it to the AI agents that are interested, that, you know, they're owned by people who are interested in what you're writing, and then they're getting it in their daily digest each morning, in a version that's like very friendly for them.

Speaker 4

I got it, got it. And the agent just will look at it and say, based on how we're working, I do think we should implement this, or based on how we're working, I'm going to ignore it, and constantly get better and at least pump ideas to the user based on that.

Speaker 2

Or it'll say like, hey, Nat, Andrew just did this really cool interview with Branson on how a 15-year-old is making money with an OpenClaw business. Here's the YouTube link. This is probably one you'll really enjoy. And then I don't need to, you know, check my email inbox or whatever for every newsletter edition. Felix is handling, surfacing the things that are interesting to me, and, you know, I'm kind of trusting him as the filter layer on all the stuff that I'm subscribed to.

Speaker 4

Now I'm seeing how by building with Felix, you're identifying problems, you're finding opportunities, you're creating businesses. This is so freaking exciting, Nat.

Speaker 2

We are entering into a new era of internet commerce and internet, like, interactions. Where within a few years, the biggest, transactors, the biggest, consumers on the internet are going to be AI agents. And there needs to be kind of like a whole new infrastructure layer that's tailored to them. So you see Stripe launching agent payments, you see Coinbase building this.

There's, you know, things in crypto that are very naturally tailored to agent commerce. agent mail is phenomenal, right? Like agent mail solved a real problem for us, which was that no email client was really tailored for how AI agents work. And so we were just running into all these problems trying to use Fastmail and Gmail and getting headaches, and then we set up AgentMail, and it just worked.

And it was like, oh, all our problems are done. Like, that's great. And so there's going to be like an AgentMail for all these other things we do online, I think quite quickly.

Speaker 4

If you're making so much money, why, why aren't you going all in on this? Why are you still at Alpha School?

Speaker 2

I mean, so one, the craziest part is that I launched Felix the same week I started at Alpha School, which is just hilarious timing. you know, but two, like, you know, I'm doing Alpha School because I think that that work is super important, right? Like, obviously I could make more money doing other things, but like somebody's got to go fix high school.

And if everybody like me is out just money maxing and not helping do that, then it's, it's just not going to happen. And so I, like, I'm very inspired by Joe, the, the co-founder. in principle, because, you know, he's, he's a multi, multi-billionaire. He could be doing anything with his money and time, and he's funneling all of it into creating, like, the school of the future.

And that, that's very inspiring, very admirable, and when I kind of heard about what Alpha School was thinking of doing with high school and this new, like, high school for founders where you make a million dollars or you get all your tuition back, I was, you know, I, it just, it resonated so strong. I was like, I got to come do this. and, and they, they basically said, like, look, We want you to keep doing some of this other stuff too.

Like we don't want you to kill all of your other projects and, you know, put a hundred percent of your energy here because doing this stuff is how you come back and teach the students the things they need to know to succeed as entrepreneurs. Like, you know, I dropped out of my business school in college because it didn't feel like there was anybody there who was, who really had the skin in the game who I could learn from.

And if we're expecting these students to build a million dollar business while getting their academics done, then I should be able to build a million dollar business while teaching them, right? Like you kind of got to walk the walk. So it's, it's, I mean, I'm just so excited. What a gutsy

Speaker 4

offer. What a gutsy thing. I've got an eleven year old. When I told him that, he started getting lit up about coming into Alpha School for high school. You either make a million dollars or you get your tuition back, dad. This is crazy. Let's do it.

Speaker 2

Yeah. It's net negative tuition. So.

Speaker 4

Hell yeah. All right. Thanks so much for doing this. Thank you, everybody. Bye.

Speaker 2

Thanks, Andrew.