AI Can Take The Grind Out Of Repetitive Work

One of the fastest ways smaller teams can gain momentum is by removing the work that quietly drains creative energy.

With AI, my team sees the biggest impact in tasks like asset variations, early UI drafts, level balancing suggestions, localization passes, repetitive QA loops and creative hypotheses for UA testing.

For example, AI works best as a first-pass tool, with the team still verifying the results. In asset variation workflows, a team can start with an approved visual direction, use AI to generate several options and then have designers select, adjust and test the strongest versions. For localization, AI can create the first draft, and a human editor checks tone, context and market fit.

Google Cloud’s 2025 research with The Harris Poll found that "90% of game developers [are] already using AI in workflows," and 95% say "AI is reducing repetitive tasks."

Once repetitive load is reduced, more time can go into product problems that actually affect retention, monetization and player experience.

Speed In Mobile Gaming Depends On How Quickly Teams Decide

Many production delays have little to do with execution itself.

They come from hesitation around which mechanic deserves the next test, which economy lever should move first, which LiveOps event deserves priority and which creative should go live tomorrow.

This is where AI becomes deeply practical inside gaming teams. When it comes to summarizing signals from dashboards, surfacing anomalies and proposing next-step hypotheses, AI helps reduce the dead air between decisions.

King’s work on Candy Crush Saga is a good example. The team uses AI inside the level design loop to test and refine levels before changes reach players, reviewing signals such as pass rates, reshuffles and progression patterns.

Fast. Clear. Actionable.

And here’s the real question inside most teams: If three weeks of product signals can be reviewed in minutes, why should key decisions still wait until next sprint?

The same Google Cloud study found that developers are already using AI for "playtesting and balancing (47%), localization and translation (45%), and for code generation and scripting support (44%)."

Roblox offers a useful example of what AI-assisted playtesting can look like in practice. The company recently introduced a playtesting agent beta for Roblox Studio that can test a game against the creator’s original plan, read logs and use the player character as an automated QA tester.

These are exactly the layers where smaller studios can speed up everyday execution without compromising senior creative judgment. For smaller teams, decision speed often matters more than raw production capacity. The faster a team interprets signals, the faster the product learns.

Workflow Design Becomes The Real Competitive Edge

The biggest leap happens when AI is woven into the way the studio actually works.

For mobile teams, this often touches the daily heartbeat of production: QA loops, LiveOps drafts, economy alerts, UA refresh cycles and experiment recommendations.

In January 2025, Wemade Next announced that it was developing "the world’s first AI Boss, 'Asterion,' for MIR5, built with NVIDIA ACE."

An AI boss is not simply a more difficult enemy. In MIR5, Asterion is designed to move beyond fixed scripted behavior "by perceiving the game environment, recording past battles and learning from them." In practice, the boss analyzes player composition and positioning, then "adapts its attack strategies in real time." For developers, the key lesson is to use AI inside clear design limits: The team still defines the character, difficulty range and fairness rules while AI adds more varied and responsive behavior.

That matters for smaller studios because it shows where the industry is heading. AI is already moving from back-office support into the structure of gameplay systems and content behavior itself.

At some point, the advantage stops coming from team size and starts coming from how intelligently the studio compounds learning every single day.

The Studios That Learn Faster Will Ship Faster

The next generation of successful mobile studios may not be the ones with the largest teams. More likely, it will be the teams that use AI in very specific production bottlenecks.

First, a small studio can use OpenClaw as a QA teammate. Instead of asking testers to manually repeat the same flows every sprint, the team can set up AI agents to run through core gameplay loops, check onboarding, identify broken states, flag crashes and summarize issues for the producer.

Second, AI can support LiveOps decision-making. A producer can feed recent performance data into an AI workflow to summarize what changed after an event, which cohorts reacted differently and which economy signals need attention. The team still decides what to change, but AI reduces the time between raw dashboards and the next testable hypothesis.

Third, AI can help with UA creative testing. A small team can turn one approved creative direction into multiple headline, image, video-script and store-page variants, then test them in small batches.

For smaller studios, the point is to remove repetitive friction from QA, LiveOps and creative testing so the team learns faster every week.​

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?