Live Vibe Coding Session: How to Build Your Own Suite of CX Tools | Episode 105
The Digital CX Podcast: Driving digital customer success and outcomes in the age of A.I. · 2026-04-21 · 55 min
Substance score
27 / 100
Five dimensions, 20 points each
What our scoring noted
Our reviewer’s read on each dimension, with quotes from the episode.
Insight Density
A handful of genuinely actionable tips emerge—using a separate LLM to generate the initial vibe-coding prompt and the confidence-score clarifying-question technique—but these are buried under extended live-demo narration that requires video to follow, repeated housekeeping, and basic observations a CX operator with any AI exposure would already know.
do the initial prompt or produce the initial prompt outside of your vibe coding tool. So you're gonna use whatever you use on a regular basis or prefer ChatGPT, Gemini, or Claude to generate that initial vibe coding prompt for you
ask me clarifying questions one by one until you're 100% sure that you can deliver this request to a high degree of accuracy
Originality
The architect/construction-worker metaphor is widely recycled, the four-stage tool taxonomy is explicitly borrowed from another creator (Sabrina Romanoff), and the 80/20 AI-vs-human framing is a ubiquitous platitude. There is no contrarian argument or first-principles reasoning anywhere in the episode.
The point being that coders of tomorrow are not gonna be construction workers, they're gonna be the architects, right?
shout out to Sabrina Romanoff for the baseline of this
Guest Caliber
This is a solo-host episode with no guest; the host is a CX podcast operator who shares small personal anecdotes (building his own podcast post-production tool, a CSM who built a renewal calculator) but provides no evidence of practitioner scale, team size, revenue, or domain authority beyond running the podcast itself.
I did a live vibe coding session on stage where we built a customer value uh story generator
one of the first things that I vibe coded for myself was a tool to help me publish these episodes that you're listening to
Specificity & Evidence
The episode scores reasonably on naming specific tools (Lovable, Bolt.new, Replit, Cursor, Windsurf, Base44, Supabase, Claude Code) and walks through a real build step-by-step, but there are no user-scale metrics, cost figures, time savings data, or rigorous before/after comparisons—anecdotes stay small and personal.
Bolt.new and replit are among those in this category
it did have a quick issue, which it essentially fixed itself
Conversational Craft
This is a solo tutorial episode with no guest, so there is no interviewing craft, follow-up questioning, or productive disagreement to evaluate; the host does offer occasional candid self-critique mid-demo but that does not substitute for conversational rigor.
I don't know what I just did. I think I just got uh I don't know.
And it may fall completely on our faces or it may not.
Conversation analysis
Computed from the transcript - who did the talking, and the verbal tics along the way.
Filler words
Episode notes
Prompt Used for today's show: Link to the app we vibe coded: Ready to dive into the future of digital tool creation? This week, we're not just talking about vibe coding – we're doing it LIVE! Join me as we explore how this transformative approach is reshaping how we build tools, solve problems, and enhance both customer and employee experiences. I'll break down what vibe coding truly means, using practical metaphors and explaining why it's turning traditional coding on its head. We’ll discuss the exciting implications, from the rise of specialized micro-SaaS to teams solving their own unique challenges. Plus, I'll share my "biggest unlock" for successful vibe coding: how to craft the perfect initial prompt to get 80% of the way there, right from the start. We'll even demo building a live polling app, so you can see the process firsthand (you might want to check out the video version!). This episode is packed with insights and takes you step-by-step through my own process and recommended tools. Don't miss this deep dive into a skill that's quickly becoming essential for anyone in the digital space.
Full transcript
55 minTranscribed and scored by The B2B Podcast Index.
1 00:00:16,530 --> 00:00:18,690 SPEAKER_00: Today, we're going to get in vibe coding, and not 2 00:00:18,690 --> 00:00:20,769 only are we going to talk about it in theory and the 3 00:00:20,769 --> 00:00:23,250 implications of it, but we're actually going to do it live on 4 00:00:23,250 --> 00:00:23,890 the episode. 5 00:00:23,969 --> 00:00:26,450 So you might want to watch this one on YouTube. 6 00:00:26,929 --> 00:00:29,890 Once again, welcome to the Digital Customer Experience 7 00:00:29,890 --> 00:00:31,890 podcast with me, Alex Turkovich. 8 00:00:32,210 --> 00:00:35,009 So glad you could join us here today and every week as we 9 00:00:35,009 --> 00:00:38,369 explore how digital can help enhance the customer and 10 00:00:38,369 --> 00:00:39,570 employee experience. 11 00:00:39,810 --> 00:00:42,450 My goal is to share what my guests and I have learned over 12 00:00:42,450 --> 00:00:45,009 the years so that you can get the insights that you need to 13 00:00:45,009 --> 00:00:47,010 evolve your own digital programs. 14 00:00:47,250 --> 00:00:50,609 If you'd like more info, need to get in touch, or sign up for the 15 00:00:50,609 --> 00:00:53,650 weekly companion newsletter that has additional articles and 16 00:00:53,650 --> 00:00:56,929 resources in it, go to digitalcustomer success.com. 17 00:00:57,010 --> 00:00:58,770 For now, let's get started. 18 00:00:59,650 --> 00:01:02,690 Hello and welcome back to the Digital Customer Experience 19 00:01:02,690 --> 00:01:06,370 Podcast, the show where we talk about all things digital in CX. 20 00:01:06,450 --> 00:01:09,569 I'm Alex Turkovich and I'm so glad you're here with me this 21 00:01:09,569 --> 00:01:11,489 week as we're talking about vibe coding. 22 00:01:11,569 --> 00:01:16,370 Now, um, if you attended the Customer Success Uh Summit in 23 00:01:16,370 --> 00:01:21,090 Austin, you'll know that I did a live vibe coding session on 24 00:01:21,090 --> 00:01:26,049 stage where we built a customer value uh story generator. 25 00:01:26,290 --> 00:01:28,290 Super cool uh use case. 26 00:01:28,450 --> 00:01:32,530 Um, and so I wanted to actually bring some of that content into 27 00:01:32,530 --> 00:01:36,530 the podcast uh so that you can also partake if you weren't able 28 00:01:36,530 --> 00:01:37,490 to attend that event. 29 00:01:37,650 --> 00:01:43,170 So um before we actually do a live demo, and yes, you know, 30 00:01:43,250 --> 00:01:47,650 I'm gonna vibe code something on the podcast today so that you 31 00:01:47,650 --> 00:01:48,210 can watch it. 32 00:01:48,290 --> 00:01:52,930 Again, you may want to resume this episode um on YouTube 33 00:01:53,170 --> 00:01:55,969 going, you know, going forward from this point because I am 34 00:01:55,969 --> 00:01:58,210 gonna be sharing a bit of content, a couple slides that I 35 00:01:58,210 --> 00:02:00,930 shared as well, and then you know, again, you I'm gonna 36 00:02:00,930 --> 00:02:03,730 basically take you over my shoulder so that you can watch 37 00:02:03,730 --> 00:02:04,370 some of this stuff. 38 00:02:04,530 --> 00:02:07,250 I think there's some discrepancy out there or maybe some 39 00:02:07,250 --> 00:02:10,930 misunderstanding about what vibe coding really is all about. 40 00:02:11,169 --> 00:02:15,009 And one of the metaphors that I like to use is essentially a 41 00:02:15,009 --> 00:02:17,250 construction industry metaphor. 42 00:02:17,409 --> 00:02:20,289 The point being that coders of tomorrow are not gonna be 43 00:02:20,289 --> 00:02:23,569 construction workers, they're gonna be the architects, right? 44 00:02:23,729 --> 00:02:28,210 So when you think of traditional coding, um, you think of, you 45 00:02:28,210 --> 00:02:31,890 know, hands on keyboard, folks writing code line by line, and 46 00:02:31,890 --> 00:02:35,409 those kinds of things, that is essentially in construction akin 47 00:02:35,409 --> 00:02:38,689 to somebody hauling bricks or mixing mortar or doing those 48 00:02:38,689 --> 00:02:39,650 kinds of things. 49 00:02:39,890 --> 00:02:44,210 Whereas in vibe coding, you know, you're essentially 50 00:02:44,210 --> 00:02:45,729 becoming the architect. 51 00:02:45,810 --> 00:02:49,090 Um, and this is happening right now in software development, but 52 00:02:49,090 --> 00:02:52,289 it's also happening right now outside of software development. 53 00:02:52,449 --> 00:02:55,729 Uh so you're not necessarily hauling bricks around and 54 00:02:56,129 --> 00:02:57,890 actually doing the construction work. 55 00:02:57,969 --> 00:03:01,009 You're making the decisions about what you want the building 56 00:03:01,009 --> 00:03:03,409 to look like after it's done. 57 00:03:03,569 --> 00:03:06,050 And, you know, to some extent in the process and making 58 00:03:06,050 --> 00:03:07,729 adjustments and those kinds of things. 59 00:03:07,890 --> 00:03:11,170 So, you know, AI, the construction crew, so to speak, 60 00:03:11,409 --> 00:03:15,170 handles the construction and the implementation, and you handle 61 00:03:15,250 --> 00:03:18,770 essentially the vision and the vibe of what it is you want to 62 00:03:18,770 --> 00:03:19,090 build. 63 00:03:19,330 --> 00:03:21,170 Now, there are some implications here. 64 00:03:21,250 --> 00:03:25,409 I've consumed a lot of content about this in recent months, and 65 00:03:25,969 --> 00:03:29,490 the implications are essentially boiled down to three things. 66 00:03:29,650 --> 00:03:33,569 First off, we're going to start seeing a lot more niche uh 67 00:03:33,810 --> 00:03:36,449 micro-SaaS software out there. 68 00:03:36,610 --> 00:03:42,050 Things that are developed to do a very, very specific thing in a 69 00:03:42,050 --> 00:03:43,650 very, very specific way. 70 00:03:44,289 --> 00:03:49,009 Um, because you can now essentially code or you know 71 00:03:49,250 --> 00:03:53,009 create these kinds of um software applications, web 72 00:03:53,009 --> 00:03:55,969 pages, all those kinds of things that do a very specific thing. 73 00:03:56,129 --> 00:03:58,930 The second implication here is that teams are now gonna have 74 00:03:58,930 --> 00:04:03,569 the ability to essentially solve their own problems instead of 75 00:04:03,569 --> 00:04:07,729 immediately looking for a vendor, a software vendor doing 76 00:04:07,729 --> 00:04:09,650 an RFP to solve their problems. 77 00:04:09,810 --> 00:04:13,890 Um you're gonna have teams that develop tools and applications 78 00:04:13,890 --> 00:04:17,170 that help them with a business process and help them with a 79 00:04:17,170 --> 00:04:20,689 business process in the way that they want to operate that 80 00:04:20,689 --> 00:04:21,329 process. 81 00:04:21,889 --> 00:04:25,409 And that leads to the third implication that, you know, in 82 00:04:25,409 --> 00:04:29,009 the not too distant future, the days of bending your own 83 00:04:29,009 --> 00:04:34,290 processes to the way a specific software operates are somewhat 84 00:04:34,290 --> 00:04:35,410 limited, to be honest. 85 00:04:35,649 --> 00:04:41,329 Now, of course, we're not getting rid of Salesforce.com or 86 00:04:41,329 --> 00:04:46,449 HubSpot or Gainsight or Vitally or any of the CSPs or any of 87 00:04:46,449 --> 00:04:49,009 those big platforms anytime soon. 88 00:04:49,170 --> 00:04:52,610 There is a lot of inherent complexity and functionality and 89 00:04:52,610 --> 00:04:57,089 infrastructure built around these uh fundamental platforms 90 00:04:57,250 --> 00:04:59,410 that you're not just gonna go vibecode, right? 91 00:04:59,569 --> 00:05:02,850 Let's kind of shove that to the side. 92 00:05:03,889 --> 00:05:06,769 That's not to say in 10 years you won't be able to, or maybe 93 00:05:06,769 --> 00:05:07,569 less than that. 94 00:05:07,810 --> 00:05:11,170 What I'm talking about, though, are all of those other things 95 00:05:11,170 --> 00:05:17,410 where you are manually doing things in spreadsheets and you 96 00:05:17,410 --> 00:05:23,250 know, docs and other places that could be an application or an 97 00:05:23,250 --> 00:05:23,889 automation. 98 00:05:24,050 --> 00:05:28,530 It could be something that feeds data and information into one of 99 00:05:28,530 --> 00:05:31,810 those platforms like a Salesforce or a HubSpot or works 100 00:05:31,810 --> 00:05:37,089 collaboratively with them via the API or whatnot, right? 101 00:05:37,329 --> 00:05:44,610 So we're somewhat limited right now in terms of our imagination 102 00:05:44,610 --> 00:05:47,810 of what could be built with this kind of technology. 103 00:05:47,970 --> 00:05:51,410 And obviously, also there are some security implications here 104 00:05:51,649 --> 00:05:57,250 because you know with generic kind of vibe coding, you're just 105 00:05:57,250 --> 00:06:01,730 kind of putting stuff out there, not necessarily in a secure way, 106 00:06:01,810 --> 00:06:02,050 right? 107 00:06:02,209 --> 00:06:07,009 So what I'm not talking about right now is things that handle 108 00:06:07,009 --> 00:06:09,569 sensitive customer data, although you can definitely do 109 00:06:09,569 --> 00:06:09,730 that. 110 00:06:09,970 --> 00:06:13,649 And if you, you know, if you hire somebody to vibe code that 111 00:06:13,649 --> 00:06:16,530 does have some engineering background, at that point you 112 00:06:16,530 --> 00:06:19,089 can you can probably build something securely. 113 00:06:19,250 --> 00:06:22,930 But for your everyday, what what I'm here to really talk about is 114 00:06:22,930 --> 00:06:27,410 just everyday usage and potential implications for vibe 115 00:06:27,410 --> 00:06:29,889 coding in your day-to-day. 116 00:06:30,050 --> 00:06:33,490 When we talk about vibe coding, there's really a uh kind of an 117 00:06:33,490 --> 00:06:38,930 iterative loop process that we follow when we write something 118 00:06:39,009 --> 00:06:40,610 or when we vibe something. 119 00:06:40,769 --> 00:06:43,490 And this iterative loop essentially takes four steps. 120 00:06:43,649 --> 00:06:44,530 First is the prompt. 121 00:06:44,610 --> 00:06:46,050 You describe what it is you want. 122 00:06:46,129 --> 00:06:47,889 That's pretty self-explanatory. 123 00:06:48,129 --> 00:06:51,889 And of course, good prompting equals good results. 124 00:06:52,129 --> 00:06:56,850 Uh, the reveal, which means AI builds it somewhat instantly. 125 00:06:56,930 --> 00:07:00,050 It takes, can take seconds, can take minutes, depending on what 126 00:07:00,050 --> 00:07:00,850 you're building. 127 00:07:01,089 --> 00:07:02,530 Then comes the vibe check. 128 00:07:02,689 --> 00:07:07,089 You look at it and you say, okay, change the functionality 129 00:07:07,089 --> 00:07:11,009 of this button, or you know, this field doesn't look quite 130 00:07:11,009 --> 00:07:14,850 right, or you know, the the colors are a little bit off, or 131 00:07:14,850 --> 00:07:18,530 whatever the, you know, whatever your feedback might be, you work 132 00:07:18,530 --> 00:07:22,610 iteratively with your preferred vibe coding tool to make those 133 00:07:22,610 --> 00:07:26,050 changes, and it'll make those changes, which is essentially 134 00:07:26,050 --> 00:07:27,089 the refinement step. 135 00:07:27,170 --> 00:07:31,170 You're you're vibing back and forth with the AI so that it 136 00:07:31,170 --> 00:07:33,649 matches hopefully the picture in your head. 137 00:07:33,810 --> 00:07:38,769 And again, the better you are at prompting up front, um the 138 00:07:38,769 --> 00:07:39,490 easier it is. 139 00:07:39,569 --> 00:07:43,329 And and I've got a huge unlock for you here in a second that um 140 00:07:43,649 --> 00:07:48,530 that will make that first initial prompt pretty much like 141 00:07:48,610 --> 00:07:50,610 it'll get you 80% of the way there. 142 00:07:50,850 --> 00:07:54,850 Now, quick note if you're building something very complex, 143 00:07:55,009 --> 00:08:00,850 I'm talking about um building you know, a web app with 144 00:08:00,850 --> 00:08:05,569 multiple tabs and sections and databases and all that kind of 145 00:08:05,569 --> 00:08:05,970 stuff. 146 00:08:06,129 --> 00:08:09,250 Um, and by the way, you can vibe code spreadsheets as well. 147 00:08:09,410 --> 00:08:13,569 Claude is especially good at that, where you can build a very 148 00:08:13,569 --> 00:08:17,970 complex um spreadsheet or model, or you know, I've used it for a 149 00:08:17,970 --> 00:08:19,569 staffing model, for instance. 150 00:08:19,810 --> 00:08:23,730 Um the more complex it is, the more you're gonna want to take 151 00:08:23,730 --> 00:08:26,769 things in bite-sized chunks, just like a software developer 152 00:08:26,769 --> 00:08:27,250 does today. 153 00:08:27,410 --> 00:08:30,050 In other words, you're not gonna want to vibe code the entire 154 00:08:30,050 --> 00:08:31,730 thing all at once. 155 00:08:31,810 --> 00:08:35,649 Um, but you are, you know, it's good to get a general layout, 156 00:08:35,730 --> 00:08:39,490 but then you're gonna want to focus on quote unquote feature 157 00:08:39,490 --> 00:08:40,610 by feature. 158 00:08:40,769 --> 00:08:44,289 Uh, focus on building certain functionality out and then 159 00:08:44,289 --> 00:08:47,729 moving on to the next rather than just you know vibing on the 160 00:08:47,729 --> 00:08:49,009 entire thing itself. 161 00:08:49,250 --> 00:08:53,569 We'll jump into this here in a second, but one of the things 162 00:08:53,729 --> 00:08:58,689 that I wanted to give you some practical advice on and just 163 00:08:58,689 --> 00:09:03,489 kind of a lay of the land on is what vibe coding tools are out 164 00:09:03,489 --> 00:09:08,609 there and and and do so in order of sophistication, so to speak. 165 00:09:08,769 --> 00:09:11,729 Now, I can't take total credit for this, although I have 166 00:09:11,729 --> 00:09:15,649 amended it a little bit, but um, Sabrina Romanoff, if you don't 167 00:09:15,649 --> 00:09:19,649 follow her on socials, she's all over TikTok and Instagram and 168 00:09:19,649 --> 00:09:19,889 YouTube. 169 00:09:20,289 --> 00:09:26,689 Sabrina Sabrina Romanoff is a fantastic AI educator. 170 00:09:26,929 --> 00:09:30,129 I've spent a lot of time consuming her content. 171 00:09:30,289 --> 00:09:34,689 And so she has these four stages essentially of vibe coding 172 00:09:34,689 --> 00:09:35,250 tools. 173 00:09:35,489 --> 00:09:37,729 The first one being you're essentially you're a 174 00:09:37,729 --> 00:09:40,689 non-technical beginner, you're just getting in, you're kicking 175 00:09:40,689 --> 00:09:41,409 the tires. 176 00:09:41,569 --> 00:09:45,329 Maybe you want to build a simple landing page, a lead funnel, 177 00:09:45,649 --> 00:09:46,769 simple tools. 178 00:09:47,009 --> 00:09:51,649 You're gonna want to look for a tool like base 44, for instance, 179 00:09:51,889 --> 00:09:54,769 which is you know very, very simple, but also somewhat 180 00:09:54,769 --> 00:09:55,329 limited. 181 00:09:55,409 --> 00:09:58,929 Uh Google AI Studio as well, if you're in the Google Suite, 182 00:09:59,089 --> 00:10:02,369 check out Google AI Studio because it does it allow it does 183 00:10:02,369 --> 00:10:04,529 allow you to do some vibe coding, but it does a lot of 184 00:10:04,529 --> 00:10:06,049 automation type stuff too. 185 00:10:06,209 --> 00:10:11,489 Um, if you happen to be on a WordPress instance and you want 186 00:10:11,489 --> 00:10:15,889 some WordPress done, um those three tools kind of fall into 187 00:10:15,889 --> 00:10:17,329 this stage one category. 188 00:10:17,489 --> 00:10:20,049 So if you don't even know what vibe coding is and you want to 189 00:10:20,049 --> 00:10:23,809 just kind of figure it out and build some simple stuff, um, 190 00:10:24,129 --> 00:10:27,009 check out base 44, Google AI Studio, 10 Web. 191 00:10:27,169 --> 00:10:31,250 When we move to stage two, we add a little bit more complexity 192 00:10:31,250 --> 00:10:36,929 and a little bit more capability into the system where you know 193 00:10:37,169 --> 00:10:41,729 you can have most of these tools allow you to manage, you know, 194 00:10:41,889 --> 00:10:46,449 either your own database or use their native uh databases, for 195 00:10:46,449 --> 00:10:47,089 example. 196 00:10:47,329 --> 00:10:54,209 Um, these tools can be a little bit harder to fix bugs or make 197 00:10:54,209 --> 00:10:57,649 edits without just burning through credits. 198 00:10:57,809 --> 00:11:01,969 And so again, that points to what I alluded to earlier, where 199 00:11:01,969 --> 00:11:04,689 you're gonna want to spend a little bit more time up front 200 00:11:05,009 --> 00:11:09,089 making sure that you are prompting really well from the 201 00:11:09,089 --> 00:11:09,569 get-go. 202 00:11:10,209 --> 00:11:14,769 Um, but some of these tools are emergent, lovable is probably 203 00:11:14,769 --> 00:11:17,809 the biggest one out there that a lot of people know about. 204 00:11:18,129 --> 00:11:22,929 Bolt.new and replit are among those in this category. 205 00:11:23,089 --> 00:11:25,809 Not the only ones, but those are kind of like the front runners, 206 00:11:25,969 --> 00:11:26,689 so to speak. 207 00:11:26,849 --> 00:11:30,369 So that's kind of that stage two intermediate vibe coder. 208 00:11:31,089 --> 00:11:33,809 Stage three is where you're moving if you do have some 209 00:11:33,809 --> 00:11:37,009 technical background, but maybe you're not a software engineer, 210 00:11:37,089 --> 00:11:39,809 but you have some code level familiarity. 211 00:11:40,049 --> 00:11:44,289 These essentially AI-powered IDEs allow you to much more 212 00:11:44,289 --> 00:11:47,889 easily refine and debug and expand on code that was 213 00:11:47,889 --> 00:11:50,289 generated in earlier um stages. 214 00:11:50,609 --> 00:11:53,889 And you know, it's it's pretty common for you to maybe do a 215 00:11:53,889 --> 00:11:58,209 prototype in a stage two tool like Lovable, and then move over 216 00:11:58,209 --> 00:12:03,329 into, you know, let's say Cursor or Google's Antigravity to do 217 00:12:03,329 --> 00:12:08,689 some more enhanced uh coding and revisions with these kinds of 218 00:12:08,689 --> 00:12:08,849 tools. 219 00:12:08,929 --> 00:12:12,529 So again, cursor AI, Windsurf AI, and Google's Anti-Gravity, 220 00:12:12,609 --> 00:12:16,689 which is super cool, um are essentially in that stage three. 221 00:12:16,769 --> 00:12:20,289 Now, stage four is this is is going to be your your highest 222 00:12:20,289 --> 00:12:26,529 quality uh and and highest bang for your buck um output in terms 223 00:12:26,529 --> 00:12:30,449 of being able to build code in a truly kind of agentic way. 224 00:12:30,689 --> 00:12:34,769 Um and and you know, stage four is essentially what software 225 00:12:34,769 --> 00:12:37,969 engineers are using today to build like production level 226 00:12:38,049 --> 00:12:39,489 high-quality code. 227 00:12:39,649 --> 00:12:43,729 Uh, it does require some technical oversight and know-how 228 00:12:43,729 --> 00:12:47,409 to be able to manage and maintain the code as well as to 229 00:12:47,409 --> 00:12:48,849 implement security features. 230 00:12:48,929 --> 00:12:52,289 But this is, you know, this is the stage you move to when you 231 00:12:52,289 --> 00:12:56,449 have hundreds and thousands of users and uh, you know, a 232 00:12:56,689 --> 00:12:58,769 complex code base to maintain. 233 00:12:58,849 --> 00:13:01,409 Uh, you're gonna basically use cloud code for this. 234 00:13:01,569 --> 00:13:05,889 Now, there is a relatively newer intermediary here in the 235 00:13:05,889 --> 00:13:10,449 anthropic slash cloud claud ecosystem called um cloud 236 00:13:10,449 --> 00:13:16,609 co-work, which essentially what it does is it combines claud 237 00:13:16,849 --> 00:13:22,689 code with just claude chat um and is is uh acting as an 238 00:13:22,689 --> 00:13:26,769 interface, so to speak, between claud code and claude, so that 239 00:13:26,769 --> 00:13:32,209 you can get those kind of claud code outputs um using natural 240 00:13:32,209 --> 00:13:33,250 language, so to speak. 241 00:13:33,409 --> 00:13:36,609 But um again, if you're if you're really advanced or 242 00:13:36,609 --> 00:13:39,889 whatnot, a lot of folks are going to be using claud code um 243 00:13:40,129 --> 00:13:43,009 probably within something like Visual Studio. 244 00:13:43,250 --> 00:13:47,729 So those are the four stages of uh vibe coding tools. 245 00:13:47,889 --> 00:13:52,209 Again, shout out to Sabrina Romanoff for the baseline of 246 00:13:52,209 --> 00:13:52,369 this. 247 00:13:52,609 --> 00:13:56,049 What we will be doing here in a second is I'll break into a 248 00:13:56,049 --> 00:14:00,529 screen share and we can start vibe coding. 249 00:14:00,769 --> 00:14:03,489 The process that I like to follow, and this is probably the 250 00:14:03,489 --> 00:14:07,889 biggest unlock for getting the best results possible from your 251 00:14:07,889 --> 00:14:11,169 first iteration, is that, well, first off, you're gonna want to 252 00:14:11,169 --> 00:14:12,129 gather your context. 253 00:14:12,369 --> 00:14:16,689 So, you know, whatever tool you're building or spreadsheet 254 00:14:16,689 --> 00:14:21,729 you're building, or whatever it is you do, you want to gather as 255 00:14:21,729 --> 00:14:26,609 much context and details about what it is you want to build as 256 00:14:26,609 --> 00:14:27,169 possible. 257 00:14:27,329 --> 00:14:30,289 Because the clearer you are up front with it, the better your 258 00:14:30,289 --> 00:14:31,250 result is going to be. 259 00:14:31,409 --> 00:14:32,529 So, what are you gonna build? 260 00:14:32,609 --> 00:14:34,369 What's the problem you're trying to solve for? 261 00:14:34,449 --> 00:14:35,569 What do you want it to look like? 262 00:14:35,729 --> 00:14:37,729 What features do you want to incorporate? 263 00:14:37,889 --> 00:14:39,889 What aesthetic are you going for? 264 00:14:40,129 --> 00:14:43,329 What do you want it not to do specifically? 265 00:14:43,489 --> 00:14:46,529 Those are the kinds of things that you'll want to gather when 266 00:14:46,529 --> 00:14:47,329 you're doing this. 267 00:14:47,489 --> 00:14:53,329 Now, um, here's where my biggest recommendation comes in is do 268 00:14:53,329 --> 00:14:57,489 the initial prompt or produce the initial prompt outside of 269 00:14:57,489 --> 00:14:59,009 your vibe coding tool. 270 00:14:59,169 --> 00:15:02,529 So you're gonna use whatever you use on a regular basis or prefer 271 00:15:02,529 --> 00:15:07,649 ChatGPT, Gemini, or Claude to generate that initial vibe 272 00:15:07,649 --> 00:15:12,609 coding prompt for you that you're gonna then put into uh 273 00:15:12,609 --> 00:15:14,289 that vibe coding tool. 274 00:15:14,529 --> 00:15:17,729 Now I am gonna give you that that prompt that I'm gonna show 275 00:15:17,729 --> 00:15:22,449 you shortly so you can you know use it as a baseline foundation. 276 00:15:22,609 --> 00:15:26,289 Um but essentially what you're asking ChatGPT or Gemini or 277 00:15:26,289 --> 00:15:32,609 Claude for is you know, give me a ready-to-go prompt that is, 278 00:15:32,849 --> 00:15:35,729 you know, that I can plug into lovable. 279 00:15:35,809 --> 00:15:39,409 Let's say we're gonna use lovable today, um, so that I can 280 00:15:39,409 --> 00:15:40,689 get the best result possible. 281 00:15:40,849 --> 00:15:44,289 So what we're gonna actually do here shortly is we're going to 282 00:15:44,289 --> 00:15:47,009 go into one of these tools, we're gonna ask it to give us 283 00:15:47,009 --> 00:15:50,049 the vibe coding prompt, and then we're gonna go into the vibe 284 00:15:50,049 --> 00:15:55,489 coding tool, we're going to pop that in and get uh, you know, 285 00:15:55,649 --> 00:15:58,769 and and watch it essentially build something for us. 286 00:15:58,929 --> 00:16:04,849 Now, in terms of what you want to build, this is where the 287 00:16:05,489 --> 00:16:09,969 infinite possibilities essentially open up where you 288 00:16:10,289 --> 00:16:16,369 can and okay, I gotta be honest, it it took a pretty big mindset 289 00:16:16,369 --> 00:16:21,489 shift for me to start thinking about how I could incorporate 290 00:16:21,489 --> 00:16:23,250 this into my daily life. 291 00:16:23,489 --> 00:16:28,529 So, I mean, look, one of the first things that I vibe coded 292 00:16:28,529 --> 00:16:33,649 for myself was a tool to help me publish these episodes that 293 00:16:33,649 --> 00:16:34,929 you're listening to. 294 00:16:35,250 --> 00:16:39,809 Um, because what you don't see coming out of recording these 295 00:16:39,809 --> 00:16:42,769 episodes is all of the post-production work that goes 296 00:16:42,769 --> 00:16:43,329 into it. 297 00:16:43,489 --> 00:16:46,769 Um, yes, you gotta edit the show and do all that kind of stuff, 298 00:16:46,929 --> 00:16:50,369 but then you know, you've got to have your show notes ready for 299 00:16:50,369 --> 00:16:50,689 YouTube. 300 00:16:50,769 --> 00:16:54,929 You have to have your um, you know, chapter, chapters and 301 00:16:54,929 --> 00:16:57,809 timestamps ready, uh, as well as your description. 302 00:16:57,969 --> 00:17:01,250 You gotta have your show notes ready for you know the podcast 303 00:17:01,250 --> 00:17:05,009 platforms, uh, you got to have some LinkedIn posts ready to go, 304 00:17:05,089 --> 00:17:07,730 you gotta have some a newsletter companion ready to go. 305 00:17:07,890 --> 00:17:13,890 Like it's there's a bunch of outputs uh that we can generate 306 00:17:13,890 --> 00:17:19,889 pretty easily now uh with the input of let's say a transcript, 307 00:17:19,970 --> 00:17:20,289 for instance. 308 00:17:20,450 --> 00:17:24,450 So what typically what I'll do is I'll get this episode edited, 309 00:17:24,609 --> 00:17:28,929 I will export the transcript with timestamps, I'll plug into 310 00:17:29,009 --> 00:17:32,129 this tool that I vibe coded, and the tool in I don't know, 10 311 00:17:32,129 --> 00:17:36,609 seconds or so gives me all of those outputs so that I can then 312 00:17:36,609 --> 00:17:40,609 proofread them, make some edits, pop them into whatever tool, 313 00:17:40,849 --> 00:17:44,929 YouTube or um, you know, podcast platforms or whatever, so that I 314 00:17:44,929 --> 00:17:47,970 can, you know, really quickly get that content updated and I'm 315 00:17:47,970 --> 00:17:49,809 not spending a ton of time writing. 316 00:17:49,970 --> 00:17:53,569 Now I know there are some people out there that will be like, 317 00:17:53,730 --> 00:17:57,649 hey, he's just, you know, you're using AI-generated content. 318 00:17:57,889 --> 00:18:01,649 And um, yeah, I I take issue with that a little bit because 319 00:18:01,649 --> 00:18:03,169 the content is all mine. 320 00:18:03,409 --> 00:18:05,329 The transcript is not AI. 321 00:18:05,409 --> 00:18:08,769 This is me talking, this is me sharing ideas, this is me 322 00:18:08,769 --> 00:18:10,450 talking about these things specifically. 323 00:18:10,609 --> 00:18:14,450 I'm I am using artificial intelligence to, you know, 324 00:18:14,690 --> 00:18:19,329 create the outlines of things and to identify key moments um 325 00:18:19,649 --> 00:18:23,490 along a podcast's kind of episode and story arc, so to 326 00:18:23,490 --> 00:18:23,889 speak. 327 00:18:24,049 --> 00:18:31,409 Um, and you know, I'm I I am a big kind of advocate for having 328 00:18:31,409 --> 00:18:34,769 artificial intelligence do 80% of the work for you. 329 00:18:35,009 --> 00:18:38,849 I am not an advocate of just having AI do stuff for you and 330 00:18:38,849 --> 00:18:42,369 then you blindly posting stuff because I've seen that done and 331 00:18:42,369 --> 00:18:44,609 it does not look good, and you can tell. 332 00:18:44,849 --> 00:18:48,369 Um, so you know, whenever whenever you use artificial 333 00:18:48,369 --> 00:18:51,569 intelligence just in general to create content, you always gotta 334 00:18:51,569 --> 00:18:54,849 give it that human eye and you always gotta make sure that, you 335 00:18:54,849 --> 00:18:56,609 know, this is actually what you want to say. 336 00:18:56,690 --> 00:18:59,009 So I'll get off my soap soapbox around that. 337 00:18:59,169 --> 00:19:02,369 But point being, that was one of the first things that I vibe 338 00:19:02,369 --> 00:19:07,569 coded was a web app that helps me take a show from transcript 339 00:19:07,730 --> 00:19:11,409 to a bunch of different assets that I can then take, edit, and 340 00:19:11,409 --> 00:19:15,169 implement in a fraction of the time that it took me before 341 00:19:15,169 --> 00:19:16,210 artificial intelligence. 342 00:19:16,289 --> 00:19:18,529 When I first launched the show, I would spend a half day 343 00:19:18,609 --> 00:19:22,129 basically um, you know, pull listening to the episode, 344 00:19:22,289 --> 00:19:24,609 pulling out things that I wanted to make sure were in there and 345 00:19:24,609 --> 00:19:25,250 those kinds of things. 346 00:19:25,329 --> 00:19:28,210 So that's um that has been a huge lifesaver. 347 00:19:28,690 --> 00:19:35,089 Um you know, it when when we were uh debating on what to vibe 348 00:19:35,089 --> 00:19:38,609 code during the conference last week, there were a lot of ideas 349 00:19:38,609 --> 00:19:43,169 uh that were brought up in that in the process of doing so. 350 00:19:43,490 --> 00:19:48,529 And those ideas um were kind of all across the board. 351 00:19:48,609 --> 00:19:49,649 A lot of it was like personal. 352 00:19:50,129 --> 00:19:54,289 Somebody said, hey, let's vibe code like a kid's chore chart uh 353 00:19:54,289 --> 00:19:56,690 or a chore tracker or something like that. 354 00:19:56,849 --> 00:20:00,769 So you can, you know, you can identify those little moments 355 00:20:01,009 --> 00:20:05,169 within your daily life where you're like, hey, it would be 356 00:20:05,169 --> 00:20:09,250 cool to have kind of an app for that and to you know really 357 00:20:09,569 --> 00:20:13,649 figure out how you can, you know, build something to make 358 00:20:13,649 --> 00:20:17,730 those kinds of daily activities or weekly activities easier to 359 00:20:17,730 --> 00:20:17,970 do. 360 00:20:18,129 --> 00:20:21,009 So for the purposes of this demonstration, um, what I've 361 00:20:21,009 --> 00:20:23,649 chosen to do is something a little bit different. 362 00:20:23,730 --> 00:20:27,649 Um, it is essentially a live poll or vote app. 363 00:20:27,970 --> 00:20:33,089 So it allows you to essentially collect answers in real time 364 00:20:33,089 --> 00:20:37,169 that are displayed with you know things like animated charts or 365 00:20:37,169 --> 00:20:37,649 whatever. 366 00:20:37,889 --> 00:20:41,970 Um, uh the reason why I I thought about this is because, 367 00:20:42,049 --> 00:20:45,970 you know, we in the in the conference we did use a uh you 368 00:20:45,970 --> 00:20:49,569 know a polling app, ones that you see kind of integrated into 369 00:20:49,730 --> 00:20:51,250 uh PowerPoint, for instance. 370 00:20:51,409 --> 00:20:54,529 But I thought, hmm, we could probably vibe code something 371 00:20:54,529 --> 00:20:58,289 similar on our own and and see if that works. 372 00:20:58,369 --> 00:21:01,169 And so what we're gonna do live on the podcast is just you know 373 00:21:01,490 --> 00:21:04,369 see if we can live code something like this. 374 00:21:04,529 --> 00:21:08,929 And it may fall completely on our faces or it may not. 375 00:21:09,009 --> 00:21:10,529 And it may be a really cool thing. 376 00:21:10,690 --> 00:21:15,329 Either way, after this episode, I will give you access via the 377 00:21:15,329 --> 00:21:19,889 show notes to a link where you can view the app, but then you 378 00:21:19,889 --> 00:21:24,129 can also download the the prompting that I used to get to 379 00:21:24,129 --> 00:21:24,609 that app. 380 00:21:24,769 --> 00:21:28,049 So we're gonna switch over to screen share and uh we're gonna 381 00:21:28,049 --> 00:21:29,409 get to some vibe coding. 382 00:21:29,649 --> 00:21:33,889 Okay, so what you're seeing here is a Google Doc that I um came 383 00:21:33,889 --> 00:21:39,970 up with and already have a misspelling on, which um it 384 00:21:40,129 --> 00:21:41,169 gives us our first prompt. 385 00:21:41,250 --> 00:21:43,329 I went ahead and pre-wrote it because you don't want to watch 386 00:21:43,329 --> 00:21:45,649 me like write a prompt for this, right? 387 00:21:45,809 --> 00:21:48,609 But um, I'll walk you through some of the key points of the 388 00:21:48,609 --> 00:21:49,009 prompt. 389 00:21:49,169 --> 00:21:52,609 First off, um like any good prompt, you're gonna want to 390 00:21:52,609 --> 00:23:54,160 essentially give AI a role to play. 391 00:23:54,240 --> 00:23:58,640 In this case, I said act as an expert in live polling survey 392 00:23:58,640 --> 00:23:59,120 technology. 393 00:23:59,599 --> 00:24:01,279 Kind of broad, but okay, cool. 394 00:24:01,599 --> 00:24:07,039 Uh with a high proficiency in vibe coding with level, then I 395 00:24:07,039 --> 00:24:10,640 gave it uh basically some context and what I want to 396 00:24:10,640 --> 00:24:11,039 build. 397 00:24:11,360 --> 00:24:14,319 Um I Said what I want it to do. 398 00:24:14,400 --> 00:24:17,519 So I would like you to produce a detailed prompt that I can enter 399 00:24:17,519 --> 00:24:21,120 into Lovable to get the best result possible for the first 400 00:24:21,120 --> 00:24:22,000 iteration. 401 00:24:22,799 --> 00:24:26,079 I gave it a primary goal for the app, which is essentially to run 402 00:24:26,079 --> 00:24:31,680 live polls with web browsers, either with an audience or on 403 00:24:31,680 --> 00:24:33,599 live streams, for instance. 404 00:24:34,079 --> 00:24:38,000 I gave it some specifics on specific features, right? 405 00:24:38,079 --> 00:24:40,400 So I said, hey, let's do two views. 406 00:24:40,480 --> 00:24:43,360 So let's do a host view and an audience view. 407 00:24:43,680 --> 00:24:47,360 Gave it a few specifics there, but nothing too crazy. 408 00:24:47,839 --> 00:24:52,559 I said the host should have the ability to display a QR code to 409 00:24:52,559 --> 00:24:55,440 allow the audience to scan via mobile phone. 410 00:24:55,920 --> 00:24:59,360 The audience view should be responsive so that it can be 411 00:24:59,360 --> 00:25:01,039 displayed on a variety of devices. 412 00:25:01,200 --> 00:25:04,480 I said the dashboard and the audience view should update in 413 00:25:04,480 --> 00:25:07,120 real time based on votes being cast. 414 00:25:07,279 --> 00:25:11,519 I said use animated progress bars and vote count tickers. 415 00:25:11,759 --> 00:25:13,839 Then I said, hey, you know, features don't need to be 416 00:25:13,839 --> 00:25:16,559 limited to the above, but definitely contain the above. 417 00:25:16,720 --> 00:25:19,920 And I said, use your practical knowledge of other live polling 418 00:25:20,160 --> 00:25:23,599 apps, core features, to determine additional 419 00:25:23,599 --> 00:25:25,440 functionality that might be needed. 420 00:25:25,680 --> 00:25:27,440 I said, this is going to be interesting. 421 00:25:27,680 --> 00:25:31,360 I said, um, basically look at my website and copy some of the 422 00:25:31,360 --> 00:25:32,160 aesthetic there. 423 00:25:32,240 --> 00:25:37,120 So I'm having it, I'm having, in this case, Gemini go and crawl 424 00:25:37,120 --> 00:25:41,759 digitalcustomer success.com to try and pull out some um, you 425 00:25:41,759 --> 00:25:44,400 know, some some color language there, maybe. 426 00:25:44,559 --> 00:25:49,759 Um, now here is basically the thing that I include in most any 427 00:25:49,759 --> 00:25:50,799 prompt these days. 428 00:25:50,960 --> 00:25:53,440 I actually just you know copied and pasted it over. 429 00:25:53,519 --> 00:25:56,000 But I include this because it's a great method to get even more 430 00:25:56,000 --> 00:25:56,720 detail out. 431 00:25:56,960 --> 00:26:00,319 So I said, ask me clarifying questions one by one until 432 00:26:00,319 --> 00:26:03,440 you're 100% sure that you can deliver this request to a high 433 00:26:03,440 --> 00:26:04,880 degree of accuracy. 434 00:26:05,039 --> 00:26:09,360 Um, here's something I've been um adding here recently a lot, 435 00:26:09,519 --> 00:26:13,440 which is provide me with a confidence score with each 436 00:26:13,440 --> 00:26:14,720 question that you ask. 437 00:26:14,960 --> 00:26:18,400 Once your certainty score reaches 100%, produce the 438 00:26:18,400 --> 00:26:20,160 lovable prompt for me. 439 00:26:20,400 --> 00:26:24,400 Do not produce a new lovable prompt after each clarifying 440 00:26:24,400 --> 00:26:28,480 question, but wait to produce it once you have that complete 441 00:26:28,480 --> 00:26:29,360 certainty. 442 00:26:29,680 --> 00:26:33,759 That last bit is something I've been doing recently because a 443 00:26:33,759 --> 00:26:37,360 lot of times what it'll want to do is produce a whole new prompt 444 00:26:37,360 --> 00:26:40,000 with every question that you answer, and it just wastes a 445 00:26:40,000 --> 00:26:43,279 whole bunch of time and tokens, and it's just not useful. 446 00:26:43,519 --> 00:26:47,440 So um, yeah, but I always have it ask me clarifying questions. 447 00:26:47,519 --> 00:26:50,480 I like seeing the confidence score because it tells me 448 00:26:50,480 --> 00:26:54,240 roughly how far we are until 100% certainty. 449 00:26:54,559 --> 00:26:57,680 So that's basically the prompt that I'm gonna start with. 450 00:26:57,759 --> 00:27:00,799 And again, this is the prompt that I'm feeding either ChatGPT, 451 00:27:00,880 --> 00:27:05,680 Gemini, or Claude to get that initial lovable prompt. 452 00:27:05,920 --> 00:27:08,160 So I will copy and paste that. 453 00:27:08,480 --> 00:27:14,640 And for this example, we're gonna use Gemini for no real 454 00:27:15,279 --> 00:27:20,160 reason other than I had it pulled up, I guess. 455 00:27:20,240 --> 00:27:22,799 Um, you could totally use ChatGPT for this. 456 00:27:22,960 --> 00:27:26,319 I think you can totally use Claude for this as well. 457 00:27:26,480 --> 00:27:30,000 I think it just kind of depends on what you're most comfortable 458 00:27:30,000 --> 00:27:30,319 with. 459 00:27:30,480 --> 00:27:34,880 Um, you know, I am going to use Pro because why not? 460 00:27:35,039 --> 00:27:37,759 But whatever you have the most history in and whatever, you 461 00:27:37,759 --> 00:27:41,200 know, knows you knows the context of you most, uh, you can 462 00:27:41,200 --> 00:27:41,440 use. 463 00:27:41,599 --> 00:27:43,120 Claude is a whole different beast. 464 00:27:43,279 --> 00:27:47,200 And I might do a future episode on Claude Co-work because 465 00:27:47,200 --> 00:27:50,000 there's some cool kind of vibe coding kind of things that you 466 00:27:50,000 --> 00:27:52,319 can do in Claude Co-work and Claude Code as well. 467 00:27:52,400 --> 00:27:55,039 So that's kind of specifically why I didn't choose Claude for 468 00:27:55,039 --> 00:27:56,799 this particular exercise. 469 00:27:57,120 --> 00:28:01,039 Anyway, um, we fed it that prompt and we're gonna let it 470 00:28:01,039 --> 00:28:02,000 chug for a second. 471 00:28:02,160 --> 00:28:04,640 So I just clicked show thinking. 472 00:28:05,120 --> 00:28:07,440 Of course, it sounds like a fantastic project. 473 00:28:07,599 --> 00:28:09,519 Current confidence score is 70%. 474 00:28:10,160 --> 00:28:12,720 First clarifying question: how do you want to handle 475 00:28:12,720 --> 00:28:15,599 authentication and vote integrity? 476 00:28:15,759 --> 00:28:16,880 That's a cool question. 477 00:28:17,039 --> 00:28:17,360 Okay. 478 00:28:17,599 --> 00:28:21,360 Uh, should the host have a have a login system to have their 479 00:28:21,360 --> 00:28:23,680 polling sessions for future use? 480 00:28:24,240 --> 00:28:28,559 I think it would be cool to do a login, but for the for the sake 481 00:28:28,559 --> 00:28:32,240 of this demonstration, I think we'll just leave it open. 482 00:28:32,319 --> 00:28:37,519 And in fact, I'm gonna put it on the um I'll host it on my 483 00:28:37,519 --> 00:28:39,599 website so that y'all can go play with it. 484 00:28:39,680 --> 00:28:40,400 How about that? 485 00:28:40,559 --> 00:28:45,759 Um, so we're just going to uh for number one, oops, for number 486 00:28:45,759 --> 00:28:55,200 one, we're going to leave it open for anyone to access. 487 00:28:55,759 --> 00:29:00,160 Okay, number two is for the audience, should they remain 488 00:29:00,160 --> 00:29:06,880 completely anonymous using browser local storage cookies 489 00:29:07,120 --> 00:29:09,039 simply for the Vogue in twice? 490 00:29:09,360 --> 00:29:13,680 Or do you want them to input a name, nickname before voting? 491 00:29:14,640 --> 00:29:15,519 Let's do this. 492 00:29:15,680 --> 00:29:25,120 Uh let's say that name entry can be optional in the case that a 493 00:29:25,120 --> 00:29:27,920 name isn't entered. 494 00:29:32,720 --> 00:29:40,960 The audience member who voted will remain anonymous. 495 00:29:41,200 --> 00:29:44,079 And I see I misspelled member, but that's okay. 496 00:29:45,039 --> 00:29:46,559 Gemini's smart enough. 497 00:29:46,799 --> 00:29:48,400 Um let's see. 498 00:29:48,559 --> 00:29:49,920 Do we need to say anything else about that? 499 00:29:50,000 --> 00:29:50,480 I don't think so. 500 00:29:50,559 --> 00:29:51,839 So we're gonna submit that. 501 00:29:52,000 --> 00:29:55,200 We're gonna see what the confidence score is next. 502 00:29:56,400 --> 00:30:00,400 But you see how we kind of um get all of this out of the way 503 00:30:00,400 --> 00:30:02,559 before we go into the vibe coding tool. 504 00:30:02,640 --> 00:30:06,480 Um, because these are all things that I would need to A, first 505 00:30:06,640 --> 00:30:11,440 think about and ideate on, um, and then implement in later 506 00:30:11,440 --> 00:30:12,799 stages in the vibe coding tool. 507 00:30:12,880 --> 00:30:16,559 This way we're coming to the vibe coding tool with a very uh 508 00:30:16,640 --> 00:30:21,200 kind of well-thought out plan and a super detailed plan. 509 00:30:21,680 --> 00:30:24,960 Next clarifying question: what types of question polls should 510 00:30:24,960 --> 00:30:25,440 we support? 511 00:30:25,599 --> 00:30:26,559 I like it. 512 00:30:26,880 --> 00:30:31,599 Uh strictly multiple choice or single answer, multiple answer, 513 00:30:31,839 --> 00:30:36,319 word cloud free text rating slide scale. 514 00:30:36,720 --> 00:30:44,640 Um for this first iteration, why don't we just do for first 515 00:30:44,960 --> 00:30:45,839 iteration? 516 00:30:46,640 --> 00:30:54,960 Let's keep it to multiple or single. 517 00:30:58,160 --> 00:30:59,519 I can't type today. 518 00:30:59,680 --> 00:31:10,079 Multiple choice or single answer um questions where the host has 519 00:31:11,279 --> 00:31:19,759 the ability to select which type of question they want to ask. 520 00:31:22,079 --> 00:31:31,039 Use the check boxes for multiple choice and radial button or yeah 521 00:31:34,000 --> 00:31:36,559 for single select. 522 00:31:37,360 --> 00:31:38,000 Cool. 523 00:31:38,720 --> 00:31:40,480 Let's see where we end up next. 524 00:31:40,960 --> 00:31:44,319 Identifying color palette, current confidence score 92%. 525 00:31:44,720 --> 00:31:45,680 That's very specific. 526 00:31:45,839 --> 00:31:46,400 Perfect. 527 00:31:46,640 --> 00:31:49,360 Uh single answer radio buttons. 528 00:31:49,599 --> 00:31:51,039 Um, okay. 529 00:31:51,519 --> 00:31:54,079 There's one final set of clarifying questions to get me 530 00:31:54,079 --> 00:31:55,279 100% aesthetics. 531 00:31:55,360 --> 00:31:59,440 Do you have specific primary, secondary hex codes for the 532 00:31:59,440 --> 00:32:02,480 digital customer brand that you want me to include in the 533 00:32:02,480 --> 00:32:06,720 prompt, or should I instruct Lovable to use modern clean B2B 534 00:32:06,720 --> 00:32:08,240 SaaS aesthetic? 535 00:32:09,200 --> 00:32:09,680 Good place. 536 00:32:10,160 --> 00:32:14,480 So I did not necessarily pick up on the colors from the website. 537 00:32:14,559 --> 00:32:18,880 I didn't really think it would, but um poll lifecycle on the 538 00:32:18,880 --> 00:32:19,839 host dashboard. 539 00:32:20,000 --> 00:32:24,559 Do we need the ability to create a queue of multiple questions in 540 00:32:24,559 --> 00:32:27,680 advance so that you can toggle them live one by one? 541 00:32:28,079 --> 00:32:29,279 Okay, this is cool. 542 00:32:29,440 --> 00:32:32,720 So yeah, that second question with the poll lifecycle, 543 00:32:32,799 --> 00:32:35,519 obviously that introduces complexity, right? 544 00:32:35,839 --> 00:32:41,279 And so at this point, you may decide to reduce complexity and 545 00:32:41,279 --> 00:32:44,799 just do a single question at a time. 546 00:32:45,039 --> 00:32:49,200 Or in this case, we're just gonna throw caution to the wind 547 00:32:49,200 --> 00:32:54,240 and essentially have it build the ability to create multiple 548 00:32:54,240 --> 00:32:58,480 questions that it then uh allows the host to move through. 549 00:32:58,720 --> 00:33:03,279 Okay, so I have grabbed my colors, primary and secondary 550 00:33:03,360 --> 00:33:04,079 from the website. 551 00:33:04,160 --> 00:33:08,480 It's that annoying orange that you see everywhere, and uh that 552 00:33:08,640 --> 00:33:10,960 green secondary color that I use. 553 00:33:12,000 --> 00:33:17,279 And for the poll lifecycle, we're just going to say let's 554 00:33:17,599 --> 00:33:26,160 create a queue where the host can pre-define multiple 555 00:33:26,480 --> 00:33:34,160 questions that they can cycle through live during the event. 556 00:33:35,279 --> 00:33:39,039 Okay, this might get us to 100%. 557 00:33:39,519 --> 00:33:41,759 We shall see here shortly. 558 00:33:42,880 --> 00:33:45,200 Okay, current confidence score. 559 00:33:45,440 --> 00:33:46,000 100%. 560 00:33:46,480 --> 00:33:48,000 That is exactly what I needed. 561 00:33:48,160 --> 00:33:48,720 I know. 562 00:33:48,880 --> 00:33:50,000 Okay, cool. 563 00:33:50,240 --> 00:33:52,079 Uh since I have all the details. 564 00:33:52,240 --> 00:33:59,200 Okay, and so here what you'll see is a prompt that I can copy 565 00:33:59,200 --> 00:34:04,799 and paste into Lovable to start vibe coding this app. 566 00:34:05,360 --> 00:34:11,279 Um, now we're not gonna spend a ton of time on this for the sake 567 00:34:11,279 --> 00:34:12,400 of this demonstration. 568 00:34:12,559 --> 00:34:14,799 Okay, this is interesting down here, by the way. 569 00:34:14,960 --> 00:34:17,360 Um, it says Superbase setup. 570 00:34:17,440 --> 00:34:20,480 For those of you who may not be familiar with Superbase, it is 571 00:34:20,480 --> 00:34:26,159 essentially a um a database platform that Lovable partners 572 00:34:26,159 --> 00:34:26,319 with. 573 00:34:26,400 --> 00:34:28,239 And so they have a very tight integration. 574 00:34:28,400 --> 00:34:32,239 And for something like this, the app is going to want to create 575 00:34:32,239 --> 00:34:35,440 its own database so it can store the questions and the responses 576 00:34:35,440 --> 00:34:36,960 and all that kind of stuff, right? 577 00:34:37,119 --> 00:34:40,639 Um, and so a lot of times the reason why lovable is so 578 00:34:40,639 --> 00:34:43,199 approachable is because you don't have to create your own 579 00:34:43,199 --> 00:34:44,639 database and whatnot. 580 00:34:44,799 --> 00:34:48,960 It will essentially do it for you, uh, which is super cool. 581 00:34:49,199 --> 00:34:53,440 And then it is telling me that I can essentially iterate um with 582 00:34:53,440 --> 00:34:56,880 lovable from here on out, which is yeah, it's exactly what we're 583 00:34:56,880 --> 00:34:57,440 gonna be doing. 584 00:34:57,679 --> 00:35:00,159 But point is I'm gonna copy and paste this. 585 00:35:00,319 --> 00:35:04,960 Um, what I would normally do actually is put this into like a 586 00:35:04,960 --> 00:35:05,119 doc. 587 00:35:05,440 --> 00:35:06,639 In fact, I may do that. 588 00:35:06,799 --> 00:35:10,319 So this is the document that I will be sharing with you, or 589 00:35:10,319 --> 00:35:13,440 that is shared in the links down below in the show notes. 590 00:35:13,519 --> 00:35:14,480 So go grab it. 591 00:35:14,639 --> 00:35:17,519 I'm going to add another tab. 592 00:35:17,839 --> 00:35:24,079 And this is where I'm going to put in the initial, the uh say 593 00:35:24,400 --> 00:35:26,719 first lovable prompt. 594 00:35:27,279 --> 00:35:27,839 Cool. 595 00:35:28,079 --> 00:35:32,880 And so you see, it does put a very clear prompt before you. 596 00:35:33,039 --> 00:35:36,319 This is if we were to just go lovable and start prompting like 597 00:35:36,319 --> 00:35:41,199 we did in Gemini, uh, we would be further behind because this 598 00:35:41,199 --> 00:35:44,239 is what it's actually, it's actually starting to 599 00:35:44,799 --> 00:35:49,440 predetermine what some of the requirements are for the data 600 00:35:49,440 --> 00:35:51,360 table and the back end essentially. 601 00:35:51,519 --> 00:35:54,719 So it's saying that you know you're gonna need a uh a poll 602 00:35:54,719 --> 00:35:59,039 table and options and votes and whatnot. 603 00:35:59,199 --> 00:36:02,880 But for the most part, you can directly attribute a lot of this 604 00:36:02,880 --> 00:36:05,759 back to you know the prompting and the questions that we got. 605 00:36:05,920 --> 00:36:08,320 Um, so just quick scan. 606 00:36:09,760 --> 00:36:15,760 I don't see anything crazy that we need to change. 607 00:36:15,840 --> 00:36:18,880 What I would do normally is go through this with a fine-tooth 608 00:36:19,039 --> 00:36:23,440 comb and just kind of add remove things just based on you know 609 00:36:23,599 --> 00:36:26,159 what the image in my head is of this thing. 610 00:36:26,320 --> 00:36:28,880 I'm not seeing anything crazy that we need to omit. 611 00:36:28,960 --> 00:36:32,159 And there's even some interesting choices here. 612 00:36:32,320 --> 00:36:35,599 For instance, ensure real-time changes feel magical. 613 00:36:35,760 --> 00:36:36,880 That's kind of cool. 614 00:36:37,039 --> 00:36:41,199 We'll see what magical uh we'll see what lovable thinks magical 615 00:36:41,199 --> 00:36:41,519 is. 616 00:36:41,679 --> 00:36:44,240 Uh, but we're just gonna run with this, right? 617 00:36:44,400 --> 00:36:50,320 We're just going to take all of this and we're gonna go over to 618 00:36:50,320 --> 00:36:51,119 lovable. 619 00:36:51,440 --> 00:36:53,440 This is what lovable looks like. 620 00:36:53,679 --> 00:36:59,280 Um, and I'm gonna just paste that prompt in there while we're 621 00:36:59,280 --> 00:36:59,760 talking. 622 00:37:00,079 --> 00:37:04,800 One thing to note is with lovable, you know, much like a 623 00:37:05,039 --> 00:37:09,360 lot of other um, you know, tools, you can uh, you know, 624 00:37:09,679 --> 00:37:12,639 predetermine certain connectors you want to use. 625 00:37:12,880 --> 00:37:16,320 This is where I could, you know, tell it some of my design 626 00:37:16,320 --> 00:37:17,360 choices as well. 627 00:37:17,519 --> 00:37:21,199 You can attach files, spreadsheets, whatever it may 628 00:37:21,199 --> 00:37:21,360 be. 629 00:37:21,599 --> 00:37:23,519 In this case, we're not doing any of that. 630 00:37:23,679 --> 00:37:26,960 Um, there is another interesting feature that lovable does have, 631 00:37:27,039 --> 00:37:28,880 which is this plan mode. 632 00:37:29,119 --> 00:39:55,349 What's cool about that is you can essentially plan the app a 633 00:39:55,349 --> 00:40:00,230 little bit with lovable before you actually vibe code the app. 634 00:40:00,549 --> 00:40:03,349 Again, this is this would be another thing that I would 635 00:40:03,349 --> 00:40:06,710 actually recommend you do, where you're going into plan mode, 636 00:40:06,789 --> 00:40:10,549 you're iterating on the plan a little bit before it actually 637 00:40:10,549 --> 00:40:13,909 builds it for you, so that then you know you're not iterating 638 00:40:13,909 --> 00:40:15,029 after it's already built it. 639 00:40:15,190 --> 00:40:17,669 In other words, you're iterating on it so that you're not 640 00:40:17,669 --> 00:40:21,269 spending a bunch of tokens iterating in real time on an 641 00:40:21,269 --> 00:40:22,309 already built app. 642 00:40:22,469 --> 00:40:25,509 In this case, we're just going for broke here, right? 643 00:40:25,589 --> 00:40:29,509 So I'm gonna hit submit on that, and we're gonna see what it 644 00:40:29,509 --> 00:40:30,149 comes back with. 645 00:40:30,309 --> 00:40:34,230 Now, one of the first things it's probably gonna ask me here 646 00:40:34,230 --> 00:40:39,989 is for permission for it to build the back end, um, which 647 00:40:40,309 --> 00:40:45,429 should be popping up right here, but um, you will start to be 648 00:40:45,429 --> 00:40:49,750 able to, as it initializes, you'll be able to start getting 649 00:40:49,750 --> 00:40:51,989 more details on what it is actually doing. 650 00:40:52,149 --> 00:40:55,669 And so, yep, just like we thought, enable cloud. 651 00:40:55,750 --> 00:41:03,029 This is essentially us giving permission to enable SuboBase to 652 00:41:03,029 --> 00:41:05,589 be set up on our behalf in the background. 653 00:41:05,829 --> 00:41:10,309 I don't have it set to just always allow just because I like 654 00:41:10,309 --> 00:41:13,269 that kind of control, but I've just allowed it to. 655 00:41:13,429 --> 00:41:17,589 And so now what it is doing is it is establishing the database 656 00:41:17,669 --> 00:41:23,109 and it is going to start writing this app before our very eyes. 657 00:41:23,669 --> 00:41:26,789 And once it gets a little bit further along, we're actually 658 00:41:26,789 --> 00:41:32,949 going to be able to get some details in terms of what is 659 00:41:32,949 --> 00:41:34,869 actually happening live. 660 00:41:36,149 --> 00:41:39,349 And so, yeah, you start to see those kinds of things 661 00:41:39,349 --> 00:41:40,549 populating. 662 00:41:40,949 --> 00:41:44,069 And so, you know, if you like watching this kind of thing, you 663 00:41:44,069 --> 00:41:48,869 can definitely get the details, or you know, you can close the 664 00:41:48,869 --> 00:41:50,309 details if you want to. 665 00:41:50,469 --> 00:41:54,309 Uh, this is asking me for some changes it needs to make to the 666 00:41:54,309 --> 00:41:55,109 database. 667 00:41:55,509 --> 00:41:58,949 This might get annoying if it asks me to do that a lot. 668 00:42:01,750 --> 00:42:04,469 Alright, so we're starting to see a little bit more detail 669 00:42:04,469 --> 00:42:05,669 populate here. 670 00:42:07,029 --> 00:42:10,469 And it basically just told me you're creating a very unsecure 671 00:42:10,469 --> 00:42:12,069 app, which is kind of true. 672 00:42:12,389 --> 00:42:17,109 So, yeah, it's starting to essentially create the back end, 673 00:42:17,349 --> 00:42:21,269 and you can see what it is writing and editing in real 674 00:42:21,269 --> 00:42:21,589 time. 675 00:42:22,549 --> 00:42:24,789 Okay, so um a couple things. 676 00:42:25,029 --> 00:42:29,349 This is about five minutes or so that this has taken me, and um, 677 00:42:29,589 --> 00:42:32,710 you'll see we are now seeing a live preview. 678 00:42:32,869 --> 00:42:39,190 It has described essentially what it has built, and uh the 679 00:42:39,190 --> 00:42:40,629 colors are kind of cool. 680 00:42:40,789 --> 00:42:44,710 I kind of like how it flipped at the primary and the secondary. 681 00:42:44,949 --> 00:42:47,349 Well, the secondary, I guess, used for a background, right? 682 00:42:47,509 --> 00:42:48,469 So cool. 683 00:42:48,629 --> 00:42:50,710 Um built the back end. 684 00:42:50,789 --> 00:42:55,190 It did have a quick issue, which it essentially fixed itself. 685 00:42:55,509 --> 00:43:00,789 But now we have a live kind of view of the app that I mean, 686 00:43:01,029 --> 00:43:01,989 okay, cool. 687 00:43:02,149 --> 00:43:03,669 It's a landing page. 688 00:43:03,750 --> 00:43:07,509 You can go to the host dashboard or you can go to the audience 689 00:43:07,509 --> 00:43:12,309 vote, which the colors on this little bit suspect, so we're 690 00:43:12,309 --> 00:43:13,750 gonna need to address that. 691 00:43:13,909 --> 00:43:18,149 Um, but if we go to the host dashboard, it's super simple, 692 00:43:18,710 --> 00:43:19,589 which is cool. 693 00:43:19,750 --> 00:43:21,589 What is your favorite color? 694 00:43:21,909 --> 00:43:26,069 We are going to select a single answer option. 695 00:43:26,230 --> 00:43:30,069 We're going to say red, yellow. 696 00:43:30,789 --> 00:43:34,149 We're going to add an option of blue. 697 00:43:35,109 --> 00:43:38,069 So now we're basically what we're doing here is we're just 698 00:43:38,069 --> 00:43:39,109 testing this thing. 699 00:43:39,349 --> 00:43:42,389 Um, and it created a question. 700 00:43:42,789 --> 00:43:47,349 Uh, and it is in draft, which I don't really know what that 701 00:43:47,349 --> 00:43:51,829 means, but I'm assuming that I can either trash it or I can go 702 00:43:52,469 --> 00:43:54,389 live with this question. 703 00:43:55,109 --> 00:43:56,710 Okay, the question is live. 704 00:43:56,869 --> 00:44:04,230 There is a QR code, and there is a link to go to that question. 705 00:44:04,469 --> 00:44:09,109 I will copy that link and I will paste it in this second tab. 706 00:44:09,669 --> 00:44:11,669 Okay, so there's my name. 707 00:44:11,829 --> 00:44:14,149 Uh, here's red, yellow, blue. 708 00:44:14,230 --> 00:44:19,349 We're gonna submit the vote, and now we're waiting for the next 709 00:44:19,349 --> 00:44:19,989 question. 710 00:44:20,549 --> 00:44:24,309 And I would assume that somewhere over here. 711 00:44:25,909 --> 00:44:27,269 So this hasn't come back yet. 712 00:44:27,349 --> 00:44:36,230 So look, I mean for a first iteration, this isn't bad. 713 00:44:36,389 --> 00:44:38,149 I don't know what I just did. 714 00:44:38,629 --> 00:44:41,269 I think I just got uh I don't know. 715 00:44:41,669 --> 00:44:45,829 It's closed for a first iteration, this isn't bad. 716 00:44:46,069 --> 00:44:54,710 Now, what I would do next is you know, as I'm kind of testing 717 00:44:54,710 --> 00:44:58,469 this, what I would be doing is essentially jotting some things 718 00:44:58,469 --> 00:45:00,389 down that aren't quite right. 719 00:45:00,789 --> 00:45:06,230 So, you know, the button on the front where it said audience, I 720 00:45:06,230 --> 00:45:08,389 think it was answer questions, something like that. 721 00:45:08,629 --> 00:45:10,710 Uh the colors were all weird here. 722 00:45:10,869 --> 00:45:18,069 Now, here I don't see any kind of ability to see answers. 723 00:45:18,629 --> 00:45:21,829 And maybe this is because we haven't published it yet, but 724 00:45:21,909 --> 00:45:25,429 um, and we can maybe publish it and see if that works. 725 00:45:25,589 --> 00:45:29,109 Now, publishing here, you can provide your own URL and things 726 00:45:29,109 --> 00:45:33,429 like that for for for you know these kind of instances. 727 00:45:33,589 --> 00:45:38,469 You know, I'll just use lovable's URL and we're gonna 728 00:45:39,029 --> 00:45:41,269 publish this public and see. 729 00:45:41,989 --> 00:45:45,669 Okay, we're just gonna publish this bad boy. 730 00:45:46,309 --> 00:45:48,069 And then maybe it'll work, right? 731 00:45:48,230 --> 00:45:51,909 So, you know, you can essentially do some testing, and 732 00:45:51,909 --> 00:45:55,429 then if you want to iterate on it, um, you're just gonna ask 733 00:45:55,429 --> 00:45:56,069 lovable. 734 00:45:56,230 --> 00:46:00,549 So um, you know, I would probably start with that button 735 00:46:00,549 --> 00:46:05,669 on the front page and say, hey, need to change the um the colors 736 00:46:05,669 --> 00:46:06,149 of that. 737 00:46:06,309 --> 00:46:11,989 Um, and then two, I would also say, you know, I don't see 738 00:46:11,989 --> 00:46:17,589 necessarily where I can view the different questions and the 739 00:46:17,589 --> 00:46:19,509 answers coming in and those kinds of things. 740 00:46:19,589 --> 00:46:22,949 Now we we've just published it, so we might test it out live 741 00:46:22,949 --> 00:46:23,190 here. 742 00:46:23,349 --> 00:46:25,589 I'm gonna go back to the host dashboard. 743 00:46:25,829 --> 00:46:27,029 What's your favorite color? 744 00:46:27,190 --> 00:46:28,149 Is closed. 745 00:46:28,469 --> 00:46:30,230 See, and I can't go back and edit it. 746 00:46:30,309 --> 00:46:31,829 So that might be an iteration. 747 00:46:31,989 --> 00:46:36,549 We say, hey, if a poll is closed, I'd like to be able to 748 00:46:36,549 --> 00:46:38,069 reopen it, for instance. 749 00:46:38,309 --> 00:46:41,909 Okay, so and you'll also notice that because we didn't don't 750 00:46:41,909 --> 00:46:46,789 have the live preview and the sidebar here, that the app is 751 00:46:46,789 --> 00:46:50,149 responsive and so it is kind of you know moving things around. 752 00:46:50,389 --> 00:46:55,190 We're gonna do um, I don't know, have you ever gone fishing? 753 00:46:56,710 --> 00:47:03,190 Single select, we're gonna do yes, no, create poll. 754 00:47:04,389 --> 00:47:07,349 Let's maybe create two of them. 755 00:47:07,829 --> 00:47:10,949 And maybe let's do a multiple choice and see what that looks 756 00:47:10,949 --> 00:47:11,669 like as well. 757 00:47:11,989 --> 00:47:17,669 Which of these is your favorite number? 758 00:47:18,230 --> 00:47:20,069 Three or four. 759 00:47:21,429 --> 00:47:22,230 Create poll. 760 00:47:22,309 --> 00:47:24,789 Okay, so now we have a couple more. 761 00:47:24,869 --> 00:47:29,109 Um, looks like we are going to launch one of these, perhaps. 762 00:47:29,750 --> 00:47:36,069 Okay, so it did update this page, which is super cool. 763 00:47:37,190 --> 00:47:40,309 Uh I'm gonna say yes and submit my vote. 764 00:47:40,549 --> 00:47:42,469 And then maybe, oh yeah, okay. 765 00:47:42,549 --> 00:47:46,069 So now because we published the app, it is basically seeing 766 00:47:46,069 --> 00:47:48,149 what's happening on the back end, right? 767 00:47:48,389 --> 00:47:53,589 And then if I go and I launch maybe the second one, it'll 768 00:47:53,589 --> 00:47:55,509 automatically close that first one. 769 00:47:55,589 --> 00:47:59,589 So the point I'm getting at here is that for a V1, this is a 770 00:47:59,589 --> 00:48:00,629 really great result. 771 00:48:00,869 --> 00:48:06,469 And you know, this is a somewhat complex app, but the point is 772 00:48:06,549 --> 00:48:10,069 you can build these things, and it's relatively simple. 773 00:48:10,230 --> 00:48:14,789 Now, what I would be doing next is going through taking note of 774 00:48:14,869 --> 00:48:18,309 you know what it is I need to fix and essentially having a 775 00:48:18,309 --> 00:48:20,629 conversation with Lovable to fix certain things. 776 00:48:20,789 --> 00:48:24,069 I would iterate upon it and I would keep iterating upon it 777 00:48:24,309 --> 00:48:28,149 until I get to the point where it is what I want it to be. 778 00:48:28,469 --> 00:48:31,669 You update the published version and you're good to go. 779 00:48:31,829 --> 00:48:33,029 So I'm gonna get out of screen share. 780 00:48:33,509 --> 00:48:36,789 Real quick, and then we'll wrap this episode up. 781 00:48:37,029 --> 00:48:42,069 When I first did this with the audience at the CS Summit in 782 00:48:42,069 --> 00:48:45,589 Austin, uh one of the things I did was I polled the audience in 783 00:48:45,589 --> 00:48:48,789 terms of their familiarity with vibe coding. 784 00:48:49,109 --> 00:48:54,629 And I was surprised to see that more than I'd say more than half 785 00:48:54,629 --> 00:48:58,710 the room didn't really know about vibe code coding. 786 00:48:58,869 --> 00:49:02,069 And I, you know, I guess that makes sense. 787 00:49:02,149 --> 00:49:04,149 It's it's a relatively new thing, right? 788 00:49:04,389 --> 00:49:10,869 And um, it's not necessarily mainstream, but it is incredibly 789 00:49:10,869 --> 00:49:14,389 powerful and it is the way that software is going. 790 00:49:14,549 --> 00:49:17,909 Whether you're a developer or you're not a developer, it's a 791 00:49:17,909 --> 00:49:18,549 thing. 792 00:49:18,869 --> 00:49:20,710 And it's a powerful thing. 793 00:49:20,949 --> 00:49:25,909 And so my goal for today is for those of you who are vibe 794 00:49:25,909 --> 00:49:27,909 coding, kudos to you. 795 00:49:27,989 --> 00:49:28,710 That's awesome. 796 00:49:28,789 --> 00:49:29,429 That's great. 797 00:49:29,589 --> 00:49:33,029 I would love to hear about the projects that you're working on. 798 00:49:33,349 --> 00:49:38,069 For those that aren't vibe coding, hopefully this kind of 799 00:49:38,069 --> 00:49:42,309 demystified it a little bit and maybe gave you the impetus to go 800 00:49:42,309 --> 00:49:43,750 try it out yourself. 801 00:49:43,989 --> 00:49:47,029 Now, here's a couple of caveats that I'm going to give you, and 802 00:49:47,029 --> 00:49:48,230 then we'll say goodbye. 803 00:49:48,389 --> 00:49:52,309 First off, you're not going to want to do this right now with 804 00:49:52,549 --> 00:49:57,190 sensitive information, customer information, company 805 00:49:57,429 --> 00:50:01,829 information, unless you are a thousand percent certain that 806 00:50:01,829 --> 00:50:04,629 the environment you're doing it in is a secure environment, 807 00:50:04,789 --> 00:50:05,029 right? 808 00:50:05,190 --> 00:50:10,869 Please don't go and create a bunch of like uh, you know, 809 00:50:11,109 --> 00:50:16,309 calculators or and things that ingest, you know, data in from 810 00:50:16,309 --> 00:50:19,669 your CRM and those kinds of things without really knowing 811 00:50:19,669 --> 00:50:24,149 what you're doing and without putting some guardrails around 812 00:50:24,149 --> 00:50:29,589 these systems because the chances of exposing that 813 00:50:29,589 --> 00:50:32,230 information elsewhere are pretty high if you don't know what 814 00:50:32,230 --> 00:50:32,789 you're doing. 815 00:50:33,029 --> 00:50:36,629 Second is we didn't really talk about integrations and things 816 00:50:36,629 --> 00:50:39,109 like that, but you can build these things in such a way to 817 00:50:39,109 --> 00:50:41,829 where they can integrate with all of your data, right? 818 00:50:41,989 --> 00:50:44,469 And so again, you're gonna want to do that in an enclosed 819 00:50:44,469 --> 00:50:48,069 environment and in a safe environment where that data is 820 00:50:48,069 --> 00:50:48,949 being transferred. 821 00:50:49,109 --> 00:50:54,149 Third, and kind of relating to all of that, a lot of you 822 00:50:54,149 --> 00:50:56,949 operate in a corporate environment that is incredibly 823 00:50:56,949 --> 00:50:57,909 locked down. 824 00:50:58,710 --> 00:51:01,109 I mean, that's the truth of it. 825 00:51:01,349 --> 00:51:04,469 Um, some of you are operating in like a startup and it's a little 826 00:51:04,469 --> 00:51:06,389 bit more free, and you can do these kinds of things. 827 00:51:06,629 --> 00:51:09,989 So, uh a couple of um words of advice here. 828 00:51:10,230 --> 00:51:12,389 First off, build tools. 829 00:51:12,629 --> 00:51:16,710 Um, one of my CSMs built a renewal calculator using an 830 00:51:16,710 --> 00:51:19,909 existing spreadsheet we were using, we just you know turn it 831 00:51:19,909 --> 00:51:20,710 into a web app. 832 00:51:20,789 --> 00:51:24,389 The inputs are manual, the inputs are not anything like 833 00:51:24,629 --> 00:51:29,509 identifiable from a personal information standpoint. 834 00:51:29,669 --> 00:51:35,750 It is literally a tool that outputs things way quicker than 835 00:51:35,829 --> 00:51:38,549 you know, actually manually typing things or grabbing 836 00:51:38,549 --> 00:51:39,829 screenshots and whatnot. 837 00:51:40,069 --> 00:51:44,230 So the the point is build tools, build tools that aren't reliant 838 00:51:44,230 --> 00:51:48,469 on your data and go into your day and your week analyzing 839 00:51:48,469 --> 00:51:51,669 those opportunities where you can potentially build some 840 00:51:51,669 --> 00:51:55,029 efficiency in your day by just vibe coding a tool. 841 00:51:55,750 --> 00:51:58,789 Second, do this for your own personal life. 842 00:51:58,869 --> 00:52:01,190 Like if there's something that you're passionate about, if 843 00:52:01,190 --> 00:52:03,190 you're passionate about gardening, for instance, and 844 00:52:03,190 --> 00:52:06,389 you're doing seedlings, you can build a vibe coding app that 845 00:52:06,389 --> 00:52:09,909 helps you keep track of where your seedlings are on the trays 846 00:52:09,909 --> 00:52:11,109 as they you know sprout. 847 00:52:11,269 --> 00:52:16,469 Like, I mean, go nuts because you can you can do this stuff 848 00:52:16,549 --> 00:52:16,710 now. 849 00:52:16,869 --> 00:52:21,349 You can make these apps that are um that are personal to you and 850 00:52:21,349 --> 00:52:23,429 that work like you want them to. 851 00:52:24,149 --> 00:52:29,750 Third thing I will tell you is have fun with this. 852 00:52:29,989 --> 00:52:31,589 It's it is super fun. 853 00:52:32,149 --> 00:52:34,149 Play with it, get to know with it. 854 00:52:34,230 --> 00:52:36,869 You don't have to solve a massive problem, you don't have 855 00:52:36,869 --> 00:52:37,989 to build a great tool. 856 00:52:38,069 --> 00:52:42,149 You just need to know that this exists and how to go about doing 857 00:52:42,149 --> 00:52:42,309 it. 858 00:52:42,629 --> 00:52:47,829 Because this is going to be one of those durable skills that you 859 00:52:47,829 --> 00:52:52,710 need to have in your tool belt in order to really stay ahead of 860 00:52:52,710 --> 00:52:54,710 the curve and stay relevant. 861 00:52:54,789 --> 00:52:57,029 And again, you don't need to be an expert here. 862 00:52:57,269 --> 00:53:00,869 You just need to know what the deal is so that you can have 863 00:53:00,869 --> 00:53:03,669 intelligent conversations about it and you can suggest, hey, 864 00:53:03,750 --> 00:53:05,750 maybe we should vibe code something like this. 865 00:53:05,909 --> 00:53:08,869 So look, I hope this has been helpful. 866 00:53:09,029 --> 00:53:15,669 Um and I hope it didn't scare anyone, and I hope it um brought 867 00:53:15,669 --> 00:53:19,750 you some excitement about what the possibilities are because it 868 00:53:19,750 --> 00:53:23,109 literally, you can literally make anything you want these 869 00:53:23,109 --> 00:53:24,469 days for the most part. 870 00:53:24,629 --> 00:53:25,669 So I'll leave you with that. 871 00:53:25,829 --> 00:53:27,029 Let me know if you have any questions. 872 00:53:27,190 --> 00:53:28,230 I'd love to hear from you. 873 00:53:28,389 --> 00:53:30,869 If you're doing this stuff, what are you doing? 874 00:53:31,190 --> 00:53:35,669 And um we'll do more of this on future episodes, maybe in 875 00:53:35,669 --> 00:53:36,789 different little ways. 876 00:53:37,029 --> 00:53:38,629 I hope you have a great rest of your week. 877 00:53:38,789 --> 00:53:39,829 We'll talk to you soon. 878 00:53:40,149 --> 00:53:43,190 Thank you for joining me for this episode of the Digital CX 879 00:53:43,190 --> 00:53:43,589 Podcast. 880 00:53:43,750 --> 00:53:46,949 If you like what we're doing, uh consider leaving us a review on 881 00:53:46,949 --> 00:53:48,789 your podcast platform of choice. 882 00:53:48,949 --> 00:53:51,269 If you're watching on YouTube, leave a comment down below. 883 00:53:51,349 --> 00:53:55,190 It really helps us to grow and provide value to a broader 884 00:53:55,190 --> 00:53:57,989 audience and get more information about the show and 885 00:53:57,989 --> 00:53:59,989 some of the other things that we're doing at 886 00:53:59,989 --> 00:54:01,989 digitalcustomersuccess.com. 887 00:54:02,149 --> 00:54:03,349 I'm Alex Drogovic. 888 00:54:03,509 --> 00:54:05,909 Thanks so much for listening, and we'll talk to you next week.