SaaStr AI Live: The 90/10 Rule. What Folks Are Really Vibe Coding Today.

Okay. In progress. All right. Hello everyone.

I think meeting is being recorded by Update AI. Oh, thank you. Update.

Now. The call is being recorded.

We hear you.

Great, great. I wonder if I can mute. No, they're all muted. Huh. All right. I think I fixed it. There's a weird toggle. That is weird. I feel like that didn't happen last time.

Are you live? Are we on Twitter? I don't see it.

We. Yeah, we are. Okay. Okay. All right. Hello everyone. Welcome to another Sastra AI Live Being recorded.

This meeting is being recorded by Update AI. That might be a new zoom setting, huh?

Yeah, it's pretty terrible actually.

It's pretty terrible zoom.

It's pretty terrible.

Maybe the good presentation give us a minute. Yeah, maybe. Maybe I have to research it afterwards.

Yeah, I think they have to announce themselves.

It's for the best.

It's for the best. But I did say it can't unmute itself, so that's a little funny.

Yep.

Okay. All right. Hello everyone. Welcome back to another Zester AI Live. We wanted to do a follow up from the AI day we did a couple weeks ago. We did not make it through the whole thing and I actually think a lot has changed in those two weeks just with the wider, let's say, release of cloud cowork to a lot of. A lot more users, including ourselves to use try. And then obviously I know also cloud code got a lot of updates in the last two weeks as well as just like the models for that are core to Claude and OpenAI. So we wanted to do an update basically on where we're at, just with the lens of our journey of like building versus buying all these Saster AI agents and now apps and kind of encompassing some of that with, you know, everything that's been going on in the last two weeks because a lot has happened. So we're going to go from there. As always, please ask questions in the chat.

This meeting is being recorded by Update.

AI and we'll take some questions at the end. You know, having a connection tonight. It's okay. Okay. All right. Just I always like to put this slide first for those who need it. And just to preface, as always, you can go to sasper AI/agents if you want more info on any of the either third party tools or things that we buy. The apps we Vibe coded today are all listed there. We have like a new community list, newer community listing that we have there as well that you can play around with and see what we use and how we use it. So that's that. Okay. So getting into our. So this is the 9010 rule, Jason, that you originated. So would love to get your thoughts here just to kind of kick us off. But basically our rule from the last, you know, nine months, 20 plus agents, six plus now, now maybe eight with the LA. The two that I'll focus on today that we made recently in the last two weeks. So a bunch of apps we've made both for internal purposes and then actually now external facing are. The rule we've had has always been, you know, buy 90% of what you need if you can, off the shelf, do it where, you know, there's already a solution for this. Like, we're not trying to Vibe code our own CRM tool or anything crazy like that. Like, you know, we have agents that we use for outbound and inbound. Those are all third party tools. Like I'm not even going to attempt to recreate those in what we're doing in bytecoding. So that's, that's an interesting mix there. So we've, we've pretty much bought 9% of what we've needed and only built a 10% where we either couldn't find a solution that really already existed pretty close to what we wanted off the shelf, or we had in the case of our AI vpm. That'll walk you guys through a bit more where we had a bunch of proprietary data that I had in one place, I basically had on my computer, we had a bunch of years of data. I couldn't find a tool that was also a reason where we went into the 10% of where it didn't exist then also more recently, I'll show you what we did with Claude, Cowork and Vibe Coding is I actually did replace a tool in the last week we were paying for. So this is kind of a new. I don't know if you would consider it a caveat to the rule, Jason, but this was a new one where, you know, we were paying for a tool, it did some of what we needed off the shelf, but it didn't do enough. And so that's where I decided it was worth the effort to build our own tool in this scenario. So, yeah, we have about 20 plus agents. Jason, you spent a lot of time vi coding some of the apps that are now forward facing. But yeah, we do use a lot of third party tools. I think in those evaluations it's typically been, you know, okay, are these vendors and tools we can trust? Again? Does it do like most of what you're looking to do and if it does like there's so many I think nuances behind the scenes that are maybe unappreciated when you start by coding and learning how to do it. Really good things like compliance, things like security, data warehousing. Like these are all things I don't, I don't want to tackle. Even as good as we've gotten, these are all things I don't want to tackle. The other thing I've already fallen into is the maintenance of all these apps. Right. Like Jason spends a lot of time in his day doing maintenance of these apps. I now have to spend a bunch of time with the apps I've created maintaining them. And so it just kind of compounds on itself where then you're also now just spending time doing a bunch of app maintenance or agent maintenance. So it is a big time suck as well. Anything you want to touch on there?

No, I, I think, I think there's a lot to dig into in here. The only sort of meta thing I'll add for folks is Emilia will show you. We, we rebuilt what I call an n +1 app. So the one this is just. I want to go deep on what we're the folks the apps you guys might be used that we use. But maybe we'll show you. We built this sponsor application for our sponsors. We have 150 sponsors for Saster A and 2026 and may come and what is interesting at a higher level is there is third party application for these what is called sponsor portal. It's a niche category of software and it's not big enough to justify significant investment and the products are not, they just have not kept up with 2026. They're terrible. So we didn't want to build one. We built our own version of something we could buy for 5k and 10k and have for years and we'll show you why. But I think there is a risk for folks building vertical apps. Building niche apps. You should not build an agent if you can buy it or an AI app. But if you fall behind too far, folks may build it out of frustration. And that's more what we did rather than try to cancel our salesforce bill. But this was one where we were driven to frustration by the mediocrity in this event software space to finally build our own. And, and it works. So it would be that that's a lost customer forever for those vendors. So we'll show you that though. Keep going.

Yeah, I'll show folks. So yeah, this is my evolution of the 9010 rule of you know, this again, we've, we've bought a lot of third party tools are on Sasser AI slash agents. You can see the ones we use multiple for outbound, we use one for inbound. But like when we, when we go to evaluate things, right. Again, if we can find a solution off this shelf, we're going to go for it, right? Like we are famously three humans, one dog and like 20 something agents now and like eight apps. So like we don't have a lot of human manpower to keep up with these to go through SOC 2 compliance to, you know, use a data warehouse other than Salesforce. Like a lot of our apps and agents all push back into Salesforce. It's a great system of record. I'm not trying to vibe code, you know, an inbound agent. Like I'm not trying to vibe code another outbound sdr. Like there are things off the shelf that do that really well. It's not a good use of your time. I think that's the other thing too. Like just because it's feasible, sometimes it may not be the best thing to buy code. Even though you could maybe do it because it's just going to be an ongoing time suck. Like I really had to weigh the pros and cons of Vibe coding. Our sponsor portal that I'll show you guys because we had something off the shelf that worked. But I just got really frustrated that it was lacking a bunch of features that I knew would be possible to vibe code into an app and like make it better. I was like, you know what? This tool that we're using off the shelf has no AI, literally zero AI. And this is not a knock on them. Like this is maybe just a category of like event software has been unjust for a very long time. So you know, hosting SAS re annual, doing these events has been always a sore point of frustration that we're kind of hostage to a lot of vendors we end up having to use because there isn't anything better out there. But I knew it would be feasible. But I was not keen on doing it because I knew it would take time. I knew to build in some like AI native features is like not my strong suit when it comes to vibe coding. And the other biggest thing was I really did not. Jason knows this. I did not want to tackle single sign on. I was like, that is complicated. Like I am not an engineer. I, you know, have been a go to market person. I don't know how to fix that. If I was like, what if that breaks? Like I'm screwed. Like, I basically actually ended up giving myself a limit of like, okay, if I can't get single sign on to work in a Vibe coded app in a day, then I'm just going to use the off the shelf tool because I can't spend that much more time on it. I will give myself a day, see if I can do it, see if I can get the integrations to work, see if it'll work for real and then I'll do all the other features because all the other features are fairly simple. And I was like, if that works then I'll launch it, but if not I'll go back to what we were using because it's just too risky. I was like, this is super risky. We have 150 sponsors. This is millions of dollars of revenue and customers at Saster that rely on this portal and this back end to work and get the information they need to come be a successful customer of ours and sponsor at Zaster. And I was like, there's just a lot of writing on this. So it was definitely scary. And I would say the thing that kind of tipped me over the edge was one, we're nine months in, right. So I wouldn't say if you just started bipoding or if you've been kicking yourself on okay, I need to start learning how to buy code apps so I can see what's possible. I would not tackle this day one, right? This was after we've done, you know, the valuation pitch calculator, the pitch deck grader. We have, you know, Sasser AI is on a vibe coded website. Saster London was on a vibe coded website. Like Saster AI is a vibe coded website. Like this is after multiple Vibe coded websites forward facing in production before I tried to even fathom tackling something like single sign on because I knew, I knew from those experiences that it was going to be complicated. I was like, it's going to suck. I already know it's kind of. So I feel like that was a lot of hard. I was like, okay, because it's going to suck. I know it's going to suck. I'm going to give myself a day. But I also think it ties back to, you know, what are. I think there's all this social media hype around. Okay, like what are people, you know, obviously lovable replit on fire Versaille. Like all, all of these tools are on fire. They're all going to be a faster like all these, all these guys are, you know, obviously benefit and Brandon and I do think there's so many great stories coming out of people who have vibe coded things or are now profitable from apps that are in production. But if you actually look at Anton's tweet that Jason wrote up from I think this was in the last week, like they posted what are most people vibe coding. And I feel like this is super interesting because it really applies to the 9010 rule of like if you look at this, it's not till number four that he got to replacing, you know, and or rebuilding a custom built SaaS app the way that we did. Literally number four, number one is rapid prototyping and that makes a ton of sense, right? Like you don't want to wait for your engineer team. Maybe you're on the go to market team so you're not as technical but you're like I just need you to fix this on the website or we have a new product or we have a new case study and I this is how I want it. Like it's perfect for that. Like you don't have to get all in the weeds. Maybe your engineering team will take it and actually make it real and forward pacing. So like that's a great use case. That's a great, I think also first use case where a lot of people come in to vibe coding and I was like, okay, that makes a ton of sense. So it's just interesting to see that reflected in his data what people are actually using by coded apps like level before I think to building internal tools. That's what we did with our AI vpm which I'll show you guys next. Again, that made a ton of sense for us because we knew it was going to be internal facing, right low risk. We couldn't find an off the shelf tool to do what we wanted in marketing. Like too many of the marketing tools right now are either like actually sales tools that have a marketing wrapper around them or just glorified copywriting tools. And that's not what we wanted. So that's where we fell into number two and built that tool. Number three is something we do a lot of, we actually do it a little bit more automated but you can basically API into making slide decks real, right? So if you have something like, you know, everyone's call recorder is here, you could take a call recording, put that into, you know, pick your poison tool, zapier edit and whatever API it into replit lovable gamma, have it spit out a custom website for the prospect you just talked to versus you know, waiting to send a generic deck to them. We do this all the time now. It's actually a really, again, really great use case for go to market. Really low risk because you're just going to send it to that prospect, right? Like you don't. If the whole, if they share it around the org, great. But it's not for like the whole Internet to see. It's fairly, you can password protect it, right? Fairly easily. It's pretty secure. Like there's probably nothing proprietary you're going to put in that deck on that website. Again, low risk. So it makes a ton of sense. So I think just interesting to see here that it's not until it's not till number four where he was like, then we see people starting to recreate simple. And I, and I appreciate. He said simple, fast apps, not, it's like not complicated. You know, simple things like the ones I'll show you next that we build super great for this. But not again. We're not trying to, we're not trying to rebuild Salesforce. I'm not trying to recreate our marketing automation platform. I'm not even trying to recreate some of the AI agents we bought off the shelf. Like those all do that really well and there's, there's just no need to build those things when you can feasibly buy them. So I'll show you some of the two things we've built more recently and also why it's. Why it's interesting that we've built these recently in the last two. Well, 10k is like a month old now and the sponsor portal is literally we code and I honestly. And part of that build versus buy, which I think is on the next slide. Yeah, two very different reasons here. And also I think part of my hesitation to rebuild something like SaaS responsors would have been greater had it not been for Claude. Cowork coming out. Right? So it came out I would think January and beta and you have to be on a max plan. So my max plan got it like fed one or something. So I didn't have it for that long but I was like, okay. Between that being literally on my machine and then Claude also having cowork and browser, I was like, oh, like it can do a lot actually. Like it can, it can see everything. It can do. It can take actions for you. So I was like, you know what if I get stuck Vibe coding this SaaS app that I need for sponsors? Because I know it's a little bit more complicated with like single sign on and like it has some unique data that's like, unique to each customer, let's say. And I was like, obviously, Single Sign on will tackle a lot of that, but if I get stuck, I felt confident having used Cowork for a couple days to be like, okay, I think Claude could probably bail me out if I get stuck. And the other part of using Cowork so much was that because it's on my machine and I was recreating an app we already used, it was easier to do it because it could already ingest all that stuff because again, it's on my machine, it was in my browser. And so it basically took all that good stuff, which I'll show you, and helped me write a spec for Vibecona and then also helped me when I got stuck a couple times with Single Sign on to get unstuck. So, like, I don't, I don't know if without it I could have done the whole project and app to completion. I'm going to be honest, like, I don't know if I could have because it just one. It kept me to my, my, you know, restriction I put on myself of like, okay, if I can do this in a day, then I'll do it. But if I can, I'm going to go back to the third party off the shelf tool we built, which I think is a good restriction. And it was a whole day. I was like, I have no meetings this day. I'm literally just going to figure out how to do. I was like, don't talk to me, don't slack me. I'm doing single file. I'm trying to figure it out. I'm like in a dark wall. And so I think there's two very different reasons here. Part of it, to an earlier point you made, Jason, was this tool in particular for SAS responsor that I decided to recreate with Bipod a had no AI features in it. I was like, it's February of 2026 and there is not one single AI, not even a lightweight AI feature. Nothing. Not like, hey, put the sponsor's name in, or put your customer's name in and then we'll, you know, we'll use AI to backfill their address and their location and how many employees they have and their company size and where they base and like, give you a little blurb about them. I was like, that's, that's AI 101. That's so basic for an agent to go into. How is that not even in the app that we've been using for the past couple years? I was super Frustrated that there was literally zero AI in the tool we were using, I thought, you know what, I think it's just time to rip the band aid and recreate it ourselves because I know for a fact I could get AI not only into this tool, but it will make life easier if the single sign on works. And so I was like, you know what, there is no. And to be fair, I also did look for a different third party tool that maybe had more AI in it that would do this like unique sponsor, but it's fairly unique. Like this is again, event SaaS apps are fairly behind and all this AI stuff, like there was not one I could find off the shelf to do this. Similar to the way that we built our AI VP of marketing, which is internal facing only. So I'll show you guys some screenshots of it and then I'll show you SaaS responsors, which is external facing. Again, same thing. We could not find a third party tool more specifically for marketing. Obviously there's a lot of sales tools out there that are really great that we're using and sometimes I do use them for marketing, but I couldn't find one that was all encompassing, that was like, okay, I'm going to take all your data from the last 10 years. Like this is something we also couldn't hire a human to do because asking a new marketer to look at 10 years of data of, hey, what's worked for sasper, for sponsors, for tickets, for customers, for media. We have like a whole media business, like would just, they would blow their brain. Like it's too much, like it was just too much complexity. They'd be like, like I don't, I don't, I don't know how to process all this as a human being. And so I was like, okay, clearly AI can easily actually process all this data, which it did. Like it again, it probably took a day because I followed this rule quite strictly. I gave it a day to like ingest all of our old data, come up with like analysis of it, come up with what's working, what's not working, what are we not doing, what are, you know, do some competitive analysis. What are other folks like us saps are doing? What's working in AI? Like what are the benefits I can get out of like putting and injecting more AI into this process? And then I let the AI run with it, right? I was like, okay, come up with an actual plan. And so that's what we did for these again, two vibe coded tools, I think two Very different reasons of like one was internal facing. So I think to Anton's point, like that's a great reason to vibe code something if it's just going to be internal facing. The other one was again to replace a simple SaaS app, but also it has zero AI functionality. So it's like there's just no benefit to sticking with this tool. I'll also say maybe to take a different angle on it if that's you right now that's where I would be worried. Like if you feel like your app has zero AI. That was literally my first frontier to try and replace replacing something. And I was like my bar is does this tool already have AI in it? And it didn't. So. So I think if that's you, I'd be a little bit more worried. But Jason, I'd like to get your. Your take on that there.

Sorry, say that again. I think we hit the point. Sorry, I missed the subtle point.

Yeah, all good. I think just like.

Oh, if you haven't. If you haven't. If you haven't built out.

Yes.

Something in. In AI in your app that, that moves. That really moves the needle. Yeah. You should give up you. The LLMs. The LMS are available to everybody. Everything got really good around last Summer Fall with Claude 3537 and they're really good now and it's not that hard. I mean here, listen, I don't want to spend all this time. I want to show folks what we build and answer questions that we didn't get. But honestly, here's the tough part guys.

This.

The, the.

The.

The vpm. Let's get to it because we're. But the VP marketing is niche to us. The sponsor portal. If Amelia with two days of hard work or day and a half is able to build something better than it's on the market, you should be embarrassed if you have. If you can't do that right. So this is. I think it's time to be honest and ask yourself is your. Does your app still make your customers jaw drop? Is it still magical? Because. Because there's, there's really no excuse today and you're going to be quickly disrupted and churned if you can't build something magical with your AI app today. Stuff so good. So. But let's keep going.

Yeah. It's so good. It's. Yeah. And to your point, there are some good questions. So I'll, I'll walk you guys through both of our more recent custom built agents and I think there's some good nuances Here of like, you know, could I build these two apps this time last year? Probably not. Like everything got, not only have things gotten really good over the last, you know, more so nine months than the last year, but in the last two weeks with the new models and obviously with Cowork, you could do a lot more, a lot, lot faster. And I think that's a big unlock that people haven't quite fully realized yet. I know I see a lot of folks who have realized this about cloud code and you know, GBT coding and all that jazz, but I think just having Cowork sit in your machine, sit in your browser, see what you're doing, be able to take actions. It's a, it's. Honestly it was the first time I was like, oh, I'm a little scared for myself. As the, as the, as the agent builder and as the person who has managed all these agents for the last nine months, I was like, well you know, give them a year. They may not need me, they may not need me in here. So we will see. Maybe we're more than a year off from that. But I was like this, it's gotten scary good crazy fast in the last two weeks. I'm like, it's only February 11th. Like it's gotten really good. So going first to our custom AI vpm. So again, we couldn't find a tool that would do this. I think the real problem here was finding a tool too that could not only ingest all of our proprietary data from the last 10 years, right. Which we needed AI to do. We knew that AI would be able to like an agent would be able to understand all the data, would be like be able to come up with an action plan, like an actual coherent plan of okay, here's what to do every single day from. And I did it for a short time. I was like, let's do it for the next six months, right? It was January now. Disaster. Let's do a six month marketing plan and you're going to output from me first at a high level, right? So this was an iteration. It was all based on data of what's working, what hasn't for you know, our sales, for our marketing, for our go to market team to really push us and keep us on track. I was like, I need something that will keep us honest and is also other than the data doesn't have bias. Right. The agent is just going to look at everything across the board. I give it. It has real time API inputs of where we are today and it'll, it'll adjust in real time. It'll say like today it was kind of roasting me for being behind on our summits. I was like, I know, I'm trying, I'm getting there. You're faster than me agents. And so it's just really interesting. So we custom built the AI VPN more specifically using, you know, third party tools we already had. Because I basically wanted to take the data of what's working the best and then put it into this new agent. I took a lot of, you know, historical data, I put it into this agent. I used Zapier because obviously that powers a lot of other workflows to push back and forth and pull back and forth. So it's got web hooks, it's got APIs, it uses Salesforce as, you know, our primary data instance. Again, I'm not trying to recreate the wheel on that one. It's a really great way to have data that's plus Salesforce already has a lot of data, right? It's got 10 years of chapter data. So I'm not going to try and recreate that. I'm just going to push and pull from Salesforce because it's already there, you know, pushed everything back in the cloud. And then we used Replit for this one to build an internal agent. You can use Replit or Lovable to build your internal agents. So we built 10K for two very specific reasons. One, because we needed more of a marketing orchestration tool and we couldn't find one. But two, also because, you know, we wanted something that would help us get to like the Keepathon. It's got us to the first 10k attendees for Sasser Annual this year and help us drive the first 10k of revenue. And it's giving us like literally actionable to do. It's like every day it's the first agent now I log into, other than like our outbound and inbound agents. But this one is typically first because it keeps us honest of okay, here are the campaigns you need to be running this week. Here's the copy for the campaigns, here's the email copy, here's the ad copy. Here's how much you should be spending on ads. Let me look at where you're at today. Every morning I'm like, agent, look at where we're at today. It'll say, okay, here's where you're at towards those attendance and revenue goals and sponsorship goals. Here's where we should, you know, adjust those levels and dials maybe a little bit more. Have you tried this thing. Or sometimes I'll be like, hey, I'm thinking of doing this, which is not in our game plan. Is it a waste of time or not? Like, it's a really good copilot for me to bounce ideas off of. So that's our, that's our AI vpm. It's more so internal facing, but I'll go back to what it looks like for a second. So this left hand rail is what our AI agent looks like. Again. It's got a lot of proprietary data, so I took some screenshots that were more high level. But this is, you know, it's like, okay, here's the setup week, here's the launch week. Here's what, here's how many tickets you need each week. When you click them, then these are also further clickable. It'll say, okay, here's what you need to do this week, right? It's telling me like, hey, create this promo code. Make sure Jason Jason 20 is on. Which it is. Make sure you're running ads to it. You know, make sure all of your AI SDRs are optimized for sponsorships and tickets. Like, here are the campaigns, here are the target audience you need to hit. Here's what you should promote to them. Like it's literally giving us all these things, which has been a super handy day to day tool. And it's been again, just a nice copilot to have kind of off the shelf and five coded. Again. It's high stakes in the fact that we rely on this now, but low stakes from the fact that only our internal team needs to access it. We had to hook up some APIs to it to have real time data, but other than that, it's not trying to solve anything crazy. And so for all intents and purposes, It's a simple SaaS app or copilot or agent or whatever you want to call it. But it works pretty well. Okay. Saster Sponsors is our newest one. This is the one that I use Cowork a lot more for. If you, you can actually go to sastersponsors.com so this is external facing. If you're logged out, which I'm logged in, you'll still see a bunch of the stuff you just. If you want to take a look at the website, just to see how it works, you can go to it. We decided we would just leave it open and then we would only gate. You would only need to sign in for things. Like if you wanted to actually submit a task, you have to sign in to pick your Booth you have to buy. So you know, you can't pick your competitor's booth to be really far from you. It's got some gated features there, but for all intensive purposes we were like, you know, a lot of our sponsors have either third party agencies or other like contractors they work with when it comes to something like Sasser. So we're going to keep it open so that anybody can access most of the information at any given time just to see it at a glance. But if they need to take an action, that's when it'll prompt them to sign in. Interestingly, that is something that I wrote into the spec with Claude. I was like, and I'll actually show you that and then I'll come back to the website. So as I've already said, we were paying for an existing tool here, but I'll open up my blood chat. Okay. It didn't come up in the browser. Let me see if I can get it to. It's so used to be on my machine it was like, can I open on your Mac? All right, cool. In the browser's a little better. All right, so this is the whole chat. I linked it in the slides. So if you want to read my whole chat with Claude on specking out the sponsor portal that I built, go for it. I actually think it's a super important step if you are going to vibe code your own simple SaaS. Apple is to write the spec first and actually that was a pro tip from Jason is to write the spec first so that it's kind of like bounded. It knows its parameters, it knows what it's going to do and it's not going to go crazy on like trying to self validate and do like a bunch of crazy features that maybe would break in that you don't need. So highly recommend writing a spec first. I happened in this case to have an existing tool so I gave Claude that existing tools URL Just the front, just the front end. I was like, here's the URL, the front end. Take a look at it, you know, see what it's doing. It looks very similar to the one that's live now and like write me a spec. But also in the new spec make sure you have, you know, basic AI features and tooling. Make sure that anything I put in is going to be able to have that functionality. You know, like let's benefit from AI. Like let's build that into the platform where the other one didn't have it and then certainly you can see it's your First I was like most importantly and needs to have single sign on. So whatever you write for the spec needs to keep that in mind that like it's going to be a single sign on tool. I literally said to plug, you know, I want to keep it open. Since our, since our customers have people that are going to work on their, work on their event sponsorships with like their agencies. That's super common, right? These are really big companies that we with sometimes some are startups and so sometimes it's also like the CEO or like their, their chief of staff is on it. And so I wrote that onto the spec. You can read it all there wonder board later. But I think it's a good format to always write the spec first. It's super important to be able to do and then like, you know, have a conversation with it. I'm like, okay, does this look. Mine looked pretty good B1. So I was like, okay, this looks like what I want. And so that was the first thing I did before I went into. In this case, these screenshots are from replit. So then I took what I wrote with Claude as a spec and I put it into replit and I, you can see when I very first started I said how can I add true single sign on? Not like faux single sign on. Sometimes if I've got an apps like it'll do stuff that's not real. So I was like true single sign on make it actually real. And I wanted to do this because as simple as it sounds, actually our old third party tool we were using for this didn't have persistent single sign on. So if I signed into our previous application of this and I submitted a bunch of stuff, disaster. And then Jason logged in, let's say to the same instance. He wouldn't see what I did. For some reason it wasn't persistent. So that part had always kind of annoyed me. And so I was like, oh, I want to do true single sign on across the org so that we only gate things that we need to anybody from their agency. So you can do it but also you know, make it smart enough where like if they join and it's their company domain or that anybody can join. Because the other annoying thing we had to do with our old platform is like me or Wendy who's on our production team or David would literally have to invite somebody anytime they need to add somebody to their instance. And I was like, why? This is the age of AI. Like can't you just look up their domain, see if they're a sponsor and then like let them into the portal. So. And the answer was yes, yes, it could do that. And so that's where again, I used a mix of Cowork to help me think through this, as well as the replit agent that is just in the agent to say, okay, what can I use to tackle Single sign on? They have a, it's not a native integration yet, but I think it's coming. They use a tool called Clerk to tackle Single sign on. And I was like, okay, let's do it. So I had to sign up for Clerk and then my chat's really long after this. But this is how I go through building true Single sign on and some light AI features into this app that we were previously using. So I'll go back to it because it's pretty cool. Exit full screen. So, yeah, this is what it came out with. I think part of where I used Cowork a lot too for this tool specifically was since a 2025 version of this exist that I paid for in that not only did I write the spec with it, I was also like, okay, you've now ingested and written the spec for the new portal. Great, I already gave that to my Vibe coding app. Now take all the information from this year and put it into this, like, help me rewrite it so that I can give it to the replay agent to put into this portal so I don't have to copy paste a million freaking times. Like, just do it for me. And then the other thing I did was actually made this a lot smoother and a lot faster. I just gave Cloud Cowork because it's on my machine. I already had all the contracts right, of all of our current sponsors, all of our current customers for Sastra Annual this year. And I said, work in this folder, go through each contract and like, this is what you're going to need to do to create this like, app. And I, I, I told Claude specifically write it in a way that a Vibe coding app will understand it because I'm going to give it to the Vibe coding agent. Like, I'm basically going to output with you as an agent and give it to another agent to deploy. And it said, okay, I'm ready. And it worked in my, you know, on my machine, in this folder, it went through all the, it went through all the contracts, etc. And, and it came out and I told it to look for a few specific things. I was like, one, you know, make sure you're capturing the company, their URL, etc. To make sure. You read each contract to see how many sponsor passes they have, because this is important for registration. And that's like one of the first things people do when they log into the sponsor portal. I like to see how many customer passes they have, see if they have any speaking stuff and then also tell me what day they sign so that I know what order that they'll be in for boost selection. Because that's what we use for boost selection. It did that in, I want to say it took like an hour because there's a lot of, there's a lot of contracts they had to read. They're a little complicated and I checked it so maybe a little less than an hour, but let's just say an hour. It took Claude go work an hour to do that. And then I told Claude, okay, great, like all the data looks good. Now go into our event registration platform, which we use Bizo. And I was like, give visible the sponsor codes it's going to need. So like, you know our. Everybody has a unique sponsor code. So like tell go into it. Like click into it. Because I had it open on my browser. I was like just clicking away and start creating. Like I was. It started making the codes on its own again. Probably took another like, whatever, 20 minutes to do that. It went through. Everybody made their codes. I was like, great, now make all of their customer nomination passcodes and all their promo codes and all that. Everything I just did there with like cloud go work in a couple hours. We used to do with a human. We'd be like, hey, check the sponsor list, Check our contract. Like go into each contract one by one, read it yourself, put it into visible, tell them how many tickets they have, create the promo code and then email it to them. Because back in the day, our old tool we were using couldn't ingest unique codes like this. So when I click this one, it goes to like a saster code. When you know a different sponsor clicks theirs, it goes to their sponsor code. I'm not going to show you their code so that you don't use them, but it goes to their unique registration code for them. And so I was like, that literally used to take us a day. And Claude just wiped it out and he knocked it out in an hour or two. What a champ. It was super interesting. I was like, I know this is something that AI can feasibly do a little bit better. It also made this entire timeline of what we do. It made our campus map more interactive so that when sponsors come in here for the first time and Get a lay of the land. They know exactly. Like, okay, what are the, what do these clouds mean? Like if you're a first timer, it's probably a little hard. So it add all these widgets so that you can see what they are. Pretty cool. And so there's a lot of other stuff in there. Like I said, you can feel free to go to sassresponsors.com that's what we built. May not be relevant to you. Well, if you're coming to Saster, it's still got like the days and times on there, but I think it's just interesting to click through it and see what is feasible and possible as a now forward facing app. Um, I'll say my biggest fear I had when I was I like tested. I would say it took me like an extra half day on SaaS responsors to deploy just because I was testing everything so much. I was like, I have not done again, I'm not an engineer, I've not done single sign on ever before in my life. This is the first time I'm doing it so I want to make sure it works. I would like sign in as like different emails and I'd be like, okay, let me try to submit something there and do something there. And I was like, I don't know, it works. Like I kept waiting for it to break a little bit more. I was like, I don't know. I was like, the single sign on is working. Could it be that we've built a better Vibe code and tool than what we were using previously and this is the first iteration of it, right? Like it's February, there's still some time disaster. So we're going to build a few more things into the Saster sponsors. But it was again, I don't know if I could have done it without the cowork element involved. Maybe it would have taken me a lot longer. I also got like a little bit stuck at one point with single sign on and it was like, try to tell Replit to do this. And I was like, okay, I told it and then it worked. So it did help a lot as like my buddy for me to get this all done. But what's the catch, right? And then we'll do Q and A. So I think I mentioned it at the top but you know, biggest catch here is again, if you're just starting to explore Vibe coding, if you're in one of those three buckets of you haven't really built out an app or agent yet, that is to this level of sophistication. I wouldn't feel embarrassed in any way by that. Like, this was a fairly, it's still simple on the surface, but was still a little bit more complicated to deploy. And so I don't think I could have done it, you know, nine months ago. This is only having built other apps into production, different websites, different things that are now out there in the universe that I knew, I knew feasibly it could be done if I just solved this single sign on thing. And so that was the biggest risk. And so I spent a little bit more time on that. That was the majority of my time is making sure that would work and then programming it and then doing a bunch of extra testing because I was like, I don't want to send this to 100 sponsors. And then I get a hundred. I was like, my worst nightmare is I code this thing I send to a hundred people and they're like, amelia, I can't log in or I can't do this or my registration code is wrong and. Or it told me I was a platinum and really I'm a gold. Like I had so much fear that it was going to get some of this wrong, but it's extra, extra, extra time testing it and I was like, I don't know, man, I've tested it all. I felt like it's working, like it works. And so then I sent it to like 12 sponsors. I was like, let me send it to 12 people, see if it works. And then they were submitting. There weren't any issues. I could see what they were submitting because I also built, I also told the app to build me a, what I call a super admin back end so I can see anytime somebody submits anything, which is super cool, which the other tool didn't have. And so this is really, again, it was a scary situation, but one where I was like, okay, I've tested it up, I just have to ship it to the first full people, see if anything breaks and then go from there. But it was honestly my worst nightmare to be like, if this doesn't work, I'm just going to. I was like, you know what, I'm just going to go back to the other tool if it doesn't work because I can't deal with like a thousand emails that they can't get into the portal because the benefits will not outweigh the cost. But yeah, the other thing is like, I do keep futzing with it, which I need to not like there are other things I want to build into this portal now where I'm like, ah, what if we did this and what if we did that and what if we like now that all the basics work and they're working fine and they work well, I'm like, there's all these other things I want to do now, but I actually need to stop messing with it. It's hard to do that I think to some degree because it's also a little bit detrimental to my time. I'm like, I just need to. Again, that's not something I would be doing if I just bought an off the shelf tool. Like some of them are how they are, right? Like you can do some additional agent training and you can do new campaigns or whatever, but you're not futzing with the actual like app and the backend itself. So I was like, I'm just gonna stop because I have to. So all of that to say, can you really vibe code an app into production? You can, but obviously with a lot of asterisks and daggers there, it should be something simple, it should be something where you know, you have something either proprietary or stuff like this where you can't find an off the shelf solution. Again, if you boil down the things we've done with it, which are, you know, websites, valuation calculators, now this SAS Responsors one which is basically a project management tool. If you think about it, it's not super comp. Like they are complex but they're not complicated in the sense that like feasibly, yes, you can do these things again versus like trying to buy code your own. I'm not going to try and buy code my own CRM and like recreate 10 years of data and touch points and who opened this email and when, like that's too complicated. I'm not gonna. So just not worth the trade offs of, you know, buying Salesforce versus building something like this. I think too why we've bought versus built a lot of things we use is a lot of these third party tools at least today are, you know, they're compliant. Whatever you need. Some, some of you only like SOC 2 or whatever or ISO, whatever, they're secure, right? Your data is safe. Like this is. Again, neither of these two tools I've built recently are storing like super proprietary data. So to some degree there's a, there's probably a little bit of risk there, but it's worth the trade off because it's not the anything is not the end of the world there. Again, it's not like table stakes and typically to these apps that we've bought and have, you know, we, we have an FD each of these, and that's not unique to us. That's just, you know, how these products work in this day and age. Most folks will pair you with an FD to get it going and to help you run it and deploy it, which, again, for a time perspective has a lot of benefits to somebody who knows how to do this fully. I'm going to let them do it. Like, I'm going to spend, you know, once a week with them. Like, I suspend once a week with like qualified artists and agent force. But I'm like, hey, it's, you know, 15 minutes. Here are things I'm kind of looking for our agent to do. They go off and do it and then we come back. Like, I'm not spending the rest of my week trying to fuss with these agents all day long because they can't. Like there's other things to do and. Any last points on that, Jason, before I get into questions?

No, I, I think you hit it. I, I, I, I want, I want to save the remaining time for questions. One. One, Captain Obvious point, though. Two, Captain, all the stuff, obviously everything, the quality of these apps you can create yourself is accelerating. If you, if you haven't done it or don't get it now, actually now's the best time to start vibe coding. Right. If you have to. Right. The next best time is probably next week because the pace of acceleration so great. Stating the obvious, I, I asked Claude what the value of Amelia's time was and Claude said, depending on how you calculate it, between 1,000 and $2,000 an hour. That's her time. Now that we're so such a lean team with so many agents of humans. So there's no economic justification for software cost to building these apps. Right? You can buy them for 10 grand. Like, it makes no economic sense. So you have to really need something that you can't buy today. It's, it's almost beyond the 9020 rule. If your time is, is if you're, if you're, if you're working in, in Tulum or Bali and you're just futzing around, I don't know, your time might be worth $5 an hour. I don't know. But this is something we had to build for someone built, that's worth 1,000 to $2,000 an hour. You have to be careful. The boundary time, you have to be careful to not fudge. But, but, but that's, that's the bar for us to build something versus buying something something. It is not economic. So any. That's what Claude said. But it is worth it because these are high impact things where we get extremely high value out of an AI VP of marketing and a sponsor portal that will interact and manage 10 million of revenue and make that process infinitely better than it's been the last 10 years. Like infinitely better with AI. So those are two thoughts but we can go go to questions from there.

Yeah, it's fine. Like somebody asked me yesterday, they're like hey would you white label the Sasser sponsors? I'm like just don't.

No, I think it's a good. I think it's. It is but, but then you have to support all the customers. You have to do all.

Yeah, I was like I'm not supporting you.

The. The future, the future of Vibe coding actually and we've worked closely with the Replit team on this. It. It is early is now that you can really build these things for real. And when we started on Replit last summer and it was true of Lovable and Bolt and others, it was very hard to get something into production. It was you. If you've watched my journey now, if you, if you put in the time and you have some familiarity with how to build software, you can build most apps that you want to. It's. It's radically better. So the next frontier is maintaining them and all the stuff if you talk about Vibe coding is about building, getting going and, and we're going to have a whole replet Vibe code at Saster AI 2026 in May 12 through 14 and we'll help you build apps and common. It'll be fun. You can build your own B2B app together. It will be very unique and we're going to promote that all and we're going to have a whole day called Saster deploy on the 12th just about deploying agents. We're going to teach you how to do all of it and get it. Get you into production. But now that you can actually build these app, who's going to maintain them for the next five years? So white labeling sounds fun but, but for. For us if we couldn't make millions from it, it wouldn't be worth doing the customer facing side. And so let's get to more questions but the interesting frontier not to get distracted is who will maintain these apps? And the, the now that we have 10 or 20 agents running and probably 10 apps we've built ourselves, it's us. Right. And so the maintenance goes more and more to the top. So issues to work on in 2026, but very interesting.

Yeah, I. I do hope one of my agents probably clock and get good enough to manage the others a little bit more.

It's a dream right now. No matter what, it's a dream right now.

I know it's. It doesn't. You know, sometimes it, it relates to the first question that we have. Sometimes he times out, like, on my Mac, I'm like, what? Like, I'm on like the beefiest MacBook Pro you can have. Like, maybe I need to move to a Mac Mini in a closet. But sometimes we'll time out on my machine. I'm like, dude, yeah, yeah.

But the app does. But these apps don't time out.

Yeah, yeah. So it's just a little funny. Okay. The first question from Steve was, is there any advice on a good way to start store and reuse prompts to reuse over and over or to test in different LLMs? I have 15 minutes. I've uploaded into cloud and it keeps crashing. Any ideas? I think just a quick one on that. If you haven't tried Cowork or in the browser or if you're not on the Max plan, I'm gonna say, like, I got so frustrated being on whatever the base plan is of Claude, whatever it's called, Pro, I was like, I have to go max. Like, this is so stupid. And then it stopped. Like, so every now and then it'll crash or he'll timeout, but definitely less often. I think having him in the browser and always using. I honestly think Opus 5 was still fine. Like Opus 6 seems to crash a little bit for the last four days, but I think it was fine. So I actually think there's. To answer your question more bluntly, there's no great solution for this. I still have a backup word doc of all my prompts and contacts that I put into different agents too. So again, there's not an AI to do this for you. So that's unfortunately still still the short answer there. Okay, next question. What percent of your. Are you English or Insights? Yeah, okay, we touched on this a little bit, so I'll try and rephrase the question a bit. So the next question from Kelly is what percentage of SaaS companies are you seeing now get hit with the current market conditions? This is probably a better question for you, Jason. Are you able to share anything about your conversations with folks in the Saster community on what makes them successful to avoid some of the kind of market reaction lately?

Well, look, the Market reaction is brutal. I mean, Shopify had an incredible quarter they just announced while we are doing this growing 30% at I think 12 billion in revenue. And it's the, you know, the market did, it's down 10.4% today. It's brutal out there. And what can you do? Well, first of all, on 20 VC with Harry and Rory, we have Michael Cannon Brooks, the CEO of Atlassian, coming to talk about it live. We recorded it yesterday. So listen on Thursday to that pod. It's pretty, pretty good because Mike talks a lot about this. Practically speaking, his response is there's nothing he can do. He's got to go with it. He's got to motivate the team and get them through it. It's like, you know, Atlassian beat the quarter. It's re accelerating at 5 billion in revenue and it trades at 4x ARR. Like our world that we know doesn't really work. If atlassian gets forex ARR if Shopify growing 30% at 12 billion falls 10.4%, the world that we've grown up in the last decade doesn't really work well. And you really can have two options. You can sort of hope and pray that we get back to the old days. I think that's what most startups are doing. When I get investor updates from folks that aren't that AI forward, that are still single product, they're just kind of hoping that things will get better because they're not publicly traded. But the simple answer is you have to get AI budget, you have to grow faster. That is what the world's saying. It's hard, cry me a river like you have to grow faster every single quarter. And if you're not in B2B, you're not getting AI budget, you're not changing the world. We had to build the sponsor portal because the dated crappy SaaS B2B products weren't agent level, they weren't disruptive, but the one we've built is disruptive. Now hundreds and hundreds of human hours are going away because AI can handle the sponsor portal. That's what you have to build something that good or it's going to get canceled. Like this 10k product. We just aren't renewing. They may not even know yet because we've ghosted them, we don't need them. There's no chance to save the deal. We've already built our own. That's happening to folks. You're either at the cutting edge of AI or you're getting displaced. And the question is Just what's the speed if all your customers are on five year contracts? You can hide if you want, but everyone, there is no middle ground anymore. That's the best advice I can tell you.

Yep. Yeah, I think too if like you're, you know, maybe.

And then, and then one last thing I would say to founders on this. I wrote this on Twitter yesterday and then I'm a longer post on Saster. Ask yourself calmly, use your own product. Is your jaw dropping? Is your jaw dropping? Almost every, if anyone that has even a couple million in revenue, up to billions at some point, your product was a jaw dropper or you never would have gotten there. You, you utterly changed the lives of a stakeholder of a customer. They didn't buy you because you're 1% better. They bought you because you were you. You're jaw droppingly better. At least for some niche use case. Be honest. In the age of AI, are you as jaw dropping as Claude? And if you're not, that's why you're decaying. And you've got to find that jaw dropping AI moment where, where your jaw drops that your AI agent is so good you can't believe that was even possible six months ago. That's how you're going to build a $10 billion company today. Or you're going to end up trading at one times revenue. There's nothing in the middle. So ask yourself honestly, would you renew your own product today? Would you pay more for your product than last year? And would your jaw drop if you're exposed to your product? Are you trying to ram something through with the decaying sales and marketing team? That is not a jaw dropper anymore. That is not a wow moment. Where's your wow moment from AI? They're all over the place. All the Saster AI tools we put up on Saster AI agents are, they're, they're, they're wow that your jaw drops when you use them. Right? You know? Sam Blonde launched a tool Monaco. It's our next AI SDR tool. Like we don't need another one. It launched today. You can find links to it on our agent page. It's even better than the other ones. You know what it does with this Monaco one? Like it finds your icp, it calls them for you and sets up a phone call or a meeting for you directly. You don't even have to do any cadences or anything. It literally sets up meeting meetings for you in your calendar. For real that have been confirmed with a human. I mean, that's a jaw dropper. Isn't it? Amelia didn't even believe how good it was until she saw it. And it's a Jaw dropper. Want to pay 53,100k for a jaw Dropper? Yes. Do I want to pay $200 a month for another crappy project management tool? No, that's today.

Yeah, I give as just to tie it all in. Right. Like, I think the big thing that took me over the edge of the last two weeks was like, I was like, okay, this tool. Like, I was like, it's time to redeploy our sponsor portal. But again, the one we've used has zero AI and that kills. I was like, I can't be sass or AI and deploy something that has no AI in it. Like, that's just one totally terrible that they haven't done at least the very basics with AI. But it's funny because after I showed it to you, just, I think he made the comment like, well, what about these other apps? And you named a couple other ones where I was like, honestly, I feel like I could start to rebuild it. Maybe not till after annual, but there's a few now that I'm, like, literally looking at where I'm like, they fall into the same bucket of. They have not benefited from AI at all. There's just no new AI features. There's nothing good about it. There's no benefits to it. I'm like, you know, I'll probably move off those two or three other tools we named next because there's no benefit to staying. Like, there just really isn't. So, yeah, Monica's the newest agent. We're gonna. We've. We've already started using it. We just got onboarded last Friday, so we'll check in in like another week or so until you guys are around on this. Sam, who you guys might have known from Brux, who was the CRO there, launched this tool after, you know, going through this very frustrating process on his own of, you know, trying to wrangle VRs and VPs of sales and other folks to do outbound. But also when you're starting out and you're less of a. Less of a, you know, maybe name brand as Brex became and then got bought, you may have problems at the early stage, filling your pipeline. Right. If you're at super early stages, you may have nothing in your CRM. And so Monica is really cool. We're actually using it for a very unique use case that I think is not a totally not their SAP, but the tool's pretty Good. I was like, you gotta let me use it. They're like, what do you have? Do you already have like three or four sales agents? I was like, yeah, but this one's so good that you gotta let me use it because I have. I was like, I have another use case for it. Like I have another part of sales and go to market that's not being tackled that I want to tackle with this agent. And then this agent can go deep on that. And so I'm pretty stuck. I'll go to the next question. That's. That's Monica. You guys should check it out. It's monaco.com. they actually own that domain. That's an interesting story, but maybe we'll have Sam on next time to talk about that too. Okay, a couple last questions here. Let me get back to our chat. Someone asked if we've been looking at openclaw or claudebot. R are. Do you. Do you want to quickly explain that Ren is on?

We haven't. Listen, I get why engineers are interested. Let me simple answer. It's not interesting to us today. And maybe breaking guardrails and having rogue agents running around is just not something we need. I get it's very interesting. And we built, yeah, we built, we built an app called Renai. You can use it. It runs autonomously and has extended memory. So I get the appeal of it, but it's really not for what we want to do, which is, you know, GTM type stuff. Anything that needs to run autonomously, we can just have an app run autonomously. We can just have these apps that we built on Replit Run 24. 7. It's really not, I'm not saying it's not exciting, but we're not interested in breaking guardrails. Actually. What's more important for us is making sure the guardrails work.

Yeah, there's.

Funny enough I said it's exciting, but today we don't need this stuff. Like, it's not that I'm not interesting. We're all over Molt Book. You can watch the things our agent wrote about buying 400000 of watches that we didn't ask for and other things which are all sort of fake that our agent wrote and, and we've built versions of it. But. I know, I just, I just, I just think that what's much more exciting is just. Just having, well, guard railed agents that know your data cold and can run on their own. That's all we need today. So I'd say we move on to the next Question today.

Yep, there's a good one. Kind of related to security and some of the points I made earlier. So you know this because it was one of our apps that broke last week. But this question from Steve was you mentioned that some of your webpage apps are public facing. What are you doing currently to protect the vibe coded apps and tools from attacks? How have you tested this?

Look, I, I think it's a great question and I think it's something that the platforms, you know, first of all this I'll give you, I'll give you two simple answers. One, the platforms have gotten better. They all do basic security scans when you launch an app now they look for, for, for private keys you've embedded in the code. They look for other things. They, they do a lot of the basic stuff which is helpful to one way or another. What you should do with the agents now is they're pretty good. You can do this in Claude code, you can do it in replit, you can do it in lovable is ask them to do the deepest security audit possible on your app at least once every month or two and they're pretty good at it. And it will, I'm not saying it's perfect, but it's better than most probably low end developers would do. If you had an outsourced dev shop and they'll find an infinite number of issues and it will take you hours and hours and hours and hours to fix them and undo it and it will overlock your app down and it will stop you from able to do uploads and it will block your internal APIs and it will drive you crazy. And each time we do an internal security update it takes about a week to recover to fix all the stuff we have to fix and unfix and refix and there are more and more third party tools. It's a real issue, it's a large issue and it is not an issue that's fully solved. But the platforms are getting better. And then before you release anything with any customer facing at least with the agent, tell them to do the most in deep security audit possible. And I'm not a security expert but as a SAS founder I've lived so many of the issues. I've been through so many security audits, we've done our own. I think you will get a decent outcome but it is an open area.

Yep. Okay, we'll take a couple more, then we'll break. Question related to just our time trade offs. You touched on it earlier but I don't know if you Want to add anything else? Do we have enough time to do everything else that we're supposed to do by spending so much time?

I think we're at the limit. Yeah, we're at the. We're at the. We're at the limit. It's a big. It's an interesting issue for the future. It's. It's an interesting issue for your team. I mean, there are better people to build and manage agents than me and Amelia out there, but there's not like so many. And how many folks you have on your team, like, who on your team could you hand these apps off to? Who can you hand off your agent management? I'm sure there are folks you, you are on your team that can do it, but I, I think honestly you're probably lucky if 5 to 1% to 5% of your team could. We could offload the management we have. And I think it's a very, It's a challenging issue of how many, you know, we are at the max. We did add Monaco, which we love, but only because it's disruptive, only because it fills a gap that we don't have. Otherwise we would not add another GTM agent. We're just overloaded with the inputs we have. Right. So I think this is an issue that most folks haven't contended with. But we're at, we're at our max and we're going to learn this year how to, how to do it.

Yep, there's some good. But I'm reading through all the questions and also AI notetakers. In the chat real quick, Someone said, can you talk about the capabilities with AI.com? we don't use that one. So sorry, I can't answer that one. All I know is that they had a Super bowl ad and then they're doing that.

I think, I think it's off point. Yeah, it's. I try. It's just, it's just, it's just a, A hosted clawbot. It's not interesting to me to pay 30 bucks a month for that. Someone else can do it.

Got it. Okay, question. What about. Okay, another question from Eric. What about the human element? I was surprised that a bullet point on the buy 90 wasn't. Essentially, I have someone on the team. Oh, I was surprised that a bullet was. That there's a human as part of the team. Yeah, I think. Not really sure what your end question is here.

You need someone to manage the agents, I think.

But yeah, you need someone to manage the agents.

There's no. Listen, maybe toward the End of this year, when we do AI workshop Wednesday, it'll change. And I know some folks will challenge it, but for the kind of stuff we're doing, this is a lot of stuff you guys want to do. GTM agents, marketing agents, sales agents, interactions with customers. There is no set and forget. There is set and less work. They are certainly each work. If you don't want to advance your agent, particularly every. Every week, it's less work than the week before, sort of. But when I catch up with Amelia each morning when we start working, she's like, I. Now's my hour to catch up with my agents every single day. Every single day. So there's no. We've talked about it before, but there is no set and forget in. In. In the kind of agents we're talking about. Unless you want mediocre outputs. If you want mediocre outputs, you know, train it for a day and go away and you'll get. You'll get mediocre benefits at best.

Yeah. I think Eric's commenting in the chat on Port his question, but I think too, like, my response back was like, a part of why we buy 90% of these things is if they'll give us a dedicated fda. Like, if they say, oh, you know, like, you'll have just our normal team behind it. I'm like, I don't want that. Like, I could do that myself. Like, I want. I want an fte. That's the, that's the new standard. That's the precedent that like Salesforce and others have said. I think if it. If you can't get an FD out of. Out of the tool you're trying to buy, maybe don't buy it or see if they'll push them to see if they'll give you one. I know that's the new gold standard. Not everybody has the resources to do it at point some scale. But for us, like, if it does, you know, if we can't get an fd, I'm more likely. And it was the same for Monica, right? Like, not only did Sam himself get on the. The call to get us set up in the agent, but he had his FD team on there to be like, okay, here's how we can onboard sester in like a day. And so again, that was part of the magic of why I was like, okay, I'll add. One, it's a pretty good. I was like, it's pretty good. Two, I was like, yeah, and she'll give us the resources to deploy it then. Then I'll use it like not, you know, then I'm more likely to use it too versus again building something where either it doesn't exist or they may or they want or maybe another reason to build something is if they won't give you an FTE then you kind of lose a lot of those benefits. Okay with that? I know we're a little bit over time, so to Jason's point, if you want to learn more, I use some of the faster annual branding for this slide deck, but faster annual.com will be there in May. We're doing a full deploy day that's new on Tuesday. So content just like this on deploying agents. Some of it will probably do, but otherwise it's going to be mostly other folks telling you how to deploy different kinds of agents. They'll go deep. They'll do deep dives. So that'll be exciting. Come to that. Thanks all for joining here. Thanks for the nice comments and all that jazz. And we will do another one of these fairly soon because the world keeps changing every it seems like every week. So. So we'll do this soon. But yeah, in the meantime, if you want to know more about the market and stuff. Yeah, listen TO it's the 20 BC podcast that Jason does with Harry and Rory every week. It is Thursday. It drops Thursday morning, so the new one will be out tomorrow morning. You can go to the 20 BC YouTube to watch it. There's a lot of really good insights. There's no politics much like this. So highly recommend listening slash watching that one too.