← Archive

Foundation · Deftouch / All Star Games

Live-ops at Deftouch — chart pressure, ratings, and a studio that scaled

Employee five at Deftouch. Real-time multiplayer cricket under chart-day clocks — and a studio that had to grow without losing the delivery muscle that made #1 possible.

Lead outcome

4.4★

RCB store rating under live pressure

Focus

Live OpsMobile GamingStudio Scaling

What I owned

At Deftouch (All Star Games) I grew from Lead QA to Associate PM: test plans → pipelines → end-to-end schedule, hiring, and risk for the cricket run. The scaling work was concrete — helping take the studio from five people to forty-two while keeping release discipline intact under Nazara / RCB chart pressure.

Narrative

Deftouch / All Star Games, Bengaluru, 2018–2022. I started on the QA floor — cohesive test plans, defect loops, documentation engineers would actually read.

As Jr. then Associate PM I owned Jira/Confluence pipelines, costing, sprint ceremonies, hiring, and milestones with chart day attached. Growing 5→42 was not a vanity headcount story: it was capacity planning, role clarity, and refusing to let scale dilute ownership. RCB Star Cricket with Nazara and Royal Challengers Bangalore was the sharpest of those clocks.

Humans of Gaming later profiled that run. I keep it here because enterprise AI programmes fail the same way games fail: unclear ownership, late risk, and teams that confuse motion with shipping.

Quality is a process, never an event

The freelance QA year drilled it; live games proved it under millions of players.

Scale the seat, not the heroics

5→42 only works if rituals and named owners scale with headcount — chart day still does not negotiate.

4.4★

RCB store rating under live pressure

#1

Top Free chart within 48 hours

3.2M

players on titles I helped ship

5 → 42

Deftouch studio scale across my years

Titles from the Deftouch run

Cricket under chart pressure, plus casual and smash titles from the same studio years — store links where the builds still ship.

Next step

Want the confidential layer — names, constraints, steering artefacts? That conversation stays over email.

Email me about this case