Last week I hosted a coffee hour in the morning European time. Since many of you are asleep at that time, I’m planning to host another coffee hour later in the day. I’d like to know if you’d be able to join if I schedule it around 9 p.m. Central European Time. We can talk about Weavy, general AI topics, or anything else on your mind—it’s a relaxed, open vibe. I’d really appreciate it if you can have your cameras on during the session; it’s all about getting to know each other.

This week I worked on a hybrid shoot for a production house. We started in AI. Setting, lighting, mood, composition. All figured out before anyone picked up a camera. The photographer used that as direct input for his light setup. The result? No driving to eight different locations. No guessing on set. One studio day. Done. A real photographer, real images, but AI did the prep work. Faster, cheaper, and the photographer walked in knowing exactly what he was going for. That's what hybrid looks like to me. Now your turn. Share what you've been working on this week. Finished result, first setup, random node, whatever. Just drop it below. 👇

People from Oregon to Serbia, 2AM timezones, cameras on, real conversations. That felt good. I walked through the rim workflow live and got some great questions along the way. Here are a few things that came up that I think are worth sharing: Always label your nodes and sources. Once you start copy-pasting images into a workflow you lose track fast. Sticky notes are your friend. Name everything. Test cheap, ship quality. I ran the whole workflow on a lower-res model first. Faster, cheaper, same logic. Once the workflow is locked, you upgrade the model. Not before. Routers keep your canvas readable. One input, multiple destinations. It sounds basic but it changes how clean your workflow looks. And a clean workflow is a workflow you actually understand three weeks later. Upscaling is harder than it looks. If you upscale a small panel image without feeding the original product references back in, the model will guess. And it will guess wrong. Feed it context, always. The workflow is the product. One of the attendees immediately saw a use case for second-hand car dealers in Serbia. That's exactly the point. You build it once, it works for a client forever. The recording is attached. Fair warning: I did not record it fullscreen. (I know.) So I will re-record the workflow properly and add it to the classroom later. Full screen this time, I promise. Thanks for showing up. Let me know what you think in the comments! Workflow: https://app.weavy.ai/flow/QIOqmzgXl2hV09GD54VWA3

You may have seen this workflow floating around. Lighthouse AI Academy — where I studied myself — featured my approach as a case study. But what I really want to share is the thinking behind it, because it's directly applicable in Weavy. I come from photography and film production. That's exactly how I approached this — not as an AI experiment, but as a shoot. The core of my approach: - Start with a production question, not an AI experiment - Lock everything upfront: face, lighting, styling, camera feel - Build one blueprint image that defines the entire world - After that, the only variable is the pose — just like a real shoot with models - AI only becomes powerful when you treat it like a production studio The full article walks through how I built this step by step in Weavy. Read it if you want to get inspired by a concrete, repeatable way of working. https://www.linkedin.com/pulse/locked-studio-how-jamy-built-brand-controlled-production-8i62f/