home / use cases / documents and vision / contract-intake

Contracts read, logged and never forgotten

Every contract that arrives by email is read on the box — parties, value, start and end dates, renewal clause, notice period — logged in a contract register, and its deadlines booked on the calendar with margin to act. Confidential terms are processed behind your firewall, never on anyone's cloud.

Watch the demo

starts when: A signed contract lands in your contracts@ mailbox

The problem

A contract gets negotiated, signed, celebrated — and then disappears into a folder. Eleven months later the notice window closes quietly, and the supplier you meant to replace renews for another year. Or the register that was supposed to prevent this exists, but it is a spreadsheet updated by hand, and it stopped being true in March.

None of the work involved is difficult. Reading a contract for its dates, logging it, setting a reminder — it is exactly the sort of routine that gets skipped under pressure, and exactly the kind of task research says machines can already carry: around 45% of professional-services work is automatable with current technology. What kept it manual was that the documents are too confidential to hand to a cloud tool.

How your Aivell does it

  1. The contract arrives by email. Forward it, or have your counterparty processes end at contracts@ — the trigger fires either way.
  2. It is read where it lives. PDFs, scans, hand-signed pages photographed at the notary — all read by the box, onboard. The terms of the deal never leave your network.
  3. The facts are pulled out. Parties, subject, value, start and end dates, renewal clause, notice period. High-value contracts and anything without a visible signature go to a human before entering the register.
  4. The register updates itself. One line per contract, appended — never rewritten — so the register is finally the thing it always claimed to be: current.
  5. The calendar does the remembering. Notice deadlines land on the contracts calendar with margin to act, owners get invited, and auto-renewing deals get an extra early warning.

The rules in the middle — how much margin, which threshold needs a human, who gets invited — are sentences in a chore, not settings in a system. Change them the way you would change office procedure, and the guardrails keep the rest honest: the register only grows, the calendar is add-only, and no counterparty ever hears from your Aivell.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · log incoming contracts ● active

pick up every contract emailed to contracts@

read it — parties, subject, value, start and end dates

find the renewal clause and the notice period

add a line to the contract register with all of it

book the notice deadline on the calendar 30 days early, invite Sofia

auto-renewing contracts get a second reminder 60 days out

value above €10,000, or no signature found? show it to Sofia before logging

reply confirming what was logged and when the reminders will fire

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Email collects contracts, confirms what was logged
Documents & Vision reads contracts onboard, scans included
Spreadsheets maintains the contract register
Calendar books renewal and notice reminders

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Calendar Can create events in the contracts calendar. Editing or removing existing events is blocked.
Spreadsheets May add lines to the contract register; corrections are new lines, existing entries stay untouched.
Email Confirmations go to the colleague who sent the contract — no mail to counterparties, ever.

Questions, answered.

Can it read a scanned contract with a handwritten signature page? +

Yes. The box reads scans and photos with an onboard vision model, so a contract that came back as a photographed signature page stapled to a PDF is handled like any other. If the signature is genuinely missing, that is one of the cases the chore escalates.

Contracts are the most confidential thing we hold. Where does the reading happen? +

On the box, in your office. The text is never sent to an AI provider or any cloud service — the extraction and the reasoning run onboard, so the terms of your deals stay exactly where the paper does.

How does it handle renewal and notice deadlines? +

It works them out from the clause — end date minus notice period — and books calendar reminders with the margin you chose, inviting the person who owns the contract. Auto-renewing deals get an earlier warning, because those are the ones that silently cost money.

Does it interpret the legal content of the contract? +

No, and it is not supposed to. It extracts the facts — who, what, how much, until when, on what notice — and logs them. Judging whether a clause is acceptable stays with your lawyer; anything unusual is flagged, not interpreted.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee