An assistant for business managers.
Connect Patchbay to your own Claude and ask what a client’s catalog should be earning, or which agreements have never been billed against — answered from the deals themselves.
The question you cannot answer from a statement.
A statement says what arrived. The agreement says what should have. Because both are records here, the difference is something you can ask about rather than reconstruct.
What business managers actually ask it
“Which agreements have an advance that is still unrecouped?”
“What has this client signed that we have never raised an invoice against?”
“Which deals have an option or a term ending in the next two quarters?”
“Show me every client whose catalog has songs with no registration behind them.”
Each of those is answered from your own records, in your own AI client, without anyone exporting anything.
How it works
You connect Patchbay to Claude once — as a connector in the Claude app, or in Claude Code. From then on it can work in your workspace when you ask it to, authenticating as you.
There is no separate place to log into and nothing new to learn. The assistant is whichever AI client you already have open; Patchbay is what gives it something true to work from.
What it can do, and the limit that actually matters
It can change things, and that is the point. Create a deal, raise an invoice, add a writer, start a split sheet and send it. A connection that could only read would leave you doing the typing anyway, which is the part worth removing.
It acts as you. Not as a service account with its own keys — as your own login, with your permissions and your refusals. It reaches exactly as far into a client workspace as you do, and everything it does is attributed to you in the record rather than to “the integration”.
It does not decide what you are paid to decide. Whether to take the deal, what to charge, whether a split is fair. It does the work between those decisions. The decisions stay yours.
Why the answers are worth anything
Most of what a business manager needs is not a number but a comparison: what was agreed against what happened. That comparison is only possible where the contract and the money are the same system.
Ask an assistant that can see one and not the other and you get a confident answer to the wrong question — which is worse than no answer, because it looks like work.
What happens without anyone asking
Contracts. Drop the agreement in and the terms come out — rates, term, what they apply to — rather than being transcribed into fields by hand.
Split information that arrives as an email. Writers, societies and identifiers are pulled out of what was sent, instead of read once and typed in again.
The gaps. A song with no writer, a deal never invoiced, a release missing something it needs — listed for you to act on rather than found by looking.
None of that is something you would think to ask for, which is the point of it running on its own. It happens whether or not anyone ever connects an AI client.
Common questions
Which AI clients does this work with?
Claude — both the desktop and web app as a connector, and Claude Code. Those are the clients the connection was built and tested against, and the ones teams are actually using it from today. We are not going to claim clients nobody has run it against.
Can it actually change things, or only look them up?
It can change things. Creating a deal, raising an invoice, adding a writer, starting a split sheet and sending it all work from your AI client. Reading alone would leave the typing with you, which is the part worth removing.
What stops it doing something I did not want?
It runs as you rather than as its own service account, so it inherits your permissions and your refusals — it cannot reach a client workspace you are not a member of — and every action it takes is recorded against you rather than against an integration. You see what happened and who it was for.
Is this a chatbot bolted onto our data?
It is the opposite arrangement. Your own AI client does the talking; Patchbay supplies the records, structured, with the deal, the invoice and the works already related to each other. That is why the answers are about your catalog rather than about music in general.
Ask what should have been paid. Not just what was.
