Send your CV

    Attach a CV (Accepted file types: pdf, doc, docx, rtf.)

    Apply for

    From Business Case to Vendor Selection: How to Avoid Costly Technology Mistakes

      Attach a CV (Accepted file types: pdf, doc, docx, rtf.)

      Share a brief

        ,

        From Business Case to Vendor Selection: How to Avoid Costly Technology Mistakes

        From Business Case to Vendor Selection: How to Avoid Costly Technology Mistakes

        Investing in new technology is one of the biggest decisions a business can make. Get it right, and you’re putting the foundations in place for better processes, improved efficiency and future growth. Get it wrong, and you could be looking at years of unnecessary costs, operational disruption and a system that doesn’t deliver what the business actually needs.

        For many organisations, particularly SMEs, selecting a new Enterprise Resource Planning (ERP) system isn’t something the leadership team does regularly. It’s a significant investment, often involving multiple stakeholders, competing priorities and decisions that will influence how the business operates for the next decade or longer.

        Yet it’s surprisingly easy for businesses to get caught up in the selection process itself.

        An impressive demonstration, a recognisable software provider or an attractive initial price can quickly become the deciding factor. The problem is that none of these necessarily tells you whether the solution is right for your organisation.

        Working in business transformation recruitment, we understand how important it is to have the right expertise involved in these decisions. Whether that’s an experienced Programme Director, an ERP Transformation Lead or a specialist Business Analyst, the people responsible for challenging suppliers, defining requirements and managing the selection process can make a significant difference.

        So, how can businesses approach technology vendor selection with confidence, avoid expensive mistakes and make sure they’re investing in the right solution?

        Building a Strong Business Case for Technology Investment

        Before approaching software vendors, it’s worth establishing exactly why the business needs to make a change.

        A strong business case should be about much more than replacing outdated technology. It needs to demonstrate how the investment will support the organisation’s wider objectives, address existing challenges and deliver measurable value.

        For leadership teams, that means answering some important questions:

        • Why does the business need to change its existing systems?
        • What are the risks of continuing with the current solution?
        • What improvements should the investment deliver?
        • Have alternative approaches been considered?
        • What will the transformation cost, including implementation and ongoing support?
        • What resources and specialist expertise will be needed?
        • How will success be measured?
        • How will the programme be managed and governed?

        These questions help move the conversation away from software features and towards genuine business outcomes.

        For example, replacing an ageing ERP system might be necessary because the existing platform is approaching the end of its supported life. However, the investment could also create opportunities to improve stock management, accelerate financial reporting, reduce manual processes or support future acquisitions.

        The strongest business cases connect technology investment directly to the organisation’s commercial and operational priorities.

        This gives the board a much clearer understanding of what the business is investing in, why it’s necessary and how it compares with other demands on budgets and resources.

        Understanding the Drivers Behind Business Transformation

        Every organisation will have different reasons for considering a new technology platform.

        For some, the decision is driven by risk. Existing systems may be unreliable, difficult to maintain or increasingly vulnerable to security threats.

        For others, the priority is improving efficiency and creating a platform that can support future growth.

        Common reasons for technology transformation include:

        Reducing operational risk:

        • Existing systems approaching end-of-support deadlines.
        • Cybersecurity vulnerabilities and compliance concerns.
        • Unreliable integrations between business systems.
        • Increasing maintenance and support costs.
        • Dependence on individuals with specialist knowledge of legacy technology.
        • Limited disaster recovery capabilities.
        • Difficulty accessing the technical skills needed to maintain existing systems.

        Improving business performance:

        • Reducing manual administration and repetitive tasks.
        • Improving financial reporting and forecasting.
        • Increasing visibility across stock, purchasing and working capital.
        • Creating more consistent processes across departments.
        • Improving customer service and order fulfilment.
        • Supporting business expansion, acquisitions and integration.
        • Introducing new automation and digital capabilities.
        • Improving access to reliable management information.

        Understanding these drivers is important because they should influence every subsequent decision, from defining requirements to evaluating potential vendors.

        A business looking to improve financial visibility may have very different priorities from one preparing to integrate several acquired businesses.

        The technology selection process needs to reflect those differences.

        Is Replacing Your Existing Technology Always the Right Answer?

        It’s easy to assume that an ageing or underperforming system needs replacing entirely.

        However, that isn’t always the most appropriate or cost-effective solution.

        One of the most valuable stages of a technology transformation programme is the initial discovery process. This is where the organisation can properly assess its current systems, business processes and future requirements before committing to a particular approach.

        Depending on the findings, the business might decide to:

        • Optimise its existing ERP platform.
        • Upgrade to a newer, supported version.
        • Introduce additional systems to address specific capability gaps.
        • Consolidate several existing platforms.
        • Replace the ERP system completely.
        • Adopt a phased approach using multiple integrated applications.
        • Introduce a two-tier ERP model.
        • Select an industry-specific solution.
        • Move to a cloud-based platform.

        Each option comes with different costs, risks, benefits and implementation requirements.

        The important thing is that the preferred solution is supported by evidence rather than predetermined by a vendor, an individual preference or the assumption that newer technology must automatically be better.

        Committing to a complete replacement before understanding the alternatives can mean spending significantly more than necessary, particularly if the existing system could meet the organisation’s needs with targeted improvements.

        Understanding the True Cost of Technology Implementation

        One of the biggest mistakes businesses can make during technology vendor selection is focusing too heavily on the initial software price.

        Licensing and implementation fees are important, but they’re only part of the overall investment.

        An ERP or wider technology transformation programme can involve significant additional costs, some of which may not be immediately obvious when reviewing vendor proposals.

        These can include:

        • Initial discovery and programme planning.
        • Software licences and subscriptions.
        • Implementation partner fees.
        • Internal project resources.
        • Interim ERP and transformation specialists.
        • Data cleansing and migration.
        • Integration with existing business systems.
        • Software testing and quality assurance.
        • Employee training and change management.
        • Temporary cover for employees supporting the project.
        • Infrastructure and security improvements.
        • Post-implementation support and hypercare.
        • Ongoing application management.
        • Contingency for unexpected challenges.

        It’s also important to establish exactly what’s included in a supplier’s proposal.

        A competitively priced implementation can quickly become expensive if essential integrations, reporting requirements or data migration activities are excluded from the original agreement.

        This is where experienced ERP Programme Directors, Business Analysts and Transformation Leads can provide real value.

        Having people involved who understand how these programmes are delivered, where costs can escalate and what questions need asking can help businesses make better-informed decisions before significant financial commitments are made.

        The cheapest option on paper isn’t always the most cost-effective solution in practice.

        How to Choose the Right Technology Vendor

        Once the business case has been approved and the organisation understands its future requirements, attention can turn to evaluating potential technology vendors.

        This is where having a structured selection process becomes particularly important.

        A vendor might offer an excellent product, but that doesn’t automatically mean it’s the right solution for your organisation.

        The evaluation needs to consider how well the platform supports the business, how it integrates with existing technology and whether the proposed implementation approach is realistic.

        Establish Clear Vendor Selection Criteria

        Rather than comparing vendors based on individual preferences, businesses should establish a consistent set of evaluation criteria.

        These might include:

        • Functional suitability: Does the system support the organisation’s key processes and requirements?
        • Industry experience: Is the solution appropriate for the sector and its specific challenges?
        • Technology and integration: Will it work effectively with existing systems and infrastructure?
        • Data and reporting: Can it provide the information and visibility the business needs?
        • Security and compliance: Does it meet relevant regulatory and security requirements?
        • User experience: Will employees be able to use the system effectively?
        • Scalability: Can the platform support future growth and organisational change?
        • Implementation capability: Does the vendor or implementation partner have the experience to deliver the project?
        • Product roadmap: Does the supplier’s future development direction align with the organisation’s requirements?
        • Customer references: Can the supplier demonstrate success with comparable organisations?
        • Total cost of ownership: What will the system cost throughout its expected lifespan?
        • Commercial terms: Are the contract, support arrangements and responsibilities clearly defined?
        • Delivery risk: Are the proposed timescales, resources and delivery approach realistic?
        • Cultural fit: Will the supplier work effectively with the organisation’s people and ways of working?

        These criteria should be weighted according to the organisation’s priorities before final proposals are assessed.

        Doing this helps prevent decisions from being influenced too heavily by a particularly impressive presentation or a supplier’s reputation.

        Why Software Demonstrations Need Careful Planning

        Software demonstrations are an important part of vendor selection, but they can also be misleading.

        Vendors naturally want to show their products at their best. They’ll demonstrate the strongest features, use carefully prepared data and focus on the areas where their software performs particularly well.

        There’s nothing inherently wrong with that. However, it doesn’t necessarily show how the system will handle the more complicated parts of your business.

        A more effective approach is to ask shortlisted vendors to demonstrate realistic scenarios based on the organisation’s actual processes and future operating model.

        For example:

        • From receiving a customer order through to collecting payment.
        • From demand planning through to purchasing and receiving stock.
        • From production planning through to finished goods.
        • From warehouse receipt through to customer dispatch.
        • From employee expenses through to financial reporting.
        • From operational activity through to management information and decision-making.

        Every shortlisted vendor should be asked to demonstrate the same scenarios.

        This creates a more objective comparison and helps identify where additional configuration, customisation or third-party software might be required.

        It also gives employees and operational leaders an opportunity to understand how the system would work in practice.

        After all, they’re the people who will ultimately be using it.

        Don’t Overlook the Implementation Partner

        Choosing the right software is only half the challenge.

        Even a well-suited technology platform can fail to deliver the expected results if the implementation is poorly managed.

        That’s why businesses need to investigate the implementation partner just as carefully as the software itself.

        Some of the most important questions to ask include:

        • Who will actually be responsible for delivering the programme?
        • Do those individuals have relevant industry experience?
        • How involved will senior consultants be throughout implementation?
        • What is the proposed approach to data migration, integration, testing and change management?
        • Will delivery depend on subcontractors or offshore resources?
        • What governance and escalation processes will be in place?
        • Can the partner demonstrate experience delivering comparable projects?
        • How will continuity be maintained if key members of the delivery team leave?
        • What support will be available after the system goes live?
        • How will changes to the original scope be managed commercially?

        It’s worth remembering that the people involved in selling the solution won’t necessarily be the people responsible for implementing it.

        Understanding who will actually deliver the programme, and having confidence in their experience, should be a priority before contracts are signed.

        From our perspective in recruitment, this is particularly relevant.

        We understand how important specialist experience can be when businesses are delivering complex transformation programmes. Having the right people involved, whether they’re part of the implementation partner’s team or representing the client, can help identify potential problems before they become much bigger issues.

        Managing Customisation Without Creating Unnecessary Complexity

        Every business has processes that it considers unique.

        Sometimes those processes genuinely provide a competitive advantage or are necessary to meet specific regulatory requirements.

        However, customising a new technology platform to replicate every existing process can introduce unnecessary cost and complexity.

        It can also make future upgrades more difficult, increase testing requirements and create greater dependence on particular suppliers or individuals.

        Before agreeing to customisation, businesses should consider three questions:

        1. Does the existing process deliver genuine commercial, operational or regulatory value?
        2. Could the organisation adapt its processes to use the system’s standard functionality?
        3. Is there another way to meet the requirement without changing the core platform?

        The aim isn’t to avoid customisation altogether.

        It’s about making sure that any changes are genuinely necessary and that the long-term benefits justify the additional investment and complexity.

        This is another area where experienced Business Analysts, Enterprise Architects and Transformation Specialists can help challenge assumptions and ensure decisions are made with the wider business in mind.

        Protecting Your Business Before Signing the Contract

        By the time a business reaches contract negotiations, there’s often considerable pressure to move forward.

        Stakeholders may be keen to get the programme started, implementation dates might already be under discussion and significant time will have been invested in the selection process.

        However, this is precisely when attention to detail matters.

        Commitments made during vendor selection need to be reflected clearly in the final contract and statement of work.

        Important areas to review include:

        • Confirmed project scope and deliverables.
        • Acceptance criteria and responsibilities.
        • Named resources and delivery commitments.
        • Project milestones and timescales.
        • Data migration and integration responsibilities.
        • Testing requirements.
        • Assumptions and exclusions.
        • Change-control procedures.
        • Service levels and support arrangements.
        • Data ownership and exit provisions.
        • Commercial protections and contractual obligations.

        What might seem like a relatively minor ambiguity during negotiations can become a significant problem once implementation begins.

        Commercial, legal and delivery specialists should all have an opportunity to review the agreement from their respective perspectives.

        It’s far easier to clarify expectations before signing than to resolve disagreements once a programme is underway.

        Why Interim Transformation Specialists Can Make a Difference

        One of the challenges organisations face during major technology investments is that the experience required to manage them isn’t always available internally.

        Most SME leadership teams don’t select and implement ERP systems regularly.

        Software vendors and implementation partners, on the other hand, work on these projects every day.

        That naturally creates an imbalance in experience.

        Bringing in an experienced interim specialist can help ensure the organisation has someone representing its interests throughout the process.

        Depending on the requirements, this might involve an:

        • Interim ERP Transformation Lead to oversee the selection process and ensure the proposed solution supports the organisation’s wider objectives.
        • Technical Business Analyst to translate business requirements into clear evaluation criteria and challenge proposed functionality.
        • Enterprise Architect to assess technology architecture, integration requirements and long-term scalability.
        • Interim Programme Director to provide strategic oversight, governance and delivery planning.
        • Procurement Specialist to support vendor evaluation, commercial negotiations and contractual arrangements.

        These specialists can support everything from developing a request for proposal and managing software demonstrations to conducting due diligence, challenging costs and negotiating implementation agreements.

        They can also help mobilise the programme once a supplier has been selected and transfer knowledge to the permanent team.

        The real value isn’t simply having someone who understands the technology. It’s having someone who knows what questions to ask, what risks to look for and how to protect the organisation’s interests.

        For businesses that don’t have this expertise internally, interim appointments can provide access to experienced professionals without immediately committing to additional permanent headcount.

        Building the Right Team for a Successful Technology Transformation

        Selecting the right technology is important, but having the right people to deliver the transformation is equally critical.

        And the skills required at the beginning of a programme won’t necessarily be the same as those needed during implementation or after the system goes live.

        For example, the Business Analyst responsible for gathering requirements during discovery may not be the person best suited to lead a complex implementation.

        Similarly, an experienced Programme Director might be needed to establish governance and oversee delivery, while specialist Data Migration Consultants or Change Managers become more important as the programme progresses.

        Depending on the size and complexity of the transformation, organisations may require expertise across:

        • Business analysis and requirements gathering.
        • Business process improvement and transformation.
        • ERP architecture and technical design.
        • Data management and system integration.
        • Programme and project management.
        • Organisational change management.
        • Software testing and quality assurance.
        • Data migration.
        • Vendor and supplier management.
        • Cutover planning and go-live.
        • Hypercare and continuous improvement.

        This is where working with a specialist business transformation recruitment partner can be particularly valuable.

        At Broster Buchanan, we understand that successful transformation programmes depend on more than simply filling vacancies.

        It’s about understanding the stage of the programme, the challenges the organisation is facing and the specific expertise needed to move things forward.

        Whether a business needs an experienced interim professional to provide immediate support or is looking to build a permanent transformation capability, having access to the right specialist talent can make a meaningful difference.

        Just as importantly, it allows organisations to bring in expertise when it’s needed, rather than committing to permanent resources before the long-term requirements are fully understood.

        The Costliest Technology Mistakes Often Start Before Implementation

        When technology transformation programmes encounter difficulties, attention naturally turns to what went wrong during implementation.

        But some of the most expensive mistakes can be traced back much earlier.

        An unclear business case, poorly defined requirements, insufficient vendor due diligence or unrealistic expectations can create problems that become increasingly difficult to resolve once delivery begins.

        The most effective way to reduce these risks is to approach technology selection as a business transformation decision, rather than simply a software purchase.

        That means having:

        • A clear and commercially justified case for change.
        • A well-defined future operating model.
        • Objective and consistent vendor evaluation criteria.
        • Realistic, scenario-based software demonstrations.
        • Thorough product and implementation partner due diligence.
        • A complete understanding of costs and contractual commitments.
        • Experienced leadership representing the organisation’s interests.

        Ultimately, the goal isn’t simply to purchase a new system.

        It’s to invest in technology that supports the organisation’s strategy, improves how the business operates and provides a foundation for future growth.

        Because choosing the wrong technology can be expensive. Spending years implementing a solution that was never right for the business in the first place can be considerably more costly.

        Frequently Asked Questions About Technology Vendor Selection

        What is technology vendor selection?

        Technology vendor selection is the process of evaluating and choosing a software provider or technology partner based on an organisation’s business requirements, technical needs, budget and long-term objectives. A structured selection process helps businesses compare potential suppliers and reduce the risks associated with major technology investments.

        What should businesses consider when selecting an ERP system?

        Businesses should assess functional requirements, integration capabilities, implementation costs, scalability, security, vendor experience and ongoing support. It’s also important to consider whether the system supports the organisation’s wider business strategy and future growth plans.

        Why is a business case important for technology investment?

        A business case helps organisations understand why an investment is necessary, what benefits it should deliver and whether the expected value justifies the cost and associated risks. It also provides a framework for measuring the success of the transformation.

        How can interim specialists support technology transformation?

        Interim transformation specialists can provide experienced leadership and technical expertise during key stages of a programme. This might include requirements gathering, vendor selection, implementation planning, project delivery and change management. They can also help organisations access specialist skills without immediately increasing permanent headcount.

        How Broster Buchanan Can Support Your Business Transformation

        Every technology transformation programme comes with its own challenges, and finding the right people to support it can be one of the most important decisions you’ll make.

        At Broster Buchanan, our Business Transformation recruitment specialists work with organisations to identify the expertise needed to support complex change programmes, from initial discovery and technology selection through to implementation and ongoing improvement.

        Whether you’re looking for an interim ERP Programme Director, a specialist Business Analyst, an experienced Transformation Lead or support building a wider project team, we can help you identify professionals with the relevant skills and experience.

        Planning a technology transformation or reviewing your existing programme?

        Get in touch today


        Lee Clarke, Senior Business Director at Broster Buchanan, specialist in technology and engineering recruitment across the UK and Europe.

        Lee Clarke – Senior Business Director
        Technology & Business Transformation

        t: +447494986917
        e: [email protected]