Marbell
Open cloud portal
Menu
A sheet of heavy cotton paper in the dark, pressed with rows of blank raised lines like the clauses of a contract. A thin line of coral light crosses it: the rows above the line are lit, the rows below are still in shadow.

Legal and contracts

A fleet that reads every contract before your counsel does.

Our agents read every contract that comes in, check each clause against your playbook and send the redline back within the hour, day or night. After signature they keep every deadline it sets: renewal notices, price reviews, breach reports.

Redline

A supplier's master agreement arrives at 21:14. The redline goes back at 22:03.

Master services agreement

Supplier draft, 38 pages

  1. 4.3

    Price review

    Fees rise each January by the consumer price index, by no more than 4 per cent.

    price.index · accepted Jan 2028 · invoice up 6.1 % · 2.1 % disputed

  2. 9.2

    Liability

    Each party's total liability is limited to the fees paid in the three twelve months before the claim.

    liability.cap · preferred · closed at 12 in 2025

  3. 11.2

    Renewal

    The agreement renews for three years twelve months unless either party gives 180 90 days' notice.

    term.renewal · 12 months · 90 days Sep 2029 · notice given on day 1 of 90

  4. 14.4

    Data protection

    The supplier processes personal data under your data processing agreement, attached as schedule 5, and reports a breach within 24 hours.

    data.dpa · missing · inserted Mar 2029 · breach at 03:20 · regulator notice drafted 04:00

Playbook 7.3 · 3 clauses changed · sent 22:03

Before signature

  1. 21:14 Received

    Your supplier's fourth agreement, on its own paper. Our agents have read the first three.

  2. 21:26 Clause 9.2

    A cap of three months' fees. Your playbook asks for twelve, which this supplier accepted last year.

  3. 21:34 Clause 11.2

    Three-year renewals on 180 days' notice become twelve months on 90.

  4. 21:41 Clause 14.4

    The supplier will hold your staff data, and the draft has no data protection terms. Your terms go in.

  5. 22:03 Sent

    The redline goes back after 49 minutes, stamped with playbook release 7.3.

After signature

  1. 2 Dec 2026 Signed

    Seven obligations go into the register.

  2. Jan 2028 Clause 4.3

    The invoice rises 6.1 per cent against a cap of 4. The agents dispute the excess before payment.

  3. Mar 2029 Clause 14.4

    The supplier reports a breach at 03:20. By 04:00 the regulator notice is drafted for your data protection officer.

  4. Sep 2029 Clause 11.2

    Usage fell a third, so under your counsel's rule the agents give notice the day the window opens.

What else the agents read
  • Non-disclosure agreements on your own template clear in minutes. Counterparty paper is read clause by clause against your playbook.
  • Amendments are compared with the signed contract, and every clause a change touches is read again.
  • Drafts in German, French, Italian or English are redlined in their own language, scans included.
  • A contract that holds up a deal in your CRM moves to the front of the queue.
  • A draft that arrives twice, by email and through your contract system, is redlined once.
Thin translucent sheets hung in a row in the dark, each pressed with the same blank rows. On every sheet the same row carries a short coral stroke, and the strokes line up through the layers.

Counterparties

Every negotiation opens with what the counterparty pushed last time.

Our agents keep every draft, concession and closed position. When a mark-up comes back, you see what moved and what it costs.

What the agents keep on each counterparty
  • Every draft and mark-up exchanged, with the clauses each change touched.
  • The positions that closed and the fallback that closed them.
  • The clauses this counterparty pushes in every negotiation.
  • Who signs on their side and how long their lawyers take to reply.
  • The open obligations under every contract you already have with them.

Playbook

Your positions, fallbacks and red lines run as code.

Limitation of liability

  1. Preferred

    Twelve months of fees

    if cap >= months(12): accept()
  2. Fallback

    Six months, on contracts under CHF 250,000

    if cap >= months(6) and value < chf(250_000): accept(fallback=1)
  3. Fallback

    Six months, with CHF 5m of insurance

    if cap >= months(6) and insured >= chf(5_000_000): accept(fallback=2)
  4. Red line
  5. Never

    Under six months

    redline(cap=months(12))
  • Your general counsel sets which fallbacks the agents may take alone.
  • Counsel can open, rerun or correct any contract. Each correction becomes a rule.
What else the playbook decides
  • Every clause gets a verdict: accepted, changed or missing. Nothing is marked as probably fine.
  • No contract goes to signature without data protection terms where personal data flows.
  • Governing law and assignment are never edited quietly. A change there is redlined back to your standard wording.
  • When a supplier's bank details differ from your last payment to it, the agents check them against your ERP before the contract goes out.
  • Carve-outs from the cap (data protection, confidentiality, wilful misconduct) are rules of their own.
  • Positions differ by contract type, deal size and counterparty risk, each a rule with its own tests.

Releases

Corrections from counsel are tested on every signed contract, then go to every agent.

contracts/playbook/liability.py
def liability_cap(draft, deal):    if draft.cap >= months(6) and deal.value < chf(250_000):    if draft.cap >= months(6) and deal.value < chf(100_000):        return accept(fallback=1)
signed contracts tested
would have been redlined differently

Release 7.4 · live at 14:22

Every redline carries its release, so any clause traces back to a rule and its tests.

Architecture

  1. Operating Code

    Your playbook, tested on your signed contracts.

  2. Gate

    Each agent has its own identity and cannot sign.

  3. Your infrastructure

    Your data centre or Marbell Cloud in Switzerland.

  4. Fleet

    Lanes by contract type, sized to the intake.

For your engineers
  • Operating Code is your senior counsel's judgment written as code: positions become if statements, the pass through a contract becomes a while loop, counterparty history becomes typed variables and every red line becomes a test. It grew out of the recursive self-improvement harness our own persistent agents run on.
  • A clause verdict is a type: accepted, changed or missing. A change carries its rule, its fallback level and its release, and the redline is built from those records.
  • Agents write through two calls, redline and send, and both stamp the playbook release.
  • Gate grants an agent access to a matter for as long as your counsel sets. After a revoke, the next request is denied.
  • A playbook change ships when it passes on every contract you have signed, at the speed the tests run. Your team can rerun any contract under any release.
  • Personal data is masked before a prompt is built, and model providers retain nothing.

Systems

The agents work inside your contract management system, which stays your record.

  1. Intake

    • Legal mailbox
    • Salesforce
    • SAP Ariba

  2. Review

    • Ironclad
    • Icertis
    • DocuSign CLM

  3. Signature

    • DocuSign
    • Adobe Acrobat Sign

  4. Obligations

    • SAP S/4HANA
    • Coupa
    • ServiceNow
All systems
  • CLM: Ironclad, Icertis, DocuSign CLM, Agiloft, SAP Ariba Contracts or your own register
  • CRM: Salesforce, Dynamics 365
  • Procurement and ERP: SAP S/4HANA, SAP Ariba, Coupa, Oracle Fusion
  • E-signature: DocuSign, Adobe Acrobat Sign
  • Document and matter management: iManage, NetDocuments, SharePoint
  • Ticketing and calendars: ServiceNow, Jira, Outlook

Drafting your own paper for the sales team runs on the same agents.

The same pressed sheet seen from above, every row now evenly lit, and a short coral line near its foot where a signature would go.

Start with last quarter's contracts.

Pick a contract type. We redline last quarter's agreements beside your counsel's, then run live for a quarter, paid against the number you choose: turnaround, redlines accepted unchanged or counsel hours.

Describe your contract queue How we work