IT procurement, vendors and contracts
A cloud commitment is ending, a software agreement is reaching its renewal date, a price grid is changing: we prepare the decision on what you actually consume and pay, with your procurement team and your IT department, then we check that the invoice matches what was signed.
This is your situation if
- A cloud or software agreement reaches its renewal date with no negotiating position
- A consumption commitment risks being under-consumed, or exceeded
- Invoiced prices do not always follow the contract's price grid
- Nobody keeps the calendar of renewal dates and notice periods
Format
Embedded: when vendor committees are regular, a KeeFinops FinOps practitioner keeps the register and prepares each committee.
Fixed scope: per renewal or per negotiation.
The product alongside: the cloud commitment schedule, recomputed at every collection.
Variable fee: as an option and in pilot only, on some negotiations, with a baseline written down at scoping.
From actual usage to signature, then to the invoice
A spend map
By vendor, by contract and by entity, drawn from invoices and contracts.
A contract register
Renewal dates, notice periods, indexations, consumption commitments and entitlements, with the exit windows.
A negotiating position
Priced on your actual usage and your invoiced prices, with scenarios at the same level: renew, reduce, switch, exit.
A commitment purchase plan
Reservations, Savings Plans and CUDs at the observed discount, after reduction.
Invoiced price checks
Line by line against the contractual price grid, gaps quantified for your vendor.
Prepared vendor committees
Agenda, consumption against commitment, decisions recorded.
We prepare the decision, you sign
- Practiced and tooled: cloud procurement and commitments
- Practiced: software vendor renewals, management of cloud providers and software vendors, contract review and invoiced price checks
- Tooled: commitment schedule
- Out of scope: hardware, telecoms, service contracts
The same file, at your scale
With your procurement department
Category plan, vendor committees, group commitments consumed by the entities.
Large enterprisesA renewal prepared
A one-off negotiation, prepared on your actual usage.
SMEs and scale-upsYour agreements and your clients'
Your cloud commitments and software agreements, and those of your clients in co-delivery.
IT service providersAlready practiced in the field
- Cloud category plan and FinOps business case handed to the Procurement department of a large services group (client case)
- Invoiced prices checked SKU by SKU against the contractual price grid, and vendor committees (client case)
- Strategic and operational committees with several cloud providers, and trade-off between marketplace and direct purchase
Before the next renewal date
Thirty minutes to list your contracts, your renewal dates and the available data.