Martin Garrix
Presave

A Spotify-first subscription flow for label and artist releases

2018Spotify Web APIPresave

Martin Garrix / STMPD RCRD Presave is a platform I built that lets fans subscribe to a Spotify artist (e.g., Martin Garrix) or to the entire record label. When new music drops, users automatically get the “presave” experience—without having to hunt for releases manually every time.

This was way before Spotify implemented this natively in March 2023; one could say we (partly) initiated it with this `proof of concept`.

The challenge

Music fans want to support releases early, but the presave flow is often fragmented or not available at all: multiple links, inconsistent experiences, and lots of manual steps. The goal was to make presaving feel effortless—one subscription that keeps working for future releases.

What I worked on

Artist + label subscriptions

Instead of one-off presave links per release, the platform is built around ongoing subscriptions: follow an artist or the full label, then let the system handle future releases. This turns “presave” into a repeatable relationship rather than a single campaign page.

Spotify integration as the core

The user value depends on Spotify being the source of truth, so the platform is designed around Spotify’s ecosystem: login/authorization, connecting user intent (“I want updates from this artist/label”), and acting when new releases appear.

A reusable campaign engine

Under the hood, this kind of platform needs patterns you can repeat: reliable flows, a consistent UI, and a structure that supports multiple artists and releases without rebuilding everything. The result is a system that scales with campaigns while maintaining a consistent experience.

Also, the more plays a song has in its first 24-48h after release, the better the results are for the artist and record label. It resulted in better overall statistics and a higher ranking, which kept the snowball effect going. And more streams mean more profit.

Tech stack

Spotify Web API
Modular Design
Custom CMS
Scheduled Releases
SASS
JavaScript

Why this work matters

This is a good example of product-minded engineering: turning a one-time marketing interaction into a smooth, repeatable user flow. It also shows how I approach platforms—create a solid foundation first, then scale features without fragmenting the experience.

It also demonstrates how I build systems that are both user-centric and commercially effective: a simple subscription model that keeps working over time, with automation that reduces friction for fans and increases first‑day momentum for releases.

By treating this as a scalable platform (not a one-off landing page), it became possible to run repeated campaigns without rebuilding flows, while keeping the experience consistent and reliable. That combination—product thinking, platform foundations, and clean UX—is the same approach I bring to larger React applications and Design System work today.