u/Icy-Walky09

ComfyUI is still the better tool when I’m exploring a look, testing ControlNets, dialing in an IPAdapter workflow, or building something I’ll reuse. But client work is different. Last week, a client changed the art direction at 11pm: same product, but four new compositions, a different background palette, and usable files by 9am.

My Comfy workflow was tuned for the original brief, specific LoRAs, masks, ControlNet settings, upscaling pass, and output logic. Changing the concept meant touching half the graph and rechecking every stage. It was powerful, but it wasn’t fast.

So now I use ComfyUI for R&D and repeatable production pipelines. For last-minute client variants, I use hosted tools where I can generate, iterate, and hand off without rebuilding the machine underneath it.

Anyone else split their workflow this way, or am I committing heresy?

I have stopped looking for the one tool that does everything. now it's: model A for the still because it understands composition, model B for motion because it doesn't melt hands, model C for the upscale.

the annoying part used to be the download/re-upload tax between them. once that's inside one pipeline it stops being annoying and starts being the actual method.

anyone else chaining across models deliberately, or is everyone still picking a favourite and going all in?