No. 02Technology
The secret isnot the model.
A powerful model is only one layer. What matters is the system around it: music-specific issue frameworks, structured outputs, provenance, and human review.
Abstract
The intelligence is not only in the model. It is in the system around it: music-specific agreement structures, clause-level issue frameworks, graded outputs, provenance, and a workflow designed to keep every finding tied to the underlying text.
This piece walks the engine end to end: how a contract is read as pages rather than scraped, how the distilled knowledge steers the reasoning, how every finding is graded red, amber, or green and pinned to the exact words, and how the same engine drafts agreements built for 2026, not 2016.
Reading, not scraping
The first thing most tools get wrong is the reading. They run a contract through optical character recognition, turn it into a stream of loose text, and lose the layout that carried half the meaning.
WALDHORN.AI hands the document to a multimodal model that sees the actual page: the columns of a royalty schedule, the indent of a sub-clause, the signature block, the initials in the margin.1 A garbled scan does not become garbled advice, because nothing was flattened into plain text first. The engine reads the way a person reads, then works from what it saw.
Taught by the real world
Ask what a legal AI was taught by. The honest answer, for most of them, is the internet.
The detection layer is organized around the agreements music teams actually use, from recording and publishing to touring, producer, brand, and sync. The recurring issues in those workflows are structured into two artifacts that guide the engine: a detection playbook that encodes how counsel reads each kind of agreement, and a graded clause library, red, amber, and green, kept current as the business changes.2
The frontier model underneath is a component, and we swap it as better ones arrive. The distilled layer is ours, and it is the part no one can shortcut: you cannot scrape it from the internet, because it was never on the internet.
The model is a rented engine. The map of the road is ours.
A specialist reads differently
Music contracts have their own language, and it is exactly where a general tool slips. Ask a generic chatbot about a clause and it will summarize the words. It will not tell you that the summary is where your masters quietly change hands.
The difference is not intelligence. It is context, held on purpose. Move down the rows below and watch the same question answered two ways.
Graded, and anchored to the page
Every finding carries a grade, so you can read the risk of a contract before you read a word of it:
- Red for a deal-breaking term, the kind that follows a career for decades.
- Amber for a material risk worth negotiating before you sign.
- Green for terms that are standard, or already in your favor.
A grade you cannot check is just an opinion. So a second pass finds the exact words each finding refers to and pins the note to that span on the page, the way a lawyer marks up a hard copy. If the engine cannot locate the language cleanly, it says so rather than guessing. You can export the marked-up copy, and the reasoning travels with it.
It writes for 2026, not 2016
Reading is defense. The same engine also writes.
Build mode drafts an agreement from a guided intake, using the distilled knowledge in reverse: instead of detecting the traps, it writes the protections in. And it drafts for the world the deal will actually live in. An agreement drafted here speaks to AI training and voice cloning, to streaming-era royalties, and to reversion terms with real dates, because a contract written for 2016 quietly fails its signer in 2026.3
More than a reader
Review and drafting sit inside a workspace that closes the whole deal: negotiation with tracked redlines, e-signature with sealed and independently verifiable envelopes, a forensic royalty audit that checks statements against the deal that produced them, and a rights vault that holds what you signed and what you own. Every step reads from the same distilled knowledge, which is why the loop holds together. Where that leaves the category is argued in The Category; what the workspace actually contains is set out in full below.
And it all happens on a human timescale. A full review streams onto the page in minutes, clause by clause, while you watch the contract get read.
Everything it does, on one plate
The schematic on the front page follows a single deal from the moment it arrives to the moment it is sealed and filed. It leaves a great deal out, deliberately: it is a story about one agreement, not a catalogue. This is the catalogue.
Bring it in
- Any music contractPDF, a scan, or a photograph taken on a phone
- A guided intakeplain questions, organized by music-deal category
- A royalty statementPDF or image, or a CSV or spreadsheet export
- An outside agreementpasted or imported, then redlined and signed here
- Parties on filethe people you deal with, filling their own blocks
Read and grade
- Clause by clausethirty-seven categories of risk, on every page
- Pinned to the wordseach finding sits on the clause that caused it
- Read from your cornerthe same contract reads differently for each side
- Contract Finderanswer questions instead of naming the document
- Statement auditagainst the deal you signed, or the statement alone
What comes out
- The Review Copyyour own pages, typeset, every finding on its clause
- Prep and tonewhat to say, rewritten in the voice you want
- A complete draftmodern protections written in, not bolted on
- A recomputed ledgerthe royalty maths, line by line, against the deal
- A demand letteritemised, with the numbers, ready to send
- Your letterheadyour logo and mark on the agreement and the dossier
- It all leavesDOCX, PDF, spreadsheet and CSV exports throughout
Agree and execute
- A real redline linkturn by turn, and no account for the other side
- Verified accessa one time code before the link opens
- A consistency checkacross every accepted change, before you close
- Amendment No. 1the original left exactly as it was
- Three ways to executethe amendment, the original, or both as one
- Signing in orderfields, sequence, nudges, a wrong address, a void
Prove it
- A SHA-256 sealchain of custody, bound inside the sealed document
- A tamper-evident logevery event, exportable, checkable by anyone
- Public verificationpaste the hash or scan the code. No account.
- A live status linknames only, and it expires with the envelope
- Into their accountthe executed copy, bound to the account not the email
Keep it
- Contract Ledgergrouped by deal, named in your words, always findable
- Client Filesa folder for each client, holding everything by reference
- Rights Vaultreleases, splits that must reach a hundred, clearances
- Registration Journeythe society, the mechanical, the publisher, in order
- Tour Plannerrouting, per show accounting, visas and withholding
- Calendar and remindersdates that come back to you before they bite
- Notes that pointmention a contract, a release or a person, and link it
Around it
- Teamsroles, and a vault, tours and drafts the whole team holds
- Share, but narrowlywho sees what, with a password, an expiry, a revoke
- Clause Libraryfifty-five clauses in plain English, open to anyone
- The Briefinga guided tour that points at the real controls
- Match Counsela human lawyer when you need one. In pilot.
- Plans and creditsfive tiers, or packs when you would rather not commit
- Refer and earnaccount credit when someone you invited subscribes
Where a human stays in the loop
A tool used around consequential agreements has to earn trust. Four commitments are built into the workspace rather than bolted on:
- Conservative under uncertainty. When the answer depends on jurisdiction or facts we cannot see, the workspace says so and points to a human, instead of inventing certainty.
- No invented law. It does not cite statutes or cases that do not exist. Where it is unsure of an authority, it names none.
- Your documents are yours. Current document-processing practices and provider roles are stated in the Privacy Policy and Subprocessors list.
- A tool, not a lawyer. WALDHORN.AI is not a law firm and forms no attorney-client relationship. For the decisions that matter, it makes you ready for counsel, not a substitute for it.
Those are not disclaimers hidden in a footer. They are the reason a non-lawyer can trust what they read here.4
Notes and references
- The document is read by a multimodal model inline, not through a separate OCR step. The providers WALDHORN.AI uses are listed on the Subprocessors page: Google Gemini by default, with optional routing to Anthropic and OpenAI models via OpenRouter.
- The playbook and clause library are maintained product artifacts. Current document processing and provider roles are stated in the Privacy Policy and Subprocessors list.
- Build mode is live today for recording agreements and mutual NDAs, with further deal types rolling out. Review is organized across the current music-deal catalog.
- See the Privacy Policy and Terms of Service for how data is handled and the limits of the service.
Taught by real deals. See it read yours.
Free to start. WALDHORN.AI is a tool, not a law firm, and does not provide legal advice.
More from the Review