Technical services and asset management

15 solutions assessed before an ERP RFP

Client
Quebec organization with complex operations
Platform
Comparative evaluation of multiple business systems
Engagement
Feasibility study, requirements definition and market review
Year
The question

How can an organization compare ERP options before issuing an RFP?

The short answer

A Quebec organization assessed 15 business software solutions before launching a formal ERP procurement process. Seven were screened out and eight advanced to deeper review. Requirements, integrations, and five-year costs were assessed. None met every objective, so PlanAxion recommended a structured RFP rather than selecting a vendor prematurely.

01

Context

A Quebec organization was considering the replacement of a critical internal system and a broader modernization of its business applications. Its needs covered asset management, projects, maintenance activities, finance and human resources.

Before approaching vendors through a formal process, leadership needed to understand which available solutions could support its operations, which integrations would be required, and what implementation and operating costs to expect over five years.

02

The challenge

The challenge was not simply to find software. The organization needed a shared, evidence-based decision framework before committing to a major project.

  • Clarify requirements: document functional and technical needs, then validate them with leadership.
  • Plan integrations: identify necessary connections to existing systems and services.
  • Compare options objectively: screen for solutions that met critical requirements.
  • Prepare the decision: assess feasibility and cost before issuing an RFP.
03

The approach

PlanAxion divided the engagement into two phases.

  1. Requirements definition. Workshops with stakeholders documented operational processes, functional and technical requirements, and integration needs, with leadership validation before market assessment.
  2. Market and solution assessment. The team identified potential solutions, performed an initial fit assessment and presented findings to leadership, including five-year implementation and operating cost estimates.

The evaluation covered project delivery, assets and maintenance, finance and human resources, along with technical capabilities and vendor fit.

04

The findings

15 solutions reviewed. No perfect match.

Fifteen solutions were examined. Seven were screened out at this stage due to vendor nonresponse, a mismatch with requirements, or lack of French availability. Eight moved forward for deeper analysis.

Several platforms could support substantial parts of the organization's processes, but none fully met all stated objectives. Estimated five-year ownership costs also varied significantly across options.

These figures describe preliminary screening. The eight shortlisted for further assessment were not a final vendor selection.

05

The recommendation

PlanAxion recommended not selecting a vendor at this stage. The next step was a deeper comparison of fit, cost and expected benefits, followed by a formal RFP to identify finalists and prepare a recommendation for leadership.

The documented outcome was a better-structured decision process, not a completed ERP implementation.

06

Transferable lessons

Lessons for your own ERP selection

  • Do not mistake screening for selection. Eight viable options do not automatically represent eight final bidders.
  • Test language requirements early. A technically suitable product can still fail a critical operational need.
  • Compare multi-year costs. Initial price alone cannot describe the cost of implementation and operation.
  • Define integrations before vendor demos. Missing integration requirements can distort a comparison.
  • Make trade-offs explicit. A rigorous process does not assume one solution will meet every requirement.

Evidence boundary: this engagement documents requirements definition, market screening and preparation for a formal procurement process. It does not document realized savings, a final purchase, or post-implementation performance.

Preparing to select an ERP?

Explore our independent ERP selection advisory and our ERP RFP guidance. Discuss the decision you need to make.

FAQ

Frequently asked questions

Why define requirements before choosing an ERP?

Requirements establish comparable criteria and distinguish essentials from secondary features. Without them, vendor demonstrations and proposals can be difficult to evaluate consistently.

Were the eight solutions final bidders?

No. They were selected for further analysis. The engagement recommended a formal RFP to identify finalists and inform the ultimate decision.

What matters beyond an ERP's purchase price?

Implementation, integration and operating costs over multiple years, as well as functional and technical fit and vendor capability, all belong in the assessment.

Did this engagement result in a purchase or completed implementation?

The record documents an assessment of 15 solutions, the screening of eight for further review, and a recommendation to proceed toward a formal RFP. It does not document a final choice or deployment.

Your project

Need to validate an ERP project before deciding?

A PlanAxion partner replies within 24 business hours.