EN
Back to the archive

The archive · Business Models · Product decision · 2015–2016

SubmitHub turns music-blog submission spam into a paid two-sided marketplace

Artists pay a small fee per submission and curators earn most of it for real feedback — reaching $46k a month within 10 months.

SubmitHub

The ideaMonetize the spam: charge artists a small fee per submission and pay curators most of it for listening, turning an unsolicited-track flood into a filtered marketplace.incremental

What it had to solve

Jason Grishkoff ran Indie Shuffle, an indie-music blog — and like every curator he was flooded with unsolicited tracks, most of which could never realistically be heard. His solo-built answer, SubmitHub, made that flood itself the business: a two-sided marketplace where musicians pay to pitch curators and curators earn money for giving real feedback. The Indie Hackers interview, shared on Hacker News on 16 October 2016, described a $46k/month SaaS built within 10 months.

How it works

Music blogs in the mid-2010s ran on unsolicited emails: artists could send a track to a hundred curators at near-zero cost, and curators could not realistically listen to all of it, so most pitches were never heard. Jason Grishkoff knew the problem from the inside — he ran Indie Shuffle, an indie-music blog — and his answer, SubmitHub, monetized the flood instead of fighting it.

SubmitHub was a two-sided marketplace: musicians paid a small fee to submit a track to a curator, and the curator kept most of that fee for listening and giving feedback. The platform's directory let artists filter blogs by genre and sort them by audience size, payments ran through Braintree with a $5 minimum transaction, and the pricing logic was explicit — a fee large enough to stop shotgun submissions, small enough that modest artists could still afford to pitch.

For the curators, the model changed what their blogs were for: Grishkoff said most of them earned their first mentionable revenue from SubmitHub, and commenters called it a 'win/win' design pattern for bootstrapping revenue onto sites and communities that had never earned before. The open question the launch discussion raised was whether paid placement could slide into payola — a risk the founder answered by pointing at feedback obligations and small, flat fees rather than per-reach pricing.

The interview was posted on Indie Hackers and reached Hacker News on 16 October 2016 under the story of a solo founder who built a $46k/month SaaS within 10 months; the thread scored 517 points and 121 comments, with Grishkoff fielding questions on everything from curation to transaction fees. The idea stands because it took the two sides' most broken interaction — spam in, spam ignored — and gave both a reason to treat every contact as valuable.

Why it lands

  • A paid submission reverses incentives: artists send only their best few pitches, and curators are paid to hear them, so every contact has value on both sides.
  • Curators keeping most of the fee gave small blogs their first real revenue from running their sites, turning the people who were drowning in spam into advocates for the platform.
  • The founder ran the demand side of the market himself, so the product was built by someone who lived the spam problem and knew which trade-offs curators would accept.
  • A flat fee large enough to deter shotgun blasts but small enough for modest artists kept the filter honest — cheap enough to try, costly enough to make every submission count.

What it did

The interview, shared on Hacker News as the story of a solo founder who built a $46k/month SaaS in 10 months, drew 517 points and 121 comments on 16 October 2016, with the founder answering questions in person. Commenters called the design a 'win/win' pattern for bootstrapping revenue onto sites that had never earned before, while others debated whether paid submissions could drift into payola.

Write-upThe Indie Hackers interview with Jason Grishkoff

What you can take

Price the noise: a small submission fee turns spam into a filter and pays the people drowning in it — the party that was being ignored starts earning from attention.

Since then

The material records no later company milestones — what survives is the October 2016 launch exchange and an interview page that stayed live for years. Within the thread the founder said he was rebuilding the iOS and Android apps from scratch in React Native and did all the technical development himself, keeping the service's largest cost at zero. The design pattern the discussion preserved — charging a small fee to fix an attention market — outlived the launch itself.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe the brief you are staring at, and see who has been given the same problem.

Free account · 3 free questions · no card

Related cases