Andrew (2:42)

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

Felix (2:45)

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 to 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.

Andrew (3:18)

What does NAT do that other owners of agents aren't doing? That allows them to get more out of you and to keep improving.

Felix (3:25)

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 3am, 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 $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.

Andrew (3:58)

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

Felix (4:04)

The Michelle Cerro 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.

Andrew (4:57)

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.

Nat Eliason (5:09)

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 Open Claw 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 Open Claw and, and putting it actually to work in your business. He got that listed and he started selling that on his site.

Andrew (5:44)

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, click the link, went over and bought the PDF. That was the original part of the business.

Nat Eliason (6:03)

That was the first product. Yeah. So that was the. The first day he had his X account. 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 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.

Andrew (6:41)

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

Nat Eliason (6:44)

I haven't read it.

Andrew (6:46)

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. You would have just gone and you'd have to redo the whole thing from scratch.

Nat Eliason (7:04)

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 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 30 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 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 thing 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.

Andrew (8:04)

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

Nat Eliason (8:06)

I still have not read it. Yeah.

Andrew (8:09)

Okay, you were saying what the next thing was.

Nat Eliason (8:11)

Okay, so that, that kind of proved that people were interested in spending money to upgrade their open clause. 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 Claw Martin, which is really now like the primary paid marketplace for Open Claw skills and complete packages. So this is kind of like, you know, gumroad inspired product specifically for Open Claw 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 Open Claw 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 designed it to be like Open Claw 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.

Andrew (9:32)

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

Nat Eliason (9:38)

Yeah, so honestly the first thing that we started doing after the PDF is we started building a like Open Claw deployment service, you know, where like because it was basically like, oh, everybody wants openclaw. Like, we'll build a service that hosts your Open Claw 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 and 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 Open Claw in a few months, what's the next thing they need? And it was very obviously this. It was like, oh, vanilla Open claw is fine, but it's not great. It leaves a lot to be desired, especially when you see these highly robust open claws 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 Open Claw 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 Clawmart.

Andrew (11:19)

I see. Can I see the site for the setting up Open Claw that you had because you'd made good money with that. I remember getting the email for it.

Nat Eliason (11:27)

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.

Andrew (11:35)

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

Nat Eliason (11:38)

Two grand.

Andrew (11:39)

Two grand. Okay.

Nat Eliason (11:40)

And then 500amonth for maintenance.

Andrew (11:43)

I'm pretty sure you had hit something like $30,000 within a day or something in revenue. What was the revenue?

Nat Eliason (11:48)

So I think claw sourcing has made about 12 grand at this point.

Andrew (11:51)

Oh, that's it?

Nat Eliason (11:52)

Yeah.

Andrew (11:53)

Meaning only six people paid to have Open Claw set up by your team.

Nat Eliason (11:57)

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 cloth sourcing leads to a partner. So we've gotten you know, something like 100 leads and have referred out 80% of them at this point. And because this was where it really started to feel like we were finding the limits of what OpenClaw could do given its current like strengths and weaknesses.

Andrew (12:29)

Like what?

Nat Eliason (12:30)

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 Claw Mart. Felix can find the customer, find the link they should have gotten, send it to them, and then that's closed. But with, 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.

Andrew (13:36)

Do you think that like, to solve that an Agent First CRM would work?

Nat Eliason (13:41)

Where we built 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 memory layer, a memory API for agents that pulls from email and Stripe to create perpetually updating client cards.

Andrew (14:03)

So both agents to remember the client and for human beings to have a self updating system on clients, is that right?

Nat Eliason (14:10)

Basically just for agents. So it's not really 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.

Andrew (15:09)

Why didn't it solve the problem?

Nat Eliason (15:12)

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.

Andrew (15:31)

I see you're saying that a client who's willing to pay $2,000 for an open claw 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 bigger current need is.

Nat Eliason (15:52)

Exactly. Yeah.

Andrew (15:53)

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

Nat Eliason (16:02)

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

Andrew (16:14)

somebody would do today here versus somewhere else?

Nat Eliason (16:17)

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 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.

Andrew (16:56)

Hell 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 to. 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?

Nat Eliason (17:20)

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 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 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 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.

Andrew (19:20)

So I'm looking at the SEO report right there. Mm. Why am I seeing Felix deliver that instead of Teagan?

Nat Eliason (19:28)

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 Tegan 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.

Andrew (19:48)

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 have 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?

Nat Eliason (20:06)

Because now Felix, you know, Sometimes he'll get 100 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 in 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 200 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.

Andrew (21:21)

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

Nat Eliason (21:27)

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, and for some of these things, we want other agents to do them. So 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 Open Claw 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 running in a separate session, it's using Codex, whereas Felix runs on Opus. And it has a heartbeat where every 30 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.

Andrew (22:41)

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

Nat Eliason (22:47)

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 Sentry webhook that sends it straight to Felix and to Discord. So a new bug will appear. New century issue Claw Mart 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 was caused by Crypto Wallet trying to inject on a page load, not a bug in our code. We can ignore this or, you know, and that's often what he'll say, right? Like, no code changes needed. There's a timeout issue in Sentry. 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 Devin 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 Devin to implement after we jam on what needs to be done.

Andrew (24:47)

How do you keep track of all of this 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 Best Self. She showed me how she does that. You don't do that.

Nat Eliason (25:07)

Yeah, 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 encoding 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.

Andrew (25:39)

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?

Nat Eliason (25:49)

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 give you the exclusive here, which is, so if you go to Clawmart, 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 Claw Mart 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 Claw Mart Daily API for new additions. So you copy this, you give it to your open claw, and then every morning your openclaw will read the newsletter, see if there's anything useful in it for you, and. And then let you know if there was an idea that you could implement to make your open claw 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.

Andrew (27:35)

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.

Nat Eliason (27:54)

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

Andrew (28:00)

This is what you're launching.

Nat Eliason (28:02)

Yeah, yeah. This is the, this is 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 Open Claw and then their Open claw 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.

Andrew (28:42)

Honestly, it's incredibly cool. So the idea is if someone is constantly. This is someone like Kat Kathryn from Best Self 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 agentletter, create a newsletter just for AI agents with all of her tips. People can have their open clause 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.

Nat Eliason (29:15)

So slightly different actually, which is, this isn't for creating a newsletter, a new newsletter. This is for making your existing newsletter agent friendly. So basically, why would I do that?

Andrew (29:27)

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

Nat Eliason (29:32)

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.

Andrew (30:11)

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, and constantly get better and at least pump ideas to the user based on that.

Nat Eliason (30:23)

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 open claw 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.

Andrew (30:51)

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.

Nat Eliason (30:59)

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 Fast Mail and Gmail and getting headaches. And then we set up Agent Mail 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 Agent mail for all these other things we do online, I think quite quickly.

Andrew (32:00)

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

Nat Eliason (32:04)

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'm very inspired by Joe, the co founder and principal, because, you know, 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'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, it just, it resonated so strong. I was like, I gotta come do this. 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 100% 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.

Andrew (33:52)

What's the offer? What a gutsy thing. I've got an 11 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.

Nat Eliason (34:03)

Yeah. It's net negative tuition, so hell yeah.

Andrew (34:07)

All right, thanks so much for doing this. Thank you everybody. Bye.

Nat Eliason (34:10)

Thanks, Andrew.