When Ali Al Hamwi, co-founder and CEO of SIFOR, started integrating generative AI into his studio's production pipeline, he planned to stay skeptical. What changed his mind was the amount of time he got back. Building out the dense, prop-heavy worlds for hyper-casual and roguelike titles like Abduct 'Em used to consume weeks of artist briefings and revisions. Using Ludo.ai's Image Generator and 3D Asset Generator on a real production stretch showed him a faster path from concept to game-ready asset.
From concept to mesh without the revision churn
SIFOR's team tested the tools on the UFO, the main character of Abduct 'Em, an isometric sandbox roguelike with dense neon visuals. The Image Generator handled initial concept work, letting the team iterate on silhouettes quickly. The 3D Asset Generator then took the approved concept through to a finished mesh. "We were surprised by everything we could do with the UFO," Al Hamwi said. Environmental props, military hardware, and shipping containers all came out of the same generation ecosystem.
The process locked in a cohesive visual language from the first asset. Once the UFO's look was set, every subsequent prop was generated against the same style reference. Nothing drifted. For a small team juggling multiple projects, this removed a bottleneck that often goes unnoticed until you add up the hours lost to revision cycles.
What the time savings actually bought
Al Hamwi did not end up with less work. The freed-up hours shifted toward decisions that require human judgment - the kind of calls an AI tool cannot make. "What stood out to me wasn't just the speed. It was how much it shortened the gap between having an idea and actually seeing it inside the game," he said. That compression of the idea-to-implementation loop changes how a small studio can experiment, especially when resources are thin.
This experience aligns with broader patterns in generative AI and LLM adoption. The tools are not replacing the creative direction; they are absorbing the repetitive, technical steps that sit between concept and execution. For developers working in AI for IT and development roles, the shift mirrors what version control or game engines did in earlier eras - they become fixtures in the toolkit rather than novelties.
A reshuffling, not a takeover
Al Hamwi rejects the binary framing that AI will either replace developers or fizzle out. "From where I sit running a small studio, I think we're looking at more of a reshuffling," he said. The technology speeds up the grunt work and gives developers more room to focus on creative decisions that round out a good game. But he also cautioned that studios need to define their own line between assistance and handing over creative judgment entirely.
"When you have limited people and limited time, getting some of that time back doesn't just mean producing faster. It gives you more room to think, experiment, and make better creative decisions," Al Hamwi said. His guess is that AI becomes another standard tool, much like version control already is.
Why this matters for IT and development professionals
The SIFOR case is not about AI generating a finished game. It is about a specific, measurable outcome: shortening the asset pipeline so that a small team can iterate faster and reserve human attention for the decisions that shape quality. For developers and IT professionals evaluating where to place AI tools in their own workflows, the takeaway is to look past the hype and measure what the tool gives back in time - then watch where that time gets reinvested. If it flows toward higher-level problem solving rather than just more output, the tool is earning its place.
Your membership also unlocks:
