Agent-to-agent billing as a GC AI module. The firm's billing agent sends out signed line items. The client's review agent checks, approves, or disputes them, and every step gets locked in with a signature. No more 90-day invoice fights. No more "we never agreed to that rate." No more piecing a matter back together six months after the fact. The envelope is the system of record.
Same protocol, two roles. Law firms use it to bill with proof. Clients use it to push back with proof. Most engagements end up running both, and once that happens, the whole industry's invoice-dispute costs start to shrink.
Friday 5:00 PM. $487K in fees across 23 matters. The billing partner clicks Send. What Acme gets is not a PDF. It's an envelope.
What got proven: the invoice is mathematically tied to the engagement letter, the rate card, and the matter scope. If Acme disputes a rate, the firm points to the signed engagement-letter clause. If the firm disputes a write-off, the client points to the signed approval. No piecing things back together. No "I don't recall agreeing to that." Ready for an audit by tax, a regulator, a malpractice carrier, or the firm's own partner-comp committee.
Monday 9:00 AM. Acme's Review agent reads the envelope and flags three problems before a human ever sees the bill.
What got proven: the client read every line, applied the engagement letter exactly as written, paid what was owed, disputed what wasn't, and got through the whole exchange in under an hour. The dispute carries its own paper trail. If it ever goes to fee arbitration, the arbitrator opens both envelopes in a browser. What used to take six weeks of emails now happens once, signed, and done.
Every line is an object signed with a cryptographic key. Privileged narrative content sits behind a ViewKey. The client sees the work, but opposing counsel never does, even if the envelope is later produced under subpoena.
Legal billing today runs on PDFs, LEDES files, e-billing portals, and a months-long appeals process. The agent-to-agent module replaces how it works underneath. The output looks the same. What's holding it up is completely different.
| What happens today | What collapses | What happens with the module |
|---|---|---|
| Firm sends PDF invoice. Client's AP enters it manually or via LEDES. | Manual entry · transcription error · format incompatibility | Signed envelope ships once. Both sides hold the same record. Zero re-entry. |
| Client questions a rate or a narrative six weeks later. | Email chain · partner call · billing-committee escalation · soft write-off to keep relationship | Review agent surfaces the deviation in minutes, cites the engagement-letter clause, ships a signed dispute envelope back same day. |
| Firm and client disagree on whether a clause was agreed to at engagement. | "Let me check with the partner" · digging through old emails · sometimes outside counsel arbitration | Engagement-letter hash is in the envelope. Either side opens it in a browser. The clause is the clause. |
| Matter goes over budget. Client did not know until invoice arrived. | Surprise overage · uncomfortable partner call · soft commitment to "watch it next time" | Budget-cap envelope is referenced by every line. SHOD gate would have prevented the line from being added without an explicit, signed budget-increase envelope. |
| Subpoena lands. Firm must produce invoices and narratives. | Privileged narratives accidentally produced · over-redaction · privilege log fights | Narrative content sits behind a ViewKey. Subpoenaed party produces the envelope; the privileged narrative remains mathematically inaccessible. |
| CFO asks "what did we actually spend on outside counsel last quarter, by matter?" | Two weeks of legal-ops aggregation · reconciliation with AP · inconsistent matter taxonomies | Every envelope is queryable. Real-time CFO dashboard. The number is signed, not estimated. |
| Fee dispute escalates to arbitration or fee-dispute board. | Months of discovery · reconstructed time entries · "best recollection" testimony | Both envelopes are evidence. The arbitrator opens them in a browser. The hearing is about interpretation, not facts. |
GC AI doesn't change. The module runs underneath the existing screens plus one new one. Customers can turn it on per matter, per vendor, or across the whole platform. What's running underneath stays the same either way.
GC AI today already receives invoices from outside counsel. Add envelope ingestion alongside LEDES. The Review agent runs automatically; the GC sees only the exceptions.
When a new matter spins up in GC AI, the engagement letter is hashed and anchored. Every future invoice from that firm carries the hash. Rate disputes become a checksum, not a memory.
Matter budgets in GC AI become signed envelopes. The firm's billing agent (if running the module on its side) cannot add a line that would push the matter over without a signed budget-increase envelope from the client.
Every signed line item can be looked up. Spend by matter, by firm, by timekeeper, by UTBMS code, by jurisdiction, all in real time, all signed, never pieced together after the fact. It's the finance team's window into what the GC sees.
When the firm also runs the module, both sides settle through envelopes. GC AI gets a per-envelope fee on both sides, the customer gets faster resolution, the firm gets faster payment.
Disputed lines do not block payment of the agreed portion. They sit in their own sealed envelope with both positions cited. Payable balance releases automatically; disputed balance stays in a structured holding pattern.
Same envelope on both sides. It drops right into the platform 1,700 teams already trust. Every quarter a customer runs it, they get harder to move off GC AI, because the firm now holds the envelope on the other side too. It takes twenty minutes once you're set up.
Walk through the module → Back to the main brief →