We run a maintenance shop, comparing CMMS software — off-the-shelf or custom development?

We faced the exact same dilemma at our hydraulics shop in Dammam three years ago and went the custom software route. The project started at 60,000 SAR and ballooned to 110,000 SAR with scope creep. To make matters worse, the agency that built it shut down two years later, leaving us unable to touch the source code. We finally migrated to an off-the-shelf system, and our yearly spend became way more predictable.

The agency quoting 85,000 SAR most likely doesn't understand the real shop-floor dynamics of a maintenance workshop. Once cross-referencing part equivalents, overhaul histories, and warranty tracking enter the picture, that quote will double and delivery will be delayed by at least six months. A workshop floor is no place to train software devs.

Edit: asked below, I wrote the answer in the second message.

If you go with an off-the-shelf tool, check two technical must-haves: offline mode support and barcode scanning. Cell service can be spotty out on the shop floor or next to field vehicles. Techs need to be able to complete work orders offline, with data auto-syncing once they reconnect. Building reliable offline data synchronization into a custom app requires serious technical muscle.

if the techs on the floor refuse to fill out the forms even the most expensive system is useless. get a trial of a ready-made software and hand it to your two most stubborn mechanics... if they can manage it stick with the off-the-shelf one imo.

Don't sign a contract right away. Ask the vendor for a one-month pilot before paying 18.000 SAR annually. Just add 30 machines to the system during that time and test it with 5 technicians. If the team gets used to it, you can move forward with an annual deal.

Do your clients expect to see their machines through their own portal and submit support tickets? Or will this software strictly be used for your own internal operations, inventory, and technician tracking? This distinction directly determines which tier of off-the-shelf packages you'll actually need.

Your core business is maintenance and service engineering, not software maintenance. Trying to run an area outside your core competencies in-house with custom code is a waste of energy. Getting an off-the-shelf CMMS and aligning your operational workflows with that system's industry-standard best practices will also speed up the professionalization of your workshop.

Exactly, and not many people know this. Don't enter any agreement without an exit plan.

A two-week notebook guides you more than a six-month forecast.

You're right. When making a decision, also write down the cost of reversal.

If you have questions, write them; I'll answer as best I can.

Exactly and not many people know this. The harder it is to reverse a decision the slower you should make it.

You're right. Mistakes made on the maintenance management software side are usually reversible but expensive.

Hasty decisions become decisions you have to fix six months later. Proven by experience.

Let me summarize the topic since several different answers were given. If you get three different answers on a topic, the question was asked wrong.

let me summarize what's been said so far. when making a decision, also write down the cost of reversal.

corrrect me if I'm wrong.

This thread is archived.

I completely agree. I mean the harder it is to reverse a decision the slower you should make it.

That's all, sorry if I went on too long.

Here's how it went for us. Hasty decisions become decisions you have to fix six months later.

Everyone rushing into maintenance management software gets stuck at the same point. I'm also curious if anyone does it differently.

I have an objection here. People defend habits, not processes. Resistance comes from there.

To get into the details: Trying to do this alone is the most expensive way.

I'm also curious if anyone does it differently.