‹ Finance & Operations recipesFinance & Operations · Agent Blueprint
Contract close
Verbal commitments that conflict with the contract draft. What sales promised on the call vs. what made it into the paper, flagged before signature.
Side by side: token usage, with and without Paperbase
~101k tokens saved · 78% less work for the agentWithout Paperbase
~130k tokens
- Read the contract draft.
- Search call transcripts and emails for what was promised to the vendor or customer.
- Manually compare every commitment against the paper.
- Ask sales what they promised.
- Sign a contract that contradicts the deal made on the call.
With Paperbase
~29k tokens
- Pull the contract draft into the record.
- Pull Commitments made about this deal across calls, emails, and Slack.
- Ask Paperbase to diff commitments against the contract language.
- Flag each conflict with the source commitment behind it.
Agent prompt
You are checking a contract draft for {{contract_or_vendor_name}} against what was actually promised.
Using Paperbase:
1. Extract the contract's key terms.
2. Pull the Commitments made about this deal - pricing, scope, timeline, services - across all interactions.
3. Diff each commitment against the contract language.
4. Flag every conflict, with the source interaction behind each.
Output:
- Every commitment that made it into the paper, confirmed.
- Every commitment that is missing or contradictory, each with the quote and date it was made.
- A negotiation checklist for the closing call.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.