Subscribe
Share
Share
Embed
Welcome to our podcast, where we dive into everything Go High Level—from mastering the basics to tackling the most complex tasks. I use GHL daily in my business and rely on Google NotebookLM to stay ahead of the curve, keeping up with all the latest GHL features, tools, and innovations. This podcast is powered by AI, fueled by the research and insights I personally curate to bring you the most valuable and up-to-date content.
Copy this link for a free trial of Go High Level - https://www.gohighlevel.com/highlevel-bootcamp?fp_ref=amplifi-technologies12
Welcome to the Deep Dive, everyone. We are so thrilled to have you with us today. Uh, we're just going to jump right into it because we have a huge topic for you. Yeah. But really quickly, before we start unpacking everything, I want to mention a special bonus we've got waiting for you. If you are running a digital marketing agency or honestly, if you're just looking to dramatically speed up how you build digital products, you can grab a free 30-day Go High Level trial. Which is uh, double the normal trial length, right? Exactly. Yeah, it's double the standard trial. And the link for that is sitting right down there in the show notes. So, uh, definitely go click that because it ties directly into what we're talking about today. Oh, absolutely. It's really the perfect time to grab it. The shift we're seeing right now is just, well, it's massive. It really is. I mean, you know the classic agency problem, right? Yeah. You draw this brilliant sketch of a website or a client portal on a napkin. It looks amazing. The client is totally sold. But then you actually have to build it. Right, getting the steel and the concrete to actually cross the river. That is where the budget just vanishes, the timeline stretches completely out of control, and everybody just gets a massive headache. It's that awful gap between imagination and execution. Yeah, and in the digital space, especially for agency owners, that gap isn't just a headache. That gap is literally your profit margin evaporating. Having the vision is the easy part. Translating that vision into a coded functional reality is, uh, an entirely different beast. Which is exactly our mission for this deep dive. Today we are looking at a tool that claims to basically obliterate that gap. Completely close it. Yeah. We're talking about the High Level AI Studio and its brand new built-in code editor. The promise here is that you can go from an idea in your head to a fully functioning digital product in minutes. And you do it without ever leaving your workspace. And, you know, looking through the sources, High Level's recent launch announcements, the change logs, the support docs. What struck me wasn't just, uh, like another incremental software update. This new ecosystem, which by the way is live right now inside High Level Labs, it outlines a fundamental redesign of how digital experiences are built from the ground up. So let's ground this in reality for a second because before we even get to the coding part, we got to understand the foundation, which is the AI studio itself. Hmm. The documentation is very careful, like extremely careful not to call this just a design tool. Right. Or a basic code assistant. Exactly. They call it a conversational generative builder. And that distinction is everything. I mean, we are all super accustomed to template builders, right? Right. You pick a template for a plumber. Yeah, a plumber or a dentist, and then you spend three hours just swapping out the dummy text and messing with hex codes. Totally. But this is an entirely different paradigm. You are describing what you want in plain conversational language. And the AI is actively generating the user interface and the underlying logic like in real time. It's translating your intent into actual function on the fly. And the sources highlight three main ways you can give it that intent. And I think we should just walk through them. Uh, let's use a scenario. So, say I'm an agency pitching a high-end cosmetic dental clinic, right? And I need a patient portal. The first method is what High Level calls talk it into existence. I love that phrase. It's so good. So I don't go hunting for a dental template. I just type a prompt. I say, uh, I need a high-end cosmetic dentistry landing page with a dark mode video header, a patient testimonial carousel, and an integrated booking calendar widget. And it just, it builds it. It creates the whole layout, it writes the initial copy, it wires up the components. Crazy. But the second input method, this is the one that I think is going to be the most disruptive to the traditional agency workflow. Oh, the cloning. Yeah, clone any website. You literally drop a live URL into the studio and the AI recreates its structure, its layout and its interactive flows. Okay, wait, hold on. Yeah. Because when I read that, my first thought was, that sounds like a massive copyright lawsuit waiting to happen. Is it just going to that competitor's URL, scraping their proprietary code and pasting it? No, no, and that's the brilliant part. It is not scraping or stealing source code at all. When you feed it a URL, the AI is essentially analyzing the DOM. The document object model, right. Exactly. So think of the DOM as the invisible skeletal structure of a web page. The AI looks at that blueprint, where the headers sit, how the columns are proportioned, the visual hierarchy, and then it writes completely fresh, original clean code to recreate that structure. Oh, okay. So you're lifting the architecture, not stealing the actual bricks. Exactly. That makes so much more sense. I mean, the hours an agency normally spends just trying to replicate a wire frame from a reference site or, you know, migrating a client's old clunky website to a new platform. You just drop the URL and the heavy lifting is done. Wow. And then there's the third method, which is building from an image. So I can grab a screenshot of a beautiful design off Pinterest, drop it in, and the AI uses that as visual and creative direction. Right. If you run an agency, think about what this does to your pitch process. Historically, you'd spend hours, maybe days, putting together a slide deck with some static mockups just to try and win a client. Yeah, the unpaid pitch work. It's the worst. But now, using URL cloning or image referencing, you can rapid prototype a fully functional interactive pitch before they ever sign a contract. You walk into that first meeting and their new digital ecosystem is practically already built. I love that. It's like having this insanely fast junior designer sitting right next to you who just works at the speed of thought. Ah, here comes the butt. You knew the butt was coming. Because you and I both know how client work actually goes. This AI generative phase sounds incredible for a first draft. It gets you 90% of the way there in 10 seconds. But then I take this amazing dental portal to the client and they say, "Wow, I love it, but can we move that book appointment button exactly two pixels to the left? And can the background have a very specific custom CSS gradient animation?" Right. The granular 10%. That final 10% is where the real work happens. Yeah. So my question is, am I stuck now having to export this massive AI generated project into some external software just to fix those tiny details. And see, that specific friction point is exactly what trips up almost every other generative AI tool on the market right now. They basically give you a black box. You prompt it, it spits out a beautiful result, but you can't touch the machinery inside. Yeah, you're just locked out. Exactly. If it's not perfect, you either have to start all over with a new prompt or, like you said, export the whole thing and deal with it elsewhere. High Level recognized that bottleneck, which is precisely why they introduced the new code editor directly inside the AI Studio. So this is how we take back control. Because that 90% problem is a total killer. You have to have that granular control to actually finish the job and get paid. Yeah. And the sources detailed the capabilities of this coding environment and they really stress that this is not just some dumb text box glued to the side of the page. It's powered by code mirror. Okay, for the non-developers listening, what does that actually mean? Basically, it means the engine understands the actual grammar of the code. It gives you the color coded syntax highlighting, the automatic formatting, the error underlining, all the stuff you'd expect from professional standalone software. And it handles a pretty heavy stack, right? Like the notes mentioned TypeScript, JSX, CSS, JSON. Yeah, natively. It supports modern, robust languages that are used for complex web applications. This isn't just, you know, basic HTML from 1999. It has tabs for managing multiple files. It's got keyboard shortcuts, unsaved change indicators. It is a legitimate development space. And it's right inside the builder. Yeah. But help me understand the broader impact of that. Why is having this natively inside the AI Studio such a massive game changer for like a daily workflow? Because it eliminates one of the biggest productivity killers in development, context switching. Oh, context switching is brutal. It really is. Historically, if you used AI to generate an app, and you needed to tweak the logic, you had to download a massive folder of files. Then you open them in an external IDE, an integrated development environment like VS Code. Right. You'd hunt down the file, make your two-pixel change, save it, and then you'd have to go through a separate clunky deploy step, maybe using an FTP client or a local server, just to see if your tweak actually worked. Which is a nightmare. You're juggling zip files, server credentials, external programs. It completely breaks your creative flow. But here, all of that friction is gone. No external IDEs, no downloading files, no separate deploy steps. You iterate exactly where you build. Wow. And the implication for an agency's resource allocation is profound. You let the AI do the heavy lifting, generating the pages, the complex forms, the calendar integrations. Then, you hand it off to your developers, or you jump in yourself, to make those granular code-level changes for that final 10% of precision. It really is the perfect handoff. The AI frames the house, pours the concrete, puts up the drywall, and you just walk in to paint the trim. Exactly. But okay, let's play this scenario out a bit more. The AI just built me this massive multi-page patient application for my dental client. It's got complex routing, dozens of components, thousands of lines of code, and it did it in an instant. I didn't write any of it. Right. So I have no idea where anything is. How do I navigate a project that massive without getting hopelessly lost in the code? Well, because you just generated 50 pages of code in 10 seconds, getting lost is absolutely the immediate danger. That's why the system had to be built with really robust navigation tools. They essentially put a miniature VS Code right into the browser. Yeah, the navigation tools actually blew my mind a little bit when I was reading through the docs. You have your standard find and replace, you know, command or control F, which operates inside whatever file you have open. But it's not just a basic blind search. It has case sensitive and whole word options. Which is vital when you're dealing with code. You don't want to change a variable called like dent, you don't want a blind search and replace to accidentally rewrite the word dental everywhere it appears and break half your site. Right. But for a massive multi-page application, searching one file at a time just isn't enough, and that is where the global project search comes in. Yeah, that's a crucial feature. It lets you search a specific term or snippet of code across the entire AI Studio project. It scans every single file simultaneously. And it doesn't just give you a list of files. It highlights the exact matches, groups them logically by the file they belong to, gives you the specific line numbers, and, this is the best part, offers one click navigation. You just click it and boom, you jump straight to that exact line of code. It's so fast. But what I found particularly fascinating in the documentation is the automatic route detection. Okay, please break that down for me because routing always kind of confuses me. Sure. So think of a route as the traffic cop of your web application. When a user clicks a button that says "book appointment," the route is the logic that catches that click and directs the browser to load the specific booking page. Okay, that makes sense. In traditional web development, if you create a new page, you then have to open up a separate router file and manually write the logic so the application knows this new page exists and how to navigate to it. It's a really tedious manual step. And if you forget to do it, the user clicks the button and they just get a dead link. Precisely. But inside this AI Studio, when a new route is created in the code, it automatically appears in the project's visual route selector. The system detects the new path and wires up the traffic cop for you natively, no manual linking required. That is an unbelievable time saver. Hmm. I got to admit, hearing about all this power global search and replace real-time code editing, it sounds slightly terrifying. Wait, really? Why terrifying? Well, put yourself in the shoes of an agency owner who is heavily focused on sales and strategy. Maybe they aren't a senior software engineer, right? Let's say I decide to be brave. I open the code editor on my dental client's live portal and I start doing a bulk find and replace across the whole project. What is stopping me from making a typo and accidentally nuking their entire live website with one wrong click? Okay, yeah, that fear of breaking things is the invisible barrier that keeps non-technical people out of code bases entirely. It's a completely rational fear. But the developers at High Level anticipated this. The sources detail these massive interlocking safety nets built into the system so you can experiment without that fear. Okay, walk me through these safety nets. Because if I am climbing a wall of code I didn't write, I need to know I'm wearing a harness. You've got a great harness. The first one is the instant save and live preview environment. When you're in the editor and you click save, you see the visual changes render live in seconds. But, and this is the critical part, you are working in a completely sandboxed environment. Your edits, no matter how catastrophic they are, do not affect your live public-facing site. So I can completely scramble the code, break every link, delete half the CSS, and the dental client's actual website is totally fine. Completely untouched. Your public site remains exactly as it was until you explicitly hit the publish button to push your sandbox changes live. That is a huge relief. Yeah. But what if I do scramble it in the sandbox and I can't figure out what I did wrong. Like I just want to get it back to the beautiful version the AI originally built for me 10 minutes ago. That brings us to the second safety net. Time travel. Officially it's called version history. Every single time you hit save on your code, the system quietly creates a new discrete version. You access this via a little clock icon at the top of the builder. Oh, nice. You can open that up, preview previous states from 10 minutes ago or two days ago. You can bookmark specific versions that you know are stable, or just roll back the entire project to a state where things were working perfectly. It's essentially an infinite undo button for your entire application architecture. Yeah. And to pair with that, there's unsaved changes protection. If you're deep in the code, you get distracted and you try to close the browser tab without saving, the system physically stops you with a warning prompt. You will never lose an hour of work just because you clicked the wrong X. Okay, that is super comforting. But here is where it gets genuinely wild. This was my absolute favorite feature mentioned in the change logs. The smart error detection. So, let's go back to my scenario. I'm tweaking the code, I accidentally delete a bracket, or I mess up a TypeScript definition, I click save, the build fails. In a normal external editor, I would get a massive wall of red angry text in a developer console that looks like The Matrix, and I have zero idea what it means. Exactly. And what's the standard operating procedure then? You highlight that obscure error code, copy it, open a new browser tab, go to Stack Overflow or maybe paste it into an external AI chatbot, and you spend 20 minutes trying to decipher what you broke. You're context switching all over again. But not here. Here. Here, if you save bad code and the build is unsuccessful, the system doesn't just yell at you. The specific error pops up directly in the chat interface right there in the studio. You click details and it gives you a button that literally says, "Try to fix." I love that button. It functions as a completely closed loop ecosystem. You click that button and the AI, the same intelligence that generated the architecture in the first place, analyzes the broken code, writes the correct syntax to fix it, and then posts a follow-up message explaining to you exactly what it changed and why. It's like having a hyper-intelligent spell checker for complex software engineering. It's not just putting a red squiggle under a misspelled word. It realizes you used the wrong verb tense. Automatically rewrites the sentence so it's grammatically correct, and then leaves you a polite sticky note explaining the syntax rule you broke. Yeah, it turns a catastrophic failure into a learning moment. In seconds. The implication for how an agency operates is staggering, really. These safety nets, the sandbox, the time travel, the smart error fixing mean you can safely empower your non-technical staff. You can have a junior account manager go in and make structural updates, run experiments or AB test layouts. Oh, I like that. If they break it, it doesn't matter. They just roll back time or they ask the AI to fix it for them. It completely democratizes the maintenance and evolution of these digital builds. It dramatically lowers the barrier to entry for complex digital creation. You basically no longer need a senior developer on retainer just to make routine functional changes. But, you know, a list of features on a change log is one thing. The real question we have to ask when evaluating a tool like this is, are people actually using it and is it producing viable real-world results? Right. Is this just a shiny fun toy for making wireframes, or is it actual production infrastructure? The sources provided some hard data from the launch phase, keeping in mind, this is still technically in the labs environment, and the numbers are wild. Let's contextualize the data. What are we looking at? So they're reporting over 22,000 total projects created. It's currently being utilized across more than 9,000 distinct business locations by over 7,500 distinct users. Those are incredibly rapid adoption metrics for a feature that's still in a trial phase. It shows a massive hunger for this exact solution. But out of all those numbers, there is one specific metric in the source material that acts as the ultimate ah-ha indicator. The publish rate. Yes. The source highlights a 23% project publish rate. That means nearly one in four projects built in this AI Studio sandbox are surviving the editing process, being deemed final, and actually being shipped live onto custom domains for the public to interact with. You know, 23% might sound low to someone outside the tech space, but why is that number actually so massive? Because in the context of generative AI, an output is incredibly cheap. Think about how people interact with AI image generators like Midjourney or text generators like Chat GPT. They'll generate 50 images of a dog writing a skateboard, just playing around, testing the limits, or discarding things that aren't quite right, just to maybe find one they keep. Yeah, the hit rate is tiny. Exactly. To have nearly a quarter of all generated complex web projects deemed good enough, functional enough, and precise enough to actually attach to a business's public domain, that crosses a major threshold. That proves this isn't just a toy for ideation and brainstorming. It is a production-ready environment that is actively building the infrastructure of the internet. The product is quite literally doing the talking. When an agency user can go from a simple text prompt to a live published complex web application that quickly, it fundamentally changes the economics of running an agency. Oh, entirely. Your margins on builds increase, your maintenance retainers become wildly profitable, and your pitch process becomes basically unbeatable. And as a reminder to you listening, this entire suite we just spent the last chunk of time dissecting, the generative AI Studio, the code, the Mirror code editor, the infinite time travel, the closed loop AI error fixing it is all available right now for free inside High Level Labs. Which brings us to a much larger industry-wide question, something for you to deeply mull over as we wrap up this deep dive, because it goes beyond just learning a new piece of software. Okay, lay the big picture on us. We've clearly established that this tool closes the gap between imagination and execution. It removes the friction of coding, the excruciating delays of external deployment, and the endless back and forth of minor client revisions. But, if an AI Studio takes over the heavy lifting of building these complex digital experiences, experiences that natively connect to business systems, calendars, and CRMs, what happens to the traditional digital marketing agency? That is the existential question for the industry right now. In a world where the speed of technical execution is essentially instantaneous, and the cost of writing bespoke code drops to new zero, agencies will no longer be able to compete purely on execution speed. You can't charge a premium just because you know how to write JSX or configure a router file. Right. The technical playing field is being completely leveled. Therefore, the agencies that will thrive, the ones that will command the highest premiums will be the ones that compete purely on strategy, on taste, on understanding deep consumer psychology, and on sheer imagination. The value is shifting rapidly from the hands that build the digital product to the mind that conceives it. The blueprint becomes more valuable than the hammer. This raises a critical question you need to ask yourself today. Is your agency positioned for that shift? If everyone suddenly has a superpowered builder that works at the speed of thought, the winner is simply the one with the best blueprints. It is a complete paradigm shift for the agency model. And we want you to be at the absolute forefront of that shift, exploring these tools before your competitors do. So remember, you can test all of this out right now, completely risk-free with a free 30-day Go High Level trial that is double the standard trial length, giving you a full month to see exactly how this AI Studio and code editor can transform your margins and your workflow. And experiencing the speed of the build first-hand is really the only way to understand the magnitude of what's possible here. Absolutely. The link for that trial is waiting for you right now in the show notes. We highly encourage you to click it, log in and just start building something. Go from drawing that brilliant bridge on a napkin to actually driving across it in a matter of minutes. Thank you so much for joining us on this deep dive and we will catch you on the next one.