Drop your biggest takeaway from this classroom lesson. One sentence is enough. Now the real challenge: this workflow is not about rims. It's about placing any product in any context. A sneaker. A piece of furniture. A bag. A bike. How would you make this work for your own projects? What would you change? Share your workflow or your idea below. 👇

Drop a comment below with your biggest takeaway from this lesson. One sentence is enough. Question: Could you use this in a workflow you're already building?

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

This is my first foray into using Weavy and I am rather enjoying it. I come from an AV background and I did System Design. I've worked with CAD and Visio to create Rack Layouts and signal flow diagrams for both the home and AV cabinets. Anyways, wiring these nodes up was fun for me! I am attaching a link so you can view it. If I took a screenshot it would be ridiculously small. https://app.weavy.ai/flow/8dpyTKjiEmNYStZnuqecCl

The aim here is to stress-test weavy to extract a single image from a storyboard whilst keeping all details exactly the same as they appear in the the smaller grid images. I have played around with using image upscales such as Topaz with limited success. The AI seems to hallucinate and fill in details such as decals on the bike and also the bike itself. After many conversations with LLMs- in case Claude it appears that the best solution is to independently create 9 single high res images. Weavy does not like trying to extract 1 single image from a grid in one sweep- it gets confused and the details are muddled at best. I'm putting this in the community to see if anyone else has come across this issue and their workflows to resolve this.