labs@atheron:~/industries/music-film/integrations$ connect --systems --automate

Catalogue feeds

One catalogue record, sent the same way to every distributor.

A catalogue goes out to many distributors and stores, each with its own feed and rules. We keep one record of every title, send it to each in the format it accepts, and join the reports that come back to your royalty and accounting systems.

Start a project See the example projects

// what matters here

What is different in this industry.

One record per title

Titles, credits, codes and dates kept once and sent everywhere from there.

Each distributor's format

Feeds such as DDEX for music and ONIX for books, built to each distributor's published specification.

Corrections that reach everyone

A change goes to every distributor at once, with a log of each delivery.

Reports joined back

Sales and usage reports matched to the same titles, for royalties and the books.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectAPIAIOpen-source model

Catalogue metadata and distribution feeds

Hypothetical. Not a client, not a result.

// The problem

A label's catalogue metadata lives in spreadsheets, and titles, credits, codes and release dates differ between what it sends to each distributor and what appears in the stores.

// What we would build

An integration hub that keeps one catalogue record and sends it to each distributor in the feed format they accept, such as DDEX for music or ONIX for books, with an open-source model that suggests fixes for missing credits, inconsistent names and mismatched codes for your team to approve.

// What is in it

One catalogue record for titles, credits, codes and dates
Feeds to each distributor in the format it accepts, such as DDEX or ONIX
Suggested fixes for credits, names and codes, approved by your team
Changes sent to every distributor at once, with a log of each delivery
A model run on servers you control, so the catalogue stays private

// Stack

Node.js
PostgreSQL
DDEX and ONIX feeds
Open-source model on GPU
DigitalOcean Toronto

// estimate

Build: ≈ US$108,000 to US$165,000, delivered within 22 weeksCAD 153,300 to 234,400
Hosting: ≈ US$4,360 a monthCAD 6,210 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route: Open-source model
Model running cost: ≈ US$4,190 a monthCAD 5,960 a month

Timeline by milestone

Specification and evaluation plan: 2.9 to 3.4 weeks
API contract agreed: 2.4 to 3.4 weeks
Working pilot: 2.9 to 4.9 weeks
Core resources built: 1.9 to 3.4 weeks
Security, gateway and connections: 1.4 to 2.4 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Production: 0.9 to 1.4 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access to each outside system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 30,600 to 46,820
Specification and evaluation plan 6.8%: CAD 10,404.00 to 15,918.80
API contract agreed 4.4%: CAD 6,732.00 to 10,300.40
Working pilot 20.4%: CAD 31,212.00 to 47,756.40
Core resources built 13.4%: CAD 20,502.00 to 31,369.40
Security, gateway and connections 8.9%: CAD 13,617.00 to 20,834.90
Docs, SDKs and load tests 4.4%: CAD 6,732.00 to 10,300.40
Production 6.8%: CAD 10,404.00 to 15,918.80
Launch and first callers 4.9%: CAD 7,497.00 to 11,470.90
Holdback, 30 days after launch (10%): CAD 15,300 to 23,410
GPU time for training and testing, at cost: CAD 300. Billed up front, at cost, outside the milestones

Start from this example

Example projectWeb app

Royalty statements for artists and authors

Hypothetical. Not a client, not a result.

// The problem

An independent label and publisher calculates royalties in an old Access database and a workbook, from distributor and retailer reports in a dozen formats, and each statement period takes weeks.

// What we would build

We move contracts, rates and history out of the old database, then build a system that imports each distributor's and retailer's report, applies the terms in your contracts as your royalty team reads them, and produces statements artists and authors see in their own portal, with payments and liabilities posted to QuickBooks Online both ways.

// What is in it

Contracts, rates, advances and history moved out of the old database
Reports from each distributor and retailer imported as they arrive
Terms applied as your royalty team sets them, with every step traceable
Statements in a portal for each artist and author
Payments and liabilities posted to QuickBooks Online, and payments read back
A dashboard of earnings by title, territory and channel

// Stack

Next.js
PostgreSQL
QuickBooks Online API
Metabase
DigitalOcean Toronto

// estimate

Build: ≈ US$104,000 to US$159,000, delivered within 26 weeksCAD 148,000 to 226,300
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data mapping and sandbox connection: 0.4 weeks
Design approved: 2.4 to 3.4 weeks
Statement layout approved by your royalty team: 1.9 to 2.9 weeks
Core features: 2.4 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
Sync built and reconciled in sandbox: 2.4 to 4.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Moved records checked with your team: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks
Live cutover: 0.9 to 1.4 weeks
Hypercare: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access to each outside system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 29,600 to 45,260
Discovery 3%: CAD 4,440 to 6,789
Data mapping and sandbox connection 4.4%: CAD 6,512.00 to 9,957.20
Design approved 3%: CAD 4,440 to 6,789
Statement layout approved by your royalty team 7.7%: CAD 11,396.00 to 17,425.10
Core features 9.1%: CAD 13,468.00 to 20,593.30
Full build 6.1%: CAD 9,028.00 to 13,804.30
Sync built and reconciled in sandbox 13.4%: CAD 19,832.00 to 30,324.20
Testing and fixes 3%: CAD 4,440 to 6,789
Moved records checked with your team 7.7%: CAD 11,396.00 to 17,425.10
Launch 3%: CAD 4,440 to 6,789
Live cutover 4.4%: CAD 6,512.00 to 9,957.20
Hypercare 5.2%: CAD 7,696.00 to 11,767.60
Holdback, 30 days after launch (10%): CAD 14,800 to 22,630

Start from this example

// questions

Questions we get about this.

Do you connect to our distributors directly?

Where they publish a feed specification or API, yes. We check each one you use before we quote.

What if a distributor rejects a catalogue feed?

The rejection is logged against the title with the distributor's reason, and your team fixes it once for every feed.

Can old catalogue spreadsheets be cleaned up first?

Yes. We bring them in, show the conflicts, and your team approves each fix.

Back to the industry: Music, film and publishing About the service: Integrations and automation

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call