ERP for a small Pakistani business: what to sort out before you pay anyone

Ask ten owners why they want an ERP and nine will say “to get organised.” That is a feeling, not a requirement. It is also where most ERP projects quietly start going wrong, long before anyone has picked a vendor.

We build these systems, so we have a bias. We would still rather you read this first and decide slowly than sign something in a hurry. Here is how we would think about it if the business were ours.

Start with the leak, not the software

Forget feature lists for a minute. Where does money or time actually disappear today? Pick the real one:

• Stock in the shop and stock in the sheet never match.
• Branch managers send sales as a photo of the register at 11 pm.
• Someone asked for a quote on Tuesday and nobody called back.
• You cannot say, right now, who is late and who is absent.

If you can name one of these, you already have a better brief than most companies that spend six figures on ERP. If you cannot name any, you do not need an ERP yet. A tidy spreadsheet and a weekly meeting will do.

What the failure numbers really say

You will hear a statistic quoted at every ERP sales meeting: Gartner research, as widely repeated, says more than 70% of ERP implementations fail to reach the goals in their original business case. Take it with some salt. It is usually quoted second-hand, and the studies behind it are mostly about larger companies in the US and Europe.

But the pattern underneath is steady across surveys. Panorama Consulting, which has surveyed ERP projects for years, keeps finding that many run over budget or over time, and that the usual causes are scope that grows halfway through and organisational problems, not broken code. One consultancy summarising Prosci’s 2025 research reports that the human side matters about six times more than the technical side when it comes to getting value out of the system.

Put simply: the software usually works. People stop using it, or nobody agreed what “done” meant.

A small caution on our own side. Hard data on small businesses in Pakistan is thin. Estimates of how much SMEs contribute to GDP range from roughly 30% to 40% depending on who you ask, and “SME” itself is defined differently by different bodies. So when someone gives you a confident number about Pakistani businesses and ERP, ask where it came from.

Five questions to answer before you pay anyone

1. What is the one number you cannot see today?

Daily sales across branches? Receivables? Open inquiries? The first version of your system should make that number visible. Everything else can wait.

2. Who types the data in, and when?

An ERP is only as good as the entries. If your counter staff are slammed at 6 pm, a system that needs six fields per sale will be skipped by Friday. Ask the vendor to show you the exact screens your cashier would use, not a dashboard.

3. What happens when the connection or power drops?

If any of your branches lose internet or electricity during the day, you need a straight answer on what the system does then. Ask for it in writing. “It should be fine” is not an answer.

4. Who inside your company owns it?

Not the vendor. Not “everyone.” One named person who can say yes or no to a change. Projects without this person drift, and drift is expensive.

5. What can you leave out for now?

Scope growth is the quiet budget killer. Write down what is not in version one. Payroll, HR, manufacturing, the lot. Anything you drop now can come back as a clean second phase.

Why one module first usually wins

Start with the module that hurts most, run it for about three months, and let your team complain about it. Those complaints are the best requirements document you will ever get. Then add the next module.

This is also why we do not publish a fixed price list. The cost depends on branches, users and modules, and anyone who quotes you before asking about those is guessing. What we can say is how we work: the scope is agreed in plain words and in writing before anything is built. You can read how that goes on our how we work page.

If you want to see it before you decide

Have a look at our ERP and business management service, which lists the modules and has an interactive demo with made-up data. If you run a clinic, a school or a retail business, the pages for hospital and clinic management and POS and inventory are closer to day-to-day reality. And if nothing off the shelf fits, custom software is the other route.

Sources

• Panorama Consulting ERP survey findings on budget, schedule and causes of overruns, as reported by CFO.com.
• Gartner and Panorama figures, and Prosci’s 2025 findings, as summarised in ECI’s overview and Alpha Apex Group’s guide. Both are second-hand summaries, so check the originals if the number matters to a decision.
• SME statistics and definitions in Pakistan: Pakistan Institute of Development Economics and The Express Tribune.

Back to Insights