Technology Strategy & Roadmaps

Use-It-or-Lose-It: The December Purchases Worth Questioning

Year-end budget pressure produces December's worst technology purchases. A few plain questions separate the bargains from next year's regrets.

A laptop with a coffee cup and notebooks on a table by a window.

December brings a special kind of deal: the salesperson who needs the year to close, the budget line that expires on the 31st, the tool that is suddenly forty percent off if you sign by Friday. Some of these are genuine opportunities. Many are next year's regrets wearing a discount.

The pressure is the tell. A purchase that only makes sense in the last two weeks of December usually does not make sense.

Key takeaways

  • A discount attached to a deadline is a sales tactic, not a reason.

  • Unspent budget is not a strategy. Money returned is cheaper than shelfware owned.

  • The December purchase still needs an owner, a use case and a review like any other.

  • Fast security review beats no security review; the calendar does not suspend the questions.

  • The best answer to year-end pressure is a decision rule agreed before the pressure arrives.

Step 1: Separate the deal from the decision

Ask the December question plainly: would we buy this in March at full price? If the honest answer is no, the discount is buying your indecision, not your approval.

The reverse test matters too. A purchase that was already planned for Q1, pulled forward for a real saving, is fine. The difference is whether the plan or the salesperson set the date.

Step 2: Run the same three questions, faster

Compressed calendar, same questions. Who owns this tool after we buy it? What data does it touch and who can reach it? What does it cost to leave: the exit terms, the data export, the renewal jump in year two?

If the answers cannot be gathered before the deadline, the deadline is doing the deciding. A vendor unwilling to answer quickly in December will not answer slowly in June.

Step 3: Count the whole first year, not the discounted start

The December price is the first line of the cost. Add the implementation time, the training, the integration, the renewal at list price, and the attention it will take from work already funded.

This fictional example shows the comparison. It is an illustration, not a prescription.

Item December framing Whole-first-year view
Price 40% off if signed by Dec 31 Discount on year one only; year two at list
Start date Immediate Team unavailable until February
Value case Everyone will use it Three probable users, no owner named

The right column is where the decision actually lives.

Step 4: Name the owner before the signature

Every December purchase needs a named owner who wanted it before the discount existed. If the honest owner is "we will figure that out," the tool is shelfware with a receipt.

The SaaS renewal review covers the security questions that apply to any tool joining the stack, and the budget-season arguments is the companion read for the conversations behind this one.

Step 5: Set the rule before next December

The durable fix is a standing rule: year-end purchases get the same review as any other, and anything over a set amount needs the named owner and the three questions in writing. Announced in January, the rule is policy. Applied under pressure in December, it feels like sabotage. Agree it early.

Frequently asked questions

Isn't rejecting a real discount just leaving money on the table?

Only if the tool was worth its whole first-year cost. A discounted tool nobody owns costs more than full price for nothing. Money returned to the budget is not lost; shelfware is.

What if the budget really does expire?

Expiring budget is a finance rule, not a technology argument. If the right purchase cannot be made well in December, the better conversation is with whoever set the rule about carrying the funds, not with a salesperson.

How fast can a security review reasonably be?

For a low-risk tool, the three questions can be answered in a day from vendor documentation. Tools touching sensitive data or broad access deserve longer, and that longer timeline is itself a reason to say not this December.

Who should be able to invoke the rule?

Anyone asked to sign. The rule only works if the person holding the pen can say "the rule we agreed in January" instead of absorbing the pressure personally.

A Defensible Next Step

If a December deal is on the table right now, ask the March question and name the owner before anything is signed. Book a Decision-Clarity Call if you want a fast, honest second look at the purchase.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Technology Strategy & Roadmaps

All CISO Insights
Technology Strategy & Roadmaps

When the CTO Says We Need to Rebuild

A rebuild proposal is a large bet. Test it against repair, phased replacement and doing nothing, and ask for evidence that the current system cannot scale.

Technology Strategy & Roadmaps

Shadow IT: Finding What Procurement Never Approved

Teams adopt tools without asking. Discover them, classify the risk, then decide to legitimize, replace or block. A five-step workflow for executives.

Technology Strategy & Roadmaps

Legacy System Replacement: The Go/No-Go Questions

Replace, wrap or tolerate an aging system? A go/no-go scorecard weighs business criticality, failure risk, replacement cost and migration risk.