# ERP Selection Decision Memo Template

> Source: https://netray.co/tools/erp-selection-decision-memo-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Write the executive memo that recommends an ERP vendor: context, options, scoring, cost, risks, conditions and approval lines.

## Category

erp-migration

## Audience

- CIO
- ERP project lead
- CFO

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Memo date

**Key:** date

**Type:** date

**Default:** 2027-03-15

#### From

**Key:** from

**Type:** text

**Default:** ERP Steering Committee

#### To

**Key:** to

**Type:** text

**Default:** Executive Leadership Team and Board

#### Recommended vendor and product

**Key:** vendor

**Type:** text

**Default:** Vendor B, Product X Manufacturing Edition

#### Implementation partner

**Key:** partner

**Type:** text

**Default:** Partner P (regional, 40 consultants)

#### Runner up

**Key:** runner_up

**Type:** text

**Default:** Vendor A

#### Winning weighted score

**Key:** score_win

**Type:** text

**Default:** 82 out of 100

#### Runner up score

**Key:** score_runner

**Type:** text

**Default:** 76 out of 100

#### Five year total cost

**Key:** five_year

**Type:** text

**Default:** USD 4.2 million including 15 percent contingency

#### Target go live

**Key:** go_live

**Type:** text

**Default:** Q3 2028, phased by plant

#### Top risks and mitigations

**Key:** risks

**Type:** textarea

**Default:** 1. Data quality of item master: cleanse before conversion, owner is Supply Chain.
2. Customisation of legacy quality workflows: re-fit to standard where possible.
3. Key person dependence on two internal experts: backfill and train two deputies.

#### Conditions of recommendation

**Key:** conditions

**Type:** textarea

**Default:** Fixed price for the design phase, named consultant team, exit and data return clauses, and a price cap on annual subscription increases.

**Blocks:**

#### Decision Memo: ERP Platform Selection

**Body:** Company: {{company}}
Date: {{date}}
From: {{from}}
To: {{to}}

#### 1. Recommendation

**Body:** We recommend {{vendor}}, implemented by {{partner}}, subject to the conditions in section 6. The recommended option scored {{score_win}} against {{score_runner}} for {{runner_up}} in the weighted evaluation.

#### 2. Why now

**Body:** Describe the business trigger in two or three sentences: end of vendor support, audit findings, growth plans, a compliance requirement or a failed upgrade. State what happens if no decision is taken.

#### 3. Options considered

**Table:**

**Columns:**

- Option
- Weighted score
- Five year cost
- Main strength
- Main concern

**Rows:**

**0:** {{vendor}}

**1:** {{score_win}}

**2:** {{five_year}}

**3:** Fit to core processes

**4:** Dependence on partner capacity

**0:** {{runner_up}}

**1:** {{score_runner}}

**0:** Stay and upgrade current system

**3:** Lowest short term cost

**4:** Support and skills risk

#### 4. Cost and timeline

**Body:** Five year total cost of ownership: {{five_year}}. Target go live: {{go_live}}. Costs cover software, implementation services, infrastructure, internal staff time, training, data migration, support and contingency.

#### 5. Key risks

**Body:** {{risks}}

#### 6. Conditions

**Body:** {{conditions}}

#### 7. Decision requested

**Body:** Approve the recommendation, authorise contract negotiation within the budget above, and appoint the executive sponsor for the implementation program.

#### Approval

**Signatures:**

- Chair, ERP Steering Committee
- Chief Financial Officer
- Chief Executive Officer

**Notes:** Replace the guidance text in section 2 with your own business case. Attach the weighted scoring sheet, reference call summary and cost model as appendices. This is a general format, not legal or financial advice.

## Content

**Intro:** After months of RFPs, demos and calls, the decision still has to be sold to people who saw none of it. This memo template puts the recommendation, the evidence, the cost and the risks on two pages so executives can approve with confidence.

**Sections:**

#### How to use the template

**Body:** Fill in the vendor, partner, scores, cost and timeline. Write the reason for the project in section 2 in your own words. Edit the risks and conditions to reflect your negotiation. Export to Word and attach the appendices: scoring matrix, total cost model, reference summary and the draft contract position. Keep the memo itself to two pages, because executives read the front page and look up details only when needed.

**Bullets:**

- Lead with the recommendation, not the history
- Show the runner up and the do nothing option
- Put the five year cost, not only licence cost
- Make conditions explicit

#### What executives want to see

**Body:** Boards and CFOs ask four questions: what are we buying, what does it cost in total, what could go wrong, and what happens if we do nothing. The memo answers each in one section. It also names the people accountable. Avoid vendor marketing language and avoid unexplained scores; refer to the appendix for how weights were set before the RFP was issued.

#### Presenting cost honestly

**Body:** Quote the full five year cost including internal staff time, data migration, training, infrastructure and contingency. A memo that shows only software fees will be challenged later when services and internal costs arrive. Show the contingency as a visible line, commonly 10 to 20 percent for ERP programs, and say what is excluded, such as major process redesign or acquisitions.

#### Common mistakes

**Body:** Memos fail when they bury the recommendation, hide dissenting views, or ask for approval without conditions. Note any committee member who disagreed and why. Conditions such as named consultants, fixed price design phase and exit rights are far easier to obtain before the board has publicly approved a preferred vendor than after.

**Cta:** If you want a technical sanity check on the integration, data conversion and AI readiness claims in your recommendation, Netray can review those sections.

**Faq:**

#### How long should an ERP decision memo be?

**Answer:** Two pages plus appendices. The first page carries the recommendation, cost and timeline. The second covers options, risks and conditions. Put scoring detail, reference notes and the cost model in appendices.

#### Should I include the losing vendors?

**Answer:** Yes, at least the runner up and the do nothing or upgrade option. Executives want to see that alternatives were compared, and it supports your negotiation position if the preferred vendor is told a credible alternative exists.

#### Who should sign the memo?

**Answer:** The steering committee chair, the CFO and the executive sponsor at a minimum. Follow your own delegation of authority for the contract value. Board approval may be needed above a threshold.

#### Can the memo recommend conditional approval?

**Answer:** It should. Approving subject to contract terms, such as price caps, named resources and exit provisions, gives your negotiators authority to walk away if the vendor refuses those conditions.

## Search terms

erp selection recommendation memo, erp vendor recommendation template, erp decision memo, erp board approval memo, erp selection report template, erp recommendation to executive committee

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json