Production software

// The problem

A film and TV production company runs schedules in spreadsheets, sends call sheets as email attachments, and collects crew start paperwork on paper for every show.

// What we would build

A production office app for web, iOS and Android: schedules by day and unit, call sheets published to the crew's phones with changes flagged, and crew onboarding with deal memos, forms and documents collected online and exported to your payroll service. Pay and banking details are seen only by the roles you choose.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• E-signature service API
• DigitalOcean Toronto

// The problem

A post-production studio tracks dailies, drives and deliverables in a spreadsheet, and finding which drive holds a take, or who has seen the latest cut, means asking around.

// What we would build

A tracker for camera cards, drives, dailies and deliverables, with proxies viewable in the browser for the people allowed to see them, on cloud storage we set up and run for you in Canada, with monitoring, backups and access logs.

// What is in it

// Stack

• Next.js
• PostgreSQL
• AWS S3 and CloudFront
• Video transcoding service
• AWS Canada

// 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 book publisher takes manuscripts by email, readers keep notes in their own files, and writers wait months with no word on where their submission stands.

// What we would build

A submissions portal designed with your editors, where writers or artists submit to open calls, readers score and comment in one place, and every submitter sees the status of their work and gets an answer, in the words your editors choose.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Object storage for files
• Transactional email
• DigitalOcean Toronto

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

// Stack

• Node.js
• PostgreSQL
• DDEX and ONIX feeds
• Open-source model on GPU
• 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

// The problem

A film's financiers, distributors and the production company each hold their own copies of the option, rights and licence agreements behind the picture, and checking the chain of title means comparing folders.

// What we would build

A shared web app where each party records the agreements behind a title, with a fingerprint of each signed document written to a private permissioned ledger that every party runs a node of. A data room of signed PDFs often does this job; the ledger helps when several parties need one record that none of them holds alone.

// What is in it

// Stack

• Next.js
• Hyperledger Besu (private, permissioned)
• PostgreSQL
• DigitalOcean Toronto