Insights on SaaS spend, licenses, and renewals

One hundred seats, as billed

Both groups renew at the same price. Only one of them logs in.

Attention paid to the contract, over its life

The second spike is always shorter than the first, and always more expensive.

Vendor ownership, as actually recorded

The vendor has a named owner for every one of these accounts. The list is only vague on one side.

Four years of nothing unusual

Every step was described the same way. Only the total looks different.

Where the software spend comes from

Finance can see the total. The total is the only part that is easy to see.

Counting the stack

The gap is not made of big platforms. It is made of small subscriptions nobody thought worth mentioning.

The contract term, drawn to scale

The clause is not hidden. It is just scheduled for the one month of the year when everyone is busy with something else.

Preparation time before the same renewal

Most negotiations are decided by this chart, not by anything said in the call.

Signs a portfolio has not been reviewed in a while

If more than one or two of the left column sounds familiar, a structured review usually surfaces more than it costs.

The findings that show up in almost every portfolio review

The pattern is consistent because the cause is consistent: purchasing is decentralised and nobody owns the aggregate view.

The same concern, two very different positions

Nobody panics on purpose. Panic is what preparation turns into when it starts too late to become anything else.

Where preparation time actually converts into leverage

Every real source of leverage, a competing quote, a usage right-size, a documented service issue, takes weeks to assemble properly.

Where a renewal negotiation is usually decided

The opening sets the tone. The two or three exchanges after it decide how much of that opening actually holds.

What a written plan covers, and where it runs out

Most leverage comes from preparation. What a document cannot do is react to the shape of a counter it never saw.

What a single audit is still worth, cycle by cycle

The failure mode is never one dramatic mistake. It is drift, compounding quietly until the next audit finds the same things.

What a renewal process needs in place to keep running without heroics

None of this is exotic. It is difficult to prioritise, which is a different problem, and the reason most companies never quite build it.

What diligence scrutinises, and what it usually skips

Individually modest, collectively real. None of it is hidden: it sits in contracts the target already holds, and nobody goes looking.

What the acquisition changes on the vendor's side of the contract

Change-of-control clauses are the exception, not the rule. Absent one, the acquisition is invisible to the contract.

One budget line, two different negotiations

Pushing back on "the AI pricing" without knowing which column you are in aims at the wrong lever in both cases.

What you can forecast, and what actually moves the bill

Two of these come off a headcount plan. The other four decide the invoice.

Nobody approved an overage. It arrived anyway.

Every month here is a reasonable adoption story. The invoice reads them all at once.

Why "why did this go up" has no owner

Your term, and the model lifecycle running underneath it

Traditional SaaS review asks what happens if the price changes. This asks what happens if the product does.

What a standard contract review covers

The bottom three rarely live in the document the commercial review actually opens.

Where the two contract shapes diverge

Most review checklists were written for the middle column and run unchanged on the right one.

One number you cannot evaluate, or two you can

What the vendor list says, and what the card statement says

A ban moves the right-hand column further out of sight. A registration step moves it left.

Four questions between a fast pilot and an unreviewed commitment

This is minutes, not a procurement cycle. Skipping it is what turns speed into exposure.