The technology purchase that is right on the day and wrong in year three

Most technology purchases are judged on the day the order goes out. Price, lead time and specification look defensible, and usually are. The decisions that hurt are the ones whose cost falls due in a year when the person who signed has moved on.

Three things settled at purchase decide that cost: the pricing unit, the support dates and the record.

The unit the price attaches to will move

A licence is priced against a unit, and units move. Per-user pricing tracks a headcount the buyer does not control. Per-device pricing looks stable until staff carry a second device. Per-core licensing follows the processor, not the workload, so a refresh onto denser CPUs raises the software bill without adding a user. Concurrent and named-user licensing are not interchangeable, and the difference shows only at peak.

Ask for the same solution quoted at the user and device counts expected in three years. Ask where the tier boundaries fall, because crossing one by a single user can cost more than the ten before it. Ask what sits in the edition above the one quoted, and whether the agreement allows a mid-term step up. Where it does not, the upgrade is a fresh purchase.

Dates expire whether or not anyone is watching

Warranty and support run to a date, not to a condition. Equipment can sit inside its hardware warranty and outside its software support at once, so the firmware fix for a live security advisory is unavailable. Return to base and next business day are different purchases, and the gap shows only during an outage.

Renewals lapse because the record is split. Serial numbers sit on the asset, entitlement in a vendor portal, the purchase order in finance, the licence key in the mailbox of an engineer who has left. No single person made a mistake. The pieces were never joined.

End of sale, end of software maintenance and end of support are three different dates, usually announced in one notice and falling years apart. The last carries the risk, and the replacement budget has to be committed in the financial year before it.

Enterprise agreements commonly reserve a right to audit, and the cost of failing one is not the missed licence. It is buying that licence retrospectively, at list price, with back-maintenance owed and a deadline set by someone else.

The record has to outlive the buyer

A specification assembled from one vendor's datasheet cannot be answered honestly by anyone else. Port counts, bundle names and model-specific terminology narrow the field to one product, and the comparison that follows is decoration. Write the requirement as capability, capacity, interfaces, support terms and lifecycle commitments. If a clause exists only because a datasheet used that word, take it out.

The record starts with that specification. It should also hold:

• every quotation received, compared on a like-for-like basis;
• why the chosen option won, including where it was weaker;
• which agreement each item sits under, and who holds it;
• an entitlement register with quantities and portal ownership;
• renewal, warranty and end-of-support dates against a named owner.

None of this improves the purchase on the day. It is what lets a successor, or an auditor, establish three years later that it was sound.