Freelance ERP Consultant in Jeddah

Backing the family member who leads the project

In a Jeddah family business, an ERP project is rarely led by an IT manager. More often it falls to a younger relative of the owners who has been asked to bring the company up to date. That person has authority on paper, but they still need to persuade a father or uncle who built the business, long-serving managers who distrust change, and an accountant who knows the old system better than anyone.

I work as their independent advisor. Before an owners' meeting, we go through what they plan to propose and where it will be challenged. When an implementer's proposal arrives, I read it with them and point out what is vague or missing. When a manager says the new system cannot handle something, I help find out whether that is true or simply unfamiliar.

Because I am outside the family and outside any vendor, I can raise points a relative might find awkward, such as a process that only exists because one senior employee prefers it. The sponsor stays in charge of every decision. My role is to make sure those decisions rest on facts. For the wider governance questions a family group faces, see my Jeddah ERP consultant page.

Reviewing a system built in-house years ago

Many established Jeddah traders run on a system written for them by a local programmer, sometimes a relative or a trusted employee, and adjusted again and again as the business grew. It often does a few things very well, such as a pricing rule unique to the company or a report the owner checks every morning, and many other things poorly or not at all.

Replacing it is a sensitive matter. The person who built it may still be on staff and may see a review as criticism. I keep the review factual and respectful. I document what the current system does, which of those functions the business genuinely depends on, where data quality has drifted and what risks come from relying on one person to maintain it.

The outcome is not always replacement. Sometimes the right step is to stabilize what exists, move accounting to a standard platform and keep a specialist tool for one job. Where replacement is right, the review becomes a list of must-carry-over functions that any new platform has to prove it can handle. The approach is close to an ERP health check, adapted to a system with no vendor behind it.

When your brand principals want better data

Jeddah has long been home to companies that hold the agency or distributorship for foreign brands, from food and personal care to equipment and vehicles. Sooner or later the principal abroad starts asking for more: sell-out by customer and region, stock on hand by item, marketing fund claims with evidence, and forecasts in their own format.

These requests often expose the limits of an older system. Sales may be recorded by invoice but not by end customer type. Promotions funded by the principal may sit in a general expense account. Stock reports may be produced by hand from several spreadsheets each month.

Before choosing any new ERP, I collect each principal's reporting requirements and turn them into a short list of data the system must capture at the point of sale and receipt. That list then becomes part of what implementers must demonstrate. It stops a familiar problem in which the new system goes live and someone still spends days each month rebuilding the principal's report by hand. I connect this to the purchasing and pricing design described on my distribution industry page.

Fitting advice around Jeddah's busy seasons

Jeddah's commercial year has peaks that owners plan around: the months when visitor numbers climb on the way to Makkah and Madinah, the weeks before Ramadan and Eid when retail and food stock moves fastest, and the city's summer events and holidays. During those stretches, warehouse managers, buyers and finance staff have little time for workshops.

A freelance arrangement suits that rhythm better than a fixed implementation team. We can schedule discovery and process sessions for quieter months, keep my involvement light during a peak and pick up again once it passes. Decisions that need owner attention are timed for when owners are actually available.

The same thinking applies to go-live. I advise against switching systems just before a peak, when a mistake in stock or pricing costs the most and staff have the least patience for learning. A go-live planned for the start of a quiet period gives the team time to settle before the next rush. Your implementer should be asked to commit to a calendar that respects these windows, and I help write that into the plan alongside the ERP implementation approach.

What stays with your team and your implementer

Working remotely from India, I cover the thinking, the documents and the independent checks. Some tasks in a Jeddah ERP project are physical, and they belong with your own people or with an implementer who can be on site.

Stock counts before migration, barcode labels on shelves, handheld scanners for the warehouse, printers for delivery notes and the network in a warehouse on the edge of the city all need hands nearby. So does on-the-spot help for staff in the first days after go-live. I make sure these tasks are named in the plan, assigned to someone and scheduled, rather than discovered the week before cutover.

The engagement runs in English. Arabic print layouts, staff instructions and training material come from Arabic speakers in your company or at your implementer, and I review their structure and completeness. If you are still deciding whether you need an implementation partner at all, my freelance ERP consultant for Saudi Arabia page explains how the roles divide. When requirements need formal documentation, my Jeddah ERP business analyst work takes that further.