Hey everyone! 🙏 I could really use some guidance and I'd be super grateful for any tips. So here's my story: I'm pretty early in my AI journey, still learning a lot, but I went to a 3-day seminar, got talking to people, and mentioned I build AI automation and software. One of them turned out to be the CEO of a big distribution company. I built her a custom inbox-assistant demo for her business and she absolutely loved it. Now I've got a call coming up to talk price and how we move forward, and honestly I'm a bit nervous because it's my first real client and she's a CEO of a serious company. She knows I'm early in this, which helps, but I still want to do it properly. Her situation: she gets 200 to 300 emails a day in Outlook (Microsoft 365). She wants the AI to sort and prioritize her inbox, write drafts in her tone (English, Dutch, French), and give her a daily brief. The company is fully Microsoft, so it'll need their IT to approve the security side. I'd love any guidance on a few things: 1. Best way to connect securely to Outlook/Microsoft 365? Microsoft Graph directly, or a provider like Nylas/Unipile? Want it to pass their IT review. 2. How would you price something like this for a real company (setup + monthly)? 3. Anything to watch out for when working with a Microsoft company that has IT security checks? 4. Any tips for keeping the AI draft-only so nothing sends without her approval? I've built the demo and even put together a proposal, just want to make sure I deliver this well. Thank you so much in advance, this community is awesome! 🙏

I have been learning a lot from this community, so I wanted to give back a little if you are editing your site manually at hostinger.com, then you can automate it using Claude or any other harness. Here's the setup: - Keep your site as plain files (HTML/CSS/JS). - Grab your FTP details from Hostinger (hPanel → Files → FTP Accounts). - Add a small deploy script (Node.js + the basic-ftp package), with your details in a .env file. Just ask Claude to write one for you or i can share mine if needed. - Publishing then becomes one command: npm run deploy — it uploads everything for you. - Your .env file just holds your FTP details, for example: FTP_HOST=145.14.xx.xx # or ftp.yourdomain.com (from hPanel) FTP_USER=u123456789 FTP_PASSWORD=your-ftp-password FTP_REMOTE_ROOT=/domains/yourdomain.com/public_html FTP_SECURE=false (Keep .env private — don't share it or commit it to a public repo.) That's it — edit your files, run one command, and your changes are live. this idea will work for any other hosting provider too just need to find the proper locations and creds. hope it helps.

Most people think the biggest mistake in AI is not using it. I disagree. The biggest mistake is using AI without changing the way you think and work. Many people ask AI to do more. Very few ask: What process should I redesign? What task should disappear completely? What decision can be improved with better information? AI is not just a tool for faster work. It's an opportunity to rethink how work gets done in the first place. So here's my question for the community: 👉 What is one process in your work or life that should no longer exist in its current form because AI can do it better? Not "faster." Better. I'm curious to see what everyone comes up with. 👇

Everyone is talking about agent loops and loop engineering right now, but most of the advice assumes you are a hardcore coder running fleets of agents around the clock. In this video I break down what an agent loop actually is (reason, act, observe, repeat), why the verification step matters more than the architecture, and how to think about a "done" criteria that your agent can actually check. I walk through a few real loops I ran, including thumbnail scoring, a three.js plane, and an Abbey Road recreation, and explain why loops are about getting you closer on the first try, not perfect output. If you have been feeling behind because you are not running five agents at once, this one is for you.

Had my first client meeting today since starting the agency. And it came from exactly where I expected it to. Not a cold email. Not an ad. Just a conversation with someone already in my network. I’d known him for a little while. Called him. Had a chat. And he invited me in. He built everything on word of mouth. No ads, no portals. Just reputation and referrals. Good guy. Knows his stuff. But he turned down a block of flats last year because he didn’t have the manpower to take it on without dropping his standards. That hit me. Because that’s not a staffing problem. That’s a systems problem. We sat down and went through his business properly. Found three areas where he was quietly losing money and reputation without even realising it. None of them were obvious. All of them were fixable. For a word of mouth business those aren’t small issues. Your reputation is your pipeline. One bad experience and the referral stops. I’m not a tech person trying to sell property businesses software. I’m a property person who knows where the gaps are because I’ve worked in them. That’s a different conversation entirely. He said call me Wednesday. So Wednesday it is.