OBP-L™ · the open billing protocol for legal

When both sides have it, billing changes.

Outside counsel signs envelopes at submission. In-house counsel verifies at receipt. Disputes settle deterministically. The future state of legal billing when buyer and firm both adopt.

Why billing today fails both sides

Billing is a one-sided narrative. Both sides absorb the cost.

Problem one

The bill is a story, not a record.

Outside counsel tells a narrative. In-house accepts or disputes. There is no shared substrate, no neutral arbiter, no cryptographic record of what was actually delivered.

Problem two

Disputes have no enforcement mechanism.

The write-down is a relationship cost, not an enforcement remedy. The firm absorbs to keep the client. The buyer absorbs what they couldn't catch. Both lose.

Problem three

There's no protocol — only software.

Every legal-tech tool is a closed system. Brightflag handles spend management. Aderant handles billing. iManage handles documents. None of them define the protocol underneath. None of them work across vendor boundaries.

The protocol · in motion

The round-trip — firm signs at submission, buyer verifies at receipt.

When both sides adopt OBP-L, billing becomes attestable infrastructure. Every billed line gets a signed envelope at submission. The buyer verifies the signature cryptographically at receipt. Disputes route deterministically. No write-down dance. No one-sided narrative. Just settlement.

F
Firm side
captures + signs the work at submission
P
OBP-L Protocol
verifies + anchors + routes
B
Buyer side
verifies the bill at receipt
Step 1 · F → P · BILL
Bill submitted
Step 2 · P → B · SIGNED
Signed at protocol
Step 3 · B → P · VERIFIED
Verified at receipt
Step 4 · P ← F · DISPUTE
Dispute returned (only if needed)

Step 1 · F → P

The firm signs and submits the bill.

At cycle close, the firm's billing system captures every billed line at source — auto-pulled from work artifacts. Each line is cryptographically signed and submitted as a BILL envelope to the OBP-L protocol.

— One billing cycle. Four cryptographic stages.

BILL envelope
F → P · auto-cycling
Step 1 of 4
Per-line evidence chain 412 items · cryptographically anchored
412
Hours billed aggregated from auto-captured ledger
284.5
Signature issued at submission
Verified

What the protocol unlocks

Three things that can't exist without a shared protocol.

Unlock one

Deterministic dispute settlement

When the envelope is signed cryptographically at submission, the bill is unilaterally enforceable. Disputes route to a neutral arbiter that reads the protocol — not to a relationship negotiation.

Unlock two

Vendor-neutral interoperability

Any firm can ship a conformant version. Any buyer can verify any envelope. Apache 2.0. Open spec. No vendor lock-in. Pyx authors the protocol and ships the canonical implementation, but the standard belongs to the industry.

Unlock three

First-mover positioning

The first OBP-L conformant firms and buyers in the country lock the press story, the procurement positioning, and the industry signaling. Whoever adopts first — claims first.

Pyx ships both sides of the protocol today.

The OBP-L protocol activates when both sides have it. But you don't have to wait — Pyx ships products for each side now, and OBP-L conformance comes as you adopt.

Become an early conformant.

First buyer. First firm. First in the country. The OBP-L conformance registry is open — sign envelopes today, get listed publicly, claim the positioning permanently.

Inquire about conformance →