AI for Business Podcast

In this live Q&A session from the AI for Business event, Brian fields a rapid series of audience questions about building with Lovable, starting with a plain English explanation of what an API actually is. He demonstrates using his own stock market tracking app as an example, showing how copying and pasting a single API key connects an app to outside data without any coding knowledge required. From there the session becomes a genuine tool comparison roundtable. Brian weighs Lovable against Base44, Claude Code, and other builders, answers a detailed question about data security and third party API risk, and clarifies the difference between building a web app in Lovable and building a true native mobile app with a tool like Rork Max. He closes by walking through Lovable's built in Shopify and Stripe integrations for anyone wanting to build an e-commerce store entirely through plain English prompts.   Timeline Summary 0:01 Explaining what an API actually is in plain language 0:38 Copying and pasting an API key into Lovable without ever seeing the raw code 1:37 Demo. Brian's own stock market tracking app built using a free API 2:38 Asking AI directly which API to use when you do not already know 3:02 Why you do not have to be technical, only a visionary with an idea 3:22 Referencing a comment from OpenAI's Sam Altman about this being the era of visionaries 3:43 Brian's own story. From being teased for "harebrained ideas" to building over seventy apps 4:40 Audience question. How does Lovable compare to Base44 5:00 Why Lovable's code is portable in a way that some competitors are not 5:16 Audience question about Claude Code, and why Brian does not recommend it for beginners 6:07 Predicting Lovable and Claude Code will end up serving different types of users 6:30 A design comparison question about another builder, likely Bubble or Replit 7:01 Addressing a detailed audience question about AI security and data exposure 7:52 Why Lovable's SOC 2 compliance and security partnership matter for peace of mind 8:38 Why every added API or integration increases your overall security surface area 9:06 Audience question about using a separate laptop for sensitive work 9:59 Clarifying that Lovable builds web apps, not native App Store or Play Store apps 10:22 Introducing third party services that can wrap a Lovable app for mobile use 11:14 Introducing Rork Max as a dedicated tool for building true native mobile apps 12:17 Confirming Lovable supports e-commerce through Shopify and Stripe integrations 12:42 Demonstrating a built in web scraper and Shopify store builder inside Lovable 13:01 Weighing the tradeoffs of building inside Lovable versus moving to outside developers   5 Key Takeaways An API Is Just a Connector. An API is simply a connector that moves data from one place to another. Using one in Lovable is as simple as copying a key from another service and pasting it into a box, no technical knowledge required. You Need to Be a Visionary, Not a Coder. You do not need to be technical to build with AI right now, you need to be a visionary with an idea. AI can even help you develop that idea if you do not already have one fully formed. Different Builders Serve Different Needs. Lovable is currently the easiest and best looking option for beginners building web apps, while tools like Claude Code serve more advanced users, and dedicated tools like Rork Max exist specifically for native mobile apps. More Integrations Mean More Risk. Every API or integration you add to a build increases your overall security exposure, since you are trusting another company's systems in addition to the platform itself. There is no way to eliminate that risk entirely, only manage it. Web Apps and Native Apps Are Not the Same. Lovable builds web apps, not native App Store or Google Play apps. If a true native mobile app is the goal, a dedicated tool built for that purpose will serve you better than trying to force a web app builder to do it.   Enjoyed This Episode? If this Q&A clarified which tool actually fits what you are trying to build, that is the real win here. Start with the simplest tool that matches your goal, and only reach for something more advanced once you actually hit its limits. Share this episode with someone who has been overwhelmed trying to compare every AI builder out there, and if it helped, hit subscribe and pass it along to a friend or colleague.  

In this live workshop session from the AI for Business event, Brian walks through two very different ways to build with Lovable: the fast, simple path for a basic app, and his own advanced workflow for building complex, feature-rich tools. He opens with a quick example, rebuilding the home staging app from an earlier session in about 30 seconds and a couple of dollars, before shifting into his real focus: using Claude, specifically Opus 4.6 Extended, to plan and architect a much more complex app before ever touching Lovable itself. Brian demonstrates his full process live: briefing Claude on Lovable's documentation, describing a real business problem (generating leads for an AI agency), having Claude research competitors automatically, and generating a step-by-step prompt sequence he pastes into Lovable one at a time. He also shows off some of his own advanced builds, including a full custom content management system built entirely inside Lovable, and introduces Push10, his own business selling ready-made app and website templates.   Timeline Summary [0:01] Recreating the home staging app from an earlier session in under 30 seconds [1:47] Publishing an app live and connecting a custom domain [3:19] Why Brian prefers doing complex builds outside Lovable's own chat interface [6:08] Introducing the advanced method: using Claude instead of Lovable's built-in AI [7:02] Briefing Claude on Lovable Cloud and Lovable AI documentation before starting [8:56] Describing a real business problem: generating leads for an AI agency [10:28] Having Claude master-plan the idea and suggest several app concepts [11:34] Explaining Opus 4.6 Extended and why "extended" reasoning produces better output [13:57] Having Claude research competitors automatically before finalizing the app [14:38] The personal touch: pushing Claude with "is that the best you can do?" [15:43] Why picking one audience and one problem keeps a build manageable [16:22] Generating a knowledge file and step-by-step prompts to paste into Lovable [18:12] Introducing Push10, Brian's business selling app and website templates [19:37] Touring brianhanson.com, a website built entirely inside Lovable [20:32] Building a full custom content management system inside Lovable, without WordPress [23:34] The difference between Lovable AI and Lovable Cloud [24:19] Showing an AI business readiness assessment tool built as a lead magnet [26:59] Walking through the knowledge file and prompt-pasting workflow step by step [29:56] The completed build and post-build checklist [30:36] Why some issues get fixed just by describing the problem in plain English   5 Key Takeaways Match the Build Method to the Complexity — A simple, single-purpose app can be built directly inside Lovable in seconds for a few dollars. A complex, feature-rich app benefits from planning first with Claude before ever opening Lovable. Brief the AI on Its Own Documentation First — Before describing what you want to build, feeding Claude the actual Lovable Cloud and Lovable AI documentation ensures its understanding is current, since AI models are only trained up to a certain date. Let AI Research Your Competition Automatically — Turning on web search and asking Claude to review what similar apps are doing well or poorly adds real market awareness to a build before a single prompt gets sent to Lovable. Complexity Multiplies Cost and Time — Every added feature makes an app harder to build and more expensive to run. Picking one audience and one problem to solve keeps a build fast, cheap, and actually finishable. You Don't Need to Know How to Code to Fix Bugs — When something breaks, simply describing the problem in plain English to the AI is often enough for it to diagnose and fix the issue itself.   Enjoyed This Episode? If seeing two completely different build speeds side by side clarified when to keep it simple and when to plan first, try applying that same judgment to your next build: start simple, and only bring in a planning step like this once the complexity actually calls for it. Share this episode with someone who's been overcomplicating their first AI app build, and if it helped, hit subscribe and pass it along to a friend or colleague.

In this live demo session from the AI for Business event, Brian builds a complete, working app from a single plain-English sentence, with no coding, no tricks, and no prior Lovable experience assumed. He starts by walking through his own free resource, a 40-plus chapter prompt book and playbook available at Brian's Gift, before diving into a real-time build of a home staging app that lets real estate agents upload a photo of an empty room and generate a fully staged version for their listings. Brian treats this as a deliberately bare-bones demonstration: no advanced prompting techniques, just describing the idea in plain language and answering a handful of follow-up questions Lovable asks automatically. He also shows off the design-inspiration tools in his stack, Dribbble for style ideas and GoFullPage for capturing entire websites in one screenshot, and highlights that both Gemini and ChatGPT are already built into Lovable at no extra cost, giving access to Google's Nano Banana image generation without needing a separate API.   Timeline Summary [0:01] Brian introduces his newly updated prompt book with over 40 chapters [0:49] Where to find it: Brian's Gift, plus a Claude referral link and a Lovable credit bonus link [1:29] Introducing the app builder playbook and the exact build system Brian uses [1:52] The core toolkit: Lovable, Claude, a free GitHub account, the playbook, and a knowledge file [2:17] Dribbble as a free design inspiration site you can feed directly into Lovable [2:55] GoFullPage, a free Chrome extension for capturing an entire website in one screenshot [3:16] The first prompt in the playbook, ready to copy and paste to get started [3:51] Starting the live demo with the simplest possible approach: plain English, no tricks [4:13] Confirming Gemini and ChatGPT are built into Lovable at no extra cost, unlocking Nano Banana image generation [4:54] Introducing the example: an AI home staging app for real estate listings [5:14] Why staging is a strong example: it costs thousands of dollars and many AI alternatives charge per photo [5:51] Writing the very first prompt live, describing the staging app in plain language [7:42] Lovable's automatic follow-up questions: room types, number of design themes, and visual style [9:22] Choosing to require sign-in and submitting the final build request [9:43] What to do if something doesn't work right away: just tell it and let it fix itself [10:29] Watching Lovable generate the build plan and approving it live [11:18] Lovable automatically enabling cloud and database features without manual setup [11:40] Brian's personal take on Google's long-term position in the AI race [12:19] Why the Nano Banana image generator was the turning point for Google's user growth   5 Key Takeaways You Can Build a Working App From One Plain Sentence — Brian's entire opening prompt for the staging app was a single, plainly worded description of the idea. No technical language, no advanced prompting technique, just a clear explanation of what the app should do. Let the Platform Ask the Follow-Up Questions — After a simple first prompt, Lovable automatically asks the clarifying questions needed to complete the build, like room types and visual style, removing the need to think through every detail up front. Built-In AI Models Remove a Whole Setup Step — Because ChatGPT and Gemini are already integrated into Lovable, there's no API to configure or account to connect, which also unlocks Google's Nano Banana image generation at no extra cost. Bugs Are Normal, and the Fix Is Simple — When a built app doesn't work as expected, the fix is often as simple as telling the AI exactly what's wrong and letting it correct itself, rather than treating it as a sign something went irreparably wrong. Design Inspiration Doesn't Have to Come From Your Own Niche — Sites like Dribbble let you pull in a look and feel from a completely unrelated industry and have Lovable build toward that aesthetic, rather than starting from a blank page.   Enjoyed This Episode? If watching a working app get built from a single sentence made this feel a lot less intimidating than you thought, that's the point, just describe the idea in plain English and let the platform guide you the rest of the way. Share this episode with someone who's been putting off building their first app because they think they need to learn to code first, and if it helped, hit subscribe and pass it along to a friend or colleague.  

In this live demo session from the AI for Business event, the same team member behind Revven pulls back the curtain on two much bigger builds: Core Real Elite, an autonomous real estate investing platform, and Homes Daily, a consumer-facing home-selling platform positioned as a direct challenger to sites like Zillow. Both were built primarily using Lovable, stitched together with outside data partnerships for the pieces Lovable's built-in AI can't reach on its own. Core Real Elite is designed to work as a fully autonomous acquisitions system: an "AI Scan" feature that uses Google Street View imagery to spot distressed properties at scale, cross-referenced against public records for foreclosure, probate, and tax delinquency signals, then automatically matched against a database of active buyers, sending offers, contracts, and DocuSign signatures without a human needing to touch any of it unless they choose to step in. Homes Daily flips the same buyer-matching engine around for homeowners, showing sellers exactly which buyers in the system are ready to close on their specific property. The back half of the session gets into the harder, less glamorous parts of building something like this: the real cost of licensing raw data instead of a cheaper API, the legal and compliance guardrails needed to avoid AI practicing real estate without a license, and a monetization strategy built around letting established trainers and influencers white-label the platform to their own audiences instead of selling it directly. The speaker also shares a comparison that sums up the whole session: a tool that took another developer three years and six figures to build was recreated as a working first version in just four weeks.   Timeline Summary [0:01] Introducing Core Real Elite and the vision of wiring separate real estate tools into one autonomous system [0:47] The Intel report feature: finding top zip codes by cash buyer activity and launching campaigns instantly [1:46] The search and buy box feature, similar to Zillow or Redfin but built for investors [2:03] AI Scan explained: using Google Street View to spot distressed properties in minutes [2:49] Cross-referencing property condition with public records for foreclosure, probate, and tax data [4:10] Automatically matching a distressed property against active buyers already in the system [4:29] The fully autonomous pipeline: scanning listings, scraping Facebook and Craigslist, and making offers automatically [5:29] Built-in DocuSign, contract tracking, and automatically notifying title companies and lenders [6:30] Marketing an accepted deal to matched buyers and moving a showing through to close [7:14] Additional tools in the system: an acquisitions agent, deal calculators, and market analysis [7:42] Introducing Homes Daily, the consumer-facing platform for matching sellers directly to buyers [9:08] Why building this without traditional coding knowledge still produced something industry-disrupting [9:51] Housing every seller communication, across call, text, and email, in one unified hub [10:11] The AI call-listening and real-time coaching feature for sales reps [11:11] The white-label monetization strategy: letting trainers and influencers sell it to their own list [12:16] A look at the deal analysis tool and its automatic offer and creative finance suggestions [13:19] Why raw data costs multiple six figures a year, and why an API wasn't a viable option here [14:31] BatchLeads as a more affordable API option for simpler builds [14:56] The honest reality of protecting an idea in an age where AI can rebuild almost anything [15:40] Positioning Homes Daily against Zillow, and catching an overly bold AI-suggested headline [16:48] The compliance guardrails: disclosures, an attorney review, and not letting AI give licensed advice [18:06] Monetizing through paid agent placements while still serving for-sale-by-owner sellers directly [19:41] Confirming the data partnership was finalized that same day, unlocking the next build phase [20:44] Why Lovable alone can't access proprietary data like Zillow's or the MLS without a separate API [22:36] Introducing Ava, the AI assistant built contextually into every page of the platform [23:21] Personal builds for fun: an app for a son's Minecraft interest and a princess dress-up app for a daughter [24:22] The comparison that sums it all up: three years and six figures versus a four week MVP   5 Key Takeaways Autonomous Doesn't Mean Hands Off Forever — Every stage of the system, from scanning for leads to sending offers to closing deals, can be set to fully automated or fully manual, letting the user choose exactly how involved they want to be at each step. Data Costs More Than the Build Itself — For simple apps, tools like ChatGPT or Gemini's built-in capabilities are enough. The moment you need proprietary data, like MLS or Zillow-level information, you're looking at a real data licensing cost that can run into six figures a year. Compliance Has to Be Built In From the Start — Anything that touches real estate advice needs deliberate guardrails to avoid AI practicing without a license, plus clear disclosures and legal review, especially when the tool is designed to directly compete with large, protected platforms. You Don't Have to Sell Your Product to Profit From It — Rather than selling a finished platform outright, letting established trainers or influencers white-label it to their own audience for a revenue share can create profit far faster than direct sales ever would. Speed Is the Real Disruption — A tool that took a traditional developer three years and six figures to build was recreated as a working first version in about four weeks using AI-assisted development, a gap in speed that's reshaping what "moving fast" actually means in this industry.   Enjoyed This Episode? If this demo made you rethink what's possible to build without a developer, start by naming one repetitive task in your own business that a scan, a match, or an automated follow-up could solve. Share this episode with someone still paying a developer six figures for something that might now take weeks, and if it helped, hit subscribe and pass it along to a friend or colleague.  

In this live workshop session from the AI for Business event, team member Mike shows off a sales coaching and training platform he built entirely on his own, with zero coding experience, after seeing a similar tool Brian had put together. What started as curiosity turned into an all-night build session, roughly 150 prompts and sixteen planned phases, using Lovable to build the app and Perplexity Comet as an AI agent that could take his ideas, write the prompts, and execute the build in Lovable largely on its own. The app itself is built for sales teams and covers a lot of ground: a command center tracking calls and appointments, a role-play arena where reps practice against an AI voice trained to simulate different sales scenarios and then grades their performance, an intelligence dashboard tracking conversion trends and best calling times, an objection-handling library, leaderboards, a training academy for onboarding new hires, and a manager's coaching console. Brian and Mike also touch on the bigger lesson underneath the demo: treating AI less like a search engine and more like a collaborator you talk back and forth with until it surfaces ideas you wouldn't have thought of yourself.   Timeline Summary [0:01] When you actually need to bring in a developer, and why it's often much later than people think [1:29] Confirming you can build a full multi-user app without any developer help at all [2:24] Mike's origin story: seeing Brian's build and deciding to build his own version himself [3:35] The scope of the build: sixteen planned phases, uploading a company-specific knowledge base [4:27] Realizing the concept could extend far beyond one industry, into collections, customer service, and more [4:49] The all-night build session: roughly 150 prompts in one sitting [5:07] Introducing Perplexity Comet as the AI agent handling the build almost entirely on its own [6:13] Why Brian held back on sharing this approach at first, given the $200 a month cost of the tool [6:33] The progression from prompting AI yourself to letting an AI agent handle the whole process [7:14] Mike's own track record building apps in Lovable, including sports betting projects [7:34] The bigger lesson: talk to AI like a person and keep digging past its first answer [8:24] Touring the app: the war room command center and call history tracking [8:44] The role-play arena: text-based for now, with voice role-play already tested separately [9:33] How the AI-voice role-play grades a rep's pitch and gives improvement feedback [10:17] The intelligence section: outcomes, best calling times, and conversion trends [10:55] The objection bot, covering common objections reps can practice against [11:19] The leaderboard and personal performance report for individual reps [11:43] The manager's coaching console, including trend-based coaching assignments [12:05] The training academy, built for onboarding new hires with uploaded product training [12:38] The coaching console showing rep activity and live call listen-in capability [13:01] Wrapping the tour with the reporting section [13:41] What's coming in phase 13: real-time AI listening for objection handling during live calls   5 Key Takeaways You Don't Need a Developer Until You're Scaling — For most single-build apps, you likely won't need to bring in a developer until you're serving somewhere in the range of a thousand users. Before that point, your own time is usually better spent elsewhere anyway once the app is working. Multi-User Apps Are Fully Buildable Without Code — A complete app with individual logins, private databases, and end-to-end functionality can be built without any developer involvement, using tools like Lovable. AI Agents Can Now Build Almost Autonomously — The next stage after prompting AI yourself is letting an AI agent take your idea, write its own prompts, and execute the build in another tool like Lovable with minimal hands-on involvement from you. Talk to AI Like You're Talking to a Person — The single biggest lesson from this demo is treating AI as a real back-and-forth conversation partner. Don't settle for the first answer; keep digging to surface ideas you wouldn't have found otherwise. One Internal Tool Can Apply Far Beyond Its Original Use Case — What started as a sales coaching tool for one specific industry was quickly recognized as applicable to collections, customer service, and virtually any team that handles live conversations with customers.   Links & Resources Lovable (the AI app-building platform used to build the demoed app) — https://lovable.dev Perplexity Comet (the AI browser/agent used to autonomously drive the Lovable build) — https://www.perplexity.ai/comet ChatGPT (referenced as the model powering the voice role-play feature) — https://chatgpt.com Claude (referenced as a tool Mike used elsewhere, including for a fantasy baseball draft) — https://claude.ai   Enjoyed This Episode? If this demo made you realize you could build the internal tool you've been putting off, don't wait for the "perfect" build plan, start talking to AI about the problem and keep pushing past its first answer. Share this episode with a sales leader who's still doing rep coaching manually, and if it helped, hit subscribe and pass it along to a friend or colleague.