The AI workspace for legal teams

Legal work, written.

Turn a legal request into a note with linked documents, review standards, and steps Seraa can run. Follow the work from the first instruction to the next decision.

task note · acme review✎ example task
Review the Acme MSA against the Vendor Terms Rulebook.

Linked document and rulebook · activate the note before running

30-day free trial

Review against your rulebooksOpen cited sourcesReuse your review methodsTrack human handoffs

Imagine Maya — sole counsel for 300 people

Fifty requests a week. One person to keep the work moving.

Monday

Intake chaos

An NDA lands in Slack, a supplier agreement by email, redlines in a DM. Maya has to piece together what needs doing and who is waiting.

Wednesday

The context hunt

The Acme review needs the agreement, last year's positions, and the playbook. All of it scattered across folders, inboxes, and memory.

Friday

An answer she still has to check

The AI answer sounds convincing. But Maya still has to find the source, check the reasoning, and decide whether to use it.

Maya needs to see what was done, what it relied on, and what still needs her judgment.

A week with Seraa

One agreement, from request to decision.

An illustrative week: Maya takes an Acme supplier agreement from a request to a review, a reusable method, and an approval request. These examples use sample documents and results.

Monday

The request becomes a plan she can read.

Maya names the agreement and her review standards. Seraa helps turn the request into a Task note: written steps linked to the documents they need. She checks the instructions, activates the note, and starts the work.

seraa — assistant

Maya

Help me review the Acme MSA.

Seraa

Which document and review standards should I use?

Maya

Use the Acme MSA and our Vendor Terms Rulebook. Flag issues for me.

Seraa

I'll prepare a Task note with those references for you to review and activate.

task note — acme msa review
StatusDraft · awaiting activationReviewReview Acme MSA against the Vendor Terms Rulebook.OutputRecord the findings and proposed changes for Maya to consider.

Activation preserves this version of the instructions for the run.

Wednesday

She checks the reasoning before the redline.

Maya highlights a clause: “This liability cap feels off.” Seraa proposes a change against her rulebook and links the source. She opens the source, checks the wording, and accepts or rejects the suggested edit.

seraa — review

Acme MSA · §7.2 Liability · suggested edit

CURRENTLiability under this Agreement shall be unlimited as to either party…
PROPOSEDExcept for confidentiality and IP infringement, liability shall not exceed the fees paid in the twelve (12) months preceding the claim…

Fictional contract wording, used to illustrate source checking — not a recommended legal position.

Thursday

A good review becomes a reusable method.

The next supplier agreement will need the same checks. Maya saves her method in a Skill note, ready to reference from the next Task. Here she uses Acme to show how the method applies. Each new Task names the agreement to review.

task note — using vendor review
Review Acme MSA using Vendor Review. Record the findings for Maya.
Linked document and reusable SkillWritten instructions guide the agentsActivate the Task note, then start a run
Documentthe agreement to reviewSkillthe method to reusePersonwho needs the result

Friday

She knows what is done and what needs her.

The review is ready for Maya. She can open the findings, inspect the run, and see the step waiting for her approval. That step stays open until she responds. Seraa does the preparation. Maya makes the decision.

task run — acme msa review
Task run Acme MSA reviewawaiting Maya
✓

Read agreement

✓

Review against rulebook

✓

Record findings

◷

Await Maya's approval

Review ready. Open the findings and step history before deciding.

The note and its run

The instructions stay with the work.

Maya can return to the note, follow its linked documents, and inspect what happened in the run. The review has a record she can reopen when the next question arrives.

What she asked for

ReviewReview Acme MSA against the Vendor Terms Rulebook.OutputRecord the findings and proposed changes.DecisionAsk Maya to approve the agreement before signing.

What happened

✓Note activated — instructions preserved for the run
✓Review completed — findings available to open
✓Proposed changes ready for review
◷Awaiting Maya — approval still pending
Each run follows the version activated for it. Later edits do not rewrite that run’s instructions.

Keep the references close

Link the agreement, rulebook, and reusable method in the note so the work names what it needs.

Know who is needed next

A human handoff identifies the person whose response is needed before that step can finish.

Carry good methods forward

Reference a Skill from another Task to reuse the review instructions and standards.

Return to the work

Open the run's steps, results, and conversation when you need to understand what happened.

Under the hood

Written instructions. Visible progress.

— Linked steps.

Resource and requirement references define dependencies between steps. Seraa checks that structure before the Task can run.

— Agents that do the work.

Agents follow the written instructions to review, draft, and extract information. Their results remain work for your team to assess.

— A version for each run.

Activation preserves the note's instructions. A run stays tied to that version as the work progresses.

— People in the process.

Steps can hand work to a person for approval, a signature, or more information. The run records the handoff and waits for the response.

Linked resourcesReusable SkillsRun historyHuman handoffs

Bring your next agreement. Put Seraa to work.

Start with a document and your review standards. Build a Task note, follow the review, and decide what happens next.

30-day free trial · [email protected]