---
# === IDENTITY ===
id: business/erp-selection/erp-reference-check-framework/2026
canonical_question: "What questions should you ask ERP vendor references that actually reveal problems?"
aliases:
  - "ERP reference check questions"
  - "vendor reference call framework"
  - "ERP due diligence reference checks"
  - "software vendor reference interview"
entity_type: concept
domain: business > erp-selection > ERP Reference Check Framework
region: global
jurisdiction: global
temporal_scope: 2020-2026

# === VERIFICATION ===
last_verified: 2026-03-08
confidence: 0.88
version: 1.0
first_published: 2026-03-08

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: stable
  last_breaking_change: null
  next_review: 2026-09-04
  change_sensitivity: low

# === CONSTRAINTS ===
constraints:
  - "Vendor-supplied references are pre-screened — they represent best-case outcomes, not typical ones"
  - "Reference customers may have different scale, industry, or module mix than your deployment"
  - "References cannot evaluate features or modules they did not implement"
  - "NDA restrictions may prevent references from disclosing cost overruns or contractual disputes"
  - "Requires shortlisting to 2-3 finalists first — running reference checks on more than 3 vendors is prohibitively time-consuming"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User is evaluating ERP vendors at the RFP stage, not the reference check stage"
    use_instead: "business/erp-selection/erp-selection-master-decision-tree/2026"
  - condition: "User needs to decide whether to continue or abandon an in-progress ERP implementation"
    use_instead: "business/erp-selection/when-to-walk-away-erp-implementation/2026"
  - condition: "User is deciding whether to build custom software vs buy ERP"
    use_instead: "business/build-vs-buy/build-vs-buy-enterprise-software/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: "selection_stage"
    question: "What stage of ERP selection is the user in?"
    type: choice
    options:
      - "Shortlisted 2-3 vendors and need to validate claims before final decision"
      - "Received vendor demos and need to verify implementation quality"
      - "Negotiating contracts and need leverage from reference intelligence"
      - "Comparing reference check frameworks for due diligence process design"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/erp-selection/erp-reference-check-framework/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-08)"

# === RELATED UNITS ===
related_kos:
  related_to:
    - id: "business/erp-selection/when-to-walk-away-erp-implementation/2026"
      label: "When to Walk Away from an ERP Implementation"
  often_confused_with:
    - id: "business/erp-selection/erp-selection-master-decision-tree/2026"
      label: "ERP selection master decision tree — includes the weighted vendor evaluation matrix and scorecard steps"
  depends_on: []
  solves: []
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "ERP Reference Checking: The neglected aspect of the Due Diligence process"
    author: Expandable Software
    url: https://www.expandable.com/blog/articles/erp-reference-checking1.html
    type: technical_blog
    published: 2024-01-15
    reliability: moderate_high
  - id: src2
    title: "ERP Software Customer Reference Checks"
    author: Technology Group International
    url: https://www.tgiltd.com/erp-selection-resources/erp-software-selection-process/erp-supplier-selection/erp-vendor-references-calls
    type: technical_blog
    published: 2024-06-01
    reliability: moderate_high
  - id: src3
    title: "Selecting an ERP System: Checking Customer References"
    author: Visibility Corporation
    url: https://www.visibility.com/blog/selecting-an-erp-system-checking-customer-references
    type: technical_blog
    published: 2024-03-01
    reliability: moderate_high
  - id: src4
    title: "ERP Selection Process Guide"
    author: Panorama Consulting Group
    url: https://www.panorama-consulting.com/erp-software-selection-guide/
    type: industry_report
    published: 2025-01-01
    reliability: high
  - id: src5
    title: "34-Point Contract Negotiations and ERP Selection Checklist"
    author: Pemeco Consulting
    url: https://pemeco.com/erp-selection-checklist/
    type: technical_blog
    published: 2024-09-01
    reliability: moderate_high
---

# ERP Reference Check Framework

## Definition

An ERP reference check framework is a structured due diligence methodology for interviewing a vendor's existing customers to validate claims that cannot be verified through demos, RFPs, or sales presentations. The framework targets five domains that vendor-controlled environments systematically obscure: implementation fidelity (did the project match promises), support quality (post-go-live responsiveness), hidden costs (change orders, unexpected licensing), organizational disruption (change management reality), and long-term satisfaction (would they choose this vendor again). [src1] Reference checks are the only reliable method for validating intangible elements like software quality, ease of implementation, and vendor responsiveness. [src2]

## Key Properties

- **Timing**: Conduct only after shortlisting to 2-3 finalists — earlier checks waste effort on vendors who may not advance
- **Source bias**: Vendor-supplied references are pre-screened; supplement with independently sourced references (user groups, LinkedIn, industry events) [src1]
- **Five critical domains**: Implementation accuracy, support responsiveness, hidden cost exposure, organizational impact, and overall satisfaction [src1]
- **Question design**: Use open-ended behavioral questions ("Describe a time when...") rather than yes/no questions to bypass rehearsed answers [src3]
- **Interview format**: Phone or video calls of 30-45 minutes per reference; minimum 3 references per finalist vendor [src4]

## Constraints

- Vendor-supplied references represent survivorship bias — you only hear from customers who stayed. Churned or failed customers are never offered as references. [src1]
- References may share the same vendor account team but use different modules, versions, or deployment models than your planned implementation. Always confirm configuration overlap before interpreting answers. [src2]
- NDA and contractual gag clauses prevent some references from disclosing cost overruns, litigation, or critical failures — silence on specific topics is itself a signal. [src5]
- Reference checks validate past vendor behavior but cannot predict future performance, especially after acquisitions, leadership changes, or product pivots. [src4]
- The framework requires that RFP evaluation and demos are already complete — reference checks are a validation step, not a discovery step. [src1]

## Framework Selection Decision Tree

```
START — User needs to validate ERP vendor claims
├── Has the user shortlisted to 2-3 finalists?
│   ├── YES → Proceed with this Reference Check Framework
│   └── NO → Complete vendor evaluation first → ERP Vendor Evaluation Criteria
├── What needs validation?
│   ├── Implementation quality and vendor promises
│   │   └── ✅ This Framework — reference checks are the primary tool
│   ├── Technical fit and feature coverage
│   │   └── → Vendor demo + RFP scoring (pre-reference stage)
│   ├── Contract terms and pricing fairness
│   │   └── → ERP Contract Negotiation (reference checks supplement this)
│   └── Whether to continue a troubled in-progress implementation
│       └── → When to Walk Away from an ERP Implementation
└── Does the user have access to independent references (not vendor-supplied)?
    ├── YES → Full framework: vendor-supplied + independent references
    └── NO → Vendor-supplied only — apply stronger skepticism filters
```

## Application Checklist

### Step 1: Prepare the reference request
- **Inputs needed**: List of finalist vendors (2-3), your planned modules, deployment model, company size, and industry
- **Output**: A request to each vendor for 3-5 references matching your profile (same industry, similar size, same modules)
- **Constraint**: Reject references that do not match at least 2 of 3 criteria (industry, size, modules) — mismatched references produce misleading signals [src1]

### Step 2: Source independent references
- **Inputs needed**: Vendor name, target modules, industry
- **Output**: 1-3 additional references sourced from user groups, LinkedIn, Gartner Peer Insights, or industry conferences
- **Constraint**: Independent references are essential for countering vendor selection bias. If you cannot find any, explicitly note this gap in your evaluation. [src4]

### Step 3: Conduct structured interviews across five domains
- **Inputs needed**: Reference contact, 30-45 minute call, standardized question set covering implementation, support, costs, disruption, and satisfaction
- **Output**: Completed interview notes scored against each domain
- **Constraint**: Use the same question set for all references across all vendors — inconsistent questioning makes cross-vendor comparison impossible [src2]

### Step 4: Synthesize and score
- **Inputs needed**: All completed reference interviews (minimum 3 per vendor)
- **Output**: Vendor comparison matrix with domain scores and red flags
- **Constraint**: A single critical red flag (e.g., "would not choose this vendor again" from 2+ references) should trigger escalation regardless of aggregate scores [src3]

## Anti-Patterns

### Wrong: Treating reference checks as a formality
Teams conduct 10-minute calls with scripted questions, check a box, and proceed with the vendor they already prefer. This approach misses the entire purpose: uncovering risks that demos and sales pitches deliberately conceal. [src1]

### Correct: Treating reference checks as investigative interviews
Allocate 30-45 minutes per call with open-ended behavioral questions. Follow up on hesitations, qualified answers, and topics the reference avoids. The most valuable information often comes from what references do not say. [src2]

### Wrong: Relying exclusively on vendor-supplied references
Vendors curate their reference lists to include only their most successful, most satisfied customers. Using only these references produces a systematically optimistic picture that does not reflect typical outcomes. [src1]

### Correct: Supplementing with independently sourced references
Find 1-3 references through user groups, LinkedIn searches, Gartner Peer Insights reviews, or industry events. Independent references have no incentive to protect the vendor relationship and provide more candid feedback. [src4]

### Wrong: Asking about features instead of experience
Questions like "Does the system support multi-currency?" can be answered by a demo. Reference calls should focus on experiential questions that demos cannot address: "How did the vendor handle the first major production issue after go-live?" [src3]

### Correct: Focusing on behavioral and outcome questions
Ask what happened when things went wrong, how the vendor responded to scope changes, and whether the total cost matched initial estimates. These questions reveal vendor character, not just product capability. [src2]

## Common Misconceptions

- **Misconception**: More references are always better — you should talk to as many as possible.
  **Reality**: Diminishing returns set in quickly. 3-5 well-matched references per vendor (including at least 1 independent) provide sufficient signal. Beyond that, the time investment outweighs the incremental information gained. [src4]

- **Misconception**: A glowing reference means the vendor is safe.
  **Reality**: Vendor-supplied references are selected because they are glowing. The relevant question is not whether they are positive, but whether their positive experience maps to your specific deployment scenario (same modules, similar scale, comparable industry complexity). [src1]

- **Misconception**: Reference checks should happen early in the selection process to filter vendors.
  **Reality**: Reference checks are a late-stage validation tool, not an early-stage filter. Conducting them before shortlisting wastes time and annoys references who may be contacted by multiple vendors. Complete RFP scoring and demos first. [src5]

## Comparison with Similar Concepts

| Concept | Key Difference | When to Use |
|---|---|---|
| ERP Reference Check Framework | Validates vendor claims through customer interviews | After shortlisting 2-3 finalists, before contract signing |
| ERP Vendor Evaluation Criteria | Scores vendors across features, cost, and strategic fit | During RFP evaluation and demo phase |
| ERP Contract Negotiation | Secures favorable terms using leverage including reference intelligence | After reference checks confirm vendor selection |

## When This Matters

Fetch this when a user has shortlisted ERP vendors and needs to validate vendor claims before making a final selection decision. Also relevant when designing a due diligence process for enterprise software procurement or when a user asks what questions to ask ERP vendor references.

## Related Units

- [When to Walk Away from an ERP Implementation](/business/erp-selection/when-to-walk-away-erp-implementation/2026)
- [Build vs Buy for Enterprise Software](/business/build-vs-buy/build-vs-buy-enterprise-software/2026)