Discover: mapping a system across a wall of diagramsDiagnose: reading dashboards to locate the problemDesign: wireframes and interface work for the solutionDeliver: shipping the finished productEvolve: continuous improvement after launchA warehouse running on a newly implemented ERP
Configure · Migrate · Train

ERP implementation

An ERP rollout judged by whether people use it, not whether it went live. Most implementations are technically successful and operationally ignored, because the processes were redesigned in a workshop and the people doing the work found a way around them.

  • Use
    Measured after go-live
  • Few
    Customisations, named
  • Clean
    Data before migration
  • Wave
    Not one big bang

Sectors that trust us

What is an ERP rollout?

An ERP rollout replaces several systems and, unavoidably, several working habits. The software configuration is the smaller half. The larger half is deciding which of your current processes are genuine requirements and which are habits that nobody has questioned since the last system was installed.

Configure or customise?
Configure by default; customise only where the process is a real advantage. Every customisation costs at each upgrade for the life of the system, so each is named in writing with its reason.
Big bang or waves?
Waves, with the first small enough that its mistakes are survivable. One cutover across every site means the configuration is first tested on the day there is no way back.

Key takeaways

  • Adoption measured: who uses which screens is checked three months after each wave.

  • Few customisations: each one is written down with the reason it earned its place.

  • Clean data first: profiled and cleaned before migration, never after it.

  • Waves, not a bang: the first wave is small enough to recover from.

  • Training in the system: role by role, on real records people recognise.

Why rollouts get ignored

Where ERP rollouts go live, get ignored, and quietly cost money.

How they get ignored

  • Processes redesigned without the people doing them.

  • Dirty data migrated and cleaned up afterwards.

  • Customisations nobody can justify at upgrade time.

  • Training is a classroom week before go-live.

  • Every site and module cut over on the same day.

  • Old systems left running beside the new one.

How we roll out

  • The people doing the work design the process.

  • Data is profiled and cleaned before it moves.

  • Each customisation is justified in writing.

  • Training happens in the system, on real records.

  • A first wave small enough to recover from.

  • Each old system has a dated switch-off.

What we deliver

From fit-gap to adoption, wave by wave, with the people who use it.

  • Fit-gap and process review

    With the people who do the work, not only their managers, and every gap costed.

  • Data profiling and migration

    Duplicates, gaps and contradictions found before anything moves, then reconciled after.

  • Configure and integrate

    Standard where possible, each exception named; staying systems wired with retries.

  • Training and adoption

    Role-based, inside the system on real records; usage reviewed after every wave.

Systems we roll out

Chosen by fit-gap and by your sites, never by a reseller margin.

We implement across SAP, Oracle, Microsoft and Odoo and hold no reseller agreement with any of them, so the recommendation follows your fit-gap, your sites and your budget. If the system you already own fits, we say so.

  • SAP S/4HANA
  • SAP Business One
  • Oracle NetSuite
  • Oracle Fusion Cloud
  • Microsoft Dynamics 365
  • Odoo
  • Infor

AI on the ERP you have

Your ERP holds the data. Let it answer questions.

Agents read the ERP you run, under its permissions, and answer with the record behind them.

  • Agents over your records

    Ask in Arabic or English and get the answer with the posting behind it attached.

  • Faster closes and quotes

    Draft reconciliations and quotes from live numbers, left for a person to approve.

  • No new system

    It sits beside the ERP you run, inside its permissions; nothing is migrated anywhere.

Works with SAP, NetSuite, Dynamics 365 and Odoo.

How it works · our method

The SiaSol five-phase method, applied to this service.

  1. 01

    Discover

    Most technology projects fail long before the first line of code — they fail at the question.

  2. 02

    Diagnose

    Every slow process has an owner and a cost.

  3. 03

    Design

    Architecture is a set of decisions you live with.

  4. 04

    Deliver

    Software not in production is just cost.

  5. 05

    Evolve

    The handover is the point, not the end.

Where we work

Close where it counts, bilingual everywhere

  • Egypt: Cairo (HQ) and nationwide delivery

  • Saudi Arabia: Riyadh, with teams on client time zones

  • Gulf and beyond: Arabic and English, one delivery standard

Cost & engagement

ERP rollout: cost and engagement

Cost follows the sites, the modules and the state of the data, and the data moves estimates further than anything else. The process and data review is quoted first, on its own.

Fixed scope · one wave at a time

The scope of a wave is locked before it starts, so an overrun has to be a decision somebody takes, never a drift nobody noticed.

  • Fixed · three to five weeks

    Review

    Fit-gap with the people doing the work, a data profile, and a wave plan with a number on each wave.

  • Per wave · quoted after the review

    One wave

    Configured, migrated, reconciled, trained and live at those sites, with usage reviewed three months on.

  • Monthly · optional

    Adoption support

    Screen-level usage review and reconfiguration after each wave, plus your trainers coached.

FAQ

What to ask about ERP implementation.

01Which ERP products do you work with?

Whichever you have chosen or are choosing, and we will give an opinion if the choice is still open. The implementation risks are remarkably similar across products: data quality, customisation creep and adoption, in that order of cost.

02How bad is our data, realistically?

Worse than the team expects and better than the worst case, almost every time. The profile tells you exactly: how many duplicate customers, how many records missing a required field, and how many contradict another system. That report takes a week.

03Can we keep our current processes?

Some, and the review is partly about telling requirements from habits. A process that exists because the previous system could not do something else is not a requirement, and keeping it as a customisation is how upgrades get expensive.

04How long is the first wave?

Usually three to five months including the review, and it deliberately covers fewer sites than the business would like. The first wave is where the configuration gets its first real test, and that test is much cheaper at two sites than at twenty.

05What happens to the old systems?

Each one gets a dated switch-off in the plan, and the ones that stay are integrated properly with retries and reconciliation. A rollout that leaves three old systems running in parallel has added a system, not replaced one: the common quiet failure.

06Who runs training, you or us?

We train your trainers in the first wave and they run it from the second, which is both cheaper and better because they speak the business language. Training happens inside the system on records people recognise, never as slides in a classroom.

07How do you know if people adopted it?

By looking at screen-level usage three months after each wave, not by asking. The useful signal is a team routing everything through one generic screen, which almost always means the specific screen asks for something they lack at that moment.

08Will this need fewer staff afterwards?

That is your decision and we ask it early, because the answer changes whether people describe their work honestly in the review. Teams told the truth up front give better process information, and that information is most of a successful rollout.

Related services

Often paired with this

Learn more

From the journal

Ready for a rollout the people on the floor actually use?

Tell us the sites and the modules. We come back with a wave plan, a data profile and a number you can take to a board.

Book the review