5 Questions to Answer Before You Invest in an ERP

Most ERP conversations start with a demo. A company decides it has outgrown spreadsheets, books calls with three vendors, and starts comparing feature lists and prices. We know, because we sit in those presale meetings every week.

What we rarely see is the groundwork. Comparing features is the easy part. The homework that decides whether an ERP will actually pay off happens before you shortlist anything, and most companies skip it entirely.

So before you sit through another demo, answer these five questions. Honestly, on paper, with your team in the room.

1. Why do you need an ERP at all?

"We need to streamline" is not a reason. It is a slogan.

Real reasons look like this: month-end closing takes twenty days. The store issues material with no record of who approved it. Sales commits delivery dates that production never sees. Three departments keep three versions of the same customer list.

If pain like that exists in your business, write it down. Every item, in plain language, with a note on what it costs you in time or money. If you cannot document the pain and it is all intuition, pause here. An ERP bought on a vague feeling tends to get implemented the same way.

That written list becomes the backbone of everything that follows: your requirements document, your demo script, and later, your test cases.

2. Does your team have room for this?

An ERP is not an IT purchase. It is an operations project, and it runs on your people's time.

Someone has to map current processes. Someone has to sit through requirement workshops, clean up years of messy master data, test every workflow, and learn the new system while still doing their day job. If your team is already at full stretch, the project will queue behind daily firefighting and quietly stall.

Look at capacity before you look at software. Free up your key people, even temporarily, or bring in cover for their routine work. A delayed start with a ready team beats an early start with an absent one.

3. Have you studied the change you are asking for?

Two very different situations get mixed up here.

If you already have a standard process that works and you simply want it running on a better system, the change is small and mostly technical.

If the process itself is broken and the ERP is your reason to rewrite it, that is a much bigger event. A new process means new habits, new approvals, and sometimes new roles. Do a short impact study first: what changes, for whom, and where the resistance will come from.

Then do the manpower math. Can the current team cover every role the new process creates? An approval step is only as good as the person who has time to approve it. If the new flow needs a storekeeper who actually records material issues, or a coordinator who actually enters orders, make sure that person exists before go-live, not after.

4. What is the return on time and effort?

Everyone calculates the money side of ERP ROI. Few calculate the other side.

Every minute your team spends inside the system is a cost: entering data, approving requests, maintaining masters. So run each requirement through a simple filter. What does this give back, and to whom?

A workflow that saves your accountant two days at month-end earns its keep. A custom report someone might glance at once a quarter does not, at least not in phase one. Being ruthless about this filter is the difference between a lean system people use and a heavy one they work around.

5. Do hosting and timeline actually fit?

Two practical filters can shrink your shortlist before you compare a single feature.

Hosting first. Some platforms, Zoho for example, run only on the vendor's cloud. If your management or your industry requires data to sit on your own server, that whole category is out. Your search narrows to open-source systems like ERPNext, or commercial platforms such as Odoo that can run on a private server or your own cloud.

Timeline second. Be honest about how much customisation your business needs. A one-month go-live plan does not fit an ERP that needs months of custom development for your use case. Match the depth of change to the calendar, or change the calendar.

Put it all in writing

Answer these five questions and you walk into your first demo holding something most buyers never bring: a documented case. Pain points with costs attached. A capacity plan. A change impact summary. A filtered requirement list. Hard constraints on hosting and timeline.

Selection becomes far easier from there, because you stop asking vendors "what can your system do?" and start asking "here is our situation, show us how you would handle it." The difference between those two conversations is the difference between buying software and solving problems.

ERP selection deserves a post of its own, and it is the next one we are writing. Until then, if you want a second pair of eyes on your groundwork, we are happy to take a look. That conversation costs nothing, and it has saved more than one company from a system it did not need.