Features of the contract renewal management software
These are the features that exist in the product today. Each section says what it stores and gives a concrete example.
Vendor and contract register
Every vendor has one or more agreements. Each agreement stores a title, annual cost estimate, currency, auto-renew flag, status and a link to the source clause. You add them by hand in the app.
What it stores or shows: Vendor name, category, agreement title, annual cost, auto-renew flag, status, source URL.
Example: Add "Harbor CRM, Annual subscription, $18,000, auto-renews" and link the order form that states the term.
Three separate dates
Each agreement keeps a renewal date, a notice deadline and a decision lead time. A person marks the notice deadline as verified against the contract. The software never guesses a date.
What it stores or shows: Renewal date, notice deadline, decision lead days, who verified the notice date and when, and where the date came from.
Example: The renewal date is Sep 30, the notice deadline is Aug 31 and the lead time is 30 days, so the internal decision target is Aug 1.
CSV import
Import many contracts at once from a CSV file. Rows are validated before they are saved, and imported dates are marked as imported until a person confirms them.
What it stores or shows: The same agreement fields as manual entry, with the date provenance set to CSV import.
Example: Upload a CSV file exported from your spreadsheet with vendor, title, renewal date and notice deadline columns and review the validation result before saving.
Review routing for Business, Finance and IT
Open a renewal review for an agreement and invite a reviewer for each role. The invitation is an email with a personal link. Reviewers answer keep, reduce, stop or unsure and give a short reason.
What it stores or shows: Reviewer role, email address, status, selection, rationale and submission time.
Example: Invite the IT lead to a review of Cedar Hosting. She answers "reduce" and explains that two environments are unused.
Reviewer page without an account
The link in the invitation opens a single page where the reviewer sees the contract summary and submits an answer. The link is hashed in the database, expires after 14 days and works once.
What it stores or shows: A hashed token, its expiry and the time it was used.
Example: A Finance reviewer clicks the link from the email, answers in under a minute and never creates a login.
Decision ledger
An authorized person records the final decision: renew, renegotiate, prepare cancellation or defer. The decision is saved with its rationale and evidence links next to every reviewer answer.
What it stores or shows: Final decision, rationale, decision maker, decision time, evidence links and notes.
Example: Record "renegotiate" for Atlas Analytics with a link to the usage report and a note that the price rises 20 percent at renewal.
Dashboard and activity timeline
The overview shows which notice deadlines are close, which dates are still unverified and which reviews wait for answers. The activity timeline lists every status change with the actor and source.
What it stores or shows: Read-only views of contracts, reviews and audit events. Audit events keep actor, action, previous value, new value and source (web, MCP, system or email link).
Example: See that the Harbor CRM notice deadline is 12 days away and that Finance has not answered yet.
Read-only MCP endpoint
The Growth plan includes an MCP endpoint with six read-only tools. You create a token in Agent Setup. The token is scoped to one workspace and only its hash is stored.
What it stores or shows: Token hash, label, creation time and last use. Tools read contracts, reviews and evidence and change nothing.
Example: Ask Claude Code which notice deadlines are unverified and get the list from your workspace. See the MCP page for setup.