There is no perfect ERP. But there is a right way to choose one. For MSMEs where decision-makers are involved in every aspect of the business, a structured approach to selection and implementation makes the difference between a system that transforms operations and one that gets abandoned six months after go-live.
Understand Your Business Before Looking at Software
The most common and expensive mistake in ERP selection: starting by evaluating vendors instead of understanding your own operations. Before you look at a single demo, document how your business actually works. Every department. Every process. Every approval.
This documentation serves two critical purposes: it tells you what you need from a system, and it helps you evaluate whether a vendor's demo reflects your reality or a generic workflow that has nothing to do with how you operate.
Step 1: Identify All Operations
List every operation that happens in your business — from sales order creation to dispatch, from purchase requisition to payment, from production planning to quality check. This is the scope of work that any system will need to handle.
Step 2: Structure Your Operations
Group related operations into logical categories. This becomes the module structure of your future system. Don't design an org chart — design a process map. How does information flow? Who hands off to whom? Where do delays typically occur?
Step 3: Create Process Flows
For each operation, map out every step — every decision point, every person involved, every data element that passes between them. This is the most time-consuming step, and also the most valuable. It will:
- Reveal inefficiencies you've normalised and stopped noticing
- Identify where automation will save the most time
- Surface the real requirements you'll need from any system
Don't skip this step
Businesses that skip process mapping end up selecting systems based on feature lists, then discovering during implementation that the system doesn't handle their actual workflow. This is the leading cause of failed ERP projects.
Step 4: Collect Ground-Level Challenges
Talk to the people who actually do the work — not just managers. Ground staff know where the real friction is. They know which tasks take hours that should take minutes, which approvals get stuck, which data gets entered twice because two systems don't talk. Their input is invaluable for designing a system that people will actually use.
Step 5: Identify What to Digitise
Not every process needs to be in the system. Evaluate each process against the value of digitising it. The highest-value candidates are repetitive, error-prone, or dependent on information from another department.
Step 6: Plan Automation
Automation goes beyond digitisation. Identify which processes can be triggered automatically — stock alerts, approval reminders, report generation, invoice creation. Automation is where the compounding productivity gains happen.
Step 7: Define What Information You Need
Decide what reports and dashboards leadership needs before implementation begins. This is often neglected — and then businesses find that the system they implemented can't produce the analysis they need. Know your information requirements in advance.
Step 8: Evaluate Vendors Against Your Requirements
With documented processes and a clear list of requirements, vendor evaluation becomes structured. Ask every vendor to demonstrate your specific use cases — not a generic demo. Ask how they handle your edge cases, your compliance requirements, your approval structures.
Accept that no system is perfect
The goal is not to find a perfect system. It's to find the best system that covers most of your needs, minimises disruption, and can be customised to handle the gaps. A clear understanding of which gaps matter most to your business will make this decision much clearer.