Running the business out of a shared drive.
Every file is in there. That is the problem — a folder can hold a contract without knowing anything that is in it.
Keep the files. Extract the facts.
The agreement stays a document. What it says — the rate, the term, the splits, who signed — becomes something you can search, check and bill against.
Why every team ends up here
Because files have to go somewhere, everyone already has an account, and a folder tree costs nothing to start. A shared drive is the lowest-friction place in the world to put a signed PDF, and for storing and sharing files it does the job well.
Nobody chose it as the system of record. It became one, quietly, because it was where the documents already were.
What a folder cannot do
Storage is not structure. A file store holds bytes and a filename. It has no concept of an advance, a term, a share or a payer, so every fact worth knowing stays sealed inside the document. That is not a shortcoming — it is what makes it general-purpose — but it means the facts are only available to someone willing to open the file and read it.
Search finds names, not facts. You can find a document called agreement. You cannot ask which deals have an option expiring this quarter, because nothing in a folder knows what an option is.
The filename becomes the data model. Which is why every team invents a convention, and why every convention decays. Final-v3-SIGNED-updated is a schema being maintained by hand, in the one field the system will let you write in.
Nothing points at anything else. The contract, the invoice raised against it and the statement that pays it are three files in three folders with no relationship between them. Reconstructing that relationship is the actual work, and it gets redone every time somebody asks.
Absence is invisible. A missing split sheet does not show up as a missing file. It shows up eighteen months later as a question you cannot answer.
What changes when the facts come out of the file
The terms become fields. Drop an agreement in and the rate, term, parties and splits are extracted for you to check rather than transcribe — so the answer to "what did we sign" is a look rather than an afternoon.
Records reach each other. The invoice is raised from the deal. The statement is linked to the agreement it pays. The recording carries its credits. Nothing has to be reassembled from three folders.
The gaps become a list. A system that knows what a complete deal or a complete song looks like can show you the incomplete ones. A folder can only show you what was put in it.
Access is by record, not by folder. Someone can be given the one release they are working on without inheriting a directory tree, and without you making a copy that immediately goes stale.
What stays where it is
The files. Audio, artwork, decks, everything you actually store — a drive is a good place for those and this is not an argument for moving them.
What moves is the layer above: the facts those documents contain, and the relationships between them. The signed PDF is still the signed PDF. It just stops being the only place the terms exist.
Common questions
Do we have to stop using our drive?
No. Keep storing files there. What changes is that the facts inside the important documents — rates, terms, splits, dates — also exist as records you can search and act on, instead of only as text inside a PDF.
Is this just a better folder structure?
No, and that is the distinction worth holding on to. A better folder structure is still a convention you maintain. The difference here is that the contents are structured, so the system can tell you which deals have an option expiring or which songs have no writer — questions no folder tree can answer however well it is named.
What happens to the documents we already have?
They come across, and the terms are extracted from them for you to check rather than retype. Getting an existing set of agreements in is white-glove.
Our naming convention actually works. Why change?
Then you have solved the finding problem, which is real progress. The one it cannot solve is the asking problem — a filename can tell you which document is which, but it cannot tell you what is missing, and it cannot connect a contract to the invoice raised against it.
