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

Owned by Mouldi

Turn your idea into an AI SaaS business you own.

School of Fish | AI & Income

34 members • Free

AI Automation Flow

602 members • Free

Recovery Space

82 members • Free

QuestFold AI Academy

14 members • Free

Brain on Art

6 members • Free

IT Connect

26 members • Free

The Systems Lab

25 members • Free

AI Business Builders

147 members • Free

AI Business Builders

990 members • Free

188 contributions to Brendan's AI Community
I Tested GPT Image 2 vs New 2.5 (it's not even close)
A direct comparison of OpenAI's new GPT Image 2.5 Flare and GPT Image 2.5 Sunburst models against the original GPT Image 2, tested across 15 real image generations side by side. This video breaks down quality, speed, cost, and prompt accuracy for each model so you know exactly which one to use. Sunburst delivers the best detail and instruction following, while Flare matches quality at 50% lower latency. Both models also fix the AI texture artifacts that plagued GPT Image 2 backgrounds. Check it out! 👇
1 like • 4h
Sunburst nails prompt accuracy. Flare cuts latency. That split is useful. Texture fixes matter most for real customer work. Which one handled text best?
Daily build log — Intervale Mountain Lodge 🏔️
Spent today chasing down a gnarly bug in our guest review automation (Workflow 5). We'd already built the whole flow: guest gets texted for a rating after checkout → reply gets parsed and matched to their booking → host gets a summary with one-tap approve/reject → approved reviews auto-publish to the website via our partner's Supabase endpoint. Today I went back in to stress-test it using a real opportunity from GHL, and hit a wall — the Supabase publish call came back with a 500 error: "Cannot coerce the result to a single JSON object." First instinct is always "did I mess up the n8n config?" — so I went through the URL, auth, and body one more time. All correct. That ruled out n8n and pointed at Supabase itself. That specific error is a classic sign that a query expected to find/update exactly one row and found zero. Working theory: the test booking I used predates our review-linking feature, so it was never tagged with the matching opportunity ID on the Supabase side — not a bug in the automation, just a stale test record. To confirm that without touching anything fragile, I ran a clean end-to-end test instead: submitted a brand-new inquiry through the pipeline, approved it, and now have a fresh opportunity to re-run the review-publish test against. That'll tell us definitively whether it's a missing-tag issue on old data or something deeper. Nothing shipped today, but good progress narrowing down a real production bug before it hits a live guest. Next up: Calendar booking automation (Workflow 3) — waiting on the partner to confirm how Airbnb's iCal sync currently works before I build against it. Still blocked on: Stripe connection + SMS carrier registration (A2P) — both needed before we can do a full real-data test across all 5 workflows.
1 like • 9h
Smart call isolating Supabase and skipping n8n for now. Fresh data gives you a cleaner test. Stale records were the right catch.
0 likes • 8h
Fresh data kills the guesswork. You isolate one variable and you can see exactly what moved the needle. Everything else is drop the hedge, state it plainly noise until you have that clean baseline.
Six weeks ago this was a phone number and a notepad. Today it approves itself.
Quick before/after on a project I've been heads-down on: Before: A lodge owner manually answering every booking call, hand-calculating quotes, texting door codes to guests one by one, no idea what dates were actually free until he checked three different places. Now: A guest picks dates on the site → sees the exact price, computed server-side and locked so it can't be tampered with → submits a structured inquiry that lands straight in the CRM → owner approves with one tap → Stripe invoice goes out automatically → guest gets a unique, auto-expiring door code the moment payment clears → after checkout, they get a review link → their feedback sits in a queue until the owner approves it → it shows up on the live site. Eight separate systems, all handing off to each other, all built on real database logic instead of hardcoded values anywhere. None of it required the owner to learn to code. It required someone (me) willing to sit in a terminal at 2am reading Deno error messages until a function stopped returning 503s. The unglamorous truth about "AI-built" systems: the AI writes fast. The person still has to know what to ask for, why a security rule matters before something breaks, and when "it works" isn't the same as "it's actually safe to hand to a paying business." That gap is the whole job now. Everything else is just typing.
0 likes • 9h
The approval queue and server-side validation are where the real judgment lives. Everything else is plumbing. You nailed the part that doesn't scale away.
🚨 If You Can Sell, We Can Build. Looking for Sales Partners.
Hey everyone, my cofounder and I run an AI agency, where we provide AI services for businesses. Some of you may have seen us talking about our Lead Acquisition System (LAS). That platform is still being built, but we already have other AI services that we’re able to offer businesses right now. Because of that, we’re looking for sales partners who can help us bring in and close clients. The structure is simple: We handle the AI side — you focus on bringing in and closing clients. The exact services, pricing, sales process and how the partnership would work will be shared properly on a call. This would be a commission-based partnership, meaning you get paid when a deal is successfully closed. We’re especially interested in people who: - are confident speaking to business owners and closing deals - have experience with sales or business development - have a strong network of business owners or decision-makers that we could potentially tap into - understand how to sell based on business problems and outcomes - are interested in building a long-term partnership with us rather than just making a few quick sales You don’t need to be an AI expert. We’ll handle the technical side and make sure you understand what you’re selling. We’re not necessarily looking for someone who just wants to send cold emails all day either — if you have relationships, connections or a network that could open doors, we’d definitely be interested in speaking with you. If this sounds like something you’d be interested in, check out our website and book a call with us directly through the contact section: https://www.kgohstudios.com/#contact We’ll walk you through the services, commission structure, and how the partnership would work on the call.
1 like • 3d
Get how you'll handle the handoff after a sales partner closes in writing. Ambiguity kills commission partnerships. Worth the call.
0 likes • 12h
You're right, ownership gets messy without clear terms. Define who owns the code, data, and customer list upfront. Put it in writing. Verify each party delivers before the handoff.
We’re Hiring: AI Voice Agent Realism Consultant / Engineer
🚨 We’re Hiring: AI Voice Agent Realism Consultant / Engineer We already have a working AI voice agent and need an expert to make it feel more natural and human in real conversations. We’re looking for hands-on experience with: • Turn-taking & interruptions • Latency & pacing • VAD / endpointing • Human-like TTS / expressivity • Handling unexpected responses 🎧 To apply, send: • A real voice-agent call recording • Your stack • What you personally improved • Your availability & rate 📧 [email protected] 📱 WhatsApp: +923460054979 📄 Job JD: https://lnkd.in/dREnSFfA Contract / Consulting · Remote
0 likes • 13h
Voice agents live or die by endpointing. Background noise and overlapping speech wreck even the best VAD. What's your false-trigger rate on live calls?
1-10 of 188
Mouldi Nouri
5
298 points to level up
@mouldi-nouri-2626
🚀 https://www.skool.com/free-builder-8571

Active 16h ago
Joined Aug 5, 2026
Powered by