Morning all, been quiet for a while, been head down getting my app out and launched on the apple app store. An incredibly fun learning experience, using Codex, Claude (Code, design), Supabase, Resend, Sentry & Railway. Looking forward to catching up with everything people have been building If you're in the UK I'd appreciate any feedback on Family Activity Finder 😀 Which you can get from the app store HERE

ARK has officially launched (for BwL members only). I used to have to go between loads of terminals, claude and chrome... I honestly had no idea which projects were half done, where they were running, even if they were still running. But now I can manage me entire crew of AI Agents and run my apps and workflows from one place. ARK – your AI OS As a member you get access for free in the skool community, check it out, give it a test and let me know what you think. It's early days so we'll be continually developing it but I wanted you to have access to improve your lives from day 1.

Three different hires. Three failed deliveries. Each time he went through the same loop: Post → Interview → Trust → Disappoint → Restart. When we spoke, he wasn't skeptical of offshore talent. He was skeptical of everything. We started with a 1-week paid trial, $500. His engineer was matched within 48 hours from our pre-vetted pool. By day 5, the engineer had delivered more than all three freelancers combined. He's now on month 4. Paying $2,000/month. Saving over $8,000/month compared to a local hire. And he hasn't touched a freelancer platform since. The model works. The key is dedicated attention , not shared capacity. DM me 'TRIAL' if you want to see if I can find you the right fit.

I built this system for a locksmith company that needed a better way to handle incoming emergency calls and assign jobs to technicians automatically. Here’s what the system does: • AI answers incoming calls • Collects customer details (name, address, issue, phone number) • Creates a job record in the database • Sends the job to technicians one by one • Includes Accept / Reject buttons inside the email • Waits for a response • If ignored → automatically escalates to the next technician • Stops immediately once someone accepts The main challenge was building the loop logic in n8n so it doesn’t notify everyone at once, and making sure the workflow instantly stops once the job status changes to “accepted.” Result: Replaces manual dispatching, prevents double assignments, reduces missed calls, and ensures technicians are assigned faster without a human coordinating everything. I recorded a Loom walkthrough showing: – A live AI call test – The n8n workflow logic – How accept/reject works – How the escalation system is structured If anyone’s curious about the backend setup, here’s the full breakdown: https://youtu.be/fG83tKiWcgA Would love to hear how you’d improve the routing or escalation logic.

A lot of people talk about “doing outbound consistently,” but what usually breaks isn’t effort it’s friction. Recently, I built a LinkedIn outreach system to remove that friction completely. What the system does: - Scrapes targeted LinkedIn leads - Researches each profile - Writes a personalized connection message per lead - Sends the connection request - Automatically sends the 1st and 2nd follow-up What this removes from the process: - Searching and opening profiles - Copy-pasting profile data - Writing messages one by one - Manually remembering and sending follow-ups Realistic time impact:~20 minutes saved per lead. At ~30 leads/week → ~10 hours saved every week. The bigger outcome: Outbound runs in the background. Messages stay personalized.Follow-ups never fall through. If you’re curious and want to see the exact workflow or explore setting something similar up for yourself, feel free to DM me and we can walk through it on a quick call.