Billy Howell (4:01)

Hey, Nick, good to see you. First time. Long time. Long time. First time. I'm one of those. I'm really excited to kind of talk about Vibe coding and help people kind of cut their teeth and show that it's approachable.

Nick Sharma (4:13)

Amazing. Yeah, we got to meet through the AI Summit. My friend Troy, I think, did a consulting session with you and was blown away by what he was able to go and build after spending like an hour with you. And then we thought, we gotta have this guy at the AI Summit and not just talk about AI, but like show people. And you ended up building an app on stage. And it was our most talked about session of the day. So thanks for doing that. And now I'm excited to take that and bring that to everybody in the limited supply community. So just to give us a little background, Billy, can you just talk about, you know, you're known for Vibe coding, but this is obviously a term that just kind of became popular. So just give us a brief background on who you are and how you got here because I also want to illustrate how accessible this can be for somebody who's listening to start leveraging or getting into the world of vibe coding.

Billy Howell (5:09)

I think kind of the most like important thing that is kind of kept me interested in coding my whole life as like a non coder, a non technical person. It's just kind of like the apps I used growing up and so like going up like you know, the ipod touch came out and so the app store just blew me away and the whole Facebook story and Snapchat. I was fascinated by Snapchat and so I always wanted to kind of build something with code. I just didn't really know what it would be. Kind of, you know, would take, would watch YouTube videos and take courses, but would always kind of tap out after a certain point of just googling questions and not knowing what was going wrong. I actually took coding class in college and got a C plus. So I'm by no means a.

Nick Sharma (5:56)

If only you got a C. But.

Billy Howell (6:00)

There we go, now we're cooking. And I guess professionally I started in consulting, doing kind of DOD consulting in dc. Um, and then I quit during the pandemic to kind of start my own business doing some SEO consulting with startups. And when ChatGPT came out I just naturally started trying to use it to help my clients and improve my own workflows. Pasting in like Google app scripts, asking ChatGPT to debug them and then going and testing them. And then Replit came out and sort of chatgpt was like a zero to one for my coding. Like, like replit would be like a one to ten because I was able to contain all of those things and self deployed apps and just iterate at the speed of light. And so then it was just kind of an obsession where I was building every idea I'd had over the last, I don't know, 20 years I've been thinking about apps, just throwing it into replit cursor lovable and seeing what I could bring to life and then continuing to just build useful stuff for my existing clients. And then it all kind of came to this point where I was looking for new SEO clients on Upwork and I saw a guy who needed something unrelated to SEO, like something with airtable, like data entry. And I was like looking at his stack and because I was really familiar with the technology he was using, I was like this is going to come out to be like $250 a month in software for something really basic like just a data entry app. And so I kind of recorded a loom and pitched him on a prototype I made of his app in like 30 minutes and was like, I could do what you asked for and use Airtable and Softr, but it's going to cost you this month. But I could also make you your own custom branded one that looks like this. And, you know, I didn't get into, I didn't say, like, this is built on replit and this is what AI coding is, because he doesn't care. He just cares if it works. And he said, I like your version better, Billy. And that was kind of the impetus for my agency, Stupid Simple Apps, was finding people who didn't even know they needed an app. But all, all of the parts were there for us to kind of piece together that, that story. And so now, yeah, I run Stupid Simple Apps and we make, we make startups, small businesses, venture studios. We make apps for all sorts of people.

Nick Sharma (8:24)

Yeah, it seems like too, you're not just, you're not making iPhone apps here. You're really figuring out workflows and processes that can be better, more efficiently conducted and turning those into an app. Is that right?

Billy Howell (8:38)

This is exactly true. They're web apps. And the process thing is interesting that you say that, because a lot of this was kind of before it was so easy to vibe code apps. I would make these long, complicated workflows in like, zapier or make.com for clients, and those can be really useful. But what it teaches you is that there's API endpoints for everything, and you just need code to talk to them. So you can build, you can take any of those workflows and turn it into an app. So I think that's really cool.

Nick Sharma (9:09)

Yeah. And so just to make sure that everybody follows along. So some of those tools you mentioned, like Cursor, Replit, we'll get into those in a second. But can you explain what an API is? I think people have seen API and some people may understand it's sort of like a connector. But what's the best way to explain an API so people can understand it for this conversation?

Billy Howell (9:31)

Yeah, so it's usually a library of endpoints. And you can think of the endpoints as, I don't know, different stores you go to. Each one is going to have different data or capabilities. So one API endpoint might retrieve user data, one API endpoint might take data and turn it into an image or transform it in some way. And so when you look at like a make.comers app here, any of those nodes that you see in there, that usually means that there is an API that you could just use in your app. So if you're ever unsure of if something can be done or if a certain use case can be done, it's good to go shopping in kind of these hubs for solutions. Or you could go to somewhere like Rapid API or apify and take a poke around and see which ones are available. But basically how it works is there's a URL and your app sends it a packet of data, including usually an API key, which is what lets you get your unique data or just attach you to a billing account, because most APIs you probably have to be paying to use them. You send the API who you are and what you're asking for, and then it'll send it back in what's called JSON format, and you can make your app read that and use it. So there's tons of them out there, like Basketball Reference, if you're into like the NBA, like, that would be a really cool one to plug into, but I actually don't know if it's public, so maybe that's a bad example. But any.

Nick Sharma (11:06)

It's almost like ways to integrate another app's data or information and make it easily digestible within your app. So you can leverage it or visualize it or pull stats or whatever.

Billy Howell (11:15)

Yeah. And you can think of it. It's useful because instead of me having to store every single NBA player's data point on my own server, someone else is doing that for me, so I can just query it. And beyond data, they also can do things like generate videos, generate images, like actually, like manipulate things.

Nick Sharma (11:36)

Wow.

Billy Howell (11:37)

So like Open API has an API where you send it a prompt and it'll generate back a result and then send it to you.

Nick Sharma (11:44)

Right? Yeah. And even like Triple Whale, for example, they plug in a bunch of models. So essentially they're using APIs from other models to enable their workflows to do what we want it to do.

Billy Howell (11:56)

Yeah, that's kind of the secret sauce of every AI coding platform. Like Cursor Replit, Lovable. Basically what they've done is they've taken all of the models and found out which ones are best at which tasks. So they'll see. Billy asked to build a database. Well, we know that Gemini is the best at building databases right now. So we're going to send them this request and we're going to prompt it in exactly the right way to get that output that we want to then turn into code. Right. So that's just Kind of some of the secret sauce there.

Nick Sharma (12:27)

Yeah. Okay, amazing. I want to dive into. So like, what is vibe coding? So coding. You know, when I was a kid, I remember. Do you ever remember using an app called Dreamweaver? It was like part of the Adobe suite back in the day to build websites. It was a terrible website builder for somebody who doesn't know much code. But between Dreamweaver and then I started to use WordPress and learned a little bit of HTML there. You know, that was probably the extent of my coding. And today I can kind of like read code because it follows this like legal type of format where everything's predefined before you get to it. But then you have to kind of remember what it defines as you go down. Yeah, but vibe coding is something that, I mean you built an app and demoed it on stage and people then built an app with you within an hour. So it's, it's much easier and it seems like you don't need to actually necessarily know the code. So how would you describe vibe coding?

Billy Howell (13:23)

Yeah, so I think it kind of to start like people, it was like a pejorative term where it was, they're kind of making fun of people. But I think it's back again. It has like a positive connotation and it's, it's just kind of like a way of like being flippant about coding and saying, you know, like, instead of planning out this multi step thing and putting it in a JIRA board like a proper software engineer, I'm just going to go off vibes and tell the AI to build me this and if it doesn't work, tell them to fix it and just kind of go that way and build in any order. And I think it's funny because you do actually learn by osmosis doing this, not in a traditional way, but you learn because you're able to rapidly iterate and just, you know, when Cursor first came out, like I was able to start working on you know, like two to three apps every weekend. Whereas like in the previous when I was just googling stuff on stack overflow, it would take me like a month to like get even close to finishing a project. So that, that rapid kind of iterative learning, building an app, then going and building it in a different platform or starting over and building it better using what you've learned. Now I understand like the React, like web framework, React and Node is what most people use for web apps. I understand it like pretty well. Mal and going into it, I had no idea what any of the folders meant or really how they were intended to work. So you do learn from it.

Nick Sharma (14:59)

Yeah, I agree. I think even with like the same thing goes for building a website or any other, even ads manager, the more you're just in it, the more you're just going to observe like, oh, if I do this, the reaction is this, okay, now I know that next time I do this how it's going to work.

Billy Howell (15:16)

Yeah, I mean it's like one of the only things that. One of the only skills that maybe you can like, you get enough feedback that you can force your way into learning. You probably wouldn't be able to do the same thing with golf. Trust me, I've tried. You need good feedback. Right. But because like the agent makes the correct fix for you and tells you where you went wrong, you can learn that way.

Nick Sharma (15:39)

I bet you can make a cool golf swing watching app that just watches your swing and immediately gives you feedback.

Billy Howell (15:48)

There's actually some really cool ones already. It's insane. They put you on a plane, they put an access through you and so they'll say like your shoulders are misaligned like 10% or like you're coming this far up. It's really cool.

Nick Sharma (16:02)

Yeah, it's crazy when. Well, maybe we're getting ahead of ourselves, but it's crazy to think that the concept of being able to build apps now in such a rapid amount of time is going. I mean, I'm just so curious about what it's going to do to the average consumer of apps because. Have you heard of Flowcode by any chance? Yeah, Flowcode is like flow code crushes because they're locked in with the massive companies that have huge procurement and privacy and data and security teams. But for the average person who's just downloading an app or wants to use an app like this, you know, like whoever had the number one spot in the app store before is, you know, it's probably not going to last because now anybody can make their own version of this app just tailored to them. Or take a, a version of the app that's already made and then enhance it to be just tailored around them.

Billy Howell (16:52)

Yeah, yeah. I think we're probably going to reach a point one day where you can just hand your login credentials to an AI and it could go in and reverse engineer the whole app and like rebuild it.

Nick Sharma (17:02)

That's crazy. How have you seen E commerce brands, whether it's on the op side, whether it's on the marketing side, or whether it's just A founder who's trying to be more efficient. What kind of problems have you seen get solved with vibe coding so far?

Billy Howell (17:23)

Yeah, I think there's two main ones. One is pulling all of your data into one place. This is a huge need for like I get this all the time from E commerce operators. Maybe you know, their marketing data is in one place, their Shopify data is in one place. You know, there's so many dashboards so they really just want to connect to those APIs and pull it into one report. Sometimes throw AI on top of that to get quick insights on like hey, you know, tell me some trends about like our marketing spend and how it relates to like our inventory or maybe make some suggestions based on like inventory we're high on and maybe could like discount. So there's a, there's a lot of interest in stuff like that. And then also you know how E Comm operators are like they have multiple brands, right? So even just rolling up because you may have used, you know, Shopify for one brand, Woocommerce for another and maybe those don't play nice together. So making your own custom kind of data viz for that. And everyone has their own KPIs that they find are most important. So yeah, bringing data into one place and then the other one is ecom operators are shrewd, right? And so they're realizing like, hey, I shouldn't be paying $50 a month for this out of stock widget on Shopify. I'm just going to build my own wait listing anything with inventory management. So at the conference this guy was, and I talked to him last week about it, about tracking shipping containers and then how that updates how many pre orders can go out in Shopify. It just doesn't connect. And every single brand is unique and their workflows are unique, which means they all have these unique problems. And so smart, smart ecom operators have been able to use AI to cut out those SaaS costs that stack up and then also just unify their data.

Nick Sharma (19:15)

Yeah, to your point too, like a lot of these, you know, if somebody's using like NetSuite for their ERP and they're using, you know, another company where they're tracking their shipments in our containers in from China and they're using Shopify and then they're also running Facebook ads. Like some of these platforms will not be talking to each other for the next two to three years, but eventually they will because they will have to. And I think this use case too is so great because you can just connect These apps without having to use like a body to do that. Right now you have to have a person who's manually doing all this. But you know, to your point just now, like tracking shipping containers and then justifying pre orders per day, allowable pre orders per day is such a great use case of two apps that for the next two years will probably not have an integration together. Like the shipping containers and Shopify have no need to talk to each other. But in this case, it's a great example.

Billy Howell (20:08)

Well, and I think going further than that, it's not so much a question of like, can it be done or will it be done in the next two years, Will the data all roll up? There's a million products out there for integrating your data together. Looker Studio or like Data Box, different things like that. But because each business has its own unique problems, even these sprawling platforms can't anticipate your needs. And also to do exactly what you want. It gets so fiddly. You know what I mean? Filter it. So it's only for this quarter, but only orders like this. You might as well be coding at that point if you're putting that much complexity into filters.

Nick Sharma (20:42)

Totally. Can you talk through the tech stack here? So somebody listening is like, okay, that's a great use case. Or maybe I should create a widget for my product page that, you know, adds an upsell or whatever it may be. What kind of tech stack are we looking at and how complex is it? You know, I'm like the one Indian who doesn't know how to code. So, you know, say it for somebody like me.

Billy Howell (21:06)

Yeah, I think having a chatgpt and replit is all you need. That's like mainly my stack. Sometimes I'll use V0 or Lovable to kind of make a pretty front end. They make really pretty UI, but at the end of the day just need ChatGPT for kind of planning and maybe troubleshooting and then repl it. Or I would say like Cursor is also a good alternative. Now that's a local coding ide, right? So it's going to be a little more intimidating. Whereas something like Replit or Lovable is all in the browser and all the code is stored in the cloud, so you don't have to worry about installing things like dependencies for specific integrations to work on your laptop. But I started with Cursor and then I went to replit and depending on like the size and the type of task, I'll flip between those two. I think Cursor is Going to be more custom, like, do anything you ask, whereas anything in the cloud is going to use the stacks that it's kind of trained to be best on. Like, does that make sense?

Nick Sharma (22:10)

Yeah, totally.

Billy Howell (22:10)

Yeah. So, like, cursor, if you want to be really custom, you're doing something that's kind of atypical or has lots of moving parts. Maybe you want to go slower, even replit or lovable, if you want to get to, like, a quick prototype, proof of concept, something super easy, like a database with username and login. But. But you can build way more complex apps in there. And I do.

Nick Sharma (22:30)

Right. And so how do you use ChatGPT versus going into a cursor or lovable or replit?

Billy Howell (22:37)

Yeah, so I just go in there and I use this app called Super Whisper, which I need to get a referral code too, because I keep plugging it in all these calls, but it's super cool. Yeah, I have the replit one. Throw that in the bio.

Nick Sharma (22:50)

I will.

Billy Howell (22:52)

With Super Whisper, it's voice to text, and I think I'm still on their free plan. And so I find that when you're talking to AI, it's more helpful to be verbose, right? Like, super helpful to be verbose. And you're just limited by how fast you can type. So I go into ChatGPT and I just describe the app. Like I would describe it to you here. And then if I have kind of unknown things, like, if I'm not sure how the app should look or how we should do something, I'll ask it to do that research. And then at the end, I'll ask it for what's called a prd. So Product Requirements Document, which is kind of something I've stolen from, like, software. Like real software engineers, right? Not file builders. And I just list, like, here's all the features, here's all the screens, like the pages we need, and here's, like, the integrations we're going to use. And then I'll just take a look at that and pop it into, like, replit or cursor and tell it to get to work. I find that makes your starting point a lot better because if you start out incorrectly out the gate, and I think this is where a lot of people get stuck, right? They've got an idea that's like. And they put in a sentence or two, and then the idea doesn't look anything like what they pictured in their head. So they're, like, trying to unwind all this code, you know, hundreds of lines of code. So you want to spend two minutes to get closer to a fully fleshed out idea before you start these. It'll save you two hours of time.

Nick Sharma (24:20)

We just onboarded two brands who are new to Applovin but very heavy Facebook spenders. One is a high AOV in home product and one is a supplement brand.

Billy Howell (24:30)

Now why?

Nick Sharma (24:31)

Well, AppLovin sees 150 million active users, users per day. The same way you'd want to test a channel like Snap is the same way we approach testing Applovin. So far, the onboarding was super smooth. We've been able to ramp up spend in just a short amount of time and I think we're still hitting our planned ROAS targets. Candidly, I haven't seen many platforms able to ramp up this quickly and I'm excited to continue investing into the channel throughout the season. I'm going to keep you updated with how our results are going, but right now you can get updates on Applovin's E Commerce Beta and be the first to know when opportunities become available at Nik Co App Beta. That's Nik Co Appeta. Check it out. Yeah. So two things I picked up since we started, two things that matter a lot. One is organization of data and the second one is the prompting, like the inputs you give it, you know. Have you figured out any tricks to make prompting better, smarter, more accurate? Like I was even scrolling Twitter yesterday and I'm sure you saw like the videos of the IKEA, the VO3 IKEA ad. Did you see that? Where like out of a box it just all opens up and everything animates perfectly. And the way that it's written, like the prompt going into veo almost looks like code. And you know, it's like, yeah, camera shot equals this, you know, this height, this, this. So I'm wondering, like, are there tools to prompt better or are there tricks to prompt better? Because, you know, most people, they, they tend to assume. And this happens in marketing too. This is why so many brands don't take off from a marketing standpoint. But they assume because they're drinking the Kool Aid, whoever they're speaking to also understands the same level of context. And I don't think, like, ChatGPT does a really good job asking questions unless you tell it to ask you questions. So have you figured out any tricks or tool, Are there tools that exist to do better prompting?

Billy Howell (26:34)

There probably are tools. I don't use them because there's just too many. I don't have the time to go experiment with them. You can get good Enough on your own. So one of the things I do, it's funny that you say about questions is in my System Prom at ChatGPT, I ask it to ask me three clarifying questions every time I send a prompt. And that just really helps get it thinking, get me thinking. So that's like number one, I would do that. And then whenever I'm coding with like an AI, like coding agent and I'm working on like adding a new feature or fixing something, I tell it to, I'll explain the problem, I'll say like diagnose the problem and find the solution, then walk me through it. But don't write any code because if you think about it, when you send a request, ChatGPT's got, say it's got 100% of brain bandwidth. It's going to spend 40% on thinking about the problem, then 60% on coding because it's going to think and then code. But if you just tell it to walk me through the problem, it's going to use 100% of that bandwidth to find the solution for you. It's going to poke around more because it's not thinking about saving tokens. So I found that really helps.

Nick Sharma (27:44)

Oh, that's really interesting. So the loophole there is, you're basically telling it to conserve tokens because it itself is trying to be efficient on the output.

Billy Howell (27:57)

And I even will tell it if I know something is going to be like a multi step thing, like it's going to build something out to come back to me to build more. I'm going to say don't worry about tokens. We can do this in multi steps. I don't know enough to know if that makes a difference, but I suspect it does. And the other neat thing about, let's see, Windsurf is kind of like Cursor. I think Cursor even has this now. But you can toggle in the chat in the input rather whether you want to chat or edit code. So you can just cut it off from coding, which is really useful and I recommend doing that.

Nick Sharma (28:34)

Interesting.

Billy Howell (28:36)

And then the other big thing is if something breaks after the agent has coded something, don't add more code on top of it. Roll it back. Most of these AI coding softwares have the ability to roll back to a checkpoint. So roll it back and then try again. Don't keep putting good code on top of bad code. Being disciplined about that makes a really big difference.

Nick Sharma (29:00)

Yeah. How easy is it to now take? Let's say you were able to build this web app and now you have at your brand for example, and they want to go and modify the design or the CSS or whatever it is. How easy is that?

Billy Howell (29:14)

Design in CSS is really easy. Like in replit, in most of them you can just like even click like a little pin button and then select elements on the page. You manly edit it in the chat, like it'll show you all the CSS values. Or you can say like delete it or modify it in this way or do this. Uh, so non technical people can very easily edit the design if you just like edit, add them to a repo. So that's a good question. No one's ever asked me that before.

Nick Sharma (29:42)

Yeah. Cause I always think like a lot of times people will think, well, you know, let's say I make an app, you know, is it easy to continue innovating? Or a year later, let's say somebody new joins the marketing team and I'm gone. You know, are they going to be able to go and take that from where it is and innovate or do they have to go back into the, you know, the text, the chat interface to make edits to that, whatever it may be?

Billy Howell (30:02)

Yeah, yeah, I might even be able to just show you one. It's, it's really like you can literally just like you're in like a bubble or webflow, just click in, into the preview in replit at least and change it. So that's a good point because yeah, you gotta have a lot of different teammates working on these on these sites.

Nick Sharma (30:22)

Totally.

Billy Howell (30:23)

Another, another good practice is to separate the app from the actual landing page or like the marketing pages. So at the beginning of the prompt tell it like specifically say don't build a landing page, this is just the app. And then you can deploy that to like app.your subdomain and then you can make a landing page either separately in a different AI or just like in webflow or click funnels or whatever you want to use. I feel like probably people might not think of that, but that's definitely something you could do.

Nick Sharma (30:58)

No, totally makes a lot of sense. What are some scrappy use cases you've seen being built very quickly and adding a ton of value, like lowest investment required for a pretty high value output.

Billy Howell (31:18)

Probably what I'm doing. Right. Like B2B finding people with like hot pain point problems at their business and then building them a custom solution rapidly, you know, three to four weeks. Right. I think that's the quickest path to like getting outsized returns on vibe coding versus making a D2C app and then having to figure out the marketing and the distribution. Right. So I'm always going to preach to go B2B first, especially if you've never done either because the average deal size is higher. It's more relationship based. One one on one versus D2C where you know, you might have like 50 customers but they're all paying you 10 bucks and there's not, it's hard to separate signal from noise on what to build. And so I think like for example, like AI receptionist for local businesses, building those custom or even just setting those up from an existing product as a big opportunity. Chatbots that are trained on companies data. Like we had a guy who manages like a restaurant group that does this charity thing every week and he wanted his menus digitized so that people can go on the site and be like, I'm in Fort Lauderdale on Thursday and I want steak. Like which one can I go to for this charity event? So yeah, little custom AI bots for people's data. Definitely useful. And that's big in E comm too, right. Shopping assistance.

Nick Sharma (32:55)

Have you started to see an internal full time role of AI coders or optimizers or I'm not really sure what the title would be, but somebody who's going into a company and saying wait a second, we've got all these processes that are being manually done. You know, we can start turning these into apps or you know, web apps to really save time or just make things a lot more efficient.

Billy Howell (33:21)

I don't know that I'm aware of that being like an internal role anywhere. But I think you certainly could make the case for yourself at your job and be that person. Yeah, because it just doesn't take that much time to spin up something that's like visually impressive and like demonstrates the value. And you know, since I've done a bunch of these podcast interviews, people DM me and be like, hey, I sold these like AI coding solutions to my boss, like to my CEO for 20k, 30k. Right. And their approach was basically build it out. Some of them built out the whole thing. I would build out just like a demo and then take a loom and send it to the CEO or set a meeting with the CEO and demo it for them there and see if you can get buy in. And even if they don't like that particular solution, they know all right, I got Billy in my back pocket now and they'll come back to you when they see something in a couple weeks that they think could be automated. So Yeah, I used to do this when I worked in consulting, was try to automate stuff in Excel when we were doing repetitive data entry and it got me on some cool projects and meet some cool people in the company. I wouldn't have. So I think it's a great idea.

Nick Sharma (34:35)

Yeah. I feel like in the next like two to five years there's going to be. There will definitely be, I. If not an AI team, I think a lot of brands or a lot of companies are going to have some sort of like AI, you know, consultant or a full time, you know, one person who's constantly trying to figure out how to make things more efficient. You know, I even remember like when notion started to become really big, this whole crowd of notion consultants and whatnot became really big because it was like, wait a second, we can make information a lot more efficient within the company. And I think that's going to happen here.

Billy Howell (35:08)

Yeah. And it's going to get to a point where it's so accessible that you're going to need an expert to point to that can say no to everyone being like, we should automate the coffee machine, you know?

Nick Sharma (35:17)

Yeah. When I wake up, it should know that 37 minutes later I should be at my coffee machine.

Billy Howell (35:25)

Yeah.

Nick Sharma (35:27)

Okay, cool. I'm curious. So like with all the apps that exist today, Shopify, Klaviyo, postscript for SMS or Triple Whale, a lot of these apps are starting to build AI. Where do you see the path? The way I kind of see it is I feel like a lot of these apps are going to try to build AI or leverage APIs of different models within their apps. And then as that becomes more familiar, we're going to start to see like marketplaces where I can go and download, you know, Billy's apps and just use them in my own store or I can subscribe to Billy's bot or something of that nature. How do you kind of see this playing out?

Billy Howell (36:09)

Yeah, I think to me the interesting thing is most of these products use these generalized LLMs. Right. Because they're like pretty good. And I think we'll see, I think we'll see a gold rush maybe of truly custom LLMs that are really actually trained on your data or data from your industry. Right. That's making them really good at understanding like, you know, I don't know, skus for like fashion rental companies, like pricing strategies for painting contractors. Right. I think that would be a huge value add and I think it's something that, I think it's something that people aren't focusing on now at all. Right. And I think that's kind of where the AI stuff started was everyone's going to have their own AI that's trained on their subject matter and somehow we've just kind of blown past that and we're using the. Because the generalized ones are so good and they do, they're trained on like the whole Internet, theoretically. But I think we're going to move towards like customized. Like this is an LLM that's trained on my data and people in my industry and it's really good at doing these four things I need it to do.

Nick Sharma (37:18)

Yeah. I even think if there's one guy who is such an amazing media buyer, why wouldn't there be a bot that he could. Or some AI or app that he has that does a weekly audit of your media buying or a weekly website audit, just takes all of this person's learnings and data points and whatnot. Or to your point about the inventory thing, you know, if somebody managed pre order inventory at Rent the Runway for years and understands how to do that at scale, you know, somebody who's running like Ben at Latico could just be like, wait, I'm just going to subscribe to this guy's app now. Yeah. And use all of his learnings to make sure that mine is perfect.

Billy Howell (37:56)

That would be really cool. I'm like picturing like you do a video call once a week to just like brain drain yourself and it asks you smart questions to train and then it comes back, it tries to solve problems, it comes back and then you can just kind of train it passively over the course of like a year and you'd have a really well trained bot.

Nick Sharma (38:15)

Is there any sort of like how have you best seen a way to like download your brain?

Billy Howell (38:29)

I think people are doing cool stuff with like Notion or like Obsidian, like taking in all their apps. I use granola lately which like records all my calls and then I can search in there. But like as far as my brain, I would have to take in like all my video content, all my written content, all my emails, and then synthesize, synthesize that somehow.

Nick Sharma (38:52)

Synthesize, synthesize.

Billy Howell (38:55)

I. I don't know. Have you seen something in this that's useful?

Nick Sharma (38:58)

No, I, I haven't. But you know, I've done, I've done the thing where you try to upload as much, you know, as many podcast transcripts or newsletters or that kind of stuff. But like to your point of the models, you know, like the whatever model it is that you Upload into it does not understand tonality. Like the same way that if you were to voice record in ChatGPT, that understands tonality, which is really interesting. So, like, there's. So, like, there are definitely ways to upload and then search, but it's still, at least from what I've seen, it's still not like. Like, for example, we. We have this thing called nickbot in our Sharma brand, Slack, and it's basically got everything that I've put out on the Internet uploaded into it, and it's. It's pretty solid and we've done a lot of work to try to make it more and more accurate, but it's still not, like, near perfect, I would say.

Billy Howell (39:54)

Yeah. Because it's got a cheat. Right. It's got to run like SQL queries in the back end to find. Oh, he's asking about this podcast. Let's search the transcript. It can't right the context windows. It just shows you how complex the human brain is. Right. These things are really smart. They're not anywhere close to what our brains can do.

Nick Sharma (40:13)

Yeah, well, our brains too, I think, are like, the more I use AI or the more I see people using AI, whether successfully or unsuccessfully. The real kind of secret sauce is in knowing where to turn and navigate and where to go next, versus just grabbing the answer and then figuring out what to do with it. Like, you know, okay, if this doesn't work, then the AI is not going to know what to do next. But if you know what to do next, that's kind of that secret sauce.

Billy Howell (40:42)

Yeah, absolutely. You think of them as like a really smart, like, high school intern or something.

Nick Sharma (40:47)

Yeah. I feel like the notion that AI is going to make people dumber is. It could be argued against pretty heavily. The same way that, like, Wikipedia would.

Billy Howell (40:59)

Yeah. I think it's going to make people crazier, though.

Nick Sharma (41:02)

For sure. For sure.

Billy Howell (41:03)

The way. And also, yeah, impatient is right. Every time I build out one of these apps and I'm doing it with my buddies and I'm like, oh, man, it's taking like five minutes to spin up this app. And it's like a miracle, like a year ago or two years, whatever, copying and pasting stuff one file at a time into ChatGPT, and now we're getting impatient. That's funny.

Nick Sharma (41:26)

No, totally. Or even the, you know, chatgpt just unlocked agents, and I was running an agent yesterday and it took 13 minutes and I was like, are you kidding me? This is what I'm paying for, 13 minutes.

Billy Howell (41:38)

Well, I was Going to say that on the brain thing. I saw a good tweet today that was like, why isn't there a chatgpt for my life where I can just be like, what does my neighbor do for work again? Yeah, stuff like that. I'm kind of working on like a solution for someone that pulls in from their Google Calendar and their email. When's the last time I was at an event or I had a meeting with them? How many times do I email them this month? And it gives them like a weighted score on like this person's really hot or this person's colder. I think that is. It's not a way to download your brain per se, but I think that's a really useful use case. Just knowledge base of your friends and your family or.

Nick Sharma (42:19)

Yeah, yeah, I agree. I was even. I was thinking last week I was abroad and I met so many cool people. You know, anybody from like a security person at a venue to a bartender to somebody who's also vacationing. And, you know, I probably collected like 30, 40 Instagrams. But the problem is like, I don't remember where I met them or in what context or, you know, I'm sure I took a selfie with half of them to remember, but those were not attached to their Instagram or their whatsapps or and whatnot. And yeah, so many use cases like that that I think are just going to be instantly solved.

Billy Howell (42:55)

I mean, same thing. I always forget to do the selfie thing. It's so smart. But I was digging for this guy's number that I wanted to follow up with. I was looking on like LinkedIn and stuff to find him. I had his number in my phone. He called me like the next week and I was like, it's just a first name and last name. It wasn't connected to your business or anything. So some sort of AI. Yeah, personal assistant, like that would be great.

Nick Sharma (43:20)

It would be crazy. I remember back in the day there were so many of these AI calendar scheduling assistants that were basically like if then scripts. But I can't imagine like what that next generation is going to be with the ability to now plug all these different models in.

Billy Howell (43:43)

The main thing I think is for stuff like this, it needs to be in the primitive apps that you use, like Google Calendar, iMessage, Telegram, whatever. Anytime you've got to download a separate app or go open a separate tab. It's just making it kind of more of a pain. It needs to work with the primitives of your os, like your contacts thing. So, yeah, Come on, Apple, open all that up more.

Nick Sharma (44:11)

I know, it's really like Apple is really a gatekeeper of that. I mean, even like I use iMessage as a, as a, as like a business app constantly. Like I need iMessage Pro, but that's never going to come with Apple.

Billy Howell (44:27)

Yeah. Yeah, that's a good point.

Nick Sharma (44:30)

Yeah. Okay, Billy, first of all, thank you for coming on and just filling my brain with excitement about AI. I feel like now I want to run through a wall and build some apps.

Billy Howell (44:41)

Yeah.

Nick Sharma (44:43)

But where can people, people want to hit you up if they want to hire you to build an app. If they want to jump on a call like Troy did and just consult with you for an hour about what they can do, how do they find you and how do they get in touch with you?

Billy Howell (44:57)

Yeah. Stupid Simple Apps is my agency. So if you Google it. Stupid hyphen. It's got hyphens in there. Stupid simple apps.com youm could fill out a form for us to build you an app on Twitter. I'm BillyJhowell and I've got a link in there to like accountly if you want to do like a one on one strategy call. But yeah, go, go watch my YouTube channel too. It's the same app. I've got kind of my strategy for building and selling your first apps in there. It's really approachable and you can do it. Like I promise just people don't follow through. Right. So like you have to be the one that does it. But there's a huge. We didn't even talk about like upwork, but there's just like people sitting there ready to pay you money to build custom software. And I just think that's so crazy and exciting.

Nick Sharma (45:43)

Totally. Yeah. I will say your content online is insanely tactical and it's very much like somebody can look at it on the left screen and they can execute on the right screen. So I highly advise that you guys check it out and if you have any questions, the call you book with Billy is going to be the highest ROI call of your life. So highly recommend doing that too.

Billy Howell (46:04)

Thanks. Thanks. Yeah, everyone super happy from it and I just want to help people execute on this stuff and make a plan to go build and sell apps because I promise you can do it. I'm not that smart and I figured it out. You just have to execute on it and practice. I mean that's the, that's the crux of where we live with how like, you know, bountiful the Internet and software is now is you can build anything. You got to just have someone tell you, hey, dumb, dumb, build this and then build this. Right? It's not going to be a hit right away, but you're going to learn from this and then you'll get towards whichever one makes you money, right?

Nick Sharma (46:40)

Totally. And the seventh, the seventh thing they build is going to be amazing.

Billy Howell (46:44)

Yeah. On the seventh day.

Nick Sharma (46:46)

Yeah, Amazing.

Billy Howell (46:47)

Cool.

Nick Sharma (46:47)

Well, Billy, thank you so much for jumping on and I'm sure we're going to have you back soon.

Billy Howell (46:52)

Awesome, man. Good to talk to you, Nick.

Nick Sharma (46:54)

Thanks for listening. We'll be back next time to cut through the noise on CPG retail and e commerce. If you enjoyed this episode, why not share it with a friend? And be sure to subscribe wherever you listen so you don't miss the next one. Sam.