The platform is the point. The label is how we proved it works. ESØTËRIC Ones runs on software we wrote, 32 releases and 139 tracks across 47 platforms, accounted for end to end, and that software is the case study.
What we built
- A catalog CMS. Releases, tracks, and the 21 credited artists, modelled properly and editable through an admin that non-engineers actually use.
- An ISRC-matched royalty engine.It ingests messy distributor CSVs from dozens of platforms, matches each line to a track by ISRC, and computes per-track splits and the label’s cut: the math that turns a pile of statements into who is owed what.
- A contracts pipeline. Agreements tracked against the artists and releases they govern, not lost in a folder.
- A self-serve artist portal.Artists log in to see their own catalog and earnings, gated to their own data, nobody else’s.
- A finance dashboard. The whole picture in one place: roughly $238 in royalties accounted for across 26 months, reconciled to the distributor data it came from.
Why it matters
This is financial data engineering and gated, multi-role apps off a single database: the unglamorous plumbing real software needs. Ingesting other people’s inconsistent data, matching it, doing the split math, and showing each person only what they should see is hard to fake and easy to get wrong. It is the same shape of work behind any system that handles money and roles.
It is also a product in waiting. A small label or an independent creator needs exactly this back office and almost never has it. The system we built for one label is a system Ebenworks can offer to others.