Splits agreed in messaging apps
Splits are captured later in unrelated tools, after the original agreement context has already started to drift.
SplitGraf Studio
The creator's operating record.
Lock the split at the source, capture derivatives with lineage, and hand off releases cleanly - so the deal still holds when the money arrives.
Source trackInviteSplit lockedDerivative approvedRelease handoffRecord preserved
The problem
This is the modern music collaboration workflow. It works until value shows up.
A producer agrees to a remix in a voice note. The A&R confirms the split in a Slack DM. The contract goes out via DocuSign three weeks later with a slightly different percentage. The collaborator signs without noticing. The release ships. Six months later the song hits 40 million streams, the royalty statement arrives, and three people remember the deal three different ways.
Versions scattered across tools
Email, DocuSign, Drive, Notion, and chat all hold different parts of the same agreement history.
No structured handoff
The move from deal agreed to release ready depends on manual re-entry and memory.
Disputes surface at value-time
The problem usually appears when the song earns money, when memory has already drifted.
What changes when the workflow has a record
The difference is not more software. It is continuity.
The same record that captured the agreement is the record that ships the release and supports review when royalty questions arrive.
Before
Remix agreed verbally -> split confirmed in WhatsApp -> contract drafted later with different terms -> distributor metadata re-entered manually -> credits missing on release -> royalty statement arrives six months later -> nobody can prove what was originally agreed.
After
Source asset selected -> terms structured at creation -> collaborator acceptance recorded -> split snapshot locked -> derivative submitted and approved -> release-ready handoff generated -> nothing relies on memory, screenshots, or email archaeology.
One record, two faces
Studio starts the record. Integrity proves what survives downstream.
The same record Studio starts is what survives diligence, settlement review, and a catalog sale. Read the Operating Record, or see the capital-side face in Integrity.
How it works
You start from a source asset, set the terms, and invite the collaborator.
They accept through a structured workflow, not an email chain. Every step produces a record. When the song earns money, the record is still there.
The split is locked into a versioned snapshot.
Versions are preserved. Nothing gets silently overwritten.
The collaborator submits their derivative.
You approve a version. The derivative enters your catalog with its lineage to the original preserved.
The release is prepared for handoff.
Your distributor receives the operating record attached.
Workflow
The workflow, step by step.
Start from a source asset.
Choose a track in your catalog. Define the collaboration type: remix, feature, cover, sample, derivative work.
Set the terms.
Define the split, the rights granted, the territories, the deliverables, the deadlines. Structured fields, not prose paragraphs.
Invite the collaborator.
A clean, branded invitation. No PDF attachments, no version confusion. The collaborator reviews, asks questions, accepts.
Lock the split.
The agreement is captured as a versioned snapshot. If terms change later, a new version is created. The original is preserved.
Receive the derivative.
The collaborator uploads through a structured submission flow. Versions tracked. Approvals recorded.
Promote to catalog.
The approved derivative enters your catalog with its lineage to the source preserved.
Hand off the release.
The release is prepared for your distributor with the operating record attached. Metadata clean, splits documented, history intact.
What this changes for your label
Cleaner releases, fewer memory fights.
Disputes that disappear before they start.
A locked split snapshot, signed at the moment of agreement, with both parties' acceptance recorded, prevents the most common post-release dispute: the memory drift between what was agreed and what someone remembers being agreed.
Releases that ship cleaner.
When the collaboration workflow is structured, the release handoff is structured. Splits, credits, metadata, and rights documentation are already captured by the time the release date approaches.
An operating record that survives the months.
Six months later, twelve months later, when a royalty statement arrives or a TikTok use triggers a question, the record is still there, intact and traceable.
Built for
Built for labels who release derivative music seriously.
If your remix workflow currently runs through WhatsApp and DocuSign, this product is built for you.
Indie labels with active remix programs
Drum and bass, tech house, UK bass, Afrobeats, electronic labels where 30-60% of releases involve collaborators outside the core roster.
Artist managers running multi-collaborator projects
Features, co-writes, sample-heavy productions where every release involves a small forest of agreements.
Producer collectives with complex internal splits
Three-to-five-person teams where every release needs to formalise what was already informally understood.
Label founders who've grown past the spreadsheet stage
Operations that worked at 5 releases per year and break at 30.
Why labels trust it
The workflow keeps its memory.
This is what we mean by an operating record. It is the durable trail of what your label agreed to and shipped. It is there when you need it, even when nobody remembers the details.
Split versions are preserved.
When a split changes, the previous version is preserved. You can see what was agreed at every point in time, not just the most recent state.
Approval history remains attached.
When a collaborator uploads a new version of their work, the approval history remains attached. You don't lose context when someone iterates.
The release handoff carries the record.
When a release is handed off to distribution, the agreement, credits, and split state move with it.
The record is still there months later.
When a royalty statement arrives, nothing relies on memory, screenshots, or email archaeology six months after the fact.
Pricing
Founding labels.
Pilot access
Pricing is set with our first partners.
Studio is in a founding-label phase. We are working with a small number of creator teams, indie labels, managers, and producer collectives to fit the collaboration workflow to real operating patterns before publishing self-serve tiers.
The pilot includes the collaboration workflow, locked split snapshots, derivative lineage, release-ready handoff, and the operating record underneath it.
Request accessFAQ
Common questions.
Is this a distributor?
No. We are not a distributor. We prepare your release for handoff to whichever distributor you use. Our job ends where theirs begins.
Do we need to use this for every release, or only collaborations?
You can use it for any release, but it's specifically designed for collaboration workflows. If you're releasing solo tracks with no derivative involvement, the workflow is overkill. If you're running remix programs, features, or sample-based productions, this is the workflow you need.
How does this integrate with our existing tools?
SplitGraf is designed to sit alongside your existing catalog, distribution, and accounting systems, not replace them. We can export release packages in formats your distributor accepts.
Is this safe for our data?
Yes. Workspace data is isolated at the database level. Standard enterprise security practices apply: encryption at rest, encrypted transit, role-based access, and audit logging.
What if a collaboration falls through?
The agreement carries a structured state. If a collaboration is declined, withdrawn, or expires, the record is preserved as-is. Nothing is silently deleted.
Can we trial this before committing?
Yes. Book a walkthrough first. There's enough depth in the product that 30 minutes with us saves significant onboarding time.
Next step
Start where the workflow actually breaks.
Most labels we speak to do not need another tool added to their stack. They need the operating record underneath the tools they already have.