Contracts auto-renewing in the next 60 days
Auto-renewals on the horizon, ranked by internal sentiment.
- Best for
- Procurement standup
- Primitives
- ContractsRenewalsSentiment
- Token savings
- 75%
The prompt
You are scanning for auto-renewals in the next 60 days. Using Sentra: 1. Pull every Contract Value Object with an auto-renew clause whose renewal date is within 60 days. 2. For each, attach: the dollar amount, the internal owner, the last approver, and the aggregate internal sentiment on the vendor. 3. Sort by dollar amount × inverse sentiment so the most expensive low-confidence renewals surface first. Output: - A table: vendor · contract value · renewal date · sentiment · owner · last approver. - A short summary of the top three "should we be auto-renewing this?" candidates, each with the two strongest quoted moments of internal concern.
See it work
Run it from
How it runs
- 01Copy the prompt into any agent connected to Sentra over MCP.
- 02The agent reads the company memory, scoped to what you are allowed to see.
- 03One grounded answer comes back, with every line traceable to its source.
Or automate it with Actions
The same prompt runs as a Sentra Action: on a schedule, or on a semantic trigger. Output lands in Slack or email, and every send waits for your approval.
Trigger idea: procurement standup
Next 60 days · 5 auto-renewals
DataViz Pro · $48k · act
sentiment · 9 mentionsNegative sentiment, duplicate capability, alternatives already priced by two teams.
DeskSuite · $22k · shrink
usage + invoices60% of seats show no activity in 90 days.
CloudRelay · $30k · keep
threadsNeutral-to-positive, load-bearing in two services, no complaints on record.
Plus two small
$6k combined, no signal either way; renew and ignore.
The prompt above becomes this. Fictional data, real mechanics: every line cites the meeting, thread, or record it came from.
Without Sentra
- 01Pull every contract with an auto-renew clause from the contract management system.
- 02Filter to those with renewal dates in the next 60 days.
- 03For each vendor, re-process internal interactions over the last 12 months to compute aggregate sentiment.
- 04Pull billing data for the contract value.
- 05Search procurement records for the last approver.
- 06Sort by value × inverse sentiment.
- 07Compose the table and the top-three deep-dive.
~130,000 tokens
With Sentra
- 01Filter `Contracts` where auto_renew = true and `renewal_date` < 60 days.
- 02For each, attach `Vendor` aggregate sentiment, contract value, owning `Actor`, last approver — all typed.
- 03Sort by value × (1 - sentiment).
- 04Compose the table and the top-three concerns.
~32,000 tokens