ERP Readiness Checklist for Growing Indonesian Companies
By Apex Horizon Digital
A company is ready for ERP when it can make the decisions the system needs. Budget and growth matter, but readiness depends more on whether the business can name process owners, agree on operating rules, prepare usable data, allocate reviewers, and support users through change. Buying software before these conditions exist usually moves unresolved disagreements into a more expensive place. This checklist provides a simple scored review that leadership, operations, finance, and IT can complete together before approving an implementation.
Key takeaways
- Readiness is the ability to make and sustain operating decisions, not merely the ability to buy software.
- Weak ownership and unclear data rules should be repaired before a large implementation starts.
- A low score does not cancel ERP; it identifies foundation work and a safer first phase.
1. Score process ownership and standardization
For each critical workflow, ask whether one accountable owner can explain the trigger, required information, decisions, exceptions, completion condition, and policy. Score zero when ownership is unclear or departments describe conflicting rules. Score one when a knowledgeable person exists but the process is mostly informal. Score two when an owner is named, the target workflow is documented, and exceptions have decision rules. ERP configuration makes operating policy visible. If the company cannot agree on the policy, the project team will either wait for decisions or encode a rule that users immediately work around.
2. Score data quality and ownership
Review customers, suppliers, products, units, prices, opening stock, user accounts, and any historical transactions needed for continuity. Score the data on ownership, completeness, uniqueness, consistency, and the ability to reconcile totals. A clean-looking spreadsheet is not enough if nobody knows who may change a product code or which file is authoritative. Record duplicates, missing keys, ambiguous units, inactive records, and fields created for personal convenience. Readiness improves when each domain has an owner, cleansing rules, a migration decision, and a sign-off method.
3. Score leadership, budget, and delivery capacity
Leadership readiness means more than approving a purchase. A sponsor must resolve conflicts, protect reviewer time, enforce agreed policies, and accept tradeoffs when scope, time, and budget compete. The budget should cover discovery, design, build or configuration, migration, integrations, testing, training, launch support, and a reasonable change allowance. Also identify the people who will attend workshops, review prototypes, prepare data, test scenarios, and support colleagues. A project can have funding and still be unready if every essential reviewer is fully committed to daily operations.
4. Score technology, integration, security, and support
List systems that must exchange data, the owner of each connection, available documentation, credentials, environments, and reconciliation expectations. Confirm how users authenticate, which roles require sensitive access, how backups are tested, and who responds to incidents. Check connectivity requirements for warehouses or branches and whether mobile or offline behavior is truly necessary. Finally, decide who handles user questions, master-data requests, defects, and enhancement ideas after launch. ERP becomes an operating dependency, so readiness includes the ability to own it after the implementation team leaves.
5. Interpret the score and choose the next action
Use five dimensions: process ownership, data, leadership, delivery capacity, and technology. Give each dimension zero, one, or two points using written evidence. A total near the bottom means foundation work should come first. A middle score supports a limited pilot with explicit risks. A strong score supports broader discovery, but it does not justify skipping validation. Review the lowest dimensions rather than celebrating the total. The most useful output is a short action list with an owner and due date for each readiness gap.
- Zero: no owner, no agreed rule, or no reliable evidence.
- One: partial ownership or documentation with material gaps.
- Two: named owner, agreed rule, usable evidence, and a practical sign-off.
- Next step: repair the weakest dimension before expanding the first implementation scope.