Carl Fairclough
Factory began as a lightweight way to record and share musical taste, testing whether that history could become portable user-owned data.

Could musical taste become useful, portable data?

Factory paired a deliberately small contribution loop with a growing catalogue, giving people a record of taste they could build over time.

Users
≈3,000

Across web, iOS, and Android

Catalogue
207,000

Tracks available to discover and review

Artists
22,000

Represented across the catalogue

  1. 1Discover
  2. 2Listen in Spotify
  3. 3Review a track
  4. 4Build a portable history

Founder-reported product metrics · 2024–2025. Catalogue totals describe the product at its later reported scale.

Factory combined a small contribution loop with a catalogue large enough to turn individual reviews into a useful record of taste.
The home experience made discovery and personal taste visible together, with listening handed off to Spotify rather than reproduced inside Factory.
The first direction leaned heavily on the brand. I moved towards a quieter interface that made logging faster and let people’s music remain the focus.
The core loop was deliberately small: choose a track, add a short review and make it available to friends.
The product connected discovery, logging, sharing and a portable personal record without turning recommendations into an engagement feed. Search, loading, empty states and data controls were treated as part of that core loop—not secondary polish.

Factory visual identity applied to social and editorial content

The visual identity supported social and editorial expression while the product interface became quieter and more focused on people’s music.

Could the core behaviour work before native distribution?

The web product tested the hardest assumption first: whether people would repeatedly contribute a short record of what they were listening to.

Reviews
10,000+

Contributed before the native launch

Time to milestone
6 months

From the beginning of the web product

Distribution
Web

The core behaviour preceded iOS and Android

  1. 1Invite people
  2. 2Discover a track
  3. 3Write a review
  4. 410,000+ reviews

Founder-reported product metric · 2024–2025. This milestone was reached before the iOS and Android applications launched.

Factory passed 10,000 reviews within six months, proving the core contribution behaviour before the native applications launched.

Would native distribution accelerate adoption?

With the contribution loop established on the web, the native launch tested whether easier access through iOS and Android could expand the audience.

Before native apps
2,000

Users on the web product

30 days after launch
≈3,000

Users across web, iOS, and Android

User growth
+50%

Within 30 days of the native launch

  1. 1Web baseline
  2. 2Native launch
  3. 3iOS and Android
  4. 430-day measure

Founder-reported product metric · 2024–2025. The comparison uses the reported user counts before launch and 30 days later, not an inferred time series.

After the iOS and Android launch, the user base grew from 2,000 to approximately 3,000 within 30 days.