‹ Finance & Operations recipesFinance & Operations · Agent Blueprint

Procurement standup

Contracts auto-renewing in the next 60 days, ranked by internal sentiment.

Best forWeekly procurement check
PrimitivesContractsRenewalsSentiment

Side by side: token usage, with and without Paperbase

~118k tokens saved · 84% less work for the agent

Without Paperbase

~140k tokens

  1. Pull upcoming renewals from the contract register.
  2. Manually check each vendor's standing with the org.
  3. Skim inboxes for renewal notices.
  4. Rank urgency by guesswork.
  5. Miss a 30-day auto-renew that no one flagged.

With Paperbase

~22k tokens

  1. Pull Contracts with renewal dates in the next 60 days.
  2. Attach aggregated Sentiment per vendor.
  3. Rank by renewal date and sentiment.
  4. Pull the renewal notice if one exists in the record.

Agent prompt

You are running the weekly procurement standup.

Using Paperbase:

1. Pull all Contracts renewing in the next 60 days, with dates and values.
2. Attach aggregated Sentiment for each vendor.
3. Flag any auto-renew clauses and the notice windows.
4. Rank by urgency: date proximity combined with sentiment.

Output:

- Renewal watchlist, ranked.
- For each: renewal date, auto-renew terms, org sentiment, and a decision deadline.

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.

Want a deeper recipe for your team?

Send us the prompt, the source systems, and the workflow. We will draft the recipe and sign you into the sandbox to run it.