Sport99

Racing games for players in every corner of the world.

Sport99 is a global mobile sports-racing game company. Our games launch worldwide in 12 languages, built and run by a team of about a hundred people. This is a look at who we are, how the business runs, and where AI fits in.
A dark sports car drifting along a coastal mountain road at sunset
12
languages our games run in
~100
people on the team
Worldwide
release, for players in every region
$8M
annual cloud and AI investment

The project in brief

A short version of the whole story: where we started, what was in the way, what we are doing about it and what it should deliver.
A globe at night with glowing orange racing routes connecting continents
Context

A global studio with AI already at work

Sport99 builds and runs mobile racing games for players worldwide, in 12 languages, with a team of about a hundred. AI already supports engineering, content, localization and the player experience.
Challenge

It had grown team by team

Long storylines outgrew our tools, spend could not be traced to a game or a language, and back-office jobs competed with live play for the same capacity.
Approach

One shared foundation, rolled out in stages

Every request is routed to the right capability, tagged by game, language and purpose, and checked against one shared library of story and character material. Offline work moves first. Player-facing work moves last.
Outcome

Faster, steadier and easier to account for

Localization in days rather than weeks, in-game characters that start replying within a second, spend traced to the team behind it, and room to add languages and game modes without starting over.

Who we are

A global games company of about a hundred people, building racing games that feel local wherever they are played.
A game studio floor where a small team works on racing game art, with a world map of players on the wall
What we make
Mobile sports-racing games with long-running storylines, characters and live seasons.
Who plays
Players around the world. Every title is released globally rather than market by market.
Languages
12 operating languages, each treated as a first-class experience rather than an afterthought.
Team
About a hundred people across engineering, content, localization, live operations and community.

What the business demands

  • Stories that last for yearsA racing game is more than cars and tracks. Its world, rivals and characters keep growing season after season, and players notice when something feels off.
  • A global audience, all at oncePlayers in every region expect the same quality on day one, in their own language, with humor and references that land locally.
  • A live service that never pausesRaces, events and conversations happen around the clock. Demand peaks sharply around launches and events, and the experience has to hold.

Where AI works in the business

AI is already part of how four areas of the company run, plus the community team. Each one has a different job to do and a different bar to clear.
A smiling pit crew member in an orange and black race suit holding a tablet in a garage
  • Engineering

    Studio tools and build pipeline
    AI sits inside the editor and the build pipeline, helping engineers write, review and understand code. The heaviest jobs are held back for quiet hours, so they never slow down anything players are using.Faster delivery, with no impact on live play
  • Content

    World-building, characters and copy
    Writers draft story, dialogue and event copy with help, and every piece is checked against our own library of world and character material, so style and storyline stay consistent from one season to the next.A consistent world, however fast we publish
  • Localization

    All 12 languages
    A new batch of text is translated into every language at once, then refined with a shared glossary that keeps names, car terms and tone consistent. Native reviewers focus on polish rather than first drafts.Delivery goes from weeks to days
  • Player experience

    In-game characters
    Characters in the game can hold real conversations with players, staying in character and following the storyline. Replies begin within a second, so talking to them feels natural.First word in under one second
  • Community

    Live operations
    The operations team gets a first-pass read on community sentiment and draft proposals for events and responses. People review and decide before anything goes out.Faster, better-informed community decisions

A season, from idea to live play

AI does not live in one department. It shows up at every stage of how a season of the game is made, shipped and run.
A player holding a phone showing a racing game with a car mid-drift
  1. Plan

    Producers and designers
    A season starts as a sketch: new tracks, rivals and events. New ideas are checked against the world we already have, so what comes next fits what came before.
  2. Write

    Writers
    Story, dialogue and event copy are drafted with help, then checked against our own library of world and character material before anyone signs off.
  3. Build

    Engineers
    AI sits inside the editor and the build pipeline. The heaviest jobs wait for quiet hours so nothing players are using slows down.
  4. Localize

    Localization team
    New text goes into all 12 languages at once and is refined against a shared glossary. Native reviewers polish rather than start from nothing.
  5. Launch

    Everyone
    The season ships worldwide, with the same quality in every region on the same day.
  6. Play

    Players and in-game characters
    Characters hold real conversations in character and in line with the storyline. Replies start within a second, and live traffic always comes first.
  7. Listen

    Community and operations
    A first-pass read on community sentiment and draft responses help the team act quickly. People decide. What we learn feeds the next season.

What growth exposed

As AI spread through the company, the problems stopped being about any one tool. They became problems with how the whole thing was run.
Many race cars bunched together on a night starting grid, competing for the same road
  1. 01

    The stories got bigger than our tools

    Long-running storylines and in-game conversations need strong memory, a consistent plot, localization that respects culture, and output we can control. Our setup struggled on all four.
  2. 02

    Every team set things up on its own

    Each group connected to AI separately. Caching, instructions and usage limits were not managed anywhere, and cost showed up as a single total with no split by game, language or purpose.
  3. 03

    Back-office work competed with live play

    Engineering batch jobs and live player conversations drew on the same capacity. At peak times, stability and response speed suffered.
  4. 04

    Little room for the next game

    Regional reach, flexible capacity and workload scheduling could not reliably support new projects that need fast responses and long memory.

One shared foundation

Instead of a collection of separate tools, AI at Sport99 now runs on a single foundation that every team shares. That is what makes it measurable, reusable and easy to extend.
Isometric race circuit where several lanes merge into one main road under a control tower
  1. Teams and products

    Everyone uses the same front door.
    Engineering, content, localization, in-game characters and the community team all connect to one shared entry point instead of building their own.
  2. Routing and scheduling

    Right job, right priority.
    Each request is sent to the capability that suits it. Live player traffic is protected, and heavy back-office work waits for quiet hours.
  3. A shared knowledge base

    One memory for the whole studio.
    Our world, characters and terminology live in one searchable library that every team draws from, so the story stays consistent everywhere.
  4. Metering

    Every call is accounted for.
    Each request is tagged by game, language and purpose, so spending can be traced back to the team and the product that caused it.

How we work with AI

A few commitments that shape every decision, from which jobs we automate to how we release changes.
Gloved hands on a racing steering wheel beside a tablet showing a checklist

People make the decisions

AI drafts, suggests and screens. Writers, engineers and operations teams review and sign off.

Players come first

Live conversations get priority at all times. Background work waits for quiet hours.

The right tool for the job

Routine work uses light capability. Deeper reasoning and review are kept for what truly needs them.

Our world stays ours

Story and character canon lives in our own library, and everything new is checked against it.

Everything is measured

Each request is tagged, so spend and quality can be traced back to a game, a language and a purpose.

Every step can be undone

We roll out in stages, with a way back at each one, and touch player-facing features last.

Where the investment goes

Spend used to be a single number. Now it can be split by game, language and purpose, and each team can see its own share.
Race car cockpit at night with a glowing telemetry dashboard
Annual cloud and AI investment, $8M
Infrastructure$4M
AI usage$4M
Player support runs on an external service and is not part of this.
  • Know who spent what

    Every request carries its game, language and purpose, so the bill can be read the way the business is organized.
  • Match effort to the job

    Routine replies and screening use light capability. Deep reasoning and review are kept for the work that truly needs it.
  • Move heavy work to quiet hours

    Localization and large engineering jobs run off-peak, which frees live capacity when players are most active.
  • Build once, share everywhere

    One managed set of instructions and stored results instead of one per team, so the same work is not paid for twice.

How we will know it works

Success is not a single number. These are the things we will check on, release after release.
A race timing tower and finish line scoreboard at dusk
Localization turnaround
From weeks to days, across all 12 languages.
Character response time
First word within one second, in every conversation.
Live play at peak
Background jobs never slow down anything a player can see.
Cost visibility
Every request traceable to a game, a language and a purpose.
Story consistency
New material is reviewed against world canon before it ships.
Speed to the next thing
A new language or game mode reuses the foundation instead of starting a new project.

How we are rolling it out

We prove the approach on low-risk work first, and only then touch anything a player can see.
A race track leading to a checkered finish gate at sunrise
  1. 01

    Start behind the scenes

    Localization and content productionSet up the shared foundation, then begin with work players never see directly. Translating into 12 languages and drafting story content are easy to check, and easy to fix if something is off.
  2. 02

    Engineering

    Studio tools and build pipelineBring the engineering teams across next, with heavy jobs scheduled for quiet hours.
  3. 03

    Community

    Sentiment review and proposalsGive the operations team a first-pass read and draft proposals, with people confirming every decision.
  4. 04

    In-game characters, last

    Live player conversationsThis is the most sensitive part of the experience, so it moves only after everything else is running smoothly, and it moves gradually, with a way back at every step.

Questions people ask

Short answers to the things that come up most often.
Work behind the scenes is easy to check and easy to fix. In-game conversations are the most sensitive part of the experience, so they move last, gradually, with a way back at every step.