Vendors and contracts

Vendor management that keeps contracts and IT budgets close

Keep vendors, contracts, budgets, purchase activity, and renewal context close to operational modules.

In short

How are vendors linked to what they supply?

Vendors are referenced by assets, purchase orders and maintenance records, so from a supplier you can see the hardware they provided and the orders raised against them, and licences carry their own vendor details.

Product proof

Already live in the product

Backed by app modules
Protected app route: /vendors

Running in production today: vendor management, vendor contracts, and IT budget tracking.

How it works

Built around real workflows

Highlights below describe capabilities already present in the protected app behind this page.

  • Vendor records
  • Contract tracking
  • Budget visibility
  • Purchase workflow alignment
Workflow

What teams can do here

  1. Step 1Register vendors
  2. Step 2Track contracts
  3. Step 3Connect procurement
  4. Step 4Review budget impact

How it works

  1. 01

    Keep a single vendor catalogue

    Store each supplier once — contact person, email, phone, address, website and tax ID — and mark vendors active or inactive without losing their history.

  2. 02

    Track contracts and SLAs

    Attach contracts to a vendor with start and end dates, contract value, SLA terms and the signed document. Status auto-updates to expiring or expired as the end date approaches.

  3. 03

    Get ahead of renewals

    Each contract carries a notice window (30 days by default) and an auto-renew flag, so contracts move to “expiring” in time for you to renegotiate or cancel.

  4. 04

    Watch the budget impact

    IT budget categories hold an allocation per fiscal year, and approved expenses roll up against them — showing spent, remaining and a status of on-track, warning or over-budget.

“

A worked example

Say a regional hospital’s IT team manages 22 suppliers — imaging vendors, an MSP, telecom, printer leasing. Each is entered once with contacts and tax IDs, and every support contract is attached with its value, SLA terms and the signed PDF. The MSP’s ₹18-lakh annual contract flips to “expiring” 30 days before its end date, prompting a renewal review with the paperwork already to hand. Meanwhile the year’s support spend is logged as approved expenses under an “AMC & Support” budget category, which shows spent, remaining and a warning state as it nears its allocation — before finance discovers the overrun at year-end.
Vendors are referenced by assets, purchase orders and maintenance records, so from a supplier you can see the hardware they provided and the orders raised against them, and licences carry their own vendor details.

Renew on your schedule, not the vendor’s

One supplier catalogue with contracts, SLA terms, signed documents and budget rollups — plus an expiring flag that fires 30 days before the end date.