A full-catalogue music streaming app costs roughly $180,000 to $400,000 to build. That is the number every pricing guide gives you, and it is the least important one in this article.
The number that decides whether you have a business is what is left of each subscription after the rights holders have been paid. On a $9.99 subscription, that figure is about one dollar.
This guide covers both: what the build costs by type of app, the four licences you need before you can legally stream a single song, and the unit economics that nobody publishes because they are uncomfortable.
What the build actually costs
Build cost tracks catalogue size, offline playback, recommendation complexity and how many platforms you ship on.

A few notes on those tiers.
The streaming engine itself — adaptive bitrate, offline caching, gapless playback, DRM — is typically $12,000 to $30,000 of the total. A recommendation engine that does more than sort by genre adds $10,000 to $35,000.
Infrastructure scales with listening, not with users. A music app with 100,000 active listeners can run $5,000 to $20,000 a month in delivery costs alone, because audio streaming is bandwidth-heavy and people listen for hours.
The four licences you need before you stream anything
This is where most music app projects die, and it has nothing to do with engineering.
A recorded song is two separate copyrights: the composition (the song as written) and the master (the specific recording). You need permission for both, and in most cases that means four distinct clearances.

Only the first has a published price. In the United States, the Copyright Royalty Board sets the statutory mechanical rate, and under the Phonorecords IV determination the all-in rate for subscription services is 15.3% of service provider revenue in 2026, rising to 15.35% in 2027.
There is a detail in that determination worth knowing: the all-in royalty is the greater of that revenue percentage or a calculation based on what you pay the labels. You cannot reduce your publishing bill by negotiating harder with the labels, because the floor moves with it.
The master use licence is the expensive one, and there is no statutory rate at all. You negotiate directly with labels or distributors, and at major-label scale that means advances and minimum guarantees that run well into six figures before a single subscriber signs up.
Where every $9.99 actually goes
Now the part that matters. Here is a $9.99 monthly subscription, taken apart.

Three things to pull out of that.
Rights holders take about 70%. That is not a pessimistic assumption — it is roughly what Spotify discloses paying out. Publishing is the smaller share at the CRB's 15.3%; the recording side is the bulk of it.
The app stores take another 15%. That assumes you qualify for Apple's and Google's small-business rate. At the standard 30%, your remaining dollar becomes a loss on every subscriber.
What is left is about $1.02 — roughly a 10% gross margin, before you have paid a single salary, bought a single advert, or repaid a penny of the build.
The payback problem
A 10% margin is survivable if subscribers stay long enough and cost little to acquire. Neither is true in consumer music apps.

At roughly $1.02 of gross profit per subscriber per month, a subscriber who stays twenty months generates about $20.40 in total. Typical acquisition costs for a consumer subscription app run $25 to $50.
That is the whole problem in one line: you lose money on every subscriber you acquire, and you lose it faster the better your marketing works.
It also means the build cost barely matters. A $200,000 platform needs roughly 196,000 subscriber-months just to repay itself from gross profit, and that is before acquisition costs, salaries or infrastructure. At 10,000 subscribers that is a little over nineteen months of everything going perfectly.
The catalogue trap
Almost every founder who has read this far reaches the same conclusion: skip the major labels, build the catalogue from independent and unsigned artists, avoid the advances entirely. It is a reasonable instinct and it is usually wrong, for a reason that has nothing to do with licensing.
The problem is discovery, not rights. People open a music app and search for something they already know. When the first three searches return nothing, they stop opening the app. An independent catalogue does not fail because it is small; it fails because it does not contain the song someone had in their head.
That has two honest implications.
First, if your product's value depends on users finding specific recordings, you need those recordings, which means label deals, which means the economics above apply in full. There is no clever route around it.
Second, and more useful: the music apps that succeed with independent catalogues are the ones where nobody arrives with a specific song in mind. A focus-music app, a yoga studio soundtrack, a label's own artist app, a genre community for people who want to discover rather than retrieve. In those products the catalogue is the point, not a substitute for one.
If you are planning to start independent and add majors later, model the business at both stages before you build. Products designed around discovery rarely survive being retrofitted into products designed around retrieval, and the switch usually means rebuilding the recommendation layer, the search experience and the pricing.
So when does a music app actually work?
It works when you change the royalty equation rather than trying to out-execute it. Every viable music app model does one of three things: avoids per-stream royalties, owns the rights, or sells to a market that pays more.

Two of those deserve expanding, because they are where most of our enquiries actually land.
Licence-free audio — sleep, meditation, focus, white noise, guided breathing — carries no per-stream royalty at all, because you commission or own the audio outright. The same $9.99 subscription that leaves you $1.02 in music leaves you $7 or more here. The build is cheaper too, because you need neither a vast catalogue nor rights management.
Podcast and spoken-word apps work for the same structural reason: speech does not attract mechanical royalties. That is why podcast platforms have economics music platforms can only envy, and why a podcast app at $40,000 to $90,000 can be a real business where a music app at four times the price is not.
How to price your project properly
Before you ask any agency for a quote, answer these. They determine the number far more than feature lists do.
- Whose music is it? Your own catalogue, a licensed one, or commissioned audio? This single answer moves the business case more than everything else combined.
- Which territories? Licensing is country by country. A US-only launch is a fundamentally different project from a global one.
- Subscription, ad-supported or free? Ad-supported royalties are calculated differently and generally harder to make work at small scale.
- How many tracks, and from how many rights holders? Ten thousand tracks from three labels is a negotiation. Ten million from thousands is a department.
- Do you need offline playback? It requires DRM and complicates both the engineering and the licence terms.
- Web, iOS, Android, or all three? Selling outside the app stores avoids the 15–30% commission, but costs you conversion.
And ask every agency one more question: what will my royalty and infrastructure costs be per thousand subscribers? If they cannot answer, they have quoted you a build without understanding the business it is meant to support.
Working with Duple IT Solutions
Duple IT Solutions builds custom mobile and streaming software for clients across the US, UK, Canada and Australia. On audio projects we start with the rights position rather than the feature list, because the licence structure determines the architecture, the pricing model and whether the thing can make money at all.
If you are weighing up a music or audio app, we will model the unit economics with you before anyone writes code — including telling you when a licence-free or spoken-word model would make a far better business than the one you came in asking for.
Get a costed music app scope →
Frequently Asked Questions
Frequently Asked Questions
An MVP with a single use case runs $25,000 to $60,000. A niche or licence-free audio app is $45,000 to $95,000, a multi-feature music app $80,000 to $180,000, and a full-catalogue Spotify-style platform $180,000 to $400,000 or more. Those are build costs only and exclude licensing entirely.
In the US, the statutory publishing rate is 15.3% of revenue in 2026 under the Copyright Royalty Board's Phonorecords IV determination. Master recording licences are negotiated separately with labels and have no fixed rate, often requiring six-figure advances. In total, expect roughly 70% of revenue to go to rights holders.
On a general catalogue, almost certainly not. Spotify reported a record 33.4% gross margin in 2026 at 300 million subscribers, and a new entrant pays the same royalties with none of the scale or negotiating leverage. Startups succeed in audio by picking models that avoid per-stream royalties, not by competing on catalogue.
Slightly cheaper to build, at roughly $40,000 to $90,000, but dramatically cheaper to run. Spoken-word content does not attract mechanical royalties, so the single largest cost line in a music app disappears entirely.
Eight to fourteen weeks for an MVP, three to five months for a niche or podcast app, five to nine months for a multi-feature music app, and nine to sixteen months for a full-catalogue platform. Licensing negotiations usually run longer than the engineering.
Royalties as a percentage of revenue, content delivery that scales with listening hours (potentially $5,000 to $20,000 a month at 100,000 active listeners), app store commission, and maintenance at 15% to 20% of build cost per year.
Need help with this?
We help businesses implement what we write about. Book a free call to discuss your specific situation.



