Preparing for ERP Implementation

Signs That "It Is Time" for Your Organization to Get ERP

Many organizations do not start from long-term planning — they start because accumulated problems have become unbearable:

• Scattered data — each department has its own Excel files with conflicting numbers, requiring daily phone calls to reconcile
• Redundant work — procurement enters data once, accounting re-enters it, and warehouse enters it again
• No data for decision-making — executives need reports but must wait 3 days to compile them, and by then the data is already outdated
• Cannot scale — the business is growing but the current system cannot keep up, requiring more staff to patch the gaps
• No audit trail — who did what and when is untraceable, making accountability impossible when problems arise
• Hidden costs are draining resources — labor costs for redundant data entry, time spent fixing errors, and lost opportunities from outdated information

If your organization shows 3 or more of these symptoms — that is a clear sign it is time to seriously consider an ERP system.

Before ERP Implementation — What You Need to Prepare

ERP implementation is not just "buying and installing software" — it is about transforming how the entire organization works. Preparation spans multiple dimensions:

1. Executive Readiness (Executive Sponsorship)

This is the most critical factor — if senior leadership is not genuinely committed, the ERP project has a very high chance of failure.

• Executives must understand that ERP is not an IT project — it is a business process improvement project
• There must be an "owner" with decision-making authority — not just delegating everything to the IT department alone
• There must be readiness to allocate resources — budget, people, and time

2. Process Readiness

Before entering data into the system, you must first understand how things work now and how you want them to work:

• Survey current processes (As-Is) — How are things done? What documents are used? Who approves?
• Design new processes (To-Be) — How should things work? What needs to change?
• Identify pain points — What are the recurring problems? Which steps are a waste of time?

3. Data Readiness

Dirty data will cause problems in your new ERP system from day one:

• Master Data — product codes, customer codes, chart of accounts, employee IDs must all be standardized
• Opening balances — carried-forward balances must be accurate and verifiable
• Data cleansing — remove duplicates, correct errors, and standardize formats

4. People Readiness

This is the dimension many organizations overlook — yet it is the primary cause of implementation failure:

• Appoint a Key User team — people who actually know the work, from every relevant department — not those who are simply "available"
• Address fears — employees fear losing their jobs, not learning fast enough, or being caught for mistakes
• Communicate clearly — Why the change? What are the benefits? Who will be affected and how?

ERP Implementation Steps — How to Succeed

Based on ERP implementation experience across many public and private organizations, these are the proven steps:

Step	Phase	Details	Key Responsible Party
1	Project Kick-off	Define scope, objectives, team, and timeline	Executives + PM
2	As-Is Analysis	Survey current processes, documents, and issues	Consultant + Key User
3	To-Be Design	Design new processes aligned with ERP	Consultant + Key User
4	Configuration	Configure system, chart of accounts, workflows, and approvals	Consultant + IT
5	Data Migration	Migrate master data and opening balances	Key User + IT
6	Testing (UAT)	Test the system with real data and verify results	Key User
7	Training	Train actual users, both Key Users and End Users	Consultant + Key User
8	Go-Live	Go live with support team ready	All departments
9	Post Go-Live Support	Monitor, resolve issues, and continuously improve	Consultant + IT

The Hard Truth — When Executives Want ERP to "Reduce Headcount"

This is the most sensitive topic in every ERP project — when executives say "Let the system replace people so we can cut costs."

The reality that must be understood first:

Why "Reducing Headcount" Should Not Be the Primary Goal

If the goal is "reducing headcount"	Typical outcome
Employees find out and resist the system	They withhold information and cooperation, causing implementation failure
Key Users are reluctant, leading to incomplete data	System misconfigured, data inaccurate, unusable in practice
Headcount reduced before Go-Live, leaving no one to run the system	No one to enter data or verify, the system is "dead" despite being installed
Top performers leave early, causing knowledge drain	People who know the work flee first, leaving only those unfamiliar with processes

How to Talk to Executives About This

If you are the one proposing the ERP project to executives, try reframing from "reducing headcount" to "increasing capacity":

Instead of saying...	Try saying...
"Reduce 5 employees"	"Support growth without needing to hire 5 more people"
"No need to hire more accounting staff"	"Accounting staff can do analysis instead of data entry"
"Save on labor costs"	"Reduce costs from errors and eliminate redundant work"
"The system can do everything, no people needed"	"The system handles routine repetitive tasks so people can focus on value-added work"

5 Things That Cause ERP Implementation Failure

From real experience across many projects, the main causes of failure are:

1. No serious Executive Sponsor — the project is dumped on IT alone with no one to make decisions when problems arise
2. Refusing to change processes — wanting a new system while insisting on doing everything the old way, resulting in excessive customization
3. Master Data not ready — skipping data cleansing and migrating garbage data into the new system
4. No proper end-user training — Key Users are asked to train the entire organization when they themselves are not yet proficient, leaving everyone unable to use the system
5. Expecting immediate results — expecting everything to be perfect on day one, when the first 1-3 months are actually an adjustment period

5 Things That Make ERP Implementation Succeed

1. Genuine executive commitment — attending Steering Committee meetings regularly and making decisions at deadlocks
2. Key Users are people who truly know the work — not those who are "most available" but those who are "most knowledgeable" about each process
3. Willingness to adapt processes — adjusting workflows to align with the system's best practices instead of customizing everything
4. Prepare data thoroughly — invest time in proper data cleansing. Good data from the start means no costly fixes later.
5. Plan Change Management — communicate before, during, and after Go-Live so everyone feels part of the transformation

Saeree ERP: Designed for Smooth Implementation

Saeree ERP is designed with Thai organizational context in mind, for both public and private sectors, based on the philosophy that "the system must adapt to people, not the other way around":

Success Factor	How Saeree ERP Supports It
Standard Processes	Built-in workflows supporting Thai procurement regulations, accounting, and budget standards
Reduced Customization	Most requirements are met through configuration — no code customization needed
Thai Language Interface	Menus, screens, and reports are all in Thai, eliminating language barriers
Data Migration Tool	Includes tools to import master data from Excel, reducing data preparation time
Thai Consultant Team	Consultants who understand Thai organizational context — no need to explain regulations and culture
Phased Implementation	Start with core modules first, then gradually expand — no need to change everything at once

A successful ERP is not the best system — it is the system that people in the organization actually use and know how to use. Success is not measured on Go-Live day but on the day everyone works through the system without needing to ask anyone.

- Saeree ERP Team

Conclusion

Starting an ERP implementation is a major undertaking requiring comprehensive preparation — executives, processes, data, and most importantly, people. A good ERP is not a tool to "reduce headcount" but a tool to "empower" people to work better, make better decisions, and maintain stronger internal controls.

If your organization is considering or starting an ERP implementation, you can schedule a demo or contact our consulting team for organization-specific guidance.