How AI Is Reshaping Enterprise ICT Procurement Decisions
The five-year CRM deal is on the table. The ERP renewal is coming up. None of these are AI procurement decisions, yet all of them may now be affected by AI. This article explores what is shifting and why it may matter for procurement teams.
The five-year CRM deal is on the table. The ERP renewal is coming up. The service desk platform contract is eighteen months in, with three and a half years remaining. None of these are AI procurement decisions. Yet all of them may now be affected by AI in ways that were not anticipated when the original business cases were written.
This is the part of enterprise AI that procurement teams are only beginning to navigate. Not the question of which AI platform to buy, but the question of whether the non-AI platforms already in the portfolio, or about to be signed, still make the same sense they did two years ago. In many organisations, the workflows those platforms support are changing. The capabilities they provide are, in some cases, being replicated, augmented, or made partially redundant by AI tools that did not exist when the original procurement decision was made.
This article is written for procurement professionals, IT leaders, and finance decision-makers in Australian organisations who are managing enterprise software portfolios and evaluating new ICT commitments in a landscape where AI is increasingly reshaping what software does, what it costs, and how long it remains fit for purpose. It sits inside the broader enterprise AI procurement framework and connects to the work on what to define before vendor evaluation.
The Software You Are Buying May Not Solve the Same Problem in Three Years
A CRM platform purchased in 2024 was typically evaluated against a set of requirements that assumed human users performing human workflows. Lead qualification, pipeline management, customer communication tracking, reporting. The platform was the right tool for those workflows at the time.
By mid-2026, AI-driven tools are performing parts of those workflows independently in many organisations. Lead scoring that was previously a CRM feature is increasingly being handled by AI models trained on broader datasets. Customer communication summaries are being generated by AI tools that sit outside the CRM entirely in some deployments. Reporting in certain environments is being supplemented or replaced by natural language querying across multiple data sources, not just CRM data.
The CRM still works. The question is whether the value proposition it was procured for may be eroding underneath a contract that assumes it is not.
This pattern is observable across multiple software categories. Enterprise resource planning, human resources information systems, IT service management, document management, and financial planning platforms all contain functionality that AI is beginning to replicate, augment, or bypass in various ways. The pace varies by category. The broader trajectory appears consistent.
For procurement teams, this may introduce a question that traditional ICT evaluation did not previously address: whether the platform being procured will still represent the best way to deliver the workflow it supports, not just at contract signing, but across the full term of the agreement.
Integration With AI Is Increasingly Becoming a Procurement Consideration
Even where a platform is not being displaced by AI, its ability to work alongside AI is becoming increasingly material to its long-term value in many enterprise contexts.
A service desk platform that cannot expose ticket data to an AI agent for first-line triage may become a bottleneck as the organisation deploys AI across its support operations. An ERP system that cannot accept AI-generated inputs or surface data through APIs for AI-driven forecasting may constrain operational improvements that other parts of the business are building toward.
Two years ago, "AI readiness" was not a procurement evaluation criterion for these categories. In 2026, the platforms that integrate well with AI tools and the platforms that do not are beginning to diverge in operational value in many organisations.
The dimensions that tend to matter most in this context include API maturity, data accessibility, support for agentic workflows where AI tools can read and write to the platform, and the vendor's architectural approach to embedding AI within the platform itself. Some vendors have invested deeply in native AI integration. Others offer surface-level features that do not extend into the data layer or workflow engine. The difference is not always visible during a demonstration but tends to surface during implementation. Organisations already using a structured approach to enterprise AI vendor evaluation may find these same dimensions relevant when assessing non-AI platforms.
For organisations evaluating new ICT commitments, AI integration capability is increasingly forming part of the functional assessment, not a separate consideration.
Many SaaS Vendors Now Have an AI Story. The Substance Varies.
The enterprise software market in 2026 is saturated with AI messaging. Nearly every major CRM, ERP, HRIS, and ITSM vendor has announced AI features. The phrase "AI-powered" can be found on virtually every enterprise software landing page.
The substance behind that messaging varies considerably.
Some vendors have made deep architectural investments, embedding models within their platform's data layer, building retrieval-augmented generation pipelines against their own data structures, and designing governance controls that give the customer visibility over how AI processes their data.
Others have integrated a third-party AI model as a bolt-on feature with limited customisation, limited governance controls, and limited transparency on how customer data is handled during AI processing. The user experience may feel similar during a demonstration. The operational and governance implications can differ materially.
A third category has rebranded existing search, analytics, or automation features as "AI" without meaningful change to the underlying technology. The distinction between genuine AI capability and repackaged existing functionality is not always apparent during evaluation.
Procurement teams that have historically evaluated CRM or ERP vendors on functional fit, commercial terms, and vendor stability are now encountering a new evaluation dimension. The quality of a vendor's AI capability, the governance model around it, and its architectural depth are becoming relevant to the procurement decision even when the organisation is not buying an AI platform. In many cases, an organisation is buying a platform that now contains AI, and the quality of that AI can affect the platform's long-term value.
Cloud Provider Commitments Are Increasingly Shaping AI Options
Many Australian organisations have existing commitments to Azure, AWS, or Google Cloud. These commitments were originally infrastructure decisions. They increasingly function as AI decisions as well.
Microsoft's enterprise AI strategy is closely integrated with Azure. Organisations already committed to Azure often find that Microsoft's AI tooling, including Copilot and Azure OpenAI Service, is the path of least resistance for AI deployment. AWS Bedrock serves a similar function within Amazon's ecosystem. Google Cloud's Vertex AI anchors its AI offering to existing Google Cloud infrastructure.
This can have procurement implications that extend beyond AI platform selection. An organisation signing a new three-year Azure commitment may not just be committing to cloud infrastructure. It may also be shaping the AI ecosystem it has the most friction-free access to. The same dynamic applies to AWS and Google Cloud.
Many of these cloud commitments were signed in 2023 or 2024, when the AI bundling strategy was less developed. Organisations that committed to a cloud provider based on infrastructure pricing, data residency, or existing application hosting are in some cases discovering that the AI capabilities available to them are substantially determined by that earlier decision. Switching cloud providers to access a different AI ecosystem can carry migration cost that was not part of the original commercial analysis. In effect, a cloud commitment may have become an AI commitment by inheritance.
For organisations evaluating major cloud renewals or new cloud commitments, the AI layer that sits on top of that infrastructure is increasingly part of the commercial calculus. The cloud provider decision and the AI platform decision are less separable than they were twelve months ago.
This dynamic also extends to existing SaaS vendors. A CRM or ERP vendor that has built its AI features on a specific cloud provider's AI infrastructure may introduce dependencies that interact with the customer's own cloud commitments in ways that were not part of the original procurement consideration. An organisation on AWS evaluating a CRM vendor whose AI features run on Azure OpenAI Service may face latency, data handling, or cost implications that only become visible during implementation.
The Pace of Change Is Making Long-Term Commitments Harder to Evaluate
Traditional ICT procurement assumes a degree of stability. A five-year ERP contract is typically evaluated against requirements that are expected to remain substantially relevant for five years. The platform may receive updates, but the fundamental value proposition is assumed to be stable. The vendor's competitive position is unlikely to change dramatically within the contract term.
Enterprise AI has compressed the timeline on which these assumptions hold.
In 2024, the leading AI models available for enterprise use were materially different from those available in 2025. By mid-2026, the landscape has shifted again. Open-source models have closed significant capability gaps with proprietary alternatives in many areas. New entrants have emerged. Established vendors have pivoted their commercial models. Pricing structures that were standard eighteen months ago are shifting.
This rate of change does not make long-term ICT commitments impossible to evaluate. It can make them harder to evaluate with the confidence that traditional procurement processes were designed to produce. The assumptions embedded in a five-year business case for any platform that touches AI, or that AI may eventually touch, carry more uncertainty than the same assumptions would have carried in 2023.
Some organisations are responding to this by evaluating the AI-adjacent risk profile of non-AI procurement decisions. Others are factoring AI trajectory into business case sensitivity analysis for major ICT commitments. The approaches vary. The underlying recognition is consistent: AI introduces a new variable into procurement decisions that were previously considered stable.
SaaS Portfolios May Be Facing a Different Kind of Rationalisation
Enterprise software portfolio rationalisation is not new. Organisations have long reviewed their SaaS portfolios for redundancy, underutilisation, and consolidation opportunities. What is changing is the nature of the redundancy.
Historically, redundancy meant two platforms doing the same thing. Two project management tools. Two communication platforms. The rationalisation exercise was straightforward: pick one, retire the other.
AI introduces a different pattern. A platform may not be redundant with another platform. It may be redundant with a capability that AI now provides without a dedicated platform at all. Document generation that previously required a specialist tool. Data entry workflows that required a dedicated interface. First-line support triage that required a ticketing system with complex routing rules. Reporting that required a business intelligence platform.
Not all of these workflows are ready to be replaced by AI today. Many are partially automatable now, with the trajectory pointing toward broader automation over the coming years. For procurement teams, the question may not be whether to cancel existing contracts immediately, but whether to evaluate new commitments and renewals with this trajectory in mind.
Consider a 2,000-seat document management platform procured in 2023 on a five-year term. At the time, the business case was built on workflow automation, version control, and collaboration features. By 2026, AI tools are generating, summarising, and routing documents in ways that replicate or bypass several of those core features in some organisations. The platform still works. The workflow it was purchased to support may be migrating away from it. The contract has three years remaining. This pattern, where the platform is not failing but the value case is shifting underneath it, is emerging across multiple enterprise software categories.
Some organisations that have begun this evaluation are not reducing their software spend. In some cases they are redirecting it, moving budget from platforms whose core value is being replicated by AI toward platforms that integrate well with AI and amplify its value. The enterprise AI build-versus-buy decision is increasingly relevant here, because the choice may no longer be just between vendors. It may be between dedicated platforms and AI-native alternatives that did not exist when the original contract was signed. The rationalisation tends to be less about cutting cost and more about aligning the portfolio with where workflows are heading, not where they were when the last contract was signed.
Questions Emerging in Enterprise ICT Procurement Evaluations
As the dynamics described in this article become more visible, a consistent set of questions is surfacing in procurement evaluations that would not have appeared in this form two years ago. These are not a checklist — they are illustrative of where ICT procurement conversations are evolving.
- Could this workflow be materially changed by AI during the contract term? The pace of AI capability development means that workflows assumed stable at the time of signing may look different in two or three years. Business cases built on current workflow assumptions may carry more uncertainty than they appear to.
- Does the platform expose APIs and support integration patterns required for AI adoption? Where AI tools are expected to interact with a platform, the maturity of the platform's API layer and its support for agentic workflows is increasingly relevant to long-term value.
- Are AI capabilities included, optional, or separately monetised? Vendors are taking different approaches to how AI features are packaged. Understanding whether AI capabilities are bundled, add-on, or priced separately affects the total cost profile of a commitment.
- How dependent does this decision make the organisation on a specific cloud or vendor ecosystem? Where a platform's AI features are built on a specific provider's infrastructure, the decision may introduce ecosystem dependencies that were not part of the original commercial analysis.
- What assumptions in the business case are most sensitive to AI-driven change? Identifying which assumptions carry the most risk if AI changes the workflow landscape is a useful input to sensitivity analysis on major ICT commitments.
These questions do not necessarily change the outcome of a procurement decision. They reflect a shift in the variables that matter.
What This May Mean for Procurement Teams
The shift described in this article is not a future scenario. Many of the AI capabilities reshaping enterprise software workflows are already in production across Australian organisations. The SaaS vendors adding AI features to their platforms are doing so now, with varying levels of substance. The cloud providers bundling AI into infrastructure commitments are already in market.
For procurement professionals, this does not change the fundamental discipline of the role. Requirements definition, vendor evaluation, commercial modelling, and governance remain the core activities. What is changing is the set of questions those activities may need to address.
A platform evaluation that does not consider AI integration capability may miss a dimension that could determine long-term value. A business case that does not model the possibility of AI-driven workflow change may overstate the value of a platform whose core function could be automated. A portfolio review that does not account for AI-driven redundancy may miss a significant consolidation opportunity.
None of these are AI procurement decisions. They are traditional ICT procurement decisions being made in a landscape that AI is actively reshaping. The procurement frameworks remain sound. The assumptions they rest on are the part that is moving.
This article provides general commercial and procurement commentary only and does not constitute legal, financial, or professional advice.