For most of the last two decades enterprise technology was bought as capital: a system was specified, licensed perpetually, installed, depreciated over several years and eventually replaced. Procurement in that world was a periodic event with a clear beginning and end, and its central question was price against specification. That world has largely gone. The dominant model now is consumption: subscriptions, per-user and per-transaction licensing, cloud services metered by the hour, and support bundled into recurring fees that renew automatically unless actively renegotiated. The consequence is that spending which used to be a discrete decision is now a continuous liability, and the leverage an organisation holds is highest at the moment of first signature and erodes steadily thereafter.

This matters now for reasons that are structural rather than cyclical. Technology landscapes have become dense webs of interdependent services, so a single supplier decision rarely stands alone; it commits the organisation to data formats, integration patterns and adjacent products. Regulatory expectations around data residency, operational resilience and third-party risk have turned contract terms that were once boilerplate into matters of compliance. And the pricing sophistication of major vendors has advanced far beyond that of most buyers, with metering, tiering and bundling designed to make consumption grow quietly. Procurement, understood properly, is the discipline that restores symmetry to that relationship. It is not a cost-control function bolted onto the technology decision; it is the point at which strategy, architecture, risk and finance are reconciled and written down in enforceable form.

The foundational error in technology procurement is to specify the thing rather than the result. A requirement expressed as a product, a feature list or a named technology imports the vendor's model of the world before the buyer has decided what problem is being solved. The disciplined starting point is the outcome: the business capability required, the conditions under which it must hold, and the measures by which its presence or absence will be judged. From that flow the functional requirements, and only then the constraints on how they may be met. A requirement is well formed when it is testable, when it distinguishes what is essential from what is merely desirable, and when it does not silently assume a particular supplier's architecture.

Vendor selection then becomes an exercise in structured comparison against those requirements rather than a response to sales narrative. The mechanisms that make it rigorous are unglamorous and reliable: weighted evaluation criteria agreed before proposals are seen, so that scoring cannot be retrofitted to a preferred answer; proof of concept or reference testing against the essential requirements rather than the demonstration the vendor prefers to give; and reference checks that probe the operational reality, including how the supplier behaves when something goes wrong. The object of selection is not the strongest product in the abstract but the best fit for this organisation's constraints, existing landscape and risk appetite. A technically superior system that cannot be integrated, staffed or afforded over its life is the wrong choice, and only a requirements-led process will reveal that before the contract is signed.

Underpinning all of this is a single principle: the commercial relationship must be designed to keep the buyer's and supplier's incentives aligned across the whole term, not merely at the point of sale. A term that looks generous at signature but rewards the supplier for the buyer's inertia is a misaligned term, however attractive the opening price.

Total cost of ownership is the analytical spine of sound procurement, and it is routinely underestimated because the visible price is the smallest part of it. A complete view of cost includes the licence or subscription itself, but also implementation and integration, data migration, training, the internal effort of operating and administering the system, support and maintenance fees, the cost of the infrastructure it runs on, and the eventual cost of migrating away from it. In consumption models a further category dominates: the cost of growth. Per-user, per-transaction and metered pricing means that success in adopting a system directly increases its cost, and pricing tiers are frequently arranged so that the unit rate deteriorates precisely as usage crosses the thresholds an organisation is most likely to reach.

Modelling this honestly requires projecting usage over a realistic horizon, typically three to five years, and stress-testing it against the scenarios the vendor's pricing is designed to exploit: rapid user growth, data volume expansion, additional environments, and the premium modules that the base offering is engineered to require. It also requires accounting for the asymmetry between entering and leaving. Onboarding costs are borne once and are visible; exit costs are borne under pressure, often years later, and are usually invisible at the point of purchase. A discount that is contingent on a multi-year commitment, on minimum consumption or on bundling adjacent products is not a saving until its full effect on the total cost curve and on future flexibility has been calculated. Treating discount as a synonym for value is one of the most reliable ways to overpay while believing the opposite.

A contract is the specification of the commercial system, and like any specification it should be designed for the conditions it will actually meet rather than the conditions at signature. The licence structure is the first design decision: perpetual against subscription, named-user against concurrent, capacity-based against consumption-based. Each carries a different exposure to change. Subscription and consumption models transfer flexibility to the buyer at the cost of predictability and of continuous renegotiation leverage held by the seller; perpetual models do the reverse. The right choice depends on how the organisation expects to grow and how confident it is in that expectation, and it should be made deliberately rather than accepted as the vendor's default.

Beyond the licence, the terms that determine whether the contract holds under change are the ones most often neglected. Price protection matters as much as opening price: caps on annual increases, fixed renewal rates and protection against mid-term repricing prevent the predictable erosion of a good initial deal. Service levels must be defined against outcomes that matter, with meaningful remedies rather than token credits, and with the measurement in terms the buyer can verify. Data terms should establish unambiguously that the organisation's data remains its own, in a form it can retrieve. And the change-of-terms provisions, the clauses that govern what the supplier may alter unilaterally, are frequently where the real risk lives, because a right to change pricing, scope or terms at the supplier's discretion quietly undoes everything negotiated elsewhere. Good structure anticipates renewal, growth, dispute and departure, and prices each into the document while the buyer still has the leverage to insist.

Lock-in is not a single phenomenon and cannot be addressed by a single clause. It accumulates through several distinct channels, and the discipline is to recognise each and to price and constrain it deliberately. Technical lock-in arises when data is held in proprietary formats, when integration depends on closed interfaces, or when the architecture is entangled with one supplier's platform such that extraction is a project in its own right. Commercial lock-in is engineered through multi-year commitments, bundled discounts that unravel if any component is removed, and renewal terms that make staying cheaper than leaving regardless of merit. Operational lock-in is the quietest: skills, processes and institutional habit form around a system until the organisation cannot imagine operating without it, and this dependency has no line in any contract.

Exit rights are the counterweight, and they must be negotiated at entry because they cannot be obtained later at any reasonable price. The essential provisions are concrete: the right to retrieve all data in a documented, usable, non-proprietary format; defined transition assistance obligations, including timelines and a cap on cost, so the incumbent is contractually bound to help rather than to obstruct; clarity on what happens to the data after termination and on how deletion is evidenced; and termination rights that are not so narrowly drawn that they can never be exercised. The test of an exit provision is not whether it exists but whether it could actually be invoked under the conditions in which an organisation typically needs to leave, which are conditions of frustration, urgency and reduced goodwill. An exit clause that assumes cooperation from a supplier the buyer is trying to escape is decoration. Designing the way out before committing to the way in is what preserves the organisation's freedom of action for the entire life of the relationship, and it is the single most consequential thing procurement can secure.

Nashua approaches technology procurement as a design discipline rather than a transactional service, and the work begins well before any supplier is contacted. The first task is to establish what outcome is actually being bought and to express it as testable requirements that separate the essential from the desirable, so that later evaluation rests on evidence rather than on the persuasiveness of a proposal. We build the total cost of ownership model early and populate it with realistic usage projections over the full contract horizon, because the model is what turns a headline price into a defensible decision and what exposes the pricing curves that grow quietly with adoption.

In selection, Nashua runs structured, weighted evaluation with the criteria fixed before proposals are seen, supported by proof of concept testing against the requirements that matter and by reference checks that probe operational behaviour under stress. In negotiation, our attention is concentrated on the terms that determine how the contract behaves over time: licence structure matched to the organisation's growth expectations, price protection and renewal caps, service levels with verifiable measurement and meaningful remedies, unambiguous data ownership and retrieval rights, and control over what the supplier may change unilaterally. We treat exit as a design requirement of entry, negotiating data portability, transition assistance and termination rights while the buyer's leverage is at its height. Throughout, we remain independent of the outcome in the sense that matters: our interest is the alignment of the commercial terms with the result the organisation needs, not the selection of any particular vendor. The deliverable is not a signed document but a relationship engineered to hold under growth, dispute and departure.

The difference Nashua makes in procurement is the closing of the asymmetry between a sophisticated vendor and a buyer who negotiates such deals occasionally. Major suppliers structure hundreds of these agreements a year and bring pricing, licensing and contractual expertise refined against thousands of counterparties; an individual organisation, however capable, meets each significant deal fresh. Nashua brings the pattern knowledge that restores balance: an understanding of where value is really won and lost, of which concessions matter and which are theatre, and of how a term that reads well at signature will behave three years into the relationship when the leverage has moved.

There is also a practical corollary that changes what the work is permitted to assume. When an engagement calls for a capability that does not yet exist, it need not wait on a procurement cycle or a vendor's roadmap. The Nashua 360 Enterprise Platform is built to accommodate almost any feature at pace, through extreme vibe coding: what is needed is described in plain language and generated quickly, but always within firm architecture principles and under stringent quality assurance, so that speed never comes at the cost of coherence, security or control. The effect is strategic rather than merely convenient. It moves the make-or-buy line, keeps optionality cheap, and lets the architecture follow the strategy rather than the strategy bending to whatever happened to be on a shelf.

What this yields in practice is procurement that is measured over the whole life of the agreement rather than at its opening. The organisations we work with retain the ability to grow, to renegotiate and to leave on terms they control, and they do so because those terms were designed in at the start rather than wished for at the end. That is the enduring value of treating procurement as engineering: the contract signed today still serves the organisation's interest when the technology, the market and the supplier have all changed, because it was built to hold under exactly those changes. Nashua's role is to ensure that what is bought is the outcome the organisation actually wanted, on commercial terms that keep it that way for as long as the relationship lasts.