A complete game soundtrack built as one continuous arc — seven escalating levels that share DNA, rise in intensity, and never repeat. Here's how it was scoped, scored, and delivered.
The brief: a side-scrolling indie game with seven distinct levels, each with its own visual world, but all part of one continuous narrative. The studio wanted music that felt like progression — Level 1 should hint at what's coming in Level 7, not feel like a separate track.
The constraints:
Anyone can write seven loops. The hard part is making seven loops that belong together — that share a motif so subtle the player doesn't consciously notice it but feels the cohesion. That's what separates a soundtrack from a playlist.
Each track below is the actual delivered loop. Played in order, they tell the story of the score the way the player experiences it.
Light, bouncy, melodic — the player's first contact with the world. Plants the central motif quietly so the brain locks onto it without realizing.
Same DNA, more rhythmic drive. The player has the mechanics down, the score reflects it.
Shifts to a minor variation of the central motif. First hint that the world is more dangerous than it looked.
Texture-led. Pads and ambient layers replace clear melody. The player should feel slightly lost.
The motif returns, now in a tense rhythmic cell. Driving but not yet at full power.
Almost the boss theme. Frantic, dense, unresolved. The player should feel the inevitability of the final encounter.
Full deployment of the motif at maximum intensity. Resolves the harmonic question that's been hanging since Level 1.
Music is only useful if it's actually integrable. Each track was delivered with the assets a real game developer needs:
WAV 24-bit/48kHz + MP3 320 kbps
Pre-trimmed loop points, sample-accurate
Drums, bass, leads, pads — for engine layering
For future remixes or adaptive cues
Sync + WFH option, signed PDF
U.S. Copyright Office submission for premium tier
Week 1. Discovery call, brief lock, motif sketches. Three 30-second sketches for the central motif sent on day three; client picked one.
Week 2. Full-length tracks for Levels 1, 4, and 7 delivered first — the anchors of the arc. Levels 2, 3, 5, 6 then composed to bridge between them. Two rounds of revisions per track included.
Week 3. Stem export, loop-point engineering, license docs, copyright registration. Final delivery with a written authorship statement covering production methodology and rights chain.
Anchoring the arc with Levels 1, 4, and 7 first — instead of writing in order — meant every middle track had a destination. Composers usually drift. Anchoring kills drift.