Software For Vendor Management

Vendor management covers the relationship with suppliers: who they are, what you have agreed, what they cost, whether they are compliant, and how well they perform. It overlaps procurement, contract management, and risk, and products in this space usually lead with one of those and treat the rest as secondary.

We sell source code you clone and run yourself, so there is nothing hosted here. For most organisations the first version of this is a spreadsheet with reminders, and it is worth saying why that works before describing what replaces it.

The four jobs, and which one you actually need

The middle column is the one where spreadsheets fail fastest and where the risk is real. Insurance certificates, right-to-work checks, safety accreditations, and data processing agreements all expire, and an expired document usually goes unnoticed until it matters.

Renewal dates are the highest-value field you will ever store

Most of the immediate saving from vendor management comes from one mechanism: knowing that a contract renews in ninety days, before the notice period closes.

Auto-renewal clauses with a notice window are common, and missing the window commits you to another term at whatever the uplift is. A list of contracts with a renewal date, a notice period, and a named owner, with a reminder set well before the deadline, captures most of that value with no software purchase at all.

If you do nothing else after reading this, build that list.

What separates the products

Beyond the repository, three things are worth testing.

Document expiry handling should chase the supplier rather than notify you. A system that emails your procurement team that a certificate expired has moved the work rather than removed it; one that emails the supplier a request and records the response has actually helped.

Approval workflow should match how your organisation really approves suppliers, which is usually less tidy than the demo. Ask what happens when the approver is away and whether delegation is possible without giving away their account.

And self-service supplier portals sound attractive and only work if suppliers use them. A small supplier will not log into a portal to upload a certificate; they will reply to an email. Systems that accept both tend to stay current.

When organisations build

Not usually for their own vendors, because the calendar-and-documents shape is well served and the compliance rules are mostly generic.

The build case is again the service version: a consultancy or managed service provider tracking suppliers on behalf of clients, a platform where each customer manages their own supplier base, a marketplace that has to verify and monitor the businesses on it. Marketplaces in particular need this and rarely find an off-the-shelf fit, because verification is part of their product rather than an internal process.

What you would start from here

There is no vendor management in this stack. No suppliers, no contracts, no documents, no expiry tracking, no approvals, and no spend analysis.

What the Vault template provides is the application: organizations as the boundary each client's supplier base lives in, roles and invitations so a client sees their own vendors, a Hono backend with Prisma and Kysely on Postgres, an admin app, and Stripe billing if you charge for access. The notifications pack covers in-app and email notification delivery, which is the mechanism the renewal and expiry reminders described above would use, though the schedule and the rules are yours to write.

You would write the supplier and contract records, the document model with expiry dates, the reminder schedule, and the approval states. Model the reminder as a job that runs against dates rather than as something set when the record is created, because dates change and a reminder scheduled once will fire against the old date.

If you are managing your own suppliers, start with the renewal list described above and see whether it is enough. The packs below are for the version you sell to somebody else.