All Posts

• From AI User to AI Builder. My Experience with the AOAI 7 Day Challenge

  7/11/2026 · Artificial Intelligence, AI Workflows, Claude Code, System Stacking, Business Automation, No-Code AI, AI for Business, Productivity, Digital Transformation

  A few weeks ago, I joined the AOAI Masterclass. Like many people, I started by using AI for writing, brainstorming, research, and content creation. But the Masterclass helped me take the next step. I learned how to build my own AI systems and business workflows using Claude Code. The biggest lesson? The real bottleneck isn't AI. It's how we design our systems and processes. Once you understand System Stacking, you stop asking AI to complete isolated tasks. Instead, you build repeatable workflows that save time, improve quality, and scale your business. If you're ready to move beyond prompting and start building with AI, I highly recommend the AOAI 7-Day Challenge. What you'll learn ✅ Build a deployable AI workflow through System Stacking. ✅ Discover why getting stuck with AI is usually a human and process problem, not a technology problem. ✅ See practical examples of AI systems stacked across multiple business functions. Bonuses 🎁 Bonus 1. Done-For-You System Stack Builder A super app that automatically builds and deploys your first AI system into your overall workflow. 🎁 Bonus 2. System Bug Hunter Identify and fix issues as your AI workflows become more advanced and powerful. 🎁 Bonus 3. Claude Code Setup for Non-Coders A practical setup guide and cheat sheet to help anyone get started with Claude Code, even without a programming background. Investment 7-Day Challenge: US$99 For anyone serious about using AI to improve the way they work, I believe this is a worthwhile investment. Who is this for? • Entrepreneurs and founders • Consultants and coaches • Content creators • Business professionals • Anyone who wants to build AI-powered systems without needing to become a software developer. I'm already applying these ideas to my own cross-cultural consulting, research, content creation, and business development. It's changing how I design workflows and think about scaling my work. If you've ever thought, "I know how to use AI, but I wish I knew how to build something with it." This challenge is a great place to start. Interested? If you'd like to join the AOAI 7-Day Challenge, send me a direct message. I'm happy to share the registration details, answer questions based on my experience, and provide my referral information if you decide to join. I'm looking forward to seeing more people become AI builders, not just AI users. Grace

• Five Lessons From My Last Consulting Project

  7/6/2026 · cross-cultural consulting, China-Europe business, Chinese clients, client experience, trust building, meaning translation, service delivery, lessons learned, Netherlands, consulting insights

  The port printed on my clients' tickets wasn't the port where the ship was docked. Nobody had told the ground team. I found out hours before a group of Chinese clients was due to board a river cruise in the Netherlands. The change had been made weeks earlier. The notification existed. It had simply stopped somewhere in the chain — head office, agency, ground level — before reaching the one person standing on the quay. By 17:30, everyone was on board. No delays. No complaints. From the client's side, nothing had happened at all. That was the point. I've just written up five lessons from a month of ground-level work with Chinese client groups — arrivals, handovers, and that boarding day. The short version: Information rarely fails at the source. It fails in the chain. The genuine product is certainty, not logistics. The exhaustion is cognitive, not physical. And the one I keep coming back to: trust is built in operational moments, not in proposals. A Chinese client who watches you solve a problem calmly at 15:45 on a quay will believe your strategic advice in a way no credentials page can achieve. Frameworks describe. Fieldwork convinces. Full post on the blog — link in the comments. If your organisation sits between Chinese and European ways of working and something keeps quietly going wrong in the handover, that gap has a structure. It can be found and named. Comment CLARITY or send me a DM and I'll show you where to look.

• How I Built This Site in a Weekend

  7/3/2026 · build, tech

  For years I published on platforms I didn't own — Substack, LinkedIn, other people's spaces. It works, until it doesn't. The algorithm shifts, the rules change, and the audience I thought was mine was never really mine at all. So I decided to build my own corner of the web: somewhere I control the content, the data, and the domain. This site is the result — and I built it in a weekend, with AI, without being a developer. Here's the honest walkthrough. The stack, in plain terms Three pieces, nothing exotic: • A front end — the pages you're reading — built with Next.js. • A database, where posts and leads live, on Supabase. • Hosting on Vercel, which redeploys the site automatically every time a change is saved. I didn't hand-write most of this. I worked with Claude Code: describing what I wanted, reviewing what it built, and testing each piece before moving on. How it came together I built it in stages, not all at once: 1. First, the writing — posts I can create, edit, and publish, and a public feed anyone can read. The core had to work before anything clever went on top. 2. Then the point of it all: leads. A contact form that saves each visitor's message straight into my own database, and an admin view where I can see every lead and log each conversation. This is what rented platforms never gave me — the relationship, captured and mine. 3. Then locking it down: a login so only I can reach the admin side, and security rules so visitors can submit the form but can't read anyone else's data. 4. Finally, polish — tags to filter posts, filtering leads by status, proper share cards when a link is posted to LinkedIn, and my own domain. The parts that weren't smooth It wasn't all clean, and the lesson I keep relearning showed up again: the hard part isn't the technology, it's the design and the details. When I added the security rules, they were a touch too strict and quietly broke the contact form — visitors got an error and their messages never saved. It took real debugging to realise the "lock the doors" step had locked a door that needed to stay open to the public. The fix was small once we found it, but it was a good reminder that shipping fast and shipping carefully have to travel together. Connecting my domain was its own small puzzle. I already run buildglobalbridges.com on another service and didn't want to touch it, so this site lives on a subdomain — blog.buildglobalbridges.com — and the two run side by side, neither stepping on the other. What I have now A site I own end to end. I write a post and it's live in seconds. Someone reaches out and their message lands in my own database, where I can track every follow-up. No middleman, no borrowed audience, no platform that can change the rules on me. If you've been meaning to build something of your own and assumed you needed to be a developer — you don't. You need a clear idea of what you want, the patience to test each piece, and a willingness to sit with the messy middle. The tools have caught up; the bottleneck is design, not code. Rented reach is fragile. Owned channels compound. This site is me betting on the second one. Grace