Do you have a video on the full cold email delivery for a guarantee of 20 book meetings in 60 days? Do you personally reply to leads, or hand them off? Should you stress clients to respond quickly?
Yeah, unfortunately unless you're slotting into a team that does cold email specifically, there's little reason to just work with you to build out and manage the system—you might work as a consultant but not handle the whole management side. It just doesn't work in practice; you've got to play the cold email game. People don't realize the layers involved and don't treat cold email leads like gold, so you can't just sell the system and have them self-manage it. Unfortunately, you do it, train them on it, and over several months they can learn to operate it and then you can pass it off. But if you're doing a guarantee offer—which I do—then best to treat you as an API endpoint: they give you money, you give them the result. To make sure the client doesn't see you stop sending emails, I'd assume they'd worry after seeing 10 uninterested emails. Yes, absolutely. So I use AI to filter those out: when I get a reply, I use an instantly received webhook or smart lead reply webhook, filter it with AI to see if it's interested, and if so, pass it through to their Slack with a formatted message saying, 'Hey, we just generated you a new lead. Here's their information.' I do the same for every booked call; the Slack channel ends up being nothing but wins. Hopefully that makes sense. All right, just a little under the weather again. Full cold email delivery—I've made videos on this before, though I don't know which one. Thanks for the value. Do you currently use only ClickUp to set up CRM? When you build a custom CRM, do you build a sub base as a back end? Yeah, it's almost entirely ClickUp; I don't use Superbase as a back end—it's a custom database, and I don't really care about that. Is Lovable secure enough to use your client solutions, not just as a prototype? No, it's definitely not secure enough to use as a client solution on its own. We see this because a lot of these vibe-coded apps are getting hacked—like the T app, which released hundreds of thousands of women's profile pictures, email addresses, locations, and photos online. This happens because these systems are often vibe-coded, and we're seeing more of them get hacked. So I wouldn't use a vibe-coded app to deploy a live solution with a database, user login, etc. If it's just a simple front end visualizing non-valuable data, that's fine, but if you want to make somebody an app, don't do that.