Cadence

The problem

Studios our size run on a stack of subscriptions plus memory: a CRM, a project tool, an invoicing app and a spreadsheet holding the parts none of them do. Nothing in that stack can refuse to let a project start because the advance has not landed.

How it works

One console organised by the lifecycle of money through a studio — acquire, close, deliver, collect, run — rather than by database tables. The rules that protect a project are conditions checked in the API, so they hold when a date gets close.

What is inside

Web

Next.js App Router, server-rendered, role-scoped throughout

Backend

Node and Postgres, with Zod schemas shared between the API and every form

Admin

Nine module groups, command palette, global search, append-only audit trail

Payments

Payment links on unpaid invoices plus webhook reconciliation

Infrastructure

Scheduled jobs with a dry-run mode, object storage, error grouping