Private beta · five legal teams

Approval is a matrix, not an email thread.

Obsignia is the contract lifecycle workspace for in-house legal teams. Contracts are drafted, redlined and approved inside it. Clause families carry their own permissions, approvals route by area and amount, and every obligation keeps a named owner after signature.

Clause level permissions · Approval by area and amount · Obligation register

OBS-4471 · Supply agreement · 14 pages · in redline
4.2Liability capLegal leadRedlinedProposed fallback: cap at 12 months of fees
7.1Payment termCommercialEditable
9.4RenewalLegal opsEditable
11.3Governing lawLegal leadLocked

Sample data. Not legal advice.

The thread

A redline in an email thread has no owner and no state.

A supply agreement comes back with nine changes. They arrive as a PDF attachment, in a thread with four people copied, two of whom have left the company. The liability cap is now unlimited. Nobody notices until the dispute.

The thread cannot say who may touch clause 4.2, cannot say whether the change was approved, and cannot say what happens in fourteen months when it renews.

Obsignia moves the contract out of the thread and gives each clause an owner, a state and a fallback.

The thread is also the only place the negotiation history lives, and it lives badly. A change made in April is a PDF on page nine of a chain, and reconstructing why the cap moved takes a search across four inboxes and one departed employee's archive.

Obsignia keeps the version, the author and the reason inside the contract. The reason field is mandatory on every change to a locked clause, and it is the first thing an auditor reads.

In a thread
Contract status, as it is today.
  • who may edit: unknown
  • approval state: unstated
  • renewal: a date in someone's calendar
In the workspace
Contract status, inside Obsignia.
  • who may edit: per clause family
  • approval state: routed by area and amount
  • renewal: a calendar with a named owner
The workspace

Three stages, and the third one is not commercial's.

Each stage has a finish line. A draft is finished when no clause sits outside the library unacknowledged. A redline is finished when every mapped change has an owner decision. Approval is finished when the matrix is satisfied, not when someone says yes in a corridor.

Stage 1

Draft

From the approved template, with the fallback library one keystroke away. Clauses outside the library are marked as they are typed.

Approved fallbacks · sample data
Liabilitycap at 12 months of fees
Payment term30 days from invoice
Governing lawCórdoba courts
Renewal60 days written notice
Termination30 days cure
Stage 2

Redline

Counterparty changes are imported, mapped to a clause family, and assigned to that family's owner. Nothing lands in a general inbox.

OBS-4471 · in redline · sample data
4.2 Liability capRedlined
7.1 Payment termEditable
9.4 RenewalEditable
11.3 Governing lawLocked
Proposed fallbackcap at 12 months of fees
Stage 3

Approve

Routing follows the approval matrix by area and amount. Legal lead signs the liability waiver, or refuses it with a reason.

Approval matrix · sample data
up to 50kowner only
50k to 500klegal lead
above 500klegal lead and CFO
any liability waiverlegal lead regardless of amount
Permissions

The clause knows who may touch it.

Permission is a property of the clause family, not of the folder, not of the person's seniority. It is set once by the legal lead and changed per contract when it must be.

Permission is not seniority. A procurement lead of fifteen years does not get the liability cap because of the fifteen years. A first year counsel does, because the family is theirs. The unit of authority is the clause, and the person is assigned to the clause.

Clause families carry an owner and an edit right

Permission is a property of the clause family, not of the folder.

Default is locked for liability, governing law and termination

It is set once by the legal lead and changed per contract when it must be.

An unlock is logged with who unlocked it and why

The reason field is mandatory on every change to a locked clause.

A redline by a non owner stays a proposal until the owner accepts

Nothing lands in a general inbox.

Approval matrix

Amount and area decide the route.

Two axes, both set by the client. A 40 thousand dollar renewal in procurement does not route the same as a 2 million dollar exclusivity. The matrix is versioned and visible to everyone who signs.

The matrix is deliberately boring to change. Adding a band needs the legal lead and is versioned, so a route cannot be loosened quietly the week a large deal closes.

up to 50kowner only
50k to 500klegal lead
above 500klegal lead and CFO
any liability waiverlegal lead regardless of amount
Obligation register

After signature is where it gets lost.

Every obligation gets a text, a date, a responsible person and a state. The register is the landing screen for legal ops, sorted by date.

An obligation with no owner shows red on the register, and the weekly digest names it.

Obligation drift is the quiet failure. A notice date moves by three days because the counterparty asked, nobody updates the register, and the notice is missed. The register compares the stored date against the contract text on every save and flags the difference.

Why now

The library was always in someone's head.

Fallback positions have always existed. They lived in a senior lawyer's memory and came out in review, one contract at a time, at the speed of that person's calendar.

A long context model against a written library makes the fallback visible at the moment of drafting. The judgement did not get cheaper. The lookup did.

What did not change is the library. A fallback is still a decision someone made and wrote down, and the model is only as good as that document. Teams without one get told so on the first call.

What it does not do

Three things stay human.

The boundary is visible in the interface too. Every waiver shows the clause, the amount and the person who owns the decision, and none of the three is inferred.

decide commercial convenience

approve a liability waiver

interpret a foreign jurisdiction

Integrations

Where contracts already arrive.

Obsignia writes the version and the state. It does not write to the counterparty.

  • email intake, mailbox
  • CLM or drive, read API
  • counterparty redline, DOCX import
  • e-signature, executed file only
  • anything else, DOCX plus PDF
Who it is for

Teams already past three hundred contracts a month.

Firms use it for secondment work, where the library belongs to the client and the reviewer changes every few weeks. The permission set travels with the family, not the reviewer, so the handover costs nothing.

For

In-house legal of 4 seats and up, and firms running secondment.

Not for

Teams under 300 contracts a month, and anyone without a written fallback library, who needs the library before the software.

Pricing

Per legal seat.

A monthly seat. No charge per contract, because a contract is the unit of work, not a deliverable.

USD, invoiced on the 1st, net 15. Annual prepay takes 12 percent off.

Beta teams pay overage only for the length of the beta, in exchange for a written read on the library.

Bands indicative while in private beta.

Desk
1 to 3 seats
300
contracts
    Bench
    4 to 12 seats
    2,000
    contracts, matrix routing
    • Matrix routing
    Request a beta seat
    Group
    13 seats and up
    Custom
    contracts
    • SSO
    Limits

    Where it breaks.

    The list is short on purpose. Every entry is something a pilot has hit, and each one is either flagged in the interface or refused before intake.

    Scanned contracts with no text layer

    OCR runs, precision drops on photographed pages, and the clause match is marked low confidence.

    Handwritten amendments

    Detected and surfaced as an image crop, never transcribed.

    Documents above 120 pages

    Precision falls after page 90. The last third is flagged for full human read.

    Common law outside the library

    Marked as out of library, no fallback suggested.

    Questions

    Questions we get.

    01Does it replace the lawyer?

    No. It removes the chase. A person approves every clause outside the library.

    02Can commercial edit the liability clause?

    Only if the legal lead grants it per contract. Default is locked.

    03Is it legal advice?

    No. It cites the approved fallback, the decision is yours.

    04Do you sign?

    No. The executed file is stored and versioned, e-signature stays with your provider.

    05Where is the data?

    Encrypted, Toronto region, DigitalOcean. 84 months, hard delete on request.

    Roadmap

    Where this goes.

    One stage at a time, and only after the previous one holds.

    Nothing in the roadmap adds a person to the loop. The direction is fewer handovers, and the register is the surface where that is measured.

    01

    Today

    Permissions, routing and the register.

    02

    Next

    Fallback library analytics.

    03

    Later

    Obligation risk scoring.

    Team

    Two people.

    Obsignia SAS, Av. Colón 1180, piso 9, Córdoba. Founded 2026.

    Mariana Ocampo, cofounder of Obsignia.

    Mariana Ocampo

    Product. Seven years in legal ops, the last two running a contract desk.

    Santiago Reartes, cofounder of Obsignia.

    Santiago Reartes

    Machine learning. Long context retrieval and clause matching.

    We are taking three more legal teams.

    Tell us your monthly volume and where the thread breaks. A person replies within two business days. If you already know the answer is a written fallback library, say so and we start there.

    Request a beta seatmariana@obsignia.org