WEBVTT

00:00:00.020 --> 00:00:03.410
Hey everybody, and welcome back to the Operational ITAM Podcast.

00:00:03.920 --> 00:00:07.550
I'm Bill Van Nort, and today we are finally talking about the one meeting in

00:00:07.550 --> 00:00:09.960
this entire discipline where you hold the cards.

00:00:10.699 --> 00:00:15.660
31 days ago, on the 1st of July, Microsoft raised list prices across most of

00:00:15.660 --> 00:00:18.140
the Microsoft 365 commercial suites.

00:00:18.810 --> 00:00:24.050
Office 365 E3 went from $23 per user per month to $26.

00:00:24.830 --> 00:00:29.170
Microsoft 365 E5 went from $57 to $60.

00:00:29.920 --> 00:00:33.280
Some of the frontline plans went up by as much as 43%.

00:00:34.060 --> 00:00:35.479
That is not the interesting part.

00:00:36.350 --> 00:00:39.740
The interesting part is that Microsoft announced all of it on the 4th of December,

00:00:40.060 --> 00:00:43.799
seven months of warning, published on their own blog, with a table,

00:00:43.950 --> 00:00:46.030
with the percentages, with the effective date.

00:00:46.640 --> 00:00:49.860
Everybody got the memo. Almost nobody had a plan.

00:00:50.390 --> 00:00:56.220
That gap between the memo and the plan is the entire subject of today's episode.

00:00:56.980 --> 00:01:00.550
Good morning, good afternoon, or good evening, wherever you're listening from.

00:01:01.050 --> 00:01:05.099
This is the show where we take the unglamorous machinery of enterprise technology

00:01:05.209 --> 00:01:07.849
and make it make sense. Grab your coffee.

00:01:08.780 --> 00:01:13.770
Today, for the first time in this series, we are playing offense. Here's the premise.

00:01:14.459 --> 00:01:19.290
Look back at what we've covered. The audit letter that arrives on somebody else's schedule.

00:01:20.010 --> 00:01:22.510
The settlement, where you're negotiating from behind.

00:01:23.260 --> 00:01:28.150
Shadow IT, which happens whether you sanction it or not Disposal,

00:01:28.540 --> 00:01:32.580
where the best possible outcome is that nothing happens to you Every one of

00:01:32.580 --> 00:01:36.620
those is reactive, something arrives and you respond well or badly,

00:01:37.400 --> 00:01:38.670
The renewal is different,

00:01:39.570 --> 00:01:43.430
The renewal is the only recurring event in asset management where the date is

00:01:43.430 --> 00:01:48.270
known years in advance Where the other side needs something from you And where

00:01:48.270 --> 00:01:54.270
you get to decide when the work begins And we blow it consistently as a profession.

00:01:54.860 --> 00:01:58.680
Let me give you the numbers and I'll name the source because on this show, we do that.

00:02:00.060 --> 00:02:03.720
Zylo publishes an annual benchmark called the SaaS Management Index.

00:02:04.330 --> 00:02:10.169
The 2026 edition says the average organization runs 305 applications and spends

00:02:10.169 --> 00:02:16.230
roughly $55.7 million a year on SaaS, up about 8% year over year,

00:02:16.590 --> 00:02:18.919
while the application count stayed essentially flat.

00:02:19.500 --> 00:02:23.470
Read that again. Flat application count. 8% more money.

00:02:25.889 --> 00:02:29.900
The growth isn't sprawl anymore. It's price. Same report.

00:02:30.220 --> 00:02:34.790
79% of IT leaders saw a price increase at renewal in the last 12 months.

00:02:35.300 --> 00:02:39.800
78% got hit with unexpected charges tied to consumption or AI pricing.

00:02:40.330 --> 00:02:47.669
And 61%, 61, cut a project or an initiative to pay for software cost increases they did not plan for.

00:02:48.320 --> 00:02:51.690
That last statistic is the one I'd put on a slide for your CFO.

00:02:52.220 --> 00:02:56.080
Software renewals are now canceling roadmap items. Not headcount,

00:02:56.400 --> 00:02:58.680
not capital projects. Roadmap.

00:02:59.230 --> 00:03:01.760
So here's my thesis, and it is not subtle.

00:03:02.480 --> 00:03:07.190
In a renewal, timing beats tactics. The clever negotiator who starts 60 days

00:03:07.190 --> 00:03:10.270
out loses to the mediocre one who started 18 months out.

00:03:11.010 --> 00:03:15.350
Every lever you'll hear about today takes months to build and four seconds to deploy.

00:03:16.010 --> 00:03:20.360
Which brings us to today's framework. I call it the 18-month clock.

00:03:21.100 --> 00:03:24.880
Four positions on the face, and each one has exactly one job.

00:03:25.490 --> 00:03:28.070
Position one, 18 months out, count.

00:03:28.890 --> 00:03:32.650
This is your effective license position from episode three, aimed at a specific

00:03:32.650 --> 00:03:34.550
agreement with a specific end date.

00:03:35.200 --> 00:03:38.710
Entitlements on the left, deployments on the right, truth in between.

00:03:39.020 --> 00:03:42.960
But for a renewal, you need a third column that an audit never asks for, usage.

00:03:43.610 --> 00:03:45.250
Not deployed, used.

00:03:46.050 --> 00:03:49.570
Logged in during the last 90 days and doing something once they got there.

00:03:50.440 --> 00:03:53.440
There's a version of shelfware we didn't fully cover in episode 3.

00:03:53.900 --> 00:03:59.190
The license that is deployed, assigned, compliant, defensible, and completely idle.

00:03:59.760 --> 00:04:03.220
It survives every audit. It fails every business case.

00:04:03.780 --> 00:04:08.130
That same Zylo Index puts average license utilization at about 54%,

00:04:08.490 --> 00:04:11.530
which means roughly a third of what you bought is doing nothing at all.

00:04:12.190 --> 00:04:17.110
At 18 months, that dead third is an asset. It's the thing you're going to stop paying for.

00:04:17.930 --> 00:04:21.260
At 60 days, it's just a number you didn't have time to verify,

00:04:21.670 --> 00:04:24.930
and the vendor will happily tell you their telemetry disagrees with yours.

00:04:25.779 --> 00:04:31.000
Position 2. 12 months out. Decide. Not decide whether to renew.

00:04:31.870 --> 00:04:34.620
Decide what you want the estate to look like on the other side.

00:04:37.600 --> 00:04:41.610
Most programs skip this, and it costs them everything. They go straight from

00:04:41.610 --> 00:04:45.480
counting to negotiating with no target state, so the vendor supplies one.

00:04:46.360 --> 00:04:49.730
The vendor's target state is always the same. More of everything.

00:04:50.010 --> 00:04:52.710
Longer term. Newest tier bundled in.

00:04:53.390 --> 00:04:57.980
Yours is a specific sentence. 1,100 seats instead of 1,400.

00:04:58.430 --> 00:05:04.279
Two tiers instead of four. And the analytics module dropped entirely because 40 people use it.

00:05:04.800 --> 00:05:08.430
Write that sentence at 12 months and get your business owners to agree to it

00:05:08.430 --> 00:05:11.089
at 12 months when nobody is under deadline pressure.

00:05:12.170 --> 00:05:15.560
Try to take 300 seats from a department six weeks before renewal,

00:05:15.560 --> 00:05:18.620
and you'll lose that fight internally before you ever reach the vendor.

00:05:19.300 --> 00:05:23.170
Position 3. Nine months out. Build the alternative.

00:05:23.870 --> 00:05:27.690
This is the position that actually generates leverage, and it's the one that gets skipped.

00:05:28.380 --> 00:05:32.339
Leverage in a renewal is not persuasion. It's not relationship.

00:05:32.800 --> 00:05:34.710
It's not how well you know your account rep.

00:05:35.380 --> 00:05:40.720
Leverage is a documented, costed, credible answer to the question, and what if we don't.

00:05:41.339 --> 00:05:45.000
Credible is the operative word, not a threat, not a bluff.

00:05:45.470 --> 00:05:49.839
An actual analysis, what it would cost to move, how long it would take,

00:05:50.160 --> 00:05:52.210
who would do it, and what breaks.

00:05:52.940 --> 00:05:56.670
You may never execute it, but you have to be able to hand somebody a page.

00:05:57.360 --> 00:06:02.890
Let me make that concrete with two live examples, both of which are still unfolding right now.

00:06:03.600 --> 00:06:06.600
Example 1. Broadcom and VMware.

00:06:07.339 --> 00:06:11.480
Perpetual licensing ended, the catalog collapsed into a handful of subscription

00:06:11.480 --> 00:06:16.700
bundles, and pricing moved to a per-core model with minimum core counts per processor.

00:06:17.380 --> 00:06:21.750
Independent advisory firms tracking these renewals report opening quotes running

00:06:21.750 --> 00:06:23.610
two to five times prior cost.

00:06:24.170 --> 00:06:29.700
Distributor communications reported by the Register in 2025 described the minimum

00:06:29.700 --> 00:06:36.420
order jumping from 16 cores to 72 per line, plus a 20% penalty for letting a

00:06:36.420 --> 00:06:38.650
subscription lapse past its anniversary.

00:06:39.360 --> 00:06:43.290
Here's the part that matters. Those same firms report that customers who arrived

00:06:43.290 --> 00:06:44.580
with a right-size core count,

00:06:45.080 --> 00:06:49.900
and a credible migration plan settled 15-30% below the opening number,

00:06:50.370 --> 00:06:55.190
and that opening quotes routinely overstated the actual footprint by 20-40%.

00:06:55.190 --> 00:06:57.850
20-40% of the quote was error.

00:06:58.970 --> 00:07:02.600
The people who found it had counted their own cores before the quote arrived.

00:07:03.180 --> 00:07:09.940
Example 2. Oracle and Java. In January of 2023, Oracle replaced its per processor

00:07:09.940 --> 00:07:15.760
and named UserPlus metrics with the Java SE Universal subscription, priced per employee.

00:07:16.290 --> 00:07:19.860
Every employee. Not Java users. Not developers.

00:07:20.210 --> 00:07:25.330
Everyone on the payroll. And Oracle's default reading includes contractors with system access.

00:07:25.940 --> 00:07:29.810
List has run around $15 per employee per month at the low bands.

00:07:30.440 --> 00:07:35.720
Do that math for a 10,000-person company, and it's roughly $1.8 million a year

00:07:36.140 --> 00:07:38.860
for a runtime that might live on 200 servers.

00:07:39.560 --> 00:07:40.730
The market responded.

00:07:41.480 --> 00:07:46.490
Research from the ITAM forum and Azul found around 79% of organizations have

00:07:46.490 --> 00:07:49.490
already migrated, are migrating, or plan to.

00:07:50.220 --> 00:07:56.990
OpenJDK is free. Adoptium, Coretto, Zulu, Red Hat, and Microsoft all publish builds.

00:07:57.610 --> 00:08:01.650
So the customer who walks into an Oracle Java renewal with a completed estate

00:08:01.650 --> 00:08:06.470
sweep is having a completely different conversation than the one who walks in with a purchase order.

00:08:07.230 --> 00:08:11.590
Both examples make the same point. The alternative doesn't have to be executed.

00:08:11.870 --> 00:08:15.080
It has to exist, on paper, with numbers.

00:08:15.850 --> 00:08:23.200
Position 4. Six months out. Ask. Now, and only now, you open the commercial conversation.

00:08:24.250 --> 00:08:27.320
You have your count, your target state, and your alternative.

00:08:28.280 --> 00:08:32.570
Six months gives both sides room to move, room to escalate internally,

00:08:32.920 --> 00:08:37.950
and room for you to walk away and come back, which is a move you cannot make at 60 days.

00:08:38.660 --> 00:08:43.650
And that's the clock. Count. Decide. Build. Ask.

00:08:44.720 --> 00:08:51.270
18, 12, 9, 6. There's a fifth position, and it's the one most of you are actually

00:08:51.270 --> 00:08:53.980
standing on. Call it the 60-day cliff.

00:08:54.490 --> 00:08:58.820
Inside 60 days, you are not negotiating. You are accepting, possibly with a

00:08:58.820 --> 00:09:01.630
small discount attached to make it feel like a negotiation.

00:09:02.070 --> 00:09:06.910
Everyone in the room knows it. The vendor knows it best. Let's take a quick break.

00:09:07.690 --> 00:09:10.940
If you're getting value from this show, subscribe wherever you're listening.

00:09:11.240 --> 00:09:14.340
And if you know someone with a renewal coming up, send them this episode.

00:09:14.679 --> 00:09:17.270
It's free and it might be worth six figures to them.

00:09:18.110 --> 00:09:22.309
Every episode with full transcripts is at operationalitam.com.

00:09:22.920 --> 00:09:25.559
Okay, now on to part two, the traps.

00:09:26.200 --> 00:09:30.429
I'm going to give you five and every one of them I have either walked into personally

00:09:30.770 --> 00:09:33.740
or watched someone walk into from about 10 feet away.

00:09:34.340 --> 00:09:36.260
Trap one, the notice window.

00:09:36.940 --> 00:09:40.290
Almost every agreement you hold contains an automatic renewal clause with the

00:09:40.290 --> 00:09:43.770
notice period. 30 days, 60 days, 90 days.

00:09:44.270 --> 00:09:48.100
Miss it and you have renewed, at whatever terms the contract specifies,

00:09:48.360 --> 00:09:49.970
which are rarely the terms you wanted.

00:09:50.570 --> 00:09:56.650
The operational fix is embarrassingly simple. Stop tracking renewal dates. Track notice dates.

00:09:57.309 --> 00:09:59.220
The renewal date is decoration.

00:10:00.049 --> 00:10:04.420
The notice date is the real deadline, and it sits one to three months earlier.

00:10:05.220 --> 00:10:08.580
Put it in the calendar, put a second reminder 30 days ahead of that,

00:10:08.940 --> 00:10:10.380
and hang the whole clock off it.

00:10:11.850 --> 00:10:15.230
Procurement reporting suggests notice windows have been quietly shrinking,

00:10:15.610 --> 00:10:22.090
60 days becoming 30, so the clause you read in 2022 may not be the clause you're under today.

00:10:22.720 --> 00:10:25.110
Read the current paper, not your memory of it.

00:10:26.030 --> 00:10:31.160
Trap 2 – The Uplift Clause This is the automatic annual increase written into

00:10:31.160 --> 00:10:35.799
the contract itself, and it's the single most expensive sentence in enterprise software.

00:10:36.840 --> 00:10:41.500
Aggregated procurement analysis puts auto-uplift clauses in the high 80% range

00:10:41.500 --> 00:10:45.580
of SaaS contracts, with typical asks around 11.5%.

00:10:46.220 --> 00:10:52.480
An 11% annual uplift, compounded over three years, is a 37% increase before

00:10:52.480 --> 00:10:54.100
anyone negotiates anything.

00:10:54.760 --> 00:10:59.250
The fix happens at signature, not at renewal. You want an explicit cap,

00:10:59.600 --> 00:11:03.929
not commercially reasonable increases, not silence, a number.

00:11:04.320 --> 00:11:07.480
If the vendor insists on an index, tie it to something published,

00:11:07.630 --> 00:11:10.160
CPI as standard, then cap the index.

00:11:10.470 --> 00:11:14.640
And get the cap to survive the renewal, so you're not renegotiating the ceiling every time.

00:11:15.350 --> 00:11:17.590
Opinion. Flagged as opinion.

00:11:18.380 --> 00:11:22.640
I would trade a point of first year discount for a hard uplift cap every single time.

00:11:23.460 --> 00:11:26.929
The discount is one year. The cap is the whole relationship.

00:11:27.720 --> 00:11:35.360
Trap 3. The Coterm. Your vendor offers to align all your agreements to one common date. For simplicity.

00:11:36.140 --> 00:11:40.150
For your convenience. Maybe with a little proration credit as a sweetener.

00:11:40.710 --> 00:11:43.270
Ask yourself whose convenience that actually is.

00:11:43.960 --> 00:11:47.720
Coterming builds one enormous renewal event covering products with completely

00:11:47.720 --> 00:11:49.160
different levels of criticality.

00:11:49.660 --> 00:11:52.610
And once they're on one paper, you can't walk away from part of it.

00:11:53.360 --> 00:11:57.990
The module nobody uses is now welded to the platform your order-to-cash process runs on.

00:11:58.720 --> 00:12:02.070
That's not simplification. That's consolidation of the vendor's leverage,

00:12:02.290 --> 00:12:04.010
and you paid a proration credit for it.

00:12:04.760 --> 00:12:09.100
There are legitimate reasons to co-term. Administrative overhead is real,

00:12:09.320 --> 00:12:13.049
and if you're a two-person team with 40 agreements, I understand the appeal.

00:12:13.630 --> 00:12:16.780
But make it a decision, not a favor you accepted.

00:12:17.510 --> 00:12:22.370
Opinion flagged. My default is staggered deliberately so there's always a renewal

00:12:22.370 --> 00:12:25.290
in flight and the vendor always knows another one is coming.

00:12:25.940 --> 00:12:31.990
Trap 4. The Discount Shell Game The vendor quotes you a discount off list price. You feel good.

00:12:32.580 --> 00:12:34.900
22% off list sounds like a win.

00:12:35.600 --> 00:12:40.130
List price is a number the vendor invents and controls. If list went up 13%

00:12:40.130 --> 00:12:44.940
in July, a 22% discount off the new list may still be more money than you paid

00:12:44.940 --> 00:12:46.190
last year off the old one.

00:12:47.140 --> 00:12:53.060
So never negotiate against list. Negotiate against your own unit price paid last term.

00:12:53.770 --> 00:12:59.400
Dollars per user per month, per core, per employee. Reduce it to a unit and

00:12:59.400 --> 00:13:01.510
compare unit to unit across terms.

00:13:02.240 --> 00:13:05.840
That single discipline will catch more money than every other tactic in this

00:13:05.840 --> 00:13:10.710
episode combined, because it's the one thing the quote is structured to prevent you from seeing.

00:13:11.510 --> 00:13:16.550
Trap 5. The Multi-Year Commitment Multi-year is often the right answer.

00:13:16.980 --> 00:13:20.870
Price protection has genuine value, especially in a market where list prices

00:13:20.870 --> 00:13:22.360
move the way they move this year.

00:13:23.180 --> 00:13:27.330
But be clear about what you're selling to buy it. You're selling optionality,

00:13:27.870 --> 00:13:32.460
the right to reduce quantity, the right to leave, and often the right to renegotiate

00:13:32.460 --> 00:13:33.540
when the business changes.

00:13:34.260 --> 00:13:40.100
So price them. Three things to insist on. One, a true down right at each anniversary,

00:13:40.290 --> 00:13:43.940
even capped at 10 or 15%, a floor you can descend to.

00:13:44.530 --> 00:13:48.020
Two, the uplift cap, applied to every year of the term.

00:13:48.590 --> 00:13:52.300
Three, an assignment clause that survives a merger or a carve-out,

00:13:52.770 --> 00:13:55.740
because if your company gets acquired and the license doesn't transfer,

00:13:56.080 --> 00:13:58.010
you just bought a very expensive coaster.

00:13:58.620 --> 00:14:03.680
That's the five. Let's do a listener question. This one comes from Indianapolis,

00:14:03.680 --> 00:14:05.550
and it is painfully well-timed.

00:14:05.730 --> 00:14:10.410
He writes, Our renewal is in six weeks and the quote doubled. What do I do?

00:14:11.190 --> 00:14:15.330
I'm going to answer this honestly, because you deserve that more than you deserve encouragement.

00:14:15.910 --> 00:14:20.170
At six weeks, you cannot win this negotiation. The leverage isn't there.

00:14:20.790 --> 00:14:23.160
Anyone who tells you otherwise is selling a webinar.

00:14:24.000 --> 00:14:27.200
But you can do three things, and all three are worth real money.

00:14:27.780 --> 00:14:31.480
First, stop negotiating price and start negotiating time.

00:14:32.060 --> 00:14:37.520
Ask for a short-term extension, three months, six months, at current pricing or close to it.

00:14:38.200 --> 00:14:41.610
Vendors grant these more often than you'd think, because it keeps the revenue

00:14:41.740 --> 00:14:43.070
and keeps you at the table.

00:14:43.800 --> 00:14:47.620
That extension isn't a concession you won, it's runway you bought,

00:14:47.960 --> 00:14:51.700
and you spend every day of it doing positions one and three of the clock.

00:14:52.200 --> 00:14:54.770
Second, attack quantity, not rate.

00:14:55.620 --> 00:14:57.700
You will not move their rate in six weeks.

00:14:58.670 --> 00:15:02.770
You may absolutely be able to move your count, because that's your data, not theirs.

00:15:03.840 --> 00:15:06.910
Pull 90 days of usage. Find the inactive seats.

00:15:07.770 --> 00:15:11.450
Every seat you remove comes off at full price, which is a better outcome than

00:15:11.450 --> 00:15:12.930
any discount you were going to get.

00:15:13.480 --> 00:15:17.950
Third, and this is the one people skip, read the actual clause that doubled it.

00:15:18.810 --> 00:15:24.100
An uplift clause? A tier change? A metric change, like the Oracle employee metric?

00:15:24.560 --> 00:15:26.100
A module that used to be optional?

00:15:26.940 --> 00:15:30.360
The quote doubling has a cause, and the cause is written down somewhere.

00:15:30.740 --> 00:15:32.080
You can't argue with a number.

00:15:32.700 --> 00:15:36.280
You can absolutely argue with a clause applied incorrectly, and I've seen that

00:15:36.280 --> 00:15:38.010
go the customer's way more than once.

00:15:38.780 --> 00:15:42.120
Then, the day it's signed, calendar next year's notice date,

00:15:42.120 --> 00:15:45.400
and start the clock. This year, you're paying tuition.

00:15:46.550 --> 00:15:51.410
Now let's go back to the library. We have been in this library since episode one.

00:15:51.980 --> 00:15:55.850
In episode three, I told you the hardest truth in software asset management.

00:15:56.450 --> 00:15:57.960
None of these books are yours.

00:15:58.720 --> 00:16:01.670
Every volume on loan, every loan with terms.

00:16:02.460 --> 00:16:06.860
In episode five, the late fee notice arrived, and I told you the librarian doesn't

00:16:06.860 --> 00:16:08.360
actually want your late fees.

00:16:08.820 --> 00:16:11.180
The librarian wants you borrowing more books.

00:16:11.850 --> 00:16:15.750
Today we go to a different room. Down the hall, past circulation,

00:16:15.750 --> 00:16:20.030
there's an office with a wall of binders and a very tired person inside.

00:16:20.800 --> 00:16:25.160
That's the serials department. Journal subscriptions. The renewals.

00:16:26.480 --> 00:16:29.430
And the serials budget works exactly like your software budget.

00:16:30.070 --> 00:16:34.030
The publisher sells a bundle, take the whole package, get a better per title

00:16:34.030 --> 00:16:36.010
rate, sign for multiple years.

00:16:36.720 --> 00:16:40.690
It renews quietly, it rises annually, and nobody reads most of it.

00:16:41.390 --> 00:16:46.220
This isn't a metaphor I'm inventing. In 2019, the University of California system

00:16:46.220 --> 00:16:50.280
walked away from its agreement with Elsevier, one of the largest academic publishers

00:16:50.280 --> 00:16:52.410
in the world. They canceled.

00:16:53.080 --> 00:16:58.360
The sky did not fall. Two years later, they signed a new agreement on terms they actually wanted.

00:16:59.090 --> 00:17:02.760
They could do that for one reason. They knew exactly which journals the researchers

00:17:02.760 --> 00:17:05.599
were reading, and how often, and could prove it.

00:17:06.330 --> 00:17:10.140
That's the whole lesson. The librarian who knows precisely which titles get

00:17:10.140 --> 00:17:14.460
opened has a completely different conversation with the publisher than the librarian who doesn't.

00:17:15.290 --> 00:17:20.460
Same publisher. Same bundle. Same price list. Different conversation.

00:17:21.210 --> 00:17:24.430
Because one of them has the usage data and the other one has a feeling.

00:17:25.160 --> 00:17:30.050
You are the librarian. Go get the usage data. Which brings us to today's principle.

00:17:30.540 --> 00:17:32.390
And let's take the whole run from the top.

00:17:32.900 --> 00:17:36.540
Hardware is a custody discipline. Software is an evidence discipline.

00:17:37.320 --> 00:17:41.840
Audit defense is a process discipline. Settlement is a commercial discipline.

00:17:42.790 --> 00:17:44.800
Shadow IT is a service discipline.

00:17:46.140 --> 00:17:51.099
Refresh is an economics discipline. Disposal is a liability discipline.

00:17:51.740 --> 00:17:55.990
And renewal is a leverage discipline. Leverage is not aggression,

00:17:56.099 --> 00:17:57.880
and it is not a personality trait.

00:17:58.170 --> 00:18:01.119
Leverage is preparation that arrived early enough to matter.

00:18:01.349 --> 00:18:05.420
It is a count you can defend, a target state your business already agreed to,

00:18:05.590 --> 00:18:07.550
and an alternative that exists on paper.

00:18:07.859 --> 00:18:10.930
Build those three things, and you barely have to negotiate at all.

00:18:11.210 --> 00:18:14.630
Show up without them, and no amount of skill in the room will save you because

00:18:14.630 --> 00:18:17.310
the deal was decided months before anyone sat down.

00:18:18.130 --> 00:18:22.310
Class dismissed. Here's your homework, and this one takes about 90 minutes.

00:18:23.020 --> 00:18:27.359
List every software agreement above whatever threshold matters in your organization.

00:18:27.990 --> 00:18:32.340
For each one, capture three dates, the renewal date, the notice date,

00:18:32.619 --> 00:18:34.460
and the date the last agreement was signed.

00:18:35.260 --> 00:18:40.140
Most of you will find the notice date is missing entirely, and that alone is worth the exercise.

00:18:40.710 --> 00:18:43.470
Then count how many renew in the next 18 months.

00:18:44.210 --> 00:18:45.550
That's your real workload.

00:18:46.560 --> 00:18:52.290
Find the largest number on that list and ask one question. Who owns this renewal?

00:18:53.119 --> 00:18:56.880
If the honest answer is nobody, you just found the most valuable 90 minutes

00:18:56.880 --> 00:18:58.250
available to you this quarter.

00:18:59.070 --> 00:19:02.460
Next episode, we answer the question I've been dodging since episode one.

00:19:03.230 --> 00:19:04.619
Do you actually need a tool?

00:19:05.890 --> 00:19:09.320
Back in that first episode, Mike from Columbus told me he couldn't afford an

00:19:09.320 --> 00:19:11.210
ITAM platform and asked what to do.

00:19:11.830 --> 00:19:16.060
I gave him a short answer. He deserved a full one, and next week he gets it.

00:19:16.780 --> 00:19:20.760
We'll walk the readiness test. Five questions, and if you fail any of them,

00:19:20.760 --> 00:19:24.140
buying a tool makes your problems more expensive instead of more visible.

00:19:24.960 --> 00:19:28.990
I've bought these platforms, implemented them, and inherited failed implementations

00:19:28.990 --> 00:19:30.970
from people who bought them for the wrong reasons.

00:19:31.650 --> 00:19:35.859
All of that is going in. Before I let you go, the case files.

00:19:36.820 --> 00:19:41.310
I've asked a few episodes running, and I'm asking again. If you've lived through

00:19:41.310 --> 00:19:44.750
something in this discipline other people can learn from, send it to me.

00:19:45.460 --> 00:19:50.260
Anonymized, sanitized, no company names. Just the situation,

00:19:50.590 --> 00:19:52.320
what you did, and what happened.

00:19:52.920 --> 00:19:58.849
Details at operationalitam.com The best teaching material in this field isn't

00:19:58.849 --> 00:20:00.030
in a framework document.

00:20:00.599 --> 00:20:02.470
It's in what happened to you last quarter.

00:20:03.180 --> 00:20:05.349
I'm Bill Van Nort, this is the Operational ITAM podcast.  Start the clock, build the alternative, and never negotiate in the last 60 days. I'll talk to you next week. Take care.