Technology consulting
Know what to change before you spend on it.
Sahla diagnoses how the business actually works, defines what should change, and helps you make the technology decisions that follow.
Standalone advisory or embedded within delivery.
Scoped and priced before we start, and we will tell you if the business case does not hold.
When you need us
The moments this work usually starts.
These are situations, not a service list. Each line below is a decision someone got stuck on.
Things we hear
- “We are about to spend on an ERP and I cannot tell if it is the right one.”
- “The project has been going for months and nobody can tell me if it will land.”
- “Everyone has an opinion on build versus buy and they all work here.”
- “The board keeps asking about AI and I do not have an honest answer yet.”
- “I need a CTO's judgement for one decision, not a CTO.”
- “Three vendors are pitching and they all sound the same.”
- “We went live six months ago and nothing actually got faster.”
- “Every department brings a different number to the same meeting.”
- “Someone else is building it and we have no way to check the status we are given.”
The questions we answer
Eight questions, in the order we work.
Consulting follows the same method as every Sahla engagement: Diagnose, Define, Deliver, Improve. Each stage answers two questions and ends in something concrete.
- Stage 01
Diagnose
Why change?
What should change?
- Technology strategy & business case
- Data, analytics & AI strategy
- Business & process analysis
You getA current-state diagnosis and a business case.
- Stage 02
Define
Which solution?
How should it be designed?
- Vendor-neutral selection & build/buy
- Requirements & solution definition
- Solution & architecture design
You getA solution definition, an architecture, and a vendor recommendation.
- Stage 03
Deliver
How should it be implemented?
How is risk controlled?
- Roadmap & sequencing
- Implementation oversight & assurance
You getAn implementation plan with governance, and independent oversight.
- Stage 04
Improve
How do you operate it?
Did it produce the result?
- Adoption & change
- AI adoption support
- Performance review
You getAn adoption plan and a results review.
In consulting-only work these stages end in decisions and documents. In delivery work they keep running into the build.
What you walk away with
Documents your team can act on, with or without us.
Everything below can be handed to your board, your team, or the vendor who ends up building it.
- 01
Roadmap
The order to do things in, and roughly when.
- 02
Business case
What the change costs, what it returns, and whether it is worth doing.
- 03
Requirements & solution definition
What the solution has to do, in enough detail that someone can build or buy against it.
- 04
Vendor evaluation & recommendation
Which platforms we looked at, how they compared, and which one we recommend.
- 05
Implementation plan & governance
Who does what, in what order, and who decides when something slips.
Data & AI advisory
AI, applied where it pays.
We answer three questions, in order, and we are comfortable when the answer to the first one is not yet.
- Should we use AI?
- Are we ready?
- How do we adopt it?
Rolling out AI across regional offices?
Why Sahla for this
Advice you can hold us to.
Platform-neutral
The right tool for the decision, not the one we are paid to resell. Who implements it afterwards is a separate decision, taken separately.
Consulting and implementation in one team
The people advising you have built these: ERP, automation, AI.
Accountable after
We do not hand over a document and disappear. The same team can oversee delivery, assure vendors, and review whether the result actually arrived.
Marwan Rekaby · Principal advisor
10+ years leading technology transformations and platform decisions for mid-market firms across MENA.
- Certified ERP & Information Systems Engineer
- Odoo certified
- PMI certified
- IBM certified
Standalone or embeddedStrategic or operationalBefore, during, or after a project
Consulting is a product on its own, not just the first step of an implementation.
Selected results
Advice that changed the decision.
One consulting-only engagement: what was at risk, what we did, and what the business decided differently.
- Operations teams across MENAAI for Business
More than 200 repetitive workflows moved from manual work into production automation.
Read the case studyProduction workflows automatedfrom0 in Sahla portfolioto200+ deployedcumulative through early 2026 - A printing manufacturer, EgyptManufacturingOdoo
Core operations are moving into one ERP — and the team is already seeing the difference.
Read the case studyCore departments on shared ERP pathfrom0 departmentsto5 core functionsimplementation phase - A hospitality operator, MENATourismOdoo
A legacy hotel system became the starting point for a connected hospitality operating platform.
Read the case studyCore platform directionfromlegacy HMSto1 connected ERP/HMS modelafter discovery and demonstration
Questions we get
Before you buy consulting.
Not always. If you already know what to build and why, go build it. You need us when the decision itself is uncertain. A few weeks of analysis is cheaper than a wrong project.
No. We are platform-neutral, and the recommendation stands whether or not we build it. Sometimes the answer is that you should not build anything yet.
Then the work is usually oversight and assurance: an independent read on whether the project is where it says it is, and what to do about it if not.
A few hours a week from the people who do the work. We do not need a dedicated project team, and we do not run workshops for their own sake.
Not sure what your business needs first?
Start with the assessment. It tells you where your operation stands and what we would look at first.
- No technology recommendation before we understand the problem.