A costly ERP mistake can happen before the first vendor call: the leadership team schedules demos without agreeing on success measures, process ownership, or data readiness. The selection can then become driven by what each vendor demonstrates best rather than by what the business needs.
This is the Metrotechs pre-selection framework for organizing those business decisions before comparing software.
Why Preparation Is the Decision That Governs Everything Else
Consider the risk when a team agrees the current system is broken and moves directly into demos. Vendors present polished workflows against sample data, while the team has not defined its own exceptions or decision rights. During implementation, that gap can surface as process misalignment, migration problems, and unresolved ownership conflicts.
Metrotechs guidance treats preparation as risk reduction: a small amount of alignment before demos can reduce rework caused by a misaligned selection.
The Four Elements of Structured Pre-Selection
Pre-selection is not the full implementation specification. In the Metrotechs framework, it is a governance foundation with four written elements completed before vendor evaluation.
Measurable business outcomes. Replace phrases such as "better visibility" or "faster close" with owned measures. Examples might include reducing order-to-cash time, closing within a defined number of business days, or eliminating a named manual reconciliation. Each outcome needs a named executive owner — the person accountable for the result after go-live, not just during the project.
Named process owners for each core workflow. Metrotechs guidance is to assign an accountable owner for order-to-cash, procure-to-pay, inventory management, financial close, and any other workflow in selection scope. This is not a project role. It is the person who understands how the workflow actually runs today, can describe the exceptions and edge cases, and will be accountable for how it runs in the new system. If that person is absent from evaluation, the team may miss the exceptions that determine whether a workflow actually fits.
Decision rights. ERP implementation roadmap guidance emphasizes explicit decision rights and ownership. The Metrotechs framework names two roles: an executive sponsor with authority to make binding decisions on scope, budget, and tradeoffs, and an internal program lead who coordinates activities and holds the team accountable day to day. Without these roles, contested decisions can become avoidable delays.
Data readiness assessment. ERP requirements guidance separates functional, technical, and non-functional requirements. Data readiness supports all three because the selected system must operate on the business records it receives. If the item, customer, vendor, or account records contain duplicates, inconsistent naming, missing fields, or contested ownership, migration can expose those problems late. Assign a business owner for each data domain; finance may own the chart of accounts and operations may own the item master, but the accountable role should match the business. IT supports migration without automatically owning the underlying records.
How Vendor Evaluation Works When Preparation Is Complete
A team that completes this preparation can evaluate vendors against its own operation. Instead of watching only a scripted demo, the team gives each vendor a scenario script built from its own operation: their actual products, their real customers, their known exception cases. A distributor with lot-tracked inventory and customer-specific pricing evaluates whether the system handles those workflows — not whether it handles a generic order.
A service business with project-based billing evaluates revenue recognition against its actual contract types. That assessment is not a vendor activity. It is an internal one. Pass-or-fail requirements — the workflows the system must handle without customization — are defined before the first presentation. Weighted selection criteria are agreed on before scoring begins.
Enterprise software evaluation guidance supports agreeing on outcomes and criteria before comparison. The Metrotechs framework uses that discipline to help evaluators score the same requirements instead of applying different expectations to each demo.
Where the Boundaries Are
Pre-selection is not implementation planning. It does not produce a project plan, a configuration specification, or a data migration map. It produces four things: written outcome definitions with named owners, named process owners for each core workflow, named decision authorities, and a data readiness assessment that identifies what needs to be cleaned before migration begins.
Detailed configuration and implementation planning follow selection, but the team should identify high-level module, integration, deployment, security, and data constraints before comparing vendors. Outcomes and process ownership govern those boundaries; vendor-specific design decisions come later.
One practical boundary worth naming: data readiness assessment does not mean data migration. It means understanding what you have. How complete is the item master? Are customer records deduplicated? Does the chart of accounts reflect how the business actually reports, or does it reflect how the business reported five years ago? Answer these questions before selection so data constraints influence vendor evaluation rather than appearing for the first time during implementation.
What to Audit Now
The following checklist reflects Metrotechs guidance based on the preparation dependencies described above. Complete these before scheduling any vendor demonstration.
- Document a prioritized set of measurable business outcomes the ERP must deliver, with a named executive owner for each. "Better reporting" is not an outcome. "Close the books within five business days of month-end, owned by the CFO" is an outcome.
- Assign a named process owner for each core workflow: order-to-cash, procure-to-pay, inventory management, and financial close. Each owner should be able to describe the current workflow, its exceptions, and what a successful future state looks like.
- Name an executive sponsor and an internal program lead with explicit decision rights before vendor evaluation begins. The sponsor must have authority to resolve scope, budget, and tradeoff decisions. The program lead coordinates activities and holds the team accountable day to day.
- Assess the item master, customer master, and chart of accounts for completeness, duplication, and naming consistency before migration planning begins. Identify which records are authoritative and which are stale or duplicated. Assign a business owner to each domain; finance may own the chart of accounts and operations may own the item master, but accountability should match the organization.
- Identify which data objects are owned by which team and whether that ownership is documented or informal. If two departments both maintain customer records, that conflict needs a resolution before the new system is configured.
- Build enough end-to-end business scenarios to cover the highest-risk workflows and exceptions using the company's own products, customers, and exception cases as the vendor evaluation script. These scenarios replace the vendor's demo script and reveal how each system handles the workflows that actually matter to the operation.
The Next Useful Step
If the leadership team cannot complete the items above in a structured working session, treat that as a signal that alignment may be incomplete. Vendor demos are unlikely to resolve disagreements about the business outcome or decision rights. It may surface during implementation, when changing direction is harder and more expensive.
The pre-selection step is not merely administrative overhead. It shapes the quality of the selection and the implementation that follows. Written outcomes, named process owners, and a data readiness assessment help the team compare vendors consistently instead of relying on the most persuasive demo.
If your team has agreed an ERP evaluation is needed but has not yet completed structured pre-selection, organizing that profile — your current systems, your workflows, your data state, your priorities — is the right first move before any vendor conversation begins. Launchpad Free is a starting point for that work; the complete structured intake and finished Enterprise Roadmap are Enterprise Launchpad capabilities.