Two Companies Ran the Same ERP Selection and Reached Opposite Conclusions

Two Companies Ran the Same ERP Selection and Reached Opposite Conclusions

How two organizations evaluated the same ERP market, used similar requirements processes, and reached different answers because they were optimizing for different outcomes

The ERP market may be the same. The right answer depends on what leadership is actually trying to achieve.

The following contrived case study illustrates how the Alentra Advisory CFO Transformation Agent, The CFO-TA, helps Executive Sponsors govern Sponsor Intent before an ERP solution is selected. The example demonstrates how Intent Governance establishes the priorities, boundaries, and tradeoffs that guide requirements weighting, vendor evaluation, solution selection, implementation, Sponsor Intent Validation, and Agentic AI design.

Before continuing, a few key concepts are helpful.

The CFO-TA is the Executive Sponsor Platform. It helps Executive Sponsors establish, validate, refine, and govern Sponsor Intent, the Executive Sponsor-owned expression of purpose that guides solution selection, SOW scope, commercial commitments, implementation decisions, accountability, validation, and expected outcomes. Sponsor Intent is formed by three Sponsor-owned responsibilities: Business Intent, Scope Intent, and Transformation Approach Intent.

Sponsor Intent Lifecycle Management Studio (SILMS) is a major capability within The CFO-TA. SILMS helps organizations establish, preserve, validate, continuously monitor, continuously improve, and prove Sponsor Intent throughout the Transformation Program lifecycle. A designated Sponsor Intent Coordinator operates the lifecycle process while Executive Sponsors retain ownership of purpose and major Sponsor-owned decisions.

Business Intent Design is the Executive Sponsor discipline for governing purpose. Intent Governance governs purpose. Execution Governance governs behavior. Together they help ensure that requirements, solution decisions, implementation activities, validation activities, and Agentic AI capabilities remain aligned with the outcomes the Executive Sponsor intends to achieve.

The ERP Selection Everyone Thought Was Objective

A global consulting firm was asked to lead ERP selections for two organizations.

Both organizations were pursuing modernization. Both wanted better reporting. Both wanted stronger controls, improved visibility, reduced operational complexity, and greater readiness for AI-enabled operations.

The same general methodology was used.

Requirements were gathered.

Processes were documented.

Workshops were conducted.

Vendors were evaluated.

Reference checks were completed.

The process appeared objective.

Yet the two companies reached different conclusions.

One selected Microsoft Dynamics.

One selected Workday Financials.

Neither decision was wrong.

At First, The Differences Appeared Small

The Executive Sponsors sounded remarkably similar.

"We need a modern ERP."

"We need better visibility."

"We need to support growth."

"We need stronger controls."

The requirements repositories told similar stories as well.

Hundreds of requirements described workflows, reports, security, approvals, integrations, financial processes, and operational capabilities.

The ERP teams believed they understood the business.

Then vendor-scoring discussions began.

That is when important differences started to emerge.

The Requirements Were Not the Problem

Both organizations had extensive requirements.

The requirements described:

• Workflows

• Security

• Reporting

• Controls

• Integrations

• General Ledger capabilities

• Planning requirements

• Data structures

The requirements defined expected behavior.

They did not define purpose.

They did not explain which outcomes mattered most.

They did not explain which tradeoffs leadership would accept.

They did not explain what should happen when legitimate business objectives competed.

The most important unanswered question remained:

What outcome is the organization actually optimizing for?

Introducing The CFO-TA

The CFO-TA is the Executive Sponsor Platform.

It is a Business-Side platform purpose-built to help Executive Sponsors govern the responsibilities that materially influence solution selection, SOW scope, commercial commitments, accountability, and expected outcomes.

The platform helps Executive Sponsors govern three Sponsor-owned responsibilities:

• Business Intent

• Scope Intent

• Transformation Approach Intent

Together they form Sponsor Intent, the Executive Sponsor-owned expression of purpose and foundation of the Transformation Definition.

Sponsor Intent Lifecycle Management Studio, or SILMS, is a major capability within The CFO-TA. SILMS is used to establish, preserve, validate, continuously monitor, continuously improve, and prove Sponsor Intent throughout the Transformation Program lifecycle.

The Executive Sponsor owns Sponsor Intent.

A designated Sponsor Intent Coordinator operates the Sponsor Intent Lifecycle Management process.

Relevant Business-Side leaders contribute the operational, financial, technology, risk, and domain knowledge needed to make Sponsor Intent actionable.

How The CFO-TA Approached the ERP Selection Differently

Most ERP selection methodologies begin with requirements.

The CFO-TA begins with Sponsor Intent.

Before requirements were weighted, before vendors were scored, and before implementation approaches were evaluated, the Executive Sponsors and leadership teams began establishing the Sponsor Intent that the ERP platform would serve.

Finance leaders contributed financial objectives.

Operations leaders contributed operational priorities.

Technology leaders contributed implementation considerations.

Business leaders contributed organizational goals.

The Executive Sponsor provided overall direction.

The Sponsor Intent Coordinator consolidated those contributions into governed Sponsor Intent Assets.

SILMS served as the governance workspace supporting the process.

The objective was simple.

Establish a governed definition of purpose before making major decisions.

A Day in the Life of the Sponsor Intent Coordinator

The Executive Sponsor remained accountable for Sponsor Intent.

The Sponsor Intent Coordinator operated the lifecycle.

On a typical day, the Sponsor Intent Coordinator did not score ERP vendors, configure software, write technical requirements, or determine which platform should be selected.

Instead, the role focused on ensuring Sponsor Intent was sufficiently explicit, governable, traceable, and actionable.

Typical activities included:

• Reviewing leadership input

• Consolidating workshop outputs

• Maintaining Sponsor Intent Assets

• Coordinating governance activities

• Reviewing findings

• Preparing Sponsor Review Packets

• Tracking assumptions and tradeoffs

• Maintaining governance history

• Monitoring changes that could affect approved Sponsor Intent

The Sponsor Intent Coordinator's primary responsibility was helping leadership discover what had not yet been sufficiently governed.

Challenges the Sponsor Intent Coordinator Encounters

One common challenge involved reporting governance.

Finance leadership wanted globally standardized reporting dimensions and enterprise-wide visibility.

Business-unit leaders supported greater visibility but argued that some local reporting structures represented real operational differences.

Neither position was unreasonable.

Another challenge involved acquisitions.

Executive leadership wanted rapid acquisition integration.

Business-unit leaders wanted to preserve specialized operating capabilities that differentiated their businesses in the market.

Again, both positions had merit.

The issue was not determining who was right.

The issue was governing the relationship between competing objectives before those issues surfaced during solution design, implementation, or operations.

How SILMS Supports Daily Governance Activities

SILMS functions as the governance workspace supporting the Sponsor Intent Lifecycle Management process.

Rather than relying on spreadsheets, disconnected workshops, and institutional memory, SILMS continuously evaluates the evolving Sponsor Intent Asset set.

SILMS analyzes:

• Sponsor Intent Assets

• Open findings

• Conditions of Success

• Trade-offs

• Decision boundaries

• Assumptions

• Validation outcomes

• Change history

Based on that analysis, SILMS recommends governance activities such as:

• Completeness Reviews

• Potential Tradeoff Reviews

• Conditions of Success Reviews

• Validation Reviews

• Change Impact Reviews

• Agentic AI Readiness Reviews

The Sponsor Intent Coordinator selects the activity.

SILMS performs the analysis.

Leadership governs the meaning.

What SILMS Identified Before Vendor Scoring Began

As part of the Sponsor Intent Lifecycle Management process, SILMS evaluated the emerging Sponsor Intent Assets.

Several governance findings emerged.

Potential Tradeoff Finding 1

Enterprise standardization favored common operating processes.

Business-unit autonomy favored local variation.

Leadership had not clearly defined when standardization should prevail and when local flexibility should be preserved.

Potential Tradeoff Finding 2

Rapid acquisition integration favored consistency.

Operational specialization favored preserving unique business practices.

Leadership had not defined how these priorities should be balanced.

Potential Tradeoff Finding 3

Workforce visibility favored integrated planning and reporting.

Organizational independence favored decentralized decision making.

The relationship had not yet been fully governed.

The objective of these findings was not to select an ERP platform.

The objective was to identify Sponsor-owned decisions that remained unresolved.

What Sponsor Intent Revealed at Company A

As Sponsor Intent matured, a clear pattern emerged.

The approved Sponsor Intent Assets emphasized:

• Enterprise Process Standardization

• Acquisition Integration Speed

• Enterprise Financial Consistency

• Reduced Technology Complexity

• Lower Cost to Operate

Individually, none of these priorities was surprising.

Collectively, they revealed something important.

Company A was fundamentally attempting to operate as one enterprise.

Its primary objective was consistency.

The ERP evaluation process began looking different once leadership made that intent explicit.

What Sponsor Intent Revealed at Company B

Company B produced a different outcome.

Its Sponsor Intent Assets emphasized:

• Workforce Visibility

• Organizational Agility

• Integrated Workforce and Financial Planning

• Leadership Insight

• Rapid Organizational Adaptation

The pattern was different.

Company B's primary objective was not operational standardization.

Its primary objective was organizational effectiveness.

The ERP market now looked different because the organization was trying to solve a different problem.

The ERP Team Could Not Answer the Question

As vendor demonstrations proceeded, the evaluation teams asked perfectly reasonable questions.

Which platform better supports acquisition integration?

Which platform better supports workforce planning?

Which platform better supports enterprise standardization?

Which platform better supports organizational agility?

The consulting firm could compare capabilities.

The vendors could demonstrate functionality.

The implementation partner could estimate effort.

None of them could determine which outcome mattered most.

That responsibility belonged to the Executive Sponsor.

Sponsor Intent provided the governing context required to answer the question.

The Scoring Model Had Never Been Neutral

This became the breakthrough.

The organizations believed they were objectively scoring software.

In reality, every ERP scoring model reflects priorities.

Every priority reflects Sponsor Intent.

Questions such as:

• Which capability matters most?

• Which tradeoff is acceptable?

• Which deficiency is tolerable?

• Which strength deserves greater weight?

cannot be answered through software features alone.

They are Sponsor-owned decisions.

Requirements score capabilities.

Sponsor Intent determines which capabilities matter.

Preparing the Sponsor Approval Package

As findings accumulated, the Sponsor Intent Coordinator prepared a Sponsor Approval Package.

The package did not recommend an ERP solution.

Instead, it summarized Sponsor-owned decisions that would influence solution selection.

Examples included:

• Standardization priorities

• Flexibility boundaries

• Acquisition objectives

• Workforce visibility expectations

• Conditions of Success

• Authorized tradeoffs

• Accountability assignments

• Decision boundaries

The Executive Sponsor reviewed the package and approved the resulting Sponsor Intent.

Only then did solution-selection activities proceed.

The ERP Recommendation Changed

The ERP vendors did not change.

The demonstrations did not change.

The requirements did not change.

The market did not change.

What changed was the governing context used to evaluate them.

Both organizations reached different conclusions because they were optimizing for different governed outcomes.

Sponsor Intent Validation Throughout the Transformation Program Lifecycle

ERP selection was not the end of the Sponsor Intent lifecycle.

After solution selection, Sponsor Intent Validation became integrated with major Transformation Program milestones.

Solution Selection Validation

Does approved Sponsor Intent remain aligned with the selected solution?

Solution Design Validation

Do major design decisions remain aligned with approved Purpose?

User Acceptance Validation

Do implemented capabilities support the intended outcomes?

Post Go-Live Validation

Are Conditions of Success actually being achieved?

Execution Governance validates behavior.

Sponsor Intent Validation validates purpose.

Sponsor Intent Improvement

Validation creates evidence.

Evidence creates learning.

Learning drives improvement.

For example, leadership may determine that acquisition integration speed has become more important than originally anticipated.

Or workforce agility may emerge as a higher priority than operational standardization.

The Executive Sponsor remains responsible for approving material refinements.

The Sponsor Intent Coordinator manages the lifecycle.

SILMS maintains complete governance traceability.

The objective is not to prevent change.

The objective is to ensure change remains governed.

How SILMS Tracks Sponsor Intent Over Time

Transformation Programs evolve.

Leadership changes.

Strategies change.

Economic conditions change.

Acquisitions occur.

AI capabilities emerge.

SILMS maintains a governed history of:

• Sponsor Intent Assets

• Findings

• Assumptions

• Tradeoffs

• Validation results

• Improvements

• Executive approvals

Years later, leadership can still understand:

• What was decided

• Why it was decided

• Which assumptions existed

• Which tradeoffs were approved

• Which evidence supported the decisions

• How Sponsor Intent evolved over time

This creates durable Sponsor-owned governance history rather than relying on institutional memory.

Why Sponsor Intent Matters for Agentic AI Design

Historically, experienced people often resolved ambiguity through judgment.

Agentic AI changes that dynamic.

An AI architect designing planning agents, reporting agents, workflow agents, governance agents, or financial-analysis agents must understand:

• What outcomes matter

• What boundaries apply

• Which tradeoffs are authorized

• Which actions require escalation

• How success is measured

• Who governs the decision

Requirements describe behavior.

Sponsor Intent provides governing purpose.

Without governed Sponsor Intent, architects must infer purpose from requirements documents, policies, interviews, and organizational habits.

With governed Sponsor Intent, architects have an authoritative Business-Side reference describing exactly what the organization intends to achieve.

The human governs the loop.

The Difference The CFO-TA Makes

Without The CFO-TA:

Strategy → Requirements → Vendor Selection → Implementation → Metrics

With The CFO-TA:

Sponsor Intent → Governance Activities → Requirements and Design → Vendor Selection → Implementation → Evidence → Sponsor Intent Validation → Sponsor Intent Improvement → Agentic AI Design

ERP selection becomes one event within a governed Sponsor Intent lifecycle.

The implementation serves Sponsor Intent.

Validation tests Sponsor Intent.

Improvement refines Sponsor Intent.

Agentic AI operationalizes governed Sponsor Intent.

Closing

Two organizations can evaluate the same ERP market.

Use similar requirements.

Follow similar methodologies.

Assess the same vendors.

And reach different conclusions.

Both can be correct.

Because ERP selection is not fundamentally a software decision.

It is a Sponsor decision.

The ERP team evaluates capabilities.

The Executive Sponsor governs purpose.

The Sponsor Intent Coordinator operates the lifecycle.

SILMS provides the governance discipline.

And Sponsor Intent determines which capabilities matter.