Jake L. Muller Principal Software Engineer

Platform · Garnet Health · 2025

Vendor Contract Management

Centralising vendor contracts and the data controllers around them, replacing legacy third-party software.

  • RoleArchitect
  • Year2025
  • StatusIn development
  • C#
  • ASP.NET MVC
  • MS SQL Server
  • React

How it works

In order: Intake; Review; Execute; Renew.INTAKE01REVIEW02EXECUTE03RENEW04CLOSED LOOPIn order: Intake; Review; Execute; Renew.01INTAKE02REVIEW03EXECUTE04RENEWCLOSED LOOP, RETURNS TO 01
What this shows

A closed loop: intake, review, execute, renew, and back.

  1. 01 · The problem

    Contract data sat with a third party. Renewal dates, surviving obligations, and the owning department were answerable only by asking the vendor whose contract was in question.

  2. 02 · What I decided

    Bring the data controllers in-house first, workflow second. Owning the contract record is what makes the renewal conversation a negotiation rather than a renewal notice.

  3. 03 · The outcome

    In development, sized against the incumbent licence at six figures of projected annual operating expenditure reduction.

Projected
100K+ / yr
Stage
In build
Platforms
Web