Blog Details

Licensing decisions made at the start of a project quietly set your cost base for years. By the time the invoice looks wrong, the user roles, the module split and the renewal dates have all been fixed by someone who was optimising for go-live, not for the next three renewals.

Two failure modes show up again and again. Over-licensing is the quiet one — full licences handed to people who only ever read a report, paid for every month until someone audits the list. Under-licensing is the loud one, and it surfaces at the worst possible time: during a vendor audit, with back-dated true-ups attached.

Map roles before you map licences

The cheapest compliant combination falls out of the user role map, not the price list. Someone approving purchase orders, someone posting journals and someone glancing at a dashboard need three different licence types. Model those roles against the vendor's own definitions first, and the licence count stops being a negotiation and starts being arithmetic.

Keep the entitlement record yourself

When an audit lands, the difference between a week of work and a month of it is whether you can answer from your own records. That means:

• a live entitlement list, not a folder of purchase confirmations
• usage reviewed against that list on a schedule, not on discovery
• a renewal calendar with rightsizing built into it
• cost modelled before commitment, so the true-up is never a surprise

We advise on and supply Microsoft and Oracle licensing, model the options against real usage, and manage renewals and true-ups so the spend tracks what the business actually consumes.