Royalty data

// 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

// Stack

• Next.js
• PostgreSQL
• QuickBooks Online API
• Metabase
• DigitalOcean Toronto

// The problem

A production company prepares the data for its tax credit claims in a workbook full of macros one person built, pulling costs, crew residency and payroll by hand for each show.

// What we would build

We start with an architecture review of the old workbook, then build a system that brings in costs from your accounting and payroll exports, tags each cost and crew member the way your accountants set out, and produces the schedules they ask for. Your accountants and advisers prepare and file the claims; we give no tax advice.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Metabase
• Accounting and payroll exports
• DigitalOcean Toronto