‹ Legal & Compliance recipesLegal & Compliance · Agent Blueprint
Contract diligence
Every commitment your side made across calls and drafts for one deal, dated and sourced, before you sign.
Side by side: token usage, with and without Paperbase
~106k tokens saved · 76% less work for the agentWithout Paperbase
~140k tokens
- Read the final contract draft.
- Search email for the negotiation thread and obligations agreed.
- Skim call transcripts for verbal commitments.
- Ask the deal team what was promised.
- Sign a contract relying on what the team remembers.
With Paperbase
~34k tokens
- Pull the contract's obligations.
- Pull every commitment made during the deal across channels.
- Attach provenance: who committed, when, and on what call.
- Cross-check the paper against the promises and flag gaps.
Agent prompt
You are running diligence on the contract for {{deal_name}} before signature.
Using Paperbase:
1. Extract the obligations from the contract draft.
2. Pull every Commitment made during the deal - our side and theirs - across calls, emails, and Slack.
3. Attach provenance to each: who, when, and where.
4. Diff the commitments against the contract language.
Output:
- An obligation list with the source behind each clause.
- Commitments made on calls that are not in the paper.
- Anything we promised that we cannot deliver, flagged before signature.Placeholders in {double_braces} are inputs the agent will ask for at runtime. Give the prompt to any agent connected to Paperbase, and the rest grounds in your own memory graph.