Opportunities › Music scrobbling aggregation across sources › Proposed app
Tallyrow
One listening history from every music app, server and player you use
- Score
- 41
- confidence 41
- Evidence
- 4
- items on the page
- Rivals
- 6
- named in sources
- First version
- 30 d
- estimate
- Type
- Mobile app
- PWA: installs on iPhone and Android
- Market since
- 2002
- Mature market · AI estimate
ScreensConcept
Mobile app: Music listeners connect sources and check scrobbling on the go; primary use is passive tracking across listening sessions. Sample screens on a phone, in the proposed brand. Their numbers are sample data.
Today
42 plays
- Streaming account26
- Home server13
- Mopidy3
- Duplicates removed4
- Sent to backends42 of 42
About this appAI proposal
Tallyrow is a hosted scrobbling hub. Connect the places you listen, such as streaming accounts and home servers, and it records each play once. It then sends every play to the tracking services you keep, so your history has no gaps when you switch apps.
It is made for listeners who move between streaming and a self-hosted library, and who do not want to run and patch a container just to keep their history whole. Setup is a few sign-ins and a server URL, done from your phone.
Unlike single-service integrations, Tallyrow treats the history as yours. See which source each play came from, spot duplicates and missing days, and replay a batch to a backend that was down.
- Tagline
- Every play counted once, wherever you heard it.
- Voice
- PlainReliableWarm
- Why this name
- Tally is a count and row is a line of entries. Together they suggest one tidy list of everything you played.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Many sources at once
Link streaming accounts and self-hosted servers side by side. Plays from all of them land in one timeline.
No member yet
Send to several backends
Forward every play to more than one tracking service, so you are not tied to a single one.
No member yet
Duplicate guard
Detects the same play reported by two sources, such as a server and a phone app, and keeps one.
No member yet
Gap finder
Flags days with no plays from a source that is usually active, so a broken connection shows up fast.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#12363AInk Teal · primary#F6F1E7Paper · surface#1D2527Charcoal · text#E2692FEmber · accent#6F9A6BMoss · data
Typography
Aa
Tallyrow
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Every play counted once, wherever you heard it.
PricingAI proposal
The material gives no competitor prices. The tiers are a starting point to test, based on the opportunity's freemium and hosted-subscription idea.
Free
Free
- 2 sources
- 1 destination
- 30 days of replay
Plus
$4 a month
- Unlimited sources
- Unlimited destinations
- Full replay and export
- Duplicate guard and gap finder
Would you pay Plus · $4 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Users do not send anything to non-users. Growth comes from search, self-hosting communities and word of mouth among listeners who run home servers.
- Do they become customers?
- Reached people are already the target buyers. Test whether self-hosters will pay for hosting instead of running it themselves.
- First customers
- Hobbyists who run Jellyfin, Plex or Subsonic at home and also use a streaming service, and already keep a tracking account.
- Where to reach them
- Self-hosting forums: Answer setup questions and offer a hosted option for people who do not want to maintain a container.
- Music tracking communities: Share a guide on closing history gaps when switching between apps, with a free signup.
- First milestone
- Fifty free signups with two or more sources linked, and ten converting to paid within 60 days.
Why people already pay for this
- VerifiedGitHub repository gained 1263 stars in 2161 days
- Public claimThe project aggregates music plays from multiple music sources including Spotify, YouTube Music, Deezer, Jellyfin, Plex, Subsonic, and self-hosted Mopidy instances.
- Public claimThe project supports scrobbling to multiple tracking backends including Last.fm, ListenBrainz, and Maloja.
- AI inferenceSelf-hosted music infrastructure (Jellyfin, Subsonic, Mopidy) is part of the ecosystem users operate within.
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Background jobsQueue with scheduled workersPolling sources and retrying sends to backends must run reliably outside web requests.
- This app · Secrets storageEncrypted credential vaultStores streaming tokens and server logins for users, so they must be encrypted at rest.
RisksAI inference
- PlatformStreaming services may limit or change the access that exposes recent plays, which could break sources without notice.
- TechnicalHome servers sit behind private networks, so a hosted service may not reach them without users opening ports or using a tunnel.
- CommercialThe evidence is an open-source project with GitHub stars. Many users may prefer to self-host it free rather than pay for a hosted version.
- DataMatching one play reported by two sources is error-prone and may drop real plays or keep duplicates.
- RegulatoryStoring listening history and third-party tokens creates privacy duties, including deletion and export on request.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.