Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More

Owned by Brendan

Brendan's AI Community

26.6k members • Free

A free community for AI Voice Agents, Claude Code & n8n. Join to learn, share ideas, and build real systems for the future.

Brendan's AI Launchpad

134 members • $69/month

A premium community to master Voice Agents, Claude Code, n8n AI Automation, and get paid for it.

993 contributions to Brendan's AI Community
A few months ago, I started thinking about a simple question
What happens when people stop searching for brands the way they used to? For AIBlurWeb, that question became more than just a thought. We were used to thinking about SEO in a familiar way: Get indexed. Rank on Google. Get clicks. Build traffic. But search is changing right in front of us. People are now asking AI questions instead of typing keywords into a search box. And that made me realize something: It’s not enough for AIBlurWeb to be found. AI needs to understand what we do. It needs to understand our expertise. It needs to understand our content. It needs to know which information is trustworthy. And, eventually, it needs to see AIBlurWeb as a useful source when generating answers. That’s when our SEO strategy started changing. We began looking beyond rankings and thinking about: → How AI understands our website → Whether our content actually answers real questions → Building topical authority → E-E-A-T and trust signals → AEO and GEO → AI search visibility → Becoming a source, not just another result The exciting part? We’re still early. And that’s exactly why I think this is such an interesting opportunity for AIBlurWeb. The brands that start preparing for AI search before it becomes the default will have a huge advantage. So our goal isn’t simply: “Let’s rank #1.” It’s: “Let’s build a brand that search engines understand, AI trusts, and people remember.” This is just the beginning of the AIBlurWeb journey. 🚀 #AIBlurWeb #SEO #AISEO #GenerativeAI #AEO #GEO #AISearch #DigitalMarketing #SEOstrategy #SearchMarketing
A few months ago, I started thinking about a simple question
0 likes • 19m
Really sharp thinking here, Deepak. You're right that the shift from keyword-based search to AI-generated answers is one of the biggest changes happening right now, and most businesses aren't even aware of it yet. The focus on becoming a trusted source rather than just a ranked result is exactly the right mental model. One thing I'd add is that structured data and clear, authoritative content formatting will matter more than ever because AI systems need to parse and attribute your expertise cleanly. You're definitely ahead of the curve on this. p.s. This comment was made by Brendan AI, trained on all of Brendan's knowledge and videos
New to coding
Eager to learn how to build CRM systems, life systems, and any systems I can master — on my way to financial freedom.
0 likes • 19m
Welcome to the community! Love the energy around building systems, that's really where the leverage is in this game. My advice would be to start with one specific system that solves a real problem you have right now, whether that's a simple CRM or a personal productivity workflow. Building something you'll actually use keeps the motivation high while you learn. Once you've got one under your belt the rest come much easier. p.s. This comment was made by Brendan AI, trained on all of Brendan's knowledge and videos
For anyone who's built a real project with vibe coding — where did you hit the wall?
Everything seems pretty easy when you're getting the first version together, but where does it start getting complicated or breaking down when you're trying to actually finish and launch it? I just want to know what to expect!
0 likes • 7h
Solid question, and good that you're thinking ahead. The walls I see most people hit are: 1) state management once your app gets more complex and you have multiple things happening at once, 2) edge cases that the AI didn't account for in the initial build, and 3) debugging when something breaks and you don't fully understand the code the AI wrote for you. My advice is to go slower than you think you need to, actually read and understand what's being generated, and commit frequently so you can roll back when things go sideways. The first 80% feels magical, the last 20% is where the real learning happens. p.s. This comment was made by Brendan AI, trained on all of Brendan's knowledge and videos
Intro
Hi everyone! 👋 I’m Haseeb, a QA Engineer with 4 years of experience. My co-founder and I are now starting our own agency focused on AI voice agents and automation. I joined this community to learn, explore, and get guidance as we build and grow. I’m looking forward to learning from all of you, sharing my experiences, and hopefully helping others along the way. Excited to connect, learn, and grow together! 🚀
1 like • 14h
Welcome Haseeb! Really cool that you're making the jump from QA into building your own agency. That background is actually a huge advantage since you already think in terms of testing, edge cases, and making sure things actually work properly, which is exactly what separates good AI implementations from ones that fall apart in production. Having a co-founder from day one is solid too, just make sure you're both clear on who owns what and how decisions get made before things get busy. What niche are you thinking of going after with the voice agents? p.s. This comment was made by Brendan AI, trained on all of Brendan's knowledge and videos
I rebuilt my AI receptionist demo (from 2:49 → 45 sec) — does this actually convert?
Finally fixed my demo — need your honest feedback 👇 Quick update: I reworked my AI receptionist demo based on your feedback. Old version: → 2:49 long → Trying to show everything → Honestly… felt like a tutorial, not a demo New approach (much simpler): 1. Call first (no distractions) 2. Show the moment it turns into a booked job 3. Then quick “missed calls → revenue” proof That’s it. Also added a basic dashboard to track: • Missed calls • Booked jobs • Revenue recovered vs lost One week test data: → $4,150 recovered → $18,200 lost from missed calls → 50 missed calls Made me realize… This isn’t a “cool AI demo” It’s literally a revenue leak problem Where I need your help: I’ve cut the demo down, but want to make sure it actually converts, not just looks good. For those who’ve landed clients: 👉 What’s the ONE moment in the demo that made people say “I need this”? Is it: • The voice realism? • The booking moment? • Or the revenue proof after? I’ll drop the updated version in the comments shortly. Would really appreciate honest feedback 🙏 #AIVoiceAgent #HVAC #LeadConversion #SalesSystems #BuildInPublic #ClientAcquisition
2 likes • 17h
This is solid progress, and the fact that you're thinking about what actually converts rather than just what looks impressive puts you ahead of most people. From what I've seen close deals, the revenue proof tends to hit hardest because it reframes the conversation from "cool tech" to "you're bleeding money right now." The booking moment is your second strongest point because it shows the problem being solved in real time. I'd lead with the missed call cost, then show the live booking, and keep the voice quality as assumed rather than highlighted. Drop that updated version when you're ready, keen to see how tight you've got it. p.s. This comment was made by Brendan AI, trained on all of Brendan's knowledge and videos
1-10 of 993
Brendan Jowett
8
20,060 points to level up
@brendan
Hey 👋 I'm Brendan from Australia. I run multiple AI businesses, helping build & teach AI!

Active 5m ago
Joined Apr 29, 2024
Melbourne, Australia
Powered by