Documents & contracts

Contract work with AI agents: check contracts, flag deadlines, draft quotes.

Contracts, quotes and certificates are paperwork with dates attached: read it, compare it with your own template, chase it, give notice in time. An agent does that by your rules and asks you before anything leaves the company. Here is a Monday with four such runs.

A Monday in contract admin

Four agent runs in one day. Each goes from trigger to result and touches several systems, not just one step.

  1. 01 · 07:30

    Request expiring certificates and file them

    The first of the month falls on this Monday: a run goes through the 64 supplier records and finds two liability certificates that expire in 60 days. Requesting missing certificates is something you approved once, so the agent sends the emails itself and follows up after five days. When the PDF comes back it checks the term and the cover against your requirement of €5,000,000, files it in the supplier folder and sets the next check.

    1. 1A run checks the certificates of all suppliers
    2. 2What expires in the next 60 days?
    3. 3The request goes out by email
    4. 4The certificate comes back and is checked
    5. 5Filed, record current, next check set
    ScheduleRecordsEmail to supplierMailboxGoogle DriveRecord
  2. 02 · 08:00

    Check notice periods and give notice in time

    The Monday run goes through all 212 contract records and looks for what enters its notice period in the next 90 days. Three contracts are in the list, each with its clause quoted. Nina answers yes in Slack for the Vento cloud storage, which would otherwise renew for 12 months and €14,400, and the agent sends the termination for 31 December.

    1. 1Every Monday a run checks all contract records
    2. 2Who enters the notice period within 90 days?
    3. 3The list quotes the clause for each contract
    4. 4One yes in Slack, then the notice goes out
    5. 5Record set to terminated, deadline on file
    ScheduleRecordsDeadline listSlackEmail to vendorRecord
  3. 03 · 09:05

    Check a draft contract and answer it

    Falkner sends the 2027 maintenance agreement to admin@. The agent turns term, notice period and the €2,450.00 a month into a record and compares clause by clause with your standard terms: three differences, each quoting both passages. Nina says yes in Slack, the reply goes to the supplier, and by the evening the signed version hangs on the same record as version 2.

    1. 1The draft contract arrives by email
    2. 2Fields, deadlines and amounts become a record
    3. 3Compared with your standard terms
    4. 4One yes in Slack, then the reply goes out
    5. 5The signed version becomes version 2
    MailboxRecordStandard termsSlackEmail to supplierRecord
  4. 04 · 14:20

    Answer an enquiry and send the quote

    Brammer Logistics asks for maintenance at three sites, with the scope of work attached as a PDF. The agent files the enquiry as a record, takes the prices for the twelve items from your price list in Google Sheets and builds quote A-2026-114 for €18,640.00. Tobias approves it in Slack, the email goes out, and without an answer the agent follows up after seven days.

    1. 1The enquiry arrives with the scope of work
    2. 2Items and prices from your price list
    3. 3The quote is built from your template
    4. 4One yes in Slack, then it goes out
    5. 5No answer, the agent follows up after 7 days
    MailboxRecordGoogle SheetsQuote templateSlackEmail to customer

Matching templates

All templates in the School

Common questions

Every step that leaves the company sits behind an approval: the agent prepares the notice, the quote or the reply as a draft and sends a short question in Slack that a person answers with yes. Narrow cases you can approve once, for example requesting missing certificates. Signatures still run through your signing tool, and the signed version comes back as a new version of the record.

From your own paperwork: standard terms and the quote template live as documents in the space, the price list as a sheet in Google Sheets, and contracts arrive from a connected inbox, from Google Drive or by upload. The assistant reads an existing process document and builds the skill from it, and you change it afterwards in conversation. A contract archive or your signing tool connects via MCP or an HTTP step.

The scan is stored as text on the document, and the skill reads the fields from that text. Uncertain values are flagged for review with the passage next to them instead of guessed. The log shows for every field which document it came from, and changes to records can be undone.

A skill only sees the folders in its scope. The management folder stays outside it, and the log shows step by step which documents a run actually read. Spaces separate teams, scope separates skills inside a team.

Describe the task. The rest takes shape on the platform.

Start for free, create your first skill with the assistant, and see what a run looks like before you connect anything.

Start for free