Flutu began in São Paulo as a music and audio studio. Over time, the work moved deeper into games, technical implementation and external development, while the company itself became more distributed.
Flutu started from a simple idea: bring together people with different musical and audio backgrounds, give them enough structure to collaborate well and let the work move between styles rather than forcing one fixed creative identity onto every project.
That idea began in São Paulo and gradually changed shape as the studio changed. Music production led into game audio. Game audio led into implementation, production systems and longer relationships with development teams. The company became less about a room and more about how a group of specialists works together.
The First Stage Was Music and Audio Production
The original studio was built around music production, composition and audio post.
That background still matters because game audio never stopped being musical or editorial. Recording, arrangement, timing, mix, listening and performance all remain useful skills even when the final destination is Unreal, Unity, Wwise or FMOD instead of a record.
The difference is that games added another layer.
Audio now had to react.
A sound needed a trigger. Music needed states. VO needed implementation. The work became interactive.
The Team Grew Around Shared Production Values
As the studio expanded, the important question was not only who was talented.
It was who could collaborate.
Game development exposes weak communication quickly because audio depends on animation, engineering, narrative, design and production. A brilliant asset delivered without context can still create a problem for the project.
So the team needed more than craft.
It needed people who could listen, receive feedback, document decisions and understand that the final judge was the game build.
Rafael Freitas Marked an Important Turning Point
The original story identifies Rafael Freitas as an important part of Flutu’s growth.
Shared experience around music, festivals, concerts and multimedia production widened the company’s perspective and helped strengthen the move toward games.
That transition did not happen by abandoning the earlier music background.
It happened by applying that background to a different production problem.
Games needed music and sound, but they also needed systems, iteration and technical integration.
Game Audio Changed the Operating Model
Once the work moved deeper into games, the production stopped being centered only around finished audio files.
Sound design needed implementation.
Music needed adaptive structures.
VO needed naming, integration and QA.
Clients needed visibility into schedules, deliveries and dependencies.
The work became closer to development.
That shift is one reason the term external development fits the company better today than a simple outsourcing label.
External Development Is More Than Remote Delivery
XDS describes external development as a professional production model where service providers support game studios across disciplines including audio, engineering, art, QA and localization. Its overview is useful context for how specialist teams participate directly in game production.
That definition matches the direction Flutu moved toward.
The relationship is not limited to “send us the brief and receive WAV files later.”
Depending on the project, the work can include direction, sound design, music, VO, technical audio, implementation, mix and QA inside the same production cycle.
Technical Audio Became Part of the Core Work
As projects became more complex, implementation could no longer sit at the edge of the service.
FMOD and Wwise became part of the workflow.
Unreal and Unity became production environments rather than places where another department would eventually put the audio.
That change matters because technical autonomy reduces waiting.
The closer the audio team is to the build, the faster it can hear the real problem and iterate.
Valencia Added Another Production Base
Flutu later established a presence in Valencia, Spain, while continuing to work with a distributed team connected to Brazil.
The move changed geography without changing the original identity of the company.
The studio remained Brazil-founded, while the operation became more international and closer to European game-development markets.
The important part was making sure the company did not become dependent on everyone sitting in the same room.
Distributed Teams Need Stronger Systems
Remote production only works when information survives outside conversation.
That means onboarding, asset tracking, naming, delivery structure, documentation and clear ownership matter more.
A distributed team cannot rely on somebody overhearing the right conversation at the next desk.
Production needs to be visible.
This is one reason Flutu increasingly invested in unified workflows rather than treating process as administrative overhead.
The Company Became More Specialized as It Became Broader
There is a useful contradiction here.
Flutu expanded from music into SFX, VO, technical audio and integration, but the company also became more specialized because all of those disciplines were increasingly focused on games.
The studio was not becoming a general audio company.
It was building more of the game-audio pipeline under one production structure.
That distinction matters.
Breadth is useful when the disciplines still share one specific production context.
A Game Audio Studio Is Also a Production Organization
Game Developer’s profile of IMBA Interactive is a useful editorial reference because it shows an audio studio through its people, responsibilities and production model rather than presenting only a service list. The profile demonstrates how sound design, music and studio operations interact inside a professional game-audio company.
That is the more useful way to understand Flutu too.
The portfolio shows the output.
The production model explains how that output gets made repeatedly across different projects.
The Current Flutu Is an Embedded Audio Partner
Today, the useful description is straightforward.
Flutu can work as an external game-audio department, or as specialist capacity inside an existing internal team.
Sometimes that means owning sound design.
Sometimes technical implementation.
Sometimes music, VO or a larger combination of the pipeline.
The structure changes according to the project.
The goal is consistent: reduce the amount of production friction the client has to carry while keeping audio connected to the game itself.
The Original Idea Is Still There
The tools changed.
The projects changed.
The company moved countries and became more distributed.
But the original idea survived: people with different backgrounds working together, learning from the work that came before them and using that knowledge to build something useful for the next project.
That part did not need a rebrand.
What Is Flutu? Who Are We? preserves another version of the company story, while Game Audio Company vs. Freelancer vs. In-House Team explains where a company like Flutu fits among other production models.
Next Step
If you want to understand Flutu through the work rather than the company history, explore our projects. If you already have a game in production, send us the project context and we can start from the part of the audio pipeline that needs ownership.
