Enterprise Software Selection Playbook - 2026

Introduction: The Enterprise Software Selection Playbook - 2026

Enterprise software selection is commonly done poorly. Get it right, and you gain a platform that drives competitive advantage, efficiency, and growth. Get it wrong, and you face years of frustration, wasted budget, and the politically painful process of starting all over again.

The good news is that most software selection failures are entirely avoidable. They don't happen because the market lacked good options or because teams weren't smart enough. They happen because the process itself was poorly structured - too slow, too complex, too internally focused, or missing critical steps entirely.

This playbook exists to fix that. Drawing on decades of experience running technology selections for organisations of all shapes and sizes - from fast-growth scale-ups to global enterprises - Viewpoint Analysis has distilled the complete selection journey into one definitive guide.

We are Technology Matchmakers. We sit in a unique position between buyers and vendors, helping both sides of the equation. That neutrality, combined with our experience on both sides of the table, gives us a perspective that no single vendor or analyst firm can offer.

What You Will Find in This Playbook

This guide follows the complete enterprise software journey in logical order:

•       Phase 0: Before You Buy - Should You Fix What You Have?

•       Phase 1: Finding Your Technology Options

•       Phase 2: Running a Market Assessment (the RFI or Rapid RFI)

•       Phase 3: The RFP - From Shortlist to Preferred Vendor

•       Phase 4: What Goes in Your RFP - Questions, Structure, and a Better Approach

•       Phase 5: Scoring, Evaluating, and Making the Decision

•       Phase 6: Announcing the Decision and Wrapping Up

Whether you are running your first selection or your fiftieth, you will find frameworks, tools, and practical advice to make the process faster, sharper, and more defensible.

Phase 0: Before You Buy - Should You Fix What You Have?

Most technology selection guides begin with market research and vendor shortlisting. This one doesn't. Before committing budget, time, and stakeholder energy to finding new technology, there are a couple of questions that every organisation must answer honestly:

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

and/or

"Can we get the current relationship back on track rather than finding new technology?"

Replacing technology is expensive, disruptive, and time-consuming. If the root cause of your dissatisfaction is poor implementation, undertrained users, a difficult relationship with your vendor, or unresolved service issues, then switching platforms may solve nothing - and create a whole new set of problems.

At Viewpoint Analysis, we have worked with many organisations who arrived at us ready to start a full vendor selection, only to discover through proper diagnosis that fixing the existing relationship was the smarter, faster, and cheaper route forward. So - do you stick or switch? Or are you still on the fence?

Stick or Switch: How to Know Which Path is Right

The 'Stick or Switch' question is deceptively simple. But answering it properly requires honest investigation across three areas:

1. Understanding the Current Situation

Before anything else, it is essential to properly understand what is really happening. This means conducting structured interviews with users at all levels - not just management - to understand genuine sentiment towards the current system. It also means reviewing the contract to understand your options, including notice periods, renewal terms, and any existing commitments.

Many organisations are surprised to discover that user sentiment is more nuanced than leadership assumed. Often, a small number of vocal critics create the impression of widespread dissatisfaction, even though most users are reasonably satisfied. Equally, some organisations miss the early warning signs of genuine system failure because front-line users feel unable to speak up.

2. Working with Your Incumbent Vendor

If the current vendor relationship has become strained, it may be that the relationship itself (rather than the product) is the problem. Changes in account management, a structured service improvement plan, or product enhancements may be sufficient to put the relationship back on track.

Our IT Service Improvement service works on behalf of the customer while engaging both the vendor and the customer team. Acting as an intermediary, we work to find common ground and to improve the situation - with the aim of creating a genuine win/win. The customer gains a better experience and gives the supplier a final opportunity to make things right. The supplier gains the opportunity to retain and extend the contract.

It is always worth giving your incumbent a structured opportunity to respond before committing to a switch. Most vendors will try very hard to retain a client when the stakes are clearly defined.

3. Exploring Alternative Options

If the incumbent cannot fix the situation, or if the technology genuinely can no longer serve the business's evolving needs, then it is time to look at alternatives. But this exploration is best done in a structured, low-commitment way - not as a full procurement process (at least not just yet) - to test whether the grass is genuinely greener before investing in a full selection.

This might involve inviting two or three alternative vendors to present their approach, without committing to a full RFI or RFP process. The resulting perspective is invaluable: sometimes organisations discover that switching would cost more than staying and investing in improvement. Other times, it confirms that a full selection process is the right course of action.

Our Stick or Switch Services

Viewpoint Analysis offers three distinct services for organisations facing this decision:

•       Stick or Switch Application Review - a structured review for organisations who are unhappy with their current application and need an objective view on whether to stay or go.

•       Renewal Stick or Switch - for organisations facing an upcoming renewal who are unsure whether to recommit or move on.

•       IT Mediation - when the supplier-customer relationship has broken down entirely. Viewpoint Analysis acts as a neutral intermediary to help both parties find a way forward before the situation reaches the legal team.

Learn more at viewpointanalysis.com/improve-technology

Defining the Problem Statement

Whether you decide to stick or switch, one of the most valuable outputs of this diagnostic phase is a clear, well-articulated problem statement. This is the single most important document you will produce in the entire selection process - and it costs almost nothing to create.

A problem statement clearly articulates the issue the business is facing, why it matters, what the consequences of inaction are, and what a successful resolution looks like. It is the foundation on which every subsequent step of the selection process is built. Vendors use it to understand your challenge. Your team uses it to stay aligned. And it forms the basis of a lean, modern RFP approach - as we will explore in Phase 4.

Phase 1: Finding Your Technology Options

Enterprise technology encompasses thousands of tools, platforms, and vendors spanning every conceivable business function. The average employee (even in IT) has direct experience with a handful of systems and may have little awareness of what the broader market offers. The most important people in any technology selection are often the future users of the new system, who are typically domain experts but not market experts.

This is why the first step in any selection should be a deliberate and wide-ranging scan of the available options. You don't know what you don't know - and the goal of this phase is to address that gap before narrowing your focus.

Where to Find Your Options:

Longlist Builder

Enter a few details about your technology requirement in our FREE Personalised Longlist Builder, and Viewpoint Analysis will send you a tailor-made report outlining all the technology vendors that you may wish to contact or consider.

Analyst and Market Research Reports

Organisations such as Gartner and Forrester publish detailed market reports covering most major enterprise software categories. These Magic Quadrants, Waves, and Market Guides give you a structured view of who the major players are and how they are positioned. Peer review platforms like G2 and Capterra also offer aggregated user feedback that can help you quickly identify which vendors have strong real-world reputations in your specific context.

These reports are a useful starting point, but have limitations. They tend to favour large, established vendors and may not reflect newer or niche players who could be an excellent fit for your specific requirements. Use them to build your initial longlist, but do not rely on them exclusively.

Your Own Team's Knowledge

You may be surprised at the knowledge held within your own team and the wider business. People carry experience from previous employers, industries, and projects - some of which may be highly relevant to your current challenge. A simple internal survey or set of informal conversations can surface vendor names, implementation war stories, and valuable insights that no analyst report can provide.

This internal knowledge should be collected early and treated as high-quality primary research. Former employees of relevant vendors, professionals who have managed similar projects elsewhere, and users with deep expertise in adjacent systems are all worth speaking with.

The Technology Matchmaker Approach

Viewpoint Analysis operates a Technology Matchmaker service which takes a different approach to the traditional market assessment. Rather than you spending weeks researching vendors and chasing sales teams, we bring the vendors to you.

In the Technology Matchmaker model, we produce a structured briefing document that describes your challenge and your context. We then invite a curated selection of vendors (all the market is available as we don't take a commission or cut of the deal) - drawn from our database of over 4,000 technology companies - to present how they would address your specific problem. You sit back, listen, and learn. It is one of the fastest and most effective ways to understand the art of the possible in any technology category.

We run specialist Matchmaker programmes across AI technology, transformation technology, ESG technology, HR technology, CRM, marketing technology, supply chain, finance, data, and business intelligence - among others.

Competitive Intelligence

It can also be worth looking at what your competitors or peer organisations use. This is not about blindly copying their choices, but about ensuring that you are at least aware of the options that are proven in your sector. If market-leading companies in your space rely on a particular platform, that is worth knowing - even if your final choice is different.

If your goal is differentiation rather than parity, looking beyond the obvious sector choices may reveal innovative solutions that competitors have yet to adopt. This is where a wider market scan pays dividends.

Industry Consultants and Experts

For particularly complex or unfamiliar technology categories, it may be worth bringing in an external consultant or hiring a subject matter expert to assist with the initial market scan. This is generally the more expensive option but can be particularly valuable in specialist technology domains where your internal team has limited prior exposure.

Viewpoint Analysis Technology Guides

We produce content across 11 different technology areas. Each is designed for the 'read up and research' phase - helping early-stage buyers to learn about a particular technology area, the key vendors in there, undestand terminology, and lots more. Check out the one that interests you the most:

• Customer Technology

• HR Technology

• Data Technology

• Finance and ERP Technology

• CRM Technology

• Supply Chain Technology

• AI Technology

• Business Intelligence & Analytics

• Transformation Technology

• ESG Technology

• Marketing Technology

Asking AI

It is clearly also worth asking your chosen AI platform for their recommendation and feedback - it's a great place to start, but it's also a good place to end - maybe asking them once all the avenues above have been tried, as it then catches anything you might have missed.

Building Your Longlist of Options:

The output of Phase 1 is a longlist - an expansive, relatively uncurated list of vendors who could plausibly meet your needs. The goal is breadth, not depth. At this stage, you are not making decisions. You are gathering options.

A healthy longlist for most enterprise software categories will contain between eight and fifteen vendors. It should include a mix of market leaders, mid-market specialists, and innovative niche players. Do not fall into the trap of only considering the largest or most well-known vendors - some of the best fits for a specific requirement come from smaller, more focused businesses whose entire product is built around exactly your problem.

Include vendors of all shapes and sizes. Even if a smaller vendor doesn't make your final shortlist, their presentation and approach may reshape your thinking about what is possible - which makes the whole process richer.

Our Technology Database

Viewpoint Analysis maintains a continuously updated database of over 4,000 enterprise technology vendors across every major category. When we run Technology Matchmaker or Rapid RFI processes for clients, we draw on this database to ensure no relevant option is missed. Contact us to discuss how we can help you build a comprehensive and relevant longlist for your specific requirement.

Phase 2: Running a Market Assessment - The RFI Process

Once you have your longlist, the next step is to run a structured market assessment. The traditional tool for this is the Request for Information, or RFI. Done well, it takes you from a broad list of possibilities to a focused shortlist of four to six vendors (our recommended number) who are genuinely worth your time and investment. Done poorly, it wastes months, alienates potential partners, and produces little useful insight - so take note of our experience to make the most of this step.

This chapter covers both the traditional RFI process and the faster, leaner alternative that we recommend: the Rapid RFI.

What Is an RFI?

A Request for Information is typically a short document that describes the buyer's challenge and invites interested vendors to respond with how they could help address it. It is a market-facing document, not an internal one, and its primary purpose is to generate enough information to enable a sensible shortlisting decision.

A well-crafted RFI is conversational, focused, and easy for vendors to respond to. A poorly crafted RFI is a sprawling questionnaire that takes weeks to produce, is painful to respond to, and generates responses that are largely copy-pasted from previous submissions — providing little real insight.

The Problem with Traditional RFIs

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

Vendor sales and pre-sales teams are stretched resources. They are focused on active deals with near-term closing potential. When an RFI arrives from a prospect who might make a purchase decision in six months - after a lengthy process - the calculus for the vendor is challenging. The longer, more complex, and more onerous the RFI, the more likely a vendor is to 'no-bid' and walk away.

This is genuinely damaging to the buyer. The vendors most likely to no-bid a difficult RFI are often the best-resourced, most in-demand ones - precisely the vendors you most want in your process. The vendors who always respond, regardless of complexity, may be doing so because they have no better prospects to focus on.

How to Run an Effective RFI

Keep It Short and Focused

An RFI does not need to be comprehensive. The goal is to give vendors enough context to understand your challenge and demonstrate whether they have a credible response. Aim for five to ten pages maximum. Our free RFI Template is a useful reference for what a well-structured, appropriately sized RFI looks like.

Lead with the Problem Statement

The single most important element of your RFI is a clear, engaging problem statement. This is your chance to sell the opportunity to the vendor's sales team - to make them want to respond. Describe your challenge in accessible, real-world language. Explain why it matters to the business. Give enough context about your organisation to help the vendor calibrate their response appropriately.

We use the phrase 'sell to the sales team' - which most procurement teams might think is a little odd. The Viewpoint Analysis team comes from a sales background, and we know how crucial it is to sell to them. The sales team has to want to bid for your business - and they also have to get approval to bid. What procurement teams tend to miss is that it costs a LOT of money to pursue an RFI or an RFP. It's critical to make the decision a simple one or some vendors just will not entertain the idea of even trying.

Remember: you want the vendor to use their full creative toolkit to address your problem. If your RFI is overly prescriptive about the solution you expect, you will compress the range of responses and potentially miss innovative approaches that you had not considered.

Include the Essential Elements

• Company Information: A concise summary of your organisation - its size, structure, sector, and where this technology requirement sits within the business.

  
  

• Project Need: The problem statement. Why are you in the market? What are you trying to solve? Who cares about it and why?

  
  

• The Process: What will happen next? Vendors want to know what they are committing to. Outline the subsequent steps clearly.

  
  

• Key Dates: When do responses need to be submitted? Be realistic - aggressive deadlines produce poor responses.

  
  

• Decision Criteria: How will you decide who makes the shortlist? Give vendors a clear sense of what 'good' looks like.

  
  

• Response Format: Keep it simple. Ask for a document or presentation, not multiple printed copies or complex spreadsheets.

  
  

• Contact Information: Who should vendors speak to if they have questions? Keep communication lines open and responsive.

  
  

• Invitation to Connect: Wherever possible, give vendors a chance to speak to your team before submitting. A ten-minute call to understand the context makes a significant difference to response quality.

Give Vendors Enough Time - But Not Too Much

Response timelines should reflect the complexity of your requirement and the notice you have provided. If you have warned vendors that the RFI is coming, a two-week response window is typically sufficient for a focused, problem-statement-led document. If the RFI arrives without prior notice, allow a little more time. Remember: every sales engagement costs the vendor in both time and money. Be respectful of that investment.

IF you decide to issue thousands of questions..... then you need to give much more time.

Be Transparent with the Sales Teams

Vendors appreciate honesty and clarity far more than most buyers realise. Tell them when the process will begin, what the timeline looks like, when they will hear back, and what the next step will be if they are shortlisted. This clarity makes the entire process run more smoothly and encourages higher-quality engagement from the vendors who matter most to you.

It's important to note that most sales teams are experts in sniffing out the truth. They will know if you are not being honest - they are trained in a myriad of different skills - and have a sensitive ear.

The Rapid RFI: A Faster Alternative

At Viewpoint Analysis, we have refined the RFI process into what we call the Rapid RFI (RRFI). The Rapid RFI is a supercharged version of the traditional process - designed to move from longlist to shortlist in the fewest possible steps without sacrificing the quality of information gathered.

The Rapid RFI focuses heavily on a concise problem statement and a structured vendor presentation format, rather than extensive written questionnaires. Vendors are invited to present how they would address the challenge, which tends to produce richer, more authentic insight than written RFI responses.

Our Rapid RFI service includes interviewing your team to understand the requirement, writing the RFI or problem statement document in vendor-friendly language, contacting and qualifying vendors, fielding initial sales calls, and hosting the vendor presentations. Your team simply needs to show up and listen. It is one of the most time-efficient ways to conduct a thorough market assessment.

When to Use the Technology Matchmaker vs the Rapid RFI

The Technology Matchmaker and the Rapid RFI serve slightly different purposes:

• Technology Matchmaker - ideal when you are early in your thinking, want to understand the art of the possible, and have limited internal knowledge of the market. Vendors come to you. You listen, learn, and discover options you may never have found independently.

• Rapid RFI - ideal when you have already identified a list of potential vendors and want to run a structured, fast assessment to determine who makes the shortlist.

Both services are available through Viewpoint Analysis. Learn more at viewpointanalysis.com/find-technology

Best Practices When Working with IT Vendors

Regardless of whether you run a traditional RFI or a Rapid RFI, the quality of your vendor relationships during the market assessment phase will significantly affect the quality of the process. Here are the golden rules:

• Create a level playing field. Avoid giving any vendor preferential access, additional time, or advance sight of the questions. Every vendor should operate under the same terms.

• Issue the RFI to all vendors simultaneously. Staggered distribution creates confusion and the appearance of favouritism.

• Be transparent and open. Share your challenges, your timeline, and your constraints with vendors. The more context they have, the better their responses will be.

• Respect their time. Every vendor response costs them money. Be flexible where you reasonably can, and avoid demands that are unnecessarily burdensome.

• Communicate bad news early. Vendors would always rather hear disappointing news promptly than hear nothing at all. If a vendor is not progressing to the shortlist, tell them promptly and explain why.

• Activate listening mode. At this stage, you are learning - not deciding. Let vendors take you through their full toolkit. Some approaches may surprise you.

The vendors who respond to your RFI or Matchmaker process are investing in your relationship. Treat that investment with respect, and you will build the kind of professional rapport that makes every subsequent stage of the process easier.

Moving to Your Shortlist

At the end of the market assessment phase, you should be in a position to identify a shortlist of four to six vendors who have demonstrated a credible, relevant, and compelling response to your challenge. The shortlist is the output of Phase 2 and the input for Phase 3.

At this stage, you are not making a final decision. You are choosing which vendors deserve further investment - from both your team and theirs. The shortlisting decision should be documented and defensible, with clear reasoning for each inclusion and exclusion.

Phase 3: The RFP - From Shortlist to Preferred Vendor

Once your shortlist is established, it is time to move to the formal proposal stage. This is where the Request for Proposal (RFP) enters the picture. The RFP is the primary mechanism for gathering detailed, structured proposals from your shortlisted vendors and moving towards a selection decision.

Done well, an RFP is a focused, professional, and efficient process that produces clear comparative data and builds confidence in the final decision. Done poorly, it becomes a bureaucratic obstacle that exhausts your team, irritates your vendors, and delays the project for months.

The Problem with Traditional RFPs

The conventional enterprise RFP has developed a well-deserved reputation for inefficiency. The typical process involves a 100-page document stuffed with hundreds - sometimes thousands - of questions, assembled by committee, issued with aggressive deadlines, and returned in responses that nobody has enough time to properly read.

This creates problems on both sides. For the buying team, the effort required to write the RFP, manage the vendor process, and then read and compare the responses often exceeds the effort of actually implementing the technology. For vendors, a complex RFP with hundreds of questions typically results in copy-pasted answers assembled by multiple departments who have never spoken to each other - which means the quality and relevance of responses is often poor.

Perhaps most damagingly, complex RFPs drive away the most capable vendors. When a sales team has to choose between spending three weeks responding to a 1500-question spreadsheet or focusing on a deal with a simpler, faster process, the choice is not always your organisation....indeed it's likely they will decline to bid, so get ready!

The 30-Day Technology Selection: A Better Way

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. And a good mechanism should not become a project in itself.

We have helped many organisations compress 90-day-plus vendor selection cycles into just 30 days - without cutting corners or compromising governance. The result is a faster decision, a more engaged set of vendors, and a team that hasn't been exhausted by the process before the real work has even begun.

The 7 Rules for a 30-Day Technology Selection

1.     Replace the 100-Page RFP with a Clear Problem Statement: Do not waste weeks developing a vast RFP document that nobody enjoys reading. Issue a concise problem statement that defines the issue you are solving, your key outcomes, and the essential criteria for success. Ask vendors to respond with how they would approach it. This keeps the focus on solving your problem, not completing templates.

2.     Go Wide, Then Go Narrow: Cast your net wide during the RFI phase, then narrow quickly to the four or five most relevant vendors for the RFP. Invest your time where it matters most.

3.     Be Transparent with Sales Teams: Tell vendors exactly what you are doing, why, and when. Make clear that you are running a fast process and that you need their full engagement. Sales teams respond extremely well to clarity and urgency.

4.     Keep the Decision Team Small: Every additional stakeholder adds scheduling complexity and delays decisions. Define a core team of three to five decision-makers who can meet quickly, review options, and commit. Others can be consulted separately if needed.

5.     Make Remote the Default: Insist on remote sessions rather than face-to-face workshops wherever possible. In a tight timeline, eliminating travel saves weeks. Vendor presentations, Q&A sessions, and internal reviews can all be done effectively online.

6.     Set Aggressive, Public Timelines: Treat the selection as a sprint. Publish the schedule - RFP issued Monday, shortlist by Friday, demos next week, decision by month-end - and hold everyone accountable. The moment timelines slip, momentum is lost.

7.     Let Vendors Help Build Your Business Case: Good vendors want you to succeed internally. Ask them to provide ROI models, business case templates, and customer success evidence. Many have dedicated resources specifically for this purpose.

Our Rapid RFP Service

The Rapid RFP (RRFP) is Viewpoint Analysis's approach to running a lean, fast, and effective RFP process. Where a traditional RFP might take three months from inception to decision, our RRFP typically completes in four to eight weeks - and produces better outcomes because vendors remain engaged throughout.

The Rapid RFP includes writing the RRFP document, hosting all initial vendor qualification calls, managing the Q&A process, scheduling and hosting vendor presentations, and guiding your team through scoring and next steps. We bring experience from hundreds of similar engagements to give your team a framework that works.

For those who need to move even faster, the 30-Day Technology Selection combines the Rapid RFI and Rapid RFP into a single, compressed process - taking you from a standing start to a vendor decision in under one month.

If you want to go it alone and try a Rapid RFP - take a look at our FREE Rapid RFP Template.

Is a 30-Day Selection Really Possible?

Yes - and it is easier than you might think. When teams simplify, communicate clearly, and maintain tight timelines, momentum builds quickly. Vendors respond faster, internal approvals come sooner, and everyone benefits from the pace of progress.

Best of all, you end the process with a decision made - not deferred. Learn more about our 30-Day Technology Selection at viewpointanalysis.com/30-day-technology-selection

Phase 4: What Goes in Your RFP

Whether you are running a traditional RFP or a Rapid RFP, the quality of the document you issue to vendors will directly affect the quality of the responses you receive. A clear, professional, and well-structured RFP signals to vendors that you are a serious buyer running an organised process - and motivates them to invest their best people and thinking in the response.

The Case for Fewer, Better Questions

Traditional RFPs are often assembled by gathering every question anyone in the business might ever want answered - resulting in documents that run to hundreds of questions across dozens of categories. This approach is flawed for several interconnected reasons.

First, the question-gathering process is itself a bureaucratic nightmare. Teams spend weeks trying to identify what to ask, often copying and pasting from old RFPs or borrowing templates from colleagues - with little thought given to whether the questions are actually relevant to the specific challenge at hand.

Second, the larger the question list, the higher the probability of vendor drop-outs. Every additional page of questions increases the likelihood that a vendor's sales team decides the process is not worth the investment. In some processes, as many as a third of invited vendors no-bid for this reason.

Third, even if vendors do respond to a 1500-question RFP, your team then faces the task of reading and comparing potentially thousands of pages of responses - an exercise that typically produces diminishing analytical returns and team exhaustion. Our experience of running vendor selection processes is that most responses get skim-read at best. Businesses love to issue large RFP packs - but hate reading the responses....

The modern approach - and the one we use in all our Rapid RFP engagements - is to ask fewer, more strategic questions and to rely heavily on the problem statement to generate the most useful vendor responses.

The Problem Statement Approach

The core insight behind the problem statement approach to RFPs 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 - and forces vendors to respond to the buyer's assumptions rather than to the actual challenge.

By issuing a clear, well-written problem statement and inviting vendors to propose their approach, you invite creative, targeted solutions. You give vendors the latitude to demonstrate their expertise rather than simply answer questions. And you produce responses that are far more useful for your evaluation team.

This approach does not mean asking no questions at all. There will always be a small number of specific, non-negotiable requirements - around security, integration, compliance, or critical functionality - that must be addressed. But this list should be short and genuinely important, not a comprehensive catalogue of every possible feature.

How to Write an Effective Problem Statement

Your problem statement should be clear, concise, and compelling. It should tell the vendor everything they need to know to formulate a relevant, specific response - and nothing more. Follow these steps:

• Identify the core problem: Define, precisely, the problem your business is trying to solve. Not the technology you think you need - the business problem. Make sure your internal team agrees on this articulation before the document goes out.

• Craft a concise summary: Summarise the problem in two to three paragraphs, providing relevant context about your organisation, your current situation, and why this challenge matters to the business.

  
  

• Select strategic must-answer questions: Identify the handful of questions that are genuinely non-negotiable. These might relate to security certification, specific integration requirements, regulatory compliance, or pricing structure. Keep this list as short as possible.

  
  

• Encourage innovative solutions: Explicitly invite vendors to demonstrate their expertise and creativity. Ask them to propose their recommended approach, not simply to answer your checklist.

What to Include in a Software or SaaS RFP

The structure of your RFP should be professional and logical. The following sections should be present in every enterprise software RFP, regardless of category:

Section 1: Executive Summary and Company Background

Provide a concise overview of your organisation - its size, sector, structure, and the business context for this procurement. Help the vendor understand who they are talking to and what kind of partner you will be.

Section 2: The Problem Statement

This is the heart of the document. Describe your challenge in clear, business-focused language. Why are you in the market? What is the cost of the current situation? What does a successful outcome look like?

Section 3: Scope and Requirements

Outline the scope of the solution you are seeking. For a SaaS procurement specifically, this section should cover the following:

• Contract term - are you looking for a one-year agreement or would you consider a longer commitment in exchange for better commercial terms?

• User numbers and geography - how many users need access, and across which locations or time zones?

• Integration landscape - which existing systems does the new solution need to connect with?

• Security and compliance requirements - what certifications, data residency requirements, and regulatory considerations apply?

• Deployment and onboarding - what support do you expect from the vendor during implementation and user rollout?

• SaaS-specific questions - uptime/availability commitments, update cadence, data portability and exit provisions, and customer success engagement model.

Section 4: Specific Questions

If there are specific, non-negotiable questions that must be addressed, include them here. Keep this section short and focused. Any question that could reasonably be answered through the vendor's general presentation should be excluded - save limited vendor attention for the things that genuinely matter.

Section 5: Commercial Information

Ask vendors to provide indicative pricing based on the defined scope. For SaaS procurements, ensure you capture the annual subscription cost, implementation and onboarding fees, training costs, integration costs, and any additional charges for support tiers, user growth, or future modules. Ask vendors to project costs over a three-to-five-year horizon.

Section 6: Process and Timeline

Be explicit about what happens next. When will shortlisted vendors be notified? When will presentations be scheduled? When do you expect to make a final decision? Clear timelines signal that you are a serious, organised buyer and help vendors resource their engagement appropriately.

Section 7: References and Evidence

Ask vendors to provide two or three relevant customer references - ideally from organisations similar to yours in size, sector, or challenge. Specify that you reserve the right to conduct independent reference calls beyond those provided.

By the way - do not disqualify vendors if they have no references in your industry. That's short-sighted and often means that vendors with industry references just keep winning, even though they aren't the best solution. Take a chance and you might just find your solution is better and more differentiated in the industry....

RFP Template

Viewpoint Analysis offers a free RFP template that covers all the essential elements of a modern enterprise software RFP. Visit viewpointanalysis.com/rfp-template to download it. For an RFI template, visit viewpointanalysis.com/rfi-template.

Phase 5: Scoring, Evaluating, and Making the Decision

Receiving vendor responses or sitting through 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 contest for who gave the best demo or who has the most charming sales director - neither of which reliably predicts a successful project outcome!

This chapter covers how to build an evaluation framework, what criteria to measure, and how to move from a scored shortlist to a confident final decision.

Why Scoring Criteria Matter

Scoring criteria serve three purposes. First, they ensure that your team is evaluating vendors against the same dimensions, which is essential when multiple stakeholders are involved in the assessment. Second, they provide the analytical structure needed to produce a defensible recommendation - one that can be explained to business leadership, finance teams, and unsuccessful vendors alike. Third, they help prevent the selection from being dominated by a single factor - usually cost - at the expense of considerations that may be more important to long-term success.

Getting the criteria right is as important as getting the questions right. Scoring against the wrong dimensions, or weighting unimportant factors too heavily, will produce a poor decision even if the process itself was well-run.

The 10 Essential Scoring 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 'out of the box' - without requiring extensive customisation or configuration? This is typically the most important single criterion and should carry significant weight in your scoring model.

2. Cost Today

What is the total cost of the solution at the point of purchase? Ensure the figure you are comparing is fully inclusive, accounting for taxes, implementation fees, and any required peripheral services. This is often the area that receives the most internal focus, but weighting it too heavily relative to other factors is a common source of poor decisions.

3. Cost Over Time

Agree on a multi-year horizon - typically three or five years - and project the total cost of ownership over that period. Build in a reasonable assumption for annual price increases, typically in the range of five to eight percent per year for SaaS products. Include training costs, integration maintenance, support tier costs, and the cost of any expected user growth.

4. Business Stability

You are not just buying software. You are entering into a medium-to-long-term relationship with a vendor business. How financially stable is that business? Are they profitable? How long have they been trading? Are they in a strong growth position, or are there signs of financial stress? Could they be acquired, and if so, what would that mean for your service?

Enterprise technology contracts often run for three to five years or longer. The vendor you select today needs to still be a strong, reliable partner at contract renewal. Do not overlook this dimension.

5. R&D Investment

Which vendor is investing in the future of the product? Research and development investment is the lifeblood of any software business - it determines whether the product will stay ahead of market needs or gradually fall behind. Ask vendors specifically about their R&D roadmap, their investment as a percentage of revenue, and the major capabilities they are developing over the next 12 to 24 months.

A vendor with a compelling roadmap that aligns with where your business is heading is a far more valuable long-term partner than one offering a feature-rich product that is not evolving.

6. Cultural Fit

This is harder to quantify, but often one of the most important factors in long-term success. Which vendor's team would you most enjoy working with? Which sales team has demonstrated professionalism, integrity, and genuine interest in your problem - as opposed to simply closing a deal?

Enterprise software implementations have difficult moments. When things go wrong (and they do) you need a partner who will step up and find solutions rather than retreat into contractual language. The cultural fit you observe in the sales process is a reasonable predictor of the relationship you will have in delivery.

7. Customer References

Have you spoken to the vendor's existing customers? Vendor-supplied references are useful but limited - vendors naturally provide their most satisfied clients. Beyond these, conduct your own independent reference calls by reaching out to known customers, industry contacts, and your professional network. Ask specific questions about the implementation experience, the quality of ongoing support, and what the reference would do differently if starting again.

8. Functional Fit

If there are specific functional areas that are particularly critical to your requirement, break them out for dedicated head-to-head comparison. Score each vendor against these specific functional dimensions separately and apply appropriate weighting. This is particularly important where a specific capability - such as a particular integration, a reporting feature, or a compliance function - is genuinely non-negotiable.

9. Partner and Ecosystem

For some technology categories, the partner ecosystem matters as much as the core product. If you will depend on a system integrator, implementation partner, or third-party technology to make the solution work, assess the strength and availability of that ecosystem for each vendor. What happens if your current partner relationship deteriorates - how easily could you find an alternative?

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. For others, timeline matters less than quality of outcome. Understand the typical implementation timeline for each vendor and what the key dependencies are - both on the vendor side and on your own team.

Building Your Scoring Model

Once you have agreed on your evaluation dimensions, assign a weighting to each one that reflects its relative importance to your specific situation. There is no universal weighting - the right balance will vary significantly based on your organisation's priorities, risk profile, and the nature of the technology you are procuring.

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

Vendor Head-to-Head

Viewpoint Analysis runs a process called the Vendor Head-to-Head, which compares shortlisted vendors across more than 20 evaluation dimensions and produces a clear, visual comparison of the options. It is one of the most useful tools we offer for teams who need to make a confident, defensible selection decision. Ask us about including this in your process.

Beyond the Numbers: The Qualitative Scoring Factors

No scoring model fully captures the complexity of an enterprise software selection. There are several qualitative dimensions that resist easy quantification but carry significant weight in practice.

Gut Feel

It sounds unscientific, but gut feel matters. After extensive engagement with each vendor - through presentations, Q&A sessions, reference calls, and negotiations - you and your team will develop an instinctive sense of which partner is most likely to deliver a successful outcome. That instinct is informed by everything you have observed, and it should not be dismissed simply because it is hard to quantify.

If the scoring model points to one vendor but your gut says another, that is worth interrogating carefully. Is the gut feeling based on something real that the model has not captured, or is it based on the quality of the vendor's hospitality rather than the quality of their product?

Trust

At the end of any selection process, the decision often comes down to a single question: who do you trust the most? Which team has demonstrated, throughout every interaction, that they are honest about their limitations, responsive to your concerns, and genuinely committed to your success?

Trust is the most durable basis for a long-term technology partnership. It is also, in our experience, usually obvious by the time you reach the final decision - even when everything else appears evenly balanced.

Investment Case

The final dimension to consider is the investment case in the round. Not just the cost of the software, but the full value proposition. Which vendor, when all factors are considered, offers the most compelling return on investment? Which one moves the needle most for your business? When the finance team conducts its final review, which option will be easiest to defend?

Cast a Vote

When Viewpoint Analysis run scoring as part of a selection process, we have one final element. We ask each person in the selection panel to cast a vote. They vote for one vendor, and only one. We find this very useful because it gets each person not just to score, but to make a decision. It's a fantastic way to get the team involved and to bring real accountability to the process.

Phase 6: Announcing the Decision and Wrapping Up Professionally

The selection decision has been made. The weighted scoring is complete, the qualitative discussion has happened, and your team has aligned on a preferred vendor. There is now one more critical - and often overlooked - phase: communicating the outcome professionally to all parties.

Telling the Preferred Vendor

Before announcing your decision publicly or beginning commercial negotiations, contact the preferred vendor privately to let them know the outcome. Be clear about the next steps - what the negotiation process will look like, who will be involved, what the target timeline is for contract execution, and what you need from them to move the process forward quickly.

This conversation should also be an opportunity to outline any remaining concerns or conditions that need to be addressed before the contract is signed. Clear communication at this stage avoids misunderstandings and sets a constructive tone for the relationship that is about to begin.

Telling the Unsuccessful Vendors

This is the step that most organisations handle poorly - or skip entirely. The vendors who did not win your business invested significant time, money, and energy in responding to your process. They deserve a proper, professional notification of the outcome and - wherever possible - an explanation of why they were not selected.

A brief, respectful notification call or letter should thank the vendor for their participation, inform them of the decision, and always offer a short debrief on the key factors that influenced the outcome.

The technology sector is smaller than most people realise. Reputations for running respectful, well-managed processes spread quickly - and so do reputations for the opposite.

Documenting the Decision

Before moving into commercial negotiations, ensure that the selection decision is properly documented. This should include the final scoring summary, the key qualitative considerations that influenced the decision, the rationale for preferring the selected vendor over the alternatives, and any conditions or caveats attached to the decision.

This documentation serves multiple purposes. It provides governance transparency for senior leadership and finance. It protects the selection team in the event of any challenge to the decision. And it forms the basis for the internal business case that will accompany the contract approval.

From Selection to Contract

The selection decision is not the end of the journey - it is the beginning of the commercial relationship. The period between preferred vendor selection and contract signature is a critical one, during which the terms of the agreement are negotiated and finalised.

Key areas to address in the commercial process include the precise scope of the contracted services, pricing and payment terms, service level agreements and support commitments, implementation milestones and acceptance criteria, data ownership and portability provisions, exit provisions and notice periods, and the consequences of material underperformance.

It is worth involving legal and procurement expertise in this phase, even if the earlier stages of the selection were led by the business or IT team. The contract you sign will govern your relationship for the duration of the agreement - it deserves careful attention.

How Viewpoint Analysis Can Help

Viewpoint Analysis is an independent technology consulting firm - Technology Matchmakers for want of a better expression - that helps organisations find, evaluate, and select enterprise software. We work with IT and business leaders at every stage of the procurement journey, from the initial 'Should we stick or switch?' conversation through to vendor selection and beyond.

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 you towards any particular product or platform. Our only objective is to help you make the best possible technology decision for your organisation.

We have also spent decades on the other side of the table, answering RFPs and participating in vendor selection processes. That experience gives us a perspective that no analyst firm or traditional IT consultant can offer. We understand what motivates vendor sales teams, what makes a selection process work, and how to structure an engagement that gets the best out of everyone involved.

Our Services for IT and Business Leaders

Find Technology - Technology Matchmaker

Our Technology Matchmaker service is 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. Matchmaker programmes are available across AI, transformation, ESG, HR, CRM, marketing, supply chain, finance, data, and business intelligence technology.

Select Technology - Rapid RFI, Rapid RFP, and 30-Day Selection

Our selection services are designed around speed, quality, and vendor engagement. The Rapid RFI takes you from longlist to shortlist efficiently. The Rapid RFP takes you from shortlist to preferred vendor. And the 30-Day Technology Selection combines both into a single, focused sprint. All are led by our team, with your team in a reviewing and deciding role rather than an administrative one.

Improve Technology - Stick or Switch, IT Mediation, and Service Improvement

Before any new selection begins, we help organisations honestly evaluate their current technology relationships. Our Stick or Switch Application Review, Renewal Stick or Switch, IT Service Improvement, and IT Mediation services are designed to ensure that switching is the right answer - not just the default response to frustration.

Let's Talk

Whether you are at the very start of your technology journey or deep into a stalled selection process, Viewpoint Analysis can help.

Contact us at:

•       contactus@viewpointanalysis.com

•       +44 113 5129252

•       www.viewpointanalysis.com

•       Request a call: viewpointanalysis.com/request-a-call

Quick Reference: The Enterprise Software Selection Checklist

Use this checklist to track progress through your selection. Each phase builds on the previous one.

Phase 0: Before You Buy

•       Have you interviewed users to understand genuine sentiment towards the current system?

•       Have you reviewed your contract and understood your exit options and renewal terms?

•       Have you given your incumbent vendor a structured opportunity to address the issues?

•       Have you explored whether alternatives exist that would genuinely be superior?

•       Have you written a clear problem statement that your whole team has agreed on?

Phase 1: Finding Your Options

•       Have you consulted analyst reports (Gartner, Forrester, G2) for your technology category?

•       Have you surveyed your internal team for prior experience with relevant vendors?

•       Have you considered a Technology Matchmaker process to bring vendors to you?

•       Have you researched what peer organisations and competitors are using?

•       Have you built a longlist of eight to fifteen vendors that includes a mix of sizes and approaches?

Phase 2: Market Assessment (RFI)

•       Have you drafted a concise, vendor-friendly RFI or problem statement document?

•       Have you given vendors advance notice that the document is coming?

•       Have you issued the RFI to all vendors simultaneously?

•       Have you set a realistic response timeline?

•       Have you provided a clear contact for vendor questions?

•       Have you documented your shortlisting criteria so the decision is defensible?

•       Have you produced a shortlist of four to six vendors with clear reasoning?

Phase 3: The RFP

•       Have you decided whether to run a traditional RFP, a Rapid RFP, or a 30-Day Selection?

•       Have you assembled a core decision team of three to five people?

•       Have you published a clear selection timeline and shared it with all vendors?

•       Have you written the RFP around a problem statement rather than an exhaustive question list?

•       Have you included all essential sections: company background, problem statement, scope, specific questions, commercial information, timeline, and references?

•       Have you issued the RFP to all shortlisted vendors simultaneously?

Phase 4: Vendor Evaluation

•       Have you agreed on your scoring dimensions and weightings before evaluations begin?

•       Have you provided all vendors with the same demo brief or scenario?

•       Have you used consistent scoring across all vendor presentations?

•       Have you contacted independent customer references, beyond those provided by the vendor?

•       Have you considered all ten evaluation dimensions — including stability, R&D, cultural fit, and trust?

•       Have you produced a Vendor Head-to-Head comparison?

Phase 5: Decision and Wrap-Up

•       Have you properly documented the selection decision and the rationale behind it?

•       Have you contacted the preferred vendor and outlined next steps?

•       Have you notified all unsuccessful vendors with a professional, respectful communication?

•       Have you offered debriefs to unsuccessful vendors who request them?

•       Have you engaged legal and procurement in the contract negotiation process?

•       Have you aligned the final contract with the selection decision, including scope, SLAs, and exit provisions?

-----

You might also get some value from the following posts:

• https://www.viewpointanalysis.com/post/it-procurement-the-complete-process-guide-for-it-buyers — "For a broader look at how technology procurement works end-to-end, our complete IT procurement guide covers the full process in detail."

  
  

• https://www.viewpointanalysis.com/post/sample-rfp-questions — "When you reach the vendor shortlisting stage, you'll need to put together an RFP — our guide to RFP questions gives you a strong foundation to build from."

  
  

• https://www.viewpointanalysis.com/post/how-to-write-a-winning-rfp-response — "Want to understand what a strong vendor response looks like? Our guide to writing a winning RFP response shows you what good looks like from the other side."

  
  

• https://www.viewpointanalysis.com/rapid-vendor-selection — "If the selection process feels like too much to manage internally, our Rapid Vendor Selection service can take the weight off your team and get you to a decision faster."

  
  

• https://www.viewpointanalysis.com/post/how-to-find-and-select-ai-technology — "If AI is the specific technology you're evaluating, we've written a dedicated selection guide that covers the unique considerations involved."

  
  

• https://www.viewpointanalysis.com/hr-technology — "Selecting HR technology? Our HR Technology hub brings together vendor profiles, guides, and selection advice in one place."

  
  

• https://www.viewpointanalysis.com/crm-technology — "Evaluating CRM platforms? Visit our CRM Technology hub for vendor profiles and selection guidance."