WEBVTT 00:00:00.000 --> 00:00:15.200 Alright. So you've probably seen these videos. Like, there's so many videos out there right now telling you that you can build Excel sheets with Quad. And look. Yes. This is actually super cool. I'm not going to sit there and pretend that it's not. But here's what nobody is telling you. That is already about to become completely obsolete 00:00:15.505 --> 00:00:33.880 because you can actually take it a step further, like way further. So instead of building a spreadsheet, you can actually build an AI artifact, like a mini web app, something that is way more interactive, more visual, more sellable than any Google Sheet you've ever seen. So we're talking about easy to visualize dashboards like app like behavior, 00:00:34.040 --> 00:00:47.345 the kind of tool that looks like a developer built it except you built it in under an hour with no code. And, specifically, a mini web app can actually include button, filters, forms, charts, and data visualization, 00:00:47.345 --> 00:00:48.945 simulation and calculators, 00:00:49.105 --> 00:00:53.345 guided workflows where the user knows exactly what to do next, 00:00:53.665 --> 00:00:55.345 and app like behavior 00:00:55.345 --> 00:00:57.025 with a real dashboard. 00:00:57.105 --> 00:01:01.670 So instead of dropping someone into a grid with rows and columns, 00:01:01.990 --> 00:01:04.070 you're actually designing an experience, 00:01:04.150 --> 00:01:13.670 and that's the difference. Because let's face it, Google Sheet and Excel are super intimidating for most people. You cannot tell me with a straight face that you actually enjoy opening spreadsheets. 00:01:14.125 --> 00:01:25.725 Like nobody does because it feels like homework. It almost feels like you're filling out a tax form, and most of us would rather avoid it. But a clean interactive web app that does the exact same thing 00:01:26.045 --> 00:01:40.310 and is easier to use, something that shows your data right away instead of having you having to dig for it, that people will pay a pretty penny for that. So here's what I did. I took a boring Google Sheet, the kind that looks super intimidating, 00:01:40.310 --> 00:01:52.415 something that's just like rows and columns doing basic math, and I actually turned it into a fully functional mini web app that I can actually sell from anywhere between $17 to $47. 00:01:52.495 --> 00:02:37.440 So no code needed, no developer, and no technical background required. And listen. The whole thing took me less than an hour using Clog and another byte coding tool that is completely underrated and that most people completely overlook. So if you've been sitting on a spreadsheet, a checklist, a tracker, or literally any kind of Excel sheet that you build to solve a real problem in your own business or maybe your boss's business, this video is going to completely change how you think about what you can actually sell. Because here's the truth. You're sitting on a gold mine right now, and you might not even realize it. So real quick, if you're new here, I'm Luna, and I've helped thousands of people build their first sellable digital product. I've been featured on Times Square's billboard for it, and I'm obsessed with finding opportunities before they even go mainstream. 00:02:37.520 --> 00:02:46.855 And right now, many web apps converted from spreadsheets. This is one of the most underrated opportunities in the digital product space. So let's get into it. So here's the thing about spreadsheets. 00:02:46.935 --> 00:02:47.975 They sell, 00:02:48.135 --> 00:03:01.630 and here's the data to back this up. So if you use a spike tool like Profitree, which actually scrapes Etsy for real sales data, you will see that spreadsheets are pulling in 6 figures in average. So you have budget trackers, meal planners, 00:03:01.630 --> 00:03:06.030 content calendars, cleaning schedules. So, yes, 6 figures from spreadsheets. 00:03:06.030 --> 00:03:13.645 So spreadsheets are high in demand because think about it. When somebody builds a spreadsheet, whether it's a budget tracker, a content calendar, 00:03:13.725 --> 00:03:25.580 a symptom log, a meal prep calculator, a habit tracker, they're solving a real problem that they or somebody else actually has. There's already logic built in, and there's already a workflow, 00:03:25.660 --> 00:03:30.060 and there's already a user who needs this. The problem is is that a spreadsheet, 00:03:30.060 --> 00:03:31.660 well, it feels like homework. 00:03:31.740 --> 00:03:40.235 Like, nobody wakes up on a Monday morning and thinks, oh, wait. I can't wait to open my Google Sheet. Like, nobody. And if you tell me with a straight face that you love Excel, 00:03:40.475 --> 00:03:51.210 uh, we can't be friends. But a clean interactive web app that does the exact same thing that visualizes your data faster, that has buttons and filters and a nice dashboard, 00:03:51.210 --> 00:03:56.490 people will pay premium for that. Because you're not selling information anymore. You're selling a transformation. 00:03:56.730 --> 00:03:57.930 You're selling speed. 00:03:58.170 --> 00:03:59.690 You're selling the results 00:03:59.930 --> 00:04:22.000 without the friction. And, also, let's face it. The problem as well now is that every spreadsheet under the sun has already been created. So if you try to sell a generic budget tracker on Etsy in 2026 or any other platform, you're gonna be competing with hundreds of other sellers who are selling the exact same thing for a dollar or even $2. 00:04:22.080 --> 00:04:29.600 So the race to the bottom is real. So what do you do? You do what almost nobody else is doing. You take that same concept, 00:04:29.680 --> 00:04:30.960 the same proven demand, 00:04:31.405 --> 00:04:38.605 and you turn it into a mini web app, something that's interactive, something that is branded, something that is sellable, and completely unsaturated. 00:04:38.605 --> 00:04:39.645 And with AI, 00:04:39.965 --> 00:04:59.580 the gap between I have a spreadsheet and I have a live sellable product is now just forty five minutes. So let me show you exactly how. My recommendation is that you use two tools for this, and I do this. Like, I use Claude and Lovable. Claude is the brain, and Lovable is the builder. Now a lot of you know that I love Claude. I talk about it consistently, 00:04:59.580 --> 00:05:26.080 but I wanna be really honest with you here because this matters. So if you jump straight into Cloud Code to build your app, your one hour project can easily turn into a two day headache, especially once you start adding things like a login system, a database, user accounts, the list goes on. Right? Cloud Code racks up also tokens really fast, and it also gets messy. And if you're a beginner, debugging is not fun on Cloud Code. But Lovable, 00:05:26.240 --> 00:05:38.535 this is a tool that I feel not a lot of people are talking about in our space. It's completely underrated in my opinion. So here's what Lovable does that changes everything. When you build in Lovable, it handles authentication, 00:05:38.535 --> 00:05:41.415 database, and your deployment automatically. 00:05:41.415 --> 00:06:08.835 So this is just a byproduct of just building the thing. And when your app is done, you can simply deploy it live, and it's gonna publish it to a real URL and a real login. Like, there's no extra step needed. So no need to upload files to the server. No need to figure out hosting. It's just done. So the workflow that I recommend that you use as a beginner is first you use Clot Chat, not Clot Code. And what you're gonna do is you're gonna use Clot Chat to think through what you're building. 00:06:09.315 --> 00:06:15.300 And then what I like to do is I use Lovable to actually build it. This way, what I'm doing is I'm using Cloud's intelligence 00:06:15.300 --> 00:06:16.340 to plan 00:06:16.500 --> 00:06:20.180 the app that I'm gonna build without burning through all my tokens. 00:06:20.340 --> 00:06:23.620 Because if I were to do the brainstorming on Cloud Code, 00:06:23.780 --> 00:06:44.790 then I would burn out all my tokens without even having started. Listen. Just to show you, I actually build the exact same tool both ways, and I want you to see the difference. So notice how the lovable version is just cleaner. The user experience is better. It feels more polished straight out of the box, and that actually matters when you're trying to sell something for $47. 00:06:44.870 --> 00:06:48.470 So Claude does the thinking for you and Lovable builds. 00:06:48.630 --> 00:06:58.415 That's a system that is beginner friendly. Now I'm not saying that you can't use Claude code. Absolutely. But this is just way easier, especially if you're a beginner. The first instinct 00:06:58.575 --> 00:07:13.120 is to open Cloud and type something like build me a health tracker app. And then they're confused when what comes back is either completely generic or totally unusable. So here's why that happens. When your prompt has no context, 00:07:13.200 --> 00:07:15.040 Cloud has to guess everything. 00:07:15.200 --> 00:07:19.600 So it has to guess what the app actually does, who is it for, 00:07:19.920 --> 00:07:33.945 what does the user experience is step by step, what gets stored, what gets calculated, what's the output. So Cloud has to fill in all those blanks on its own, and its guesses are not your business. So instead, 00:07:34.105 --> 00:07:42.250 here's a prompt that I like to use, and this one changed everything for me. So first, what I do is that I upload a spreadsheet 00:07:42.410 --> 00:07:47.450 that is similar to what I wanna sell, and I upload it directly into Clotshot, 00:07:47.450 --> 00:07:51.315 and then I write. I want to convert this uploaded spreadsheet 00:07:51.315 --> 00:07:55.955 into a simple mini web app. Your job is to analyze a spreadsheet 00:07:55.955 --> 00:08:02.035 as a product system, not just data. Review what the file does, how the data is connected, 00:08:02.195 --> 00:08:12.160 what the outcome is for the user, and translate it into a simplified mini app idea. Give me a complete product brief. So that one prompt 00:08:12.240 --> 00:08:14.400 by itself gives you everything. 00:08:14.480 --> 00:08:52.085 It comes back with what the app should do, what the user journey looks like, what the MVP needs to include, and what you can leave out for now. So think of it as like having a product manager inside your computer, one who actually goes through the spreadsheet. And here's why this step matters so much before you even open Lovable, because ideas are cheap, and clarity is what sells. And listen. I've watched people spend three hours on Lovable building something, and then they realize halfway that they don't even know what the main outcome of the app is supposed to be, and then they have to tear it down and start over. But when you do this product brief step first, 00:08:52.565 --> 00:09:00.245 you walk into the build knowing exactly what you're creating. You have a clear output. You know what the user is going to do, 00:09:00.645 --> 00:09:01.525 what they get, 00:09:01.925 --> 00:09:07.980 and why they would pay for it. And that is the difference between a product that sells and a product that just exists. 00:09:08.060 --> 00:09:20.845 Now here's a step that most tutorials completely skip, and it's the one that's gonna save you the most time. So once I have the product brief, I don't immediately jump into Lovable. I do one more thing. I ask Claude, 00:09:21.085 --> 00:09:57.245 what decisions do I need to make before any code gets written? And then it's gonna come back for me with a list of questions. Things like, can user edit their data after they submit it? Is this a single user app or a shared one? Does the app need to save data between session? What does the dashboard actually need to show? Does the user need to export anything? When I did this for this project, Claude gave me eight questions. So I answered all eight in about ninety seconds. So ninety seconds, that's it. But those ninety seconds locked in every decision that would have caused me to rebuild sections later. 00:09:57.750 --> 00:10:00.070 So every time an app breaks 00:10:00.150 --> 00:10:05.750 and someone says, like, I don't know why it's doing this, it's always because they made an assumption 00:10:05.910 --> 00:10:10.790 instead of making a decision. So they skipped the step. So good architecture 00:10:10.790 --> 00:10:16.795 is actually chosen before you actually start building. You don't try to figure it out while you're debugging, 00:10:17.035 --> 00:10:23.435 trying to wonder why the data isn't saving. Okay. So now we're inside Lovable, and this is where the magic happens. 00:10:23.675 --> 00:10:31.880 But, actually, I wanna show you how I actually do this because it's different from what most people do. So most people open Lovable, 00:10:32.040 --> 00:10:39.240 and they're gonna try to describe the entire app in one giant prompt. Everything at once. The login, the dashboard, the form, the calculation, 00:10:39.725 --> 00:11:02.110 the mobile layout, the color scheme, all in one go. And listen. The output is gonna look okay until a real user actually touches it and things start to break, especially when you have a very long prompt. So things might not connect the way you expect. Like, the logic might feel off. So here's what I like to do instead. I like to build in layers. So prompt number one is gonna be the foundation, 00:11:02.350 --> 00:11:11.595 the database, the login, the app shelf, nothing else. Right? I'm not building features yet. I'm building the skeleton, the bones. Then prompt two is gonna be the onboarding. 00:11:11.675 --> 00:11:12.875 How does a user 00:11:13.195 --> 00:11:20.850 get set up? Right? What do they need to tell the app before they can start using it? Prompt number three is gonna be the core features. In this case, 00:11:21.090 --> 00:11:23.490 so it could be the daily tracking form. 00:11:23.650 --> 00:11:27.170 So this is the thing the users actually comes back to do every day, 00:11:27.570 --> 00:11:37.215 and this is the heart of the app. Then we have prompt number four, which is a dashboard. This is where users see their data summarized, the charts, the progress, the indicators, 00:11:37.375 --> 00:11:38.975 the key numbers at glance. 00:11:39.135 --> 00:11:49.890 And then we have prompt number five, which is the report generator slash the exporting feature. So can the user get their data out? Would it be a PDF, a CSV file, 00:11:49.970 --> 00:11:56.210 a summary, like something that they can take and use? And then prompt number six is settings, account preferences, 00:11:56.770 --> 00:11:57.250 profile, 00:11:57.725 --> 00:12:02.365 or any customization option. And then prompt number seven is the final polish. 00:12:02.525 --> 00:12:04.925 Right? The loading states, error messages, 00:12:05.085 --> 00:12:13.430 mobile fixes, like the tiny things that make it feel finished versus dysfunctional. So why does this matter? Because when you build in layers, 00:12:13.510 --> 00:12:17.990 each step has a solid foundation underneath it. And if something breaks, 00:12:18.230 --> 00:13:05.355 you know exactly which layer broke. You don't have to dig through a thousand lines of AI generated code trying to figure out what went wrong or trying to go back and trying to, like, revive code it. Right? You simply go back to the layer or the prompt that broke, and then you fix that layer. And then the total time across all these seven prompts, depending on how complex they are, it's gonna take anywhere between half an hour to forty five minutes. And when it's done, all you have to do is, like, click around, debug it, and just deploy it. So you're gonna get a real URL, a real database, real login, ready to share, ready to sell. So after I build, I always run one complete user journey from start to finish before I show it to anyone. So I recommend that you sign up as a new user, you go through the onboarding, 00:13:05.515 --> 00:13:07.675 you use the core feature, you check the dashboard, 00:13:08.140 --> 00:13:29.555 you open it on mobile, and you can test mobile as well. This is where you can find bugs. In my case, I found three bugs on this build. So a calculation showing the wrong value in one spot, I had a display issue on mobile where the button was overlapping text, and then I also had the report was pulling in the wrong date range. So it was nothing catastrophic, 00:13:29.795 --> 00:13:55.755 but things that a real user would actually notice. So here's what I didn't do. I didn't ask it to fix one thing separately. Separately. Like, I knew exactly where the error were based on how I prompted it, but what I did is that I told this specifically, okay. So this section needs to be fixed. Right? And I explained exactly what the fixes needed to be. Because with AI, you can easily fix something, and then it's gonna accidentally 00:13:55.835 --> 00:14:01.195 remove something else and break something else. Right? And it happens a lot. You fix a button, 00:14:01.595 --> 00:14:14.110 and then suddenly the dashboard stops loading, and it's not working. Right? So that's not ideal. Instead, what I recommend you do is that you batch all these bugs into one single prompt. You describe each issues clearly. 00:14:14.190 --> 00:14:26.505 You told it exactly what the expected behavior is, and then you add one critical line at the end. Fix only what I listed. Do not modify anything else. So that prompting itself 00:14:26.905 --> 00:14:45.670 is gonna help you fix the three bugs in about two minute. And then, essentially, what I recommend you do is that you batch your fixes. And trust me, this is gonna make all the difference. Alright. So here's what I want you to actually take away from this. You probably already have the raw material for a mini web app sitting somewhere in your Google Drive, and you just have no idea. 00:14:45.990 --> 00:15:08.200 It could be a tracker that you built for yourself. It could be a checklist that you sent to clients. It could be an Excel sheet formula that you put together to solve a problem in your own business or your own life. It could be something that you built for free for yourself and that you never thought could become a product. So that thing right there with the right prompt and the right order can become an AI artifact. 00:15:08.200 --> 00:15:10.600 Something that can become a $27 00:15:10.600 --> 00:15:13.800 product, a $47 product, even a $97 00:15:13.800 --> 00:15:32.860 product. And you can do that by tomorrow because the tools are here. The technology is getting better and better every single day. The market is still completely wide open, but most people haven't caught on to this yet. And the only thing standing between you and a sellable product is knowing what to prompt and in what order. Now if you want to go deeper on this, 00:15:33.180 --> 00:15:58.504 on how to find the right niche, how to price your app, how to actually sell it without a big audience, I put together a free course right here on YouTube that actually walks you through the entire system from a to z. So comment the word free down below, and I'll send it directly to you. And listen, do me a favor right now. Open your Google Drive, look at what's already in there, because I promise you, you're closer than you think. Alright, guys. I'll see you in the next one. Bye.