Notion for the music business.

Why teams start here

Because it is free-form and immediate. Nobody has to approve it, nothing has to be configured, and the shape of the thing can change on a Tuesday afternoon when the work changes. For a small team writing down what it knows, that is the right trade.

None of that is a mistake to be corrected. A team that has written down its own process has done something most have not.

What changes when the documents become records

A general-purpose workspace stores what you type. It has no built-in idea of what a split sheet is, what makes a registration complete, or which identifier belongs on a recording rather than a composition. Those rules do not disappear — they move into your head, or into a convention the team agrees to keep.

That works while the person who set it up is still the person using it. It stops working when the team grows, when a client's team joins, or when the convention needs an owner and does not have one. The document was never wrong; it just cannot check itself.

What a music-native system already knows

What a deal is, and what an invoice against it should say. Record, publishing, master, brand and catalog deals each carry their own shape, and an invoice starts from the deal rather than from a blank template.

That a song and a recording are different things. Compositions, masters, writers, publishers and the identifiers that link them are separate records with their own rules, not columns someone chose.

That publishing and master splits are separate pools. Neither inherits from the other, and the system will not let one quietly imply the other.

That a release has a checklist and a deadline. Tracks, artists, assets, clearances and delivery, with what is missing visible rather than remembered.

That people from different companies need different access. A manager, a business manager, a label contact and a lawyer can each be in the same client workspace at their own level.

Why teams move off it

This is the most common thing we replace, so the pattern is familiar. It is rarely one breaking point — it is four at once.

It never joins up to anything. A general-purpose workspace has no native connection to where music data actually comes from. Every registration, statement and identifier arrives by somebody pasting it in, which means the workspace is only as current as the last person who had an hour.

Sharing stops at the edge of your company. The people who need a view are a client's lawyer, a label contact, a co-manager at another firm. Giving each of them exactly the right slice, and nothing else, is not what a document workspace's permissions were designed for.

Somebody has to keep it alive. The templates, the relations, the conventions that make it work are maintained by a person. That person becomes a dependency, and the system degrades quietly whenever they are busy.

It was never built for this. Everything above follows from that. It is a general tool doing a specialist job, and the gap gets paid for in hours rather than in software.

What we would actually suggest

Keep the docs. Meeting notes, planning, internal wikis, anything whose value is that a person wrote it — there is no reason to move that, and we are not asking you to.

Move the records. Anything that has to be correct, has to be shared with someone outside your company, or has to still be right in two years. That is the half where being a document rather than a record costs you.

The migration is ours to do. Bringing an existing workspace or database across is white-glove — you are not being handed an importer.