Sonaris for record labels
Releases as projects, masters and artwork with version history, a store for vinyl, digital and merch, and fans, press and artists on one CRM. Launch week runs on one flow instead of twelve logins.
- Every release as a project1 / 14Projects
- Masters, press kits and a room per release6 / 14FilesFolioCanvasChatProfiles
- A store, fans and an A&R pipeline11 / 14CommerceSitesPaymentsCRMForms
- Launch week on one trigger14 / 14FlowsMessagesChecklists
An illustrative workspace. The business, people and figures are fictional.
Every release as a project
Singles, EPs and LPs each start from their own template, with phases for pre-release, announce, launch week and post-release. The timeline view shows the whole release schedule, and saved lenses cut it to this quarter or one artist.
- Board, list and timeline views with saved lenses
- Templates with phases, tasks and owners
- Phases that can run a flow when they advance
Masters, press kits and a room per release
Masters and artwork keep their version history in the release's folder. The press kit and one-sheet are Folio pages, the campaign map is a canvas tab, and the artist and their manager join the release's chat room as guests.
- Versioned files with previews and expiring share links
- Folio pages for press kits, one-sheets and the label handbook
- Campaign maps on a canvas next to the tasks
- Artists see their own release and nothing else
A store, the fans who use it and an A&R pipeline
Vinyl, CD and merch are products with variants and stock, and downloads deliver themselves. The site has artist bios, audio and the storefront in one place. Every buyer, press contact and artist is one CRM record, and the demo form feeds an A&R pipeline.
- Products, variants, stock and digital delivery
- Artist bios, audio, downloads and a storefront from the catalog
- Segments such as “bought the last LP”, with newsletters and campaigns
- Demo submissions that arrive as a contact and a deal
£28
£12
£8
Launch week on one trigger
When a release advances to launch week, one flow publishes the store page, emails the fans who bought the last record and assigns the release-day checklist. Orders deliver downloads and tag buyers, demos land in the A&R pipeline, and shared inboxes for orders and press keep every thread on the contact.
- One trigger, as many actions across modules as you need
- Shared inboxes, with tickets and SLAs for order queries
- A release-day checklist the whole team works from
- Trigger · ProjectsPhase advanced to Launch weekwhen
- Action · SitesPublish the store pagethen
- Action · CRMSend to “Bought the last LP”then
- Action · ChecklistsAssign “Release day” to the teamthen
- Action · ChatPost to #night-drivethen
- Trigger · CommerceOrder placedwhen
- ConditionOrder includes a digital productif
- Action · CommerceSend digital downloadthen
- Action · CRMTag contact “buyer-2026”then
- Action · ChatPost to #salesthen
- Trigger · FormsDemo submittedwhen
- Action · CRMCreate a deal in the A&R pipelinethen
- Action · CRMTag contact “demo-2026”then
- Action · ChatPost to #a-and-rthen
Artists, fans, press and stock on one record
A fan who bought the last LP, emailed about a parcel and came to the launch show is one contact with all of it on it. The release they bought sits on the same database as the masters, the campaign and the money.
- ProjectsNight Drive moved to Launch week
- SitesStore page published
- CRMCampaign to 2,140 fans
- CommerceOrder #1042 · Maya Okafor
- MessagesFour review copies requested
- FormsDemo from Lune Harbour
- ChecklistsRelease day 12/12
Start with one module. Add the rest as you grow.
Every module works with every other from the day you switch it on, and your data exports whenever you want.