In many companies, IT procurement becomes involved late. The solution has already been chosen by the business function, IT has completed its technical review, and procurement is then expected to compare offers or negotiate the contract.
As long as only a few contracts are in place, this may not stand out. It becomes more difficult when SaaS contracts renew automatically, unused licences continue to run, or several tools with similar functions are being used across the organisation.
IT sourcing therefore starts well before price negotiation. First, it must be clear which application is actually needed, who will use it and what contractual consequences are linked to the decision. The question of how the company can later exit a solution also belongs on the table early.
This gives IT considerable weight in indirect procurement. Software, cloud services, consulting and managed services reach deep into processes and often bind organisations for years.
Procurement is then not only negotiating conditions. It is helping ensure that decisions are robust before the contract is signed.
What IT procurement means for companies
IT procurement covers software, hardware, cloud services and IT services. In practice, the more difficult part is usually not hardware, but software, SaaS and external services.
Rarely is this simply about ordering a product. Contract scope, usage rights, interfaces, support and contract terms all influence what the solution ultimately costs and how flexible the company remains.
Procurement does not need to answer technical questions on its own. But it should be involved early enough to make the commercial and contractual consequences of a decision visible.
The issue is not only which requirements exist today. Procurement should also know which providers are realistic options, how costs will develop with more users and how difficult a later provider change would be.
This is how IT procurement connects internal demand with what is available in the market and what can sensibly be agreed in the contract.
As a category, IT belongs in many companies to indirect procurement. The services sourced usually do not flow directly into the company’s own product, but they have a significant impact on processes and cost structures.
Why IT sourcing works differently from traditional procurement
Software cannot be compared in the same way as a clearly specified component or a standardised service. Providers bundle functions differently, pricing models change with user numbers or modules, and technical requirements continue to evolve.
This is particularly clear with SaaS. A low entry price says little about what a solution will cost after two or three years. Additional users, storage, support packages or interfaces can change the overall bill.
With IT service providers, another form of dependency can arise. Anyone who implements an application or configures processes builds up knowledge about systems, workflows and specific characteristics within the company. If this knowledge is not properly documented, switching provider can become much more difficult than expected.
For procurement, the question is therefore not only about price, but also about future dependency.
Even during selection, companies should consider how the solution will be introduced, operated and eventually replaced.
IT procurement starts with clear requirements
A typical process looks like this: the business function already has a preferred tool, the technical review is underway or already complete, and procurement then receives an offer with the request to negotiate better conditions.
At that point, there is not much room left to manoeuvre.
It is better to clarify demand earlier. Essential functions should be separated from nice-to-have features. Existing interfaces, affected user groups and the question of which data will be processed by the application are just as relevant.
With software, the difference between two providers often does not become apparent in the demo. It appears later in data export, permissions, support or when an additional function is suddenly only available in a larger package.
Clear internal responsibilities are also required. The business function understands the process, IT assesses integration and security, and further functions review data protection or other requirements where needed. Procurement brings the market and contractual side together.
If these roles are missing, sourcing can quickly move through several rounds of alignment without anyone being clear about who actually decides.
The article on organisation in procurement explains how such responsibilities can be structured more generally.
Software procurement: keeping licences and actual use in view
In software procurement, unnecessary costs often do not arise when the contract is signed, but months later.
Additional licences were booked for a project. The project has long since ended, but the accounts are still active. Another business function is now using a second tool with similar functionality. Another team has sourced software independently because the regular route took too long.
These cases add up.
That is why actual usage belongs to software procurement just as much as selecting new solutions. Who has access? Which licences are being used? Which contracts renew in the coming months? Do user numbers and the purchased package still match?
With SaaS contracts, timing is often decisive. Anyone who first looks at usage data a few days before the notice period expires may still be able to discuss price, but hardly the fundamental demand or alternatives.
A regular review of renewals, user numbers and contract deadlines creates significantly more room for action.
Software procurement: the entry price is only part of the calculation
A low licence price does not automatically make software inexpensive.
Implementation often brings further effort: data needs to be migrated, interfaces set up and employees trained. Some functions require additional modules, changes to the system generate extra costs, and if the company later switches provider, part of this work begins again.
For software procurement, total cost of ownership is therefore a more useful measure than the price in the first contract year.
Depending on the solution, this can include:
- licence or subscription costs
- implementation and project management
- interfaces and data migration
- training and internal change effort
- operation, support and maintenance
- extensions and additional modules
- internal effort from IT and business functions
- costs of a later provider change
This view can put an apparently expensive solution into perspective. If implementation, operation or support are easier, a higher licence price may be commercially justifiable. Conversely, a low-cost offer can quickly become expensive if almost every extension is charged separately.
Similar questions arise in cost optimisation in procurement. In IT, this is often less about an individual discount and more about understanding the cost logic behind a contract.
Selecting IT service providers: day rates say little about the result
Two providers can quote the same day rate and still cause very different overall costs.
One works with a well-coordinated team, documents properly and delivers with little rework. With another, contacts change, tasks have to be explained several times, or additional services only appear during the project.
Before comparing prices, it should therefore be as clear as possible what is actually being sourced. Consulting is different from implementation. Ongoing operation is different from a clearly defined project.
It is also important to know who will actually do the work. In larger IT projects, providers may use partner companies, freelancers or nearshore teams. This can work perfectly well, but it should be transparent.
In provider evaluation, day rates are therefore only one factor among several. Depending on the project, experience, availability, documentation, working methods or security requirements may also be relevant.
Selecting such partners is directly linked to supplier management and risk management in procurement. With IT, risks are often simply less visible than in a physical supply chain.
Contracts in IT sourcing: think about exit before it becomes necessary
When a contract is signed, attention usually sits with implementation. The project needs to start, deadlines are set and the business function is waiting for the new solution.
Many contractual clauses only become interesting years later.
A long notice period can then become just as relevant as automatic renewal or a price adjustment right. With cloud and SaaS solutions, there is also the question of what happens to the data after the contract ends.
Can the company export it completely? In what format? What support does the provider offer during migration? And how long does access remain available after the contract ends?
These points are usually easier to clarify before the contract is signed than at the moment when the switch has already been decided.
Price development should also not come as a surprise at renewal. If functions are only available in larger packages or the provider can adjust prices, this belongs in the commercial evaluation of the solution.
With recurring SaaS expenditure, the internal procurement process also plays a role. If ordering, approval and invoice checking do not fit together, procurement can quickly lose visibility. The article on maverick buying prevention also addresses the importance of practical procurement routes and clear approval processes.
Shadow IT often starts with a practical problem
A business function needs a tool at short notice. The software can be booked online, a credit card is enough, and the team can start within minutes.
For the individual user, this is initially the easiest solution.
A few months later, several people may be working with it. Data sits with the provider, automatic renewal has been agreed and procurement does not know that the contract exists.
This is how shadow IT often develops: not through deliberate circumvention, but because the official route was too slow or too complicated in that specific situation.
The consequences go beyond additional software costs. Depending on the application, data protection, information security, access rights or documentation may also be affected.
Bans alone rarely solve the problem. Smaller software requirements need a simple approval route, known contacts and standards that do not turn every app into a major project.
The connection to maverick buying is obvious. With IT, however, there is an additional dimension: buying an application often also creates access rights, data flows and longer-term contractual commitments.
Embedding IT sourcing as a category in indirect procurement
How many SaaS contracts are there in the company? Which of them expire in the next six months? Which tools perform similar tasks? And which business functions source software independently?
In many organisations, even these questions cannot be answered easily.
That is exactly where procurement’s role begins. It does not need to assess architecture or make the technical product selection alone. But it needs transparency over expenditure, contracts and suppliers.
Only then does it become visible where several solutions exist side by side, which providers have created relevant dependencies and which contracts should be reviewed early.
Software, IT consulting and managed services therefore fit naturally into the category logic of indirect procurement. This classification makes it easier not only to look at individual contracts, but also to recognise developments over time.
The article on developing a procurement strategy takes this perspective further: away from individual orders and towards market understanding and more deliberate supplier work.
When external support in IT procurement can be useful
Sometimes the issue is not lack of awareness, but simply lack of capacity.
Contracts need to be reviewed, several renewals are due at the same time, a tender is running and internally no one is available to take full ownership of the topic. Vacancies can also make IT procurement critical quickly, because notice periods do not wait until a position has been filled.
In other cases, the actual problem is initially unclear. High software costs may result from too many licences, unfavourable contract terms or several business functions having sourced similar solutions.
Simply negotiating harder on price will not solve that.
SJL Management & Consulting supports companies in setting up IT sourcing more effectively as part of procurement. The focus is on transparent expenditure and contracts, clear responsibilities and sourcing decisions that continue to work beyond the first contract period.
You can find more about possible areas of support under Our Services. Insights into typical mandates are available under Projects.
Conclusion: good IT procurement starts before negotiation
The greatest advantage is often transparency. Which software is being used? Which contracts are expiring? Where are costs arising that nobody is actively questioning anymore?
That is where IT procurement becomes effective.
When procurement, IT and business functions work together early, many problems do not have to be solved later through the contract. Requirements are clearer, alternatives remain open for longer and renewals do not come as a surprise.
Companies that want to develop their IT procurement or IT sourcing within indirect procurement can involve SJL Management & Consulting for consulting, project support and interim management.
Talk to us if your IT sourcing needs to do more than renew contracts.
FAQ
What is IT procurement?
IT procurement covers the sourcing of software, hardware, cloud services and IT services, as well as the related commercial and contractual tasks. This includes demand clarification, provider selection, cost evaluation and supplier work.
What does IT sourcing mean?
IT sourcing means the selection and procurement of IT services and solutions. This can include software, SaaS solutions, cloud services, IT consulting, managed services and development services.
What is part of IT procurement?
IT procurement starts with demand clarification and extends through provider selection and contract negotiation to the review of licences and ongoing contracts. Depending on the solution, IT, data protection, information security and the affected business functions also need to be involved.
What matters in software procurement?
In addition to the licence price, actual usage and contractual conditions are important. User numbers, renewal deadlines, price adjustments, integration effort and options for a later provider change can strongly influence the commercial viability of a solution.
Why is total cost of ownership important in IT sourcing?
With software and SaaS, many costs only arise after the contract has been signed. Implementation, data migration, interfaces, training, support and later extensions should therefore be included in the commercial evaluation of a solution.
What is shadow IT?
Shadow IT occurs when business functions use software, apps or cloud services outside the intended IT and procurement processes. This can create additional costs and risks relating to data protection, information security or contract management.
When can external support in IT procurement be useful?
External support can be useful when contracts and IT expenditure are not transparent, several renewals or tenders are due at the same time, or the organisation temporarily lacks the procurement capacity needed for IT sourcing.