IT Procurement: The Complete Process Guide for IT Buyers

What Is IT Procurement?

IT procurement is the end-to-end process by which an organisation identifies, evaluates, selects, and acquires technology - hardware, software, services, or a combination of all three. It covers everything from the initial recognition that a technology need exists, through to contract signature, implementation, and ongoing vendor management.

IT procurement gives organisations a competitive edge: the right technology, at the right price, with the right vendor, at the right time. Done poorly, it leads to expensive mistakes, failed implementations, and years of frustration trying to make the wrong system work.

This guide covers the complete IT procurement journey from the perspective of the buyer - with practical frameworks, best practices, and honest advice drawn from years of running technology selections for organisations of all shapes and sizes.

The IT Procurement Lifecycle - An Overview

A well-structured IT procurement process follows six distinct phases:

Before You Buy: Should you fix what you already have, or is a switch genuinely necessary? It's a step that many miss - but even when things look bleak, there is always the chance to rescue the situation.

Market Discovery: Understanding what technology options exist and building a longlist of potential vendors.

Market Assessment (RFI): Narrowing the longlist to a focused shortlist through a structured Request for Information process.

Formal Evaluation (RFP): Gathering detailed proposals from shortlisted vendors and moving towards a selection decision.

Scoring and Decision-Making: Evaluating vendors against structured criteria and making a defensible final choice.

Each phase builds on the last. Skipping steps - particularly the diagnostic Phase 0 and the wide market scan of Phase 1 - is one of the most common causes of IT procurement failure. However, for those wanting to move quickly, we often see the phases merged.

------

Before You Buy - Stick or Switch?

Most IT procurement guides begin with market research. This one does not. Before investing significant time, money, and internal energy in finding new technology, every organisation should ask two honest questions:

"Is the problem with the technology itself - or with how we are using it?"

"Can the current vendor relationship be fixed, rather than replaced?"

This matters because replacing technology is expensive, disruptive, and time-consuming. If the root cause of dissatisfaction is poor implementation, undertrained users, an unresolved service issue, or a difficult vendor relationship, then switching platforms often solves nothing - and creates an entirely new set of problems.

Running a 'Stick or Switch' review is also important for one other reason - to make sure everyone is on the same page. It's a great idea to check that things are really that bad - and that it isn't just lots of grumbling that has got out of control. It also enables us to document the decision - and have a baseline for what don't want in the future.

Take a look at how Viewpoint Analysis runs the Stick or Switch Review.

How to Diagnose the Situation

A proper diagnosis involves three steps. First, conduct structured conversations with users at all levels of the organisation - not just management - to understand genuine sentiment towards the current system. It is common to find that a small number of vocal critics have created the impression of widespread dissatisfaction, when most users are reasonably satisfied. The opposite is also possible: front-line users may have serious concerns that have never reached leadership.

Second, review your current contract. Understand your renewal terms, notice periods, and exit provisions before making any decisions. You may have more flexibility - or less - than you realise.

Third, give your incumbent vendor a structured opportunity to respond. Most vendors will work hard to retain a client when the stakes are clearly defined. A service improvement plan, changes in account management, or product enhancements may be sufficient to resolve the situation without the cost and disruption of switching.

If after this diagnosis a switch is genuinely warranted, you have an additional benefit: you will have a much clearer and more honest problem statement to take into the market.

The Problem Statement: The Most Important Document in IT Procurement

Whether you decide to stick or switch, one output from this diagnostic phase is invaluable: a clear, well-articulated problem statement.

A problem statement defines the business challenge you are trying to solve, why it matters, what the consequences of inaction are, and what a successful resolution looks like. It is the foundation on which every subsequent phase of the IT procurement process is built. Vendors use it to understand your challenge. Your internal team uses it to stay aligned. And it dramatically improves the quality of responses you receive throughout the selection process.

A good problem statement is typically a page or two long. It describes the business problem - not the technology you think you need - and gives vendors enough context to formulate a genuinely relevant response.

-----

Market Discovery

Enterprise technology is a vast and complex landscape. Most internal teams - even experienced IT professionals - have direct knowledge of only a handful of systems and may have limited visibility of what the broader market offers. The people with the most at stake in a technology selection are often the future users of the new system, who are domain experts but not technology market experts.

This is why market discovery is so important, and why it deserves real investment of time and curiosity before the procurement process formally begins.

Sources for Market Research

Analyst Reports. Organisations such as Gartner and Forrester publish structured market reports covering most major enterprise software categories. Magic Quadrant reports, Forrester Wave analyses, and similar research give a useful high-level view of the vendor landscape. Peer review platforms like G2 and Capterra offer aggregated user feedback that can quickly surface which vendors have strong real-world reputations in specific contexts.

These reports are a valuable starting point but should not be the only source. They tend to favour large, established vendors and may not reflect newer or specialist players who could be an excellent fit for your specific need.

Your Own Team's Knowledge. Do not underestimate the knowledge held within your organisation. People carry experience from previous employers, industries, and projects that may be highly relevant. A simple internal survey or a few informal conversations can surface vendor names, implementation experiences, and insights that no analyst report provides.

Technology Matchmaking. Viewpoint Analysis operates a Technology Matchmaker service that takes a different approach to market research. Rather than spending weeks researching vendors yourself, you provide a structured briefing document describing your challenge, and we invite a curated selection of relevant vendors to present how they would address it. You listen, learn, and discover options you may never have found independently - in a fraction of the time. We work across AI, HR, CRM, finance, supply chain, marketing, data, and business intelligence technology, among other areas.

Competitive Intelligence. Consider what peer organisations and competitors are using. This is not about copying their choices, but about ensuring you are aware of technology that is proven in your sector. Equally, looking beyond obvious sector choices can reveal innovative solutions that competitors have yet to adopt.

AI Tools. AI platforms can provide a useful initial scan of the vendor landscape for most technology categories. They are a good starting point - and a good catch-all at the end of the process to make sure nothing relevant has been missed.

Building Your Longlist

The output of market discovery is a longlist - a broad, relatively uncurated collection of vendors who could plausibly meet your need. Aim for eight to fifteen vendors across a mix of market leaders, mid-market specialists, and innovative niche players. Resist the temptation to only consider the largest, most well-known names. Some of the best-fit solutions come from smaller, more focused businesses whose entire product is built around exactly your problem.

-----

The RFI Process - From Longlist to Shortlist

Once you have a longlist, the next step is a structured market assessment - traditionally done through a Request for Information, or RFI. The purpose is to move from a broad list of possibilities to a focused shortlist of four to six vendors who are genuinely worth a deeper investment of time.

The Problem with Traditional RFIs

The conventional RFI process has a significant structural flaw: it is designed almost entirely around the buyer's needs, with little thought given to the vendor's perspective.

Vendor sales teams are stretched resources. When an RFI arrives from a prospect who might make a purchase decision in six months - after a lengthy, complex process - the calculus for the vendor is challenging. The longer and more onerous the RFI, the more likely a strong vendor is to decline to respond. This is genuinely damaging. The vendors most likely to walk away from a difficult RFI are often the best-resourced and most in-demand - precisely the ones you most want to hear from.

How to Run an Effective RFI

Keep it short. An effective RFI does not need to be comprehensive. Five to ten pages is typically sufficient. The goal is to give vendors enough context to understand your challenge and demonstrate a credible response - not to answer every conceivable question.

Lead with the problem statement. The most important element of any RFI is a clear, engaging description of your challenge. Use the problem statement developed in Phase 0. Write it in accessible, business-focused language. Make the vendor want to respond - this is, in effect, a sales document aimed at their sales team.

Include the essentials. Every RFI should cover: a concise company overview, the problem statement, a description of the process and what happens next, key dates, shortlisting criteria, preferred response format, and contact details for vendor queries.

Give vendors time - and a human to speak to. Allow a realistic response window. Where possible, offer vendors a short call to understand the context before they respond. A ten-minute conversation makes a measurable difference to response quality.

Be transparent about the process. Tell vendors when the process begins, what the timeline looks like, when they will hear back, and what the next step will be if they are shortlisted. Vendors appreciate clarity, and clarity produces better engagement.

The Rapid RFI: A Faster Alternative

Viewpoint Analysis has refined the RFI process into what we call the Rapid RFI. Rather than issuing a written questionnaire, the Rapid RFI uses a concise problem statement to invite structured vendor presentations. This produces richer, more authentic insight than written responses - and typically completes the longlist-to-shortlist journey in a fraction of the time of a traditional process.

Our Rapid RFI service manages the entire process: writing the briefing document, contacting and qualifying vendors, managing the Q&A, and hosting presentations. Your team simply shows up, listens, and makes a shortlisting decision.

Moving to Your Shortlist

At the end of the market assessment, you should be able to identify four to six vendors who have demonstrated a credible and relevant response to your challenge. This decision should be documented and defensible, with clear reasoning for each inclusion and exclusion.

------

The RFP - From Shortlist to Preferred Vendor

With your shortlist established, the formal Request for Proposal (RFP) is the mechanism for gathering detailed proposals and moving towards a selection decision.

The Problem with Traditional RFPs

The conventional enterprise RFP has developed a well-deserved reputation for inefficiency. Typical processes involve a lengthy document packed with hundreds of questions, assembled by committee, issued with tight deadlines, and returned in responses that nobody has enough time to properly read.

For the buying team, the effort required to write, manage, and review a complex RFP often exceeds the effort of the actual implementation. For vendors, a sprawling question list typically produces copy-pasted answers with little genuine engagement with the buyer's specific challenge.

Most damagingly, complex RFPs drive away capable vendors. When a sales team must choose between spending three weeks on a 1,500-question spreadsheet or focusing on a simpler, faster process elsewhere, the answer is not always your organisation.

A Better Approach: The Problem Statement RFP

The core insight behind a modern RFP is this: the vendor is the expert, not the buyer. The buyer knows their problem. The vendor knows how to solve it. An RFP that tries to prescribe the solution through exhaustive questions misses the opportunity to hear what the vendor would genuinely recommend.

By building the RFP around a clear problem statement and inviting vendors to propose their approach, you invite creative, targeted responses. You give vendors the latitude to demonstrate their expertise. And you produce proposals that are far more useful for your evaluation team.

This does not mean asking no questions. A small number of specific, non-negotiable requirements — around security, integration, compliance, or critical functionality - should always be included. But that list should be short and genuinely important, not a comprehensive catalogue of every possible feature.

What to Include in a Technology RFP

A well-structured RFP should include these sections:

Executive Summary and Company Background. Who you are, your size, sector, structure, and the business context for this procurement.

The Problem Statement. The heart of the document. Your challenge in clear, business-focused language. Why you are in the market. What a successful outcome looks like.

Scope and Requirements. The scope of the solution you are seeking, including: contract term preferences, user numbers and geography, integration landscape, security and compliance requirements, deployment and onboarding expectations, and for SaaS specifically - uptime commitments, data portability provisions, and customer success model.

Specific Questions. Genuinely non-negotiable requirements only. Keep this section short.

Commercial Information. Indicative pricing across the defined scope, projected over a three-to-five-year horizon. For SaaS: subscription cost, implementation fees, training, integration, and support tier pricing.

Process and Timeline. What happens next, and when. Clear timelines signal that you are a serious, organised buyer.

References and Evidence. Two to three relevant customer references, with the right to conduct independent reference calls.

The 30-Day Technology Selection

At Viewpoint Analysis, we believe that vendor selection should be fast. It is not the project - it is the mechanism to find the right technology for the project. A well-designed process should not become a project in itself.

We have helped many organisations compress 90-day selection cycles into just 30 days, without cutting corners or compromising governance. The 30-Day Technology Selection achieves this through seven core principles: replacing the 100-page RFP with a problem statement; going wide and then narrowing fast; being transparent with vendor sales teams; keeping the decision team small; making remote the default; setting aggressive public timelines; and letting vendors help build your business case.

The result is a faster decision, a more engaged vendor set, and a team that has not been exhausted by the process before the real work has even begun.

------

Scoring and Evaluation - How to Make a Defensible Decision

Sitting through vendor presentations is only useful if you have a clear and consistent framework for evaluating what you have seen and heard. Without structured scoring criteria, technology selection becomes a competition for the most charming sales director or the most polished demo - neither of which reliably predicts a successful outcome.

The 10 Essential Evaluation Dimensions

1. Solution Fit. How closely does the vendor's proposed solution match your stated requirement? Which vendor offers the closest match to your specific needs without extensive customisation? This is typically the most important single criterion.

2. Cost Today. The total cost at the point of purchase, fully inclusive - subscription, implementation, onboarding, and any required peripheral services.

3. Cost Over Time. Project the total cost of ownership over three to five years. Build in realistic assumptions for annual price increases (typically five to eight percent for SaaS), user growth, and support tier costs.

4. Business Stability. You are entering a medium-to-long-term relationship with a vendor business. How financially stable is that business? Are they profitable? Could they be acquired? The vendor you select today needs to still be a strong partner at contract renewal.

5. R&D Investment. Which vendor is investing in the future of the product? A compelling roadmap that aligns with where your business is heading is worth significant weight. A feature-rich product that is not evolving is a liability in a fast-moving market.

6. Cultural Fit. Which vendor team would you most enjoy working with over a multi-year partnership? The cultural fit you observe in the sales process is a reasonable predictor of the relationship you will have when things get difficult - and in enterprise technology, difficult moments are inevitable.

7. Customer References. Go beyond vendor-supplied references. Conduct independent reference calls through your professional network. Ask specific questions about the implementation experience, ongoing support quality, and what the reference would do differently.

8. Functional Fit. For any critical functional areas - specific integrations, reporting capabilities, compliance functions - score vendors in dedicated head-to-head comparisons with appropriate weighting.

9. Partner and Ecosystem. For technology categories that depend on system integrators or third-party implementations, assess the strength and availability of each vendor's partner ecosystem.

10. Time to Value. How quickly can each vendor realistically deliver a working solution? For some organisations, speed of deployment is a critical competitive factor.

Building Your Scoring Model

Assign a weighting to each dimension that reflects its importance to your specific situation. There is no universal weighting - the right balance depends on your organisation's priorities, risk profile, and the nature of the technology being procured.

A simple approach: allocate 100 points across your chosen dimensions and score each vendor out of five or ten on each. Multiply score by weighting to produce a weighted total. The highest score is not automatically the winner - but it gives you an objective starting point for the final conversation.

Beyond the Numbers

No scoring model fully captures the complexity of an IT procurement decision. Several qualitative dimensions always carry significant weight.

Gut feel. After extensive engagement with each vendor, your team will develop an instinct for which partner is most likely to deliver a successful outcome. That instinct is informed by everything you have observed and should not be dismissed. If the scoring model points one way but your gut says another, interrogate that carefully - but do not ignore it.

Trust. At the end of most selection processes, the decision often comes down to a single question: who do you trust the most? Which team has been honest about their limitations, responsive to concerns, and genuinely committed to your success - not just to closing a deal?

A final vote. When we run scoring at Viewpoint Analysis, we end with one additional step: we ask each member of the selection panel to cast a single vote for one vendor. This forces each person not just to score, but to make a decision - and brings real accountability into the room.

-----

Common IT Procurement Mistakes - and How to Avoid Them

Starting with technology, not the problem. Many organisations jump straight to researching vendors before clearly defining what problem they are trying to solve. The result is a selection process built on shaky foundations.

Building an RFP by committee. Documents produced by gathering every question anyone might ever want answered tend to be unwieldy, inconsistent, and exhausting for vendors to respond to. A smaller, empowered team produces better RFPs.

Only looking at the obvious names. Analyst reports and brand familiarity create gravitational pull towards a small number of large vendors. Some of the best-fit solutions come from focused specialists who do not have the biggest marketing budgets.

Treating selection as the project. Selection is the mechanism to find the right technology. When it becomes a project in itself - consuming months of management time and internal resource - it exhausts the organisation before the real work has even begun.

Neglecting vendor relationships. The way you treat vendors during the selection process signals the kind of client you will be. Slow to respond, unclear on timelines, dismissive of their investment - these behaviours drive away the best vendors and create a reputation that lingers.

Making it all about cost. Price matters, but overweighting cost relative to solution fit, cultural alignment, and vendor stability is one of the most reliable routes to a poor long-term outcome.

Skipping the Stick or Switch question. Organisations that move straight to procurement without honestly diagnosing whether their current situation can be fixed often discover - too late - that they have incurred significant cost and disruption to end up in a broadly similar position.

------

IT Procurement Best Practices

Define the problem before searching for the solution. Invest time in writing a clear, business-focused problem statement that your whole team agrees on before approaching the market.

Go wide before you go narrow. Build a genuinely broad longlist before narrowing to a shortlist. Options you dismiss early may turn out to be the best fit.

Make the process easy for vendors. The vendors most likely to deliver excellent outcomes are also the ones with the most options for where they invest their sales resources. Make your process one they want to engage with.

Move at speed. A slower selection is not a better selection. Compressed timelines maintain momentum, keep vendor engagement high, and produce decisions faster - which is when the real value of any technology investment begins.

Be transparent throughout. Tell vendors what is happening and when. Tell unsuccessful vendors promptly and honestly. Tell your internal stakeholders what the timeline and decision criteria are. Transparency makes every stage of the process run more smoothly.

Document everything. A defensible selection decision - one that can be explained to leadership, finance, and unsuccessful vendors - requires a clear record of how you got there.

Involve the right people, not everyone. A core decision team of three to five people is more effective than a large committee. Others can be consulted without being given a vote.

------

How Viewpoint Analysis Can Help

Viewpoint Analysis is an independent technology consulting firm - Technology Matchmakers - that helps organisations find, evaluate, and select enterprise software. We work with IT and business leaders at every stage of the IT procurement journey, and with technology vendors who want to understand, attract, and retain customers.

What makes us different is our position. We are genuinely neutral - we have no commercial relationship with the vendors we recommend and no incentive to steer buyers towards any particular product. We have also spent years on the other side of the table, responding to RFPs and participating in selection processes. That experience gives us a perspective that no analyst firm or traditional IT consultant can offer.

Our Services for IT and Business Leaders

Technology Matchmaker - the fastest way to understand the art of the possible in any technology category. We bring curated, relevant vendors to you for structured presentations, without the overhead of a traditional RFI process.

Rapid RFI - takes you from longlist to shortlist quickly and efficiently, without sacrificing the quality of information gathered.

Rapid RFP - takes you from shortlist to preferred vendor in four to eight weeks, with our team managing the process throughout.

30-Day Technology Selection - combines the Rapid RFI and Rapid RFP into a single, compressed sprint from standing start to vendor decision.

Stick or Switch Services - before any new selection begins, we help organisations honestly evaluate whether switching is truly the right answer, and we support organisations in improving or mediating difficult vendor relationships.

Ready to talk?

Contact us at contactus@viewpointanalysis.com | +44 113 5129252 | viewpointanalysis.com/request-a-call