Skip to content
NEW: Contract & SLA Management is now in open beta. Learn more →

Contract Intelligence

Ask Your Contracts. Get Answers with the Clause Cited.

Upload every order form, SLA, DPA, and MSA. Then ask in plain English — "what’s our termination notice with Segment?" or "which vendors give us SLA credits?" — and get back the answer with the exact clause quoted.

What it actually looks like

NotebookLM-style. Inline numbered badges. Hover or click to see the exact source clause.

You ask:
What’s the termination notice across our top three contracts, and which one auto-renews?
Stack Builder responds:

Your three largest contracts have notably different termination terms:

  • · Segment: 90 days’ written notice before the renewal date 1
  • · Snowflake: 30 days, with no auto-renewal clause 2
  • · Braze: 60 days, auto-renews for successive 12-month terms 3

Only Braze auto-renews. Segment requires affirmative renewal but the 90-day notice means you must decide by mid-September to exit cleanly in December.

1 Segment Order Form, §6.2 View source →

"Either party may terminate this Order Form at the end of the then-current Subscription Term by providing written notice no fewer than ninety (90) days prior to the end of such Subscription Term."

2 Snowflake Order Schedule, §4 View source →

"This Order Schedule may be terminated by Customer for convenience upon thirty (30) days’ written notice. This Schedule does not renew automatically."

3 Braze Order Form, §7.1 View source →

"Subscription Term shall automatically renew for successive twelve (12) month periods unless either party provides written notice of non-renewal at least sixty (60) days prior to the end of the then-current term."

Why citations matter

A contract answer you can’t verify is worse than no answer. Three reasons we built this differently.

Your legal team won’t take "the AI said so"

Every claim links to the source clause. You verify in 10 seconds before forwarding the answer to procurement.

Hallucinations are caught instantly

If the cited clause doesn’t support the claim, you spot it. Most "AI Q&A over docs" products skip this and trust the model.

Audit trail by default

Every Q&A is logged. Show your security team what was asked, what was retrieved, what was answered. Audit log retains 365 days on Enterprise.

How it works under the hood

Standard RAG with one twist: clause-level retrieval and verbatim quoting are enforced in the prompt, not left to the model’s discretion.

1. UPLOAD

PDF or DOCX. Order form, DPA, SLA, MSA. Tag with vendor and type.

2. EXTRACT

n8n + Claude extracts structured fields (~60s). Chunks the text into searchable units. Embeddings stored in pgvector.

3. ASK

Query the Research Assistant in-app or `/msb ask` in Slack. Vector search retrieves top-K relevant chunks (similarity ≥ 0.65).

4. CITE

Claude answers with inline `[N]` badges, verbatim clause quotes, and signed-URL links back to the original document.

The method

Interrogate your contracts by hand

The questions that matter are rarely answered on one page of one contract. This procedure is how you answer them without reading everything twice. Half a day for the first question, minutes for later ones.

  1. Write the question before you open anything

    "What are we committed to if we cut headcount next year" is answerable. "What is in our contracts" is not. The question determines which clauses matter.

  2. Identify the clause types that could answer it

    Minimum commitments, seat floors, auto-renew, termination for convenience, price escalators. You are looking for four or five clause types, not the whole document.

  3. Pull just those clauses from every contract into one sheet

    One row per contract, one column per clause type, quoting the actual wording. Paraphrasing is where errors enter — and the wording is what you will be held to.

  4. Read down the columns, not across the rows

    Comparing the same clause across every vendor is where the outliers appear. Reading contract by contract, you normalise to whatever you read first.

  5. Record the answer and the clauses it rests on

    Next time the question is asked, you want the answer and its evidence, not a second afternoon.

Worked example Illustrative

Question: "What is our exposure if we reduce seats by 30% next year?"

Contracts holding relevant clauses 9
With seat floors 5
Allowing mid-term reduction 2
With price escalators on reduction 3
Exposure if all seats cut $0 saved on 5 of 9

Reading it: Five contracts with seat floors means a 30% headcount reduction saves nothing on most of the stack. That is a procurement position to fix at renewal, and it is invisible until the clauses sit in one column.

The shortcut: Contract chat searches the clause text across every agreement at once, so steps 2 and 3 collapse into a question.

Frequently Asked Questions

How does it know what’s in my contracts?
We extract structured text from your uploaded PDFs and DOCX files, split them into searchable chunks, and embed them with OpenAI text-embedding-3-small. When you ask a question, the most relevant clauses are retrieved and passed to Claude with a strict citation requirement.
What kinds of questions can I ask?
Anything that’s in the document — termination notice periods, auto-renewal clauses, liability caps, SLA penalties, DPA sub-processors, IP assignment, data residency. Comparative questions work too: "Which contracts have the longest termination notice?" or "Show me every vendor with sub-processor change rights."
Why do the answers cite specific clauses?
Because contract Q&A without citations is useless — you can’t take a generic AI answer to your legal team. Every claim links back to the source clause, with the verbatim text quoted so you can verify before acting.
Where does my contract data go?
Stored in our database with column-level encryption (per-team Vault keys + pgcrypto). Sent to Anthropic Claude for the actual Q&A — covered by your team’s AI consent toggle. Original files in Supabase Storage with 5-minute signed-URL expiry. ISO 27001 controls A.5.14, A.8.24, A.8.26 in our security page.
Can I ask this in Slack too?
Yes. `/msb ask ` works in any Slack channel where the MSB app is installed. Returns the same cited answer in a Block Kit message. Pair a stack with a Slack workspace via the integration setup.
What if a contract isn’t extracted correctly?
You’ll see the extraction confidence and can re-run extraction or edit fields manually. Most standard contract structures (order forms, DPAs, SLAs, MSAs) are extracted in under 60 seconds with >95% accuracy on the structured fields.

Stop reading contracts. Start asking them.

Free to try. Upload up to 3 contracts on the Free plan, unlimited on Team. Available in-app and via /msb ask in Slack.

No credit card required. Free plan available.