Built by Someone Who's Lived Inside ERP
Why MR ERP Solutions Exists
After 12+ years inside ERP projects — from first implementations to emergency rescues — I kept seeing the same pattern: businesses were being handed a system, not a solution. Consultants who didn't understand the business. Developers who built what was asked, not what was needed. Business owners left on their own the moment go-live was declared.
I started MR ERP Solutions to do it differently: deep technical expertise combined with real business understanding — one architect, accountable from day one through long after go-live. Every project gets treated like it's my own business running on the line. Because I've been on the inside long enough to know — it always is.
Every Stage. Every Industry. Since 2012.
Vertical Expertise Across 8+ Countries
What "150+ Projects" Actually Means
Numbers are abstract. Here's what the work looked like in practice — the kind of situations that show up regularly, and what happened when they were resolved properly.
A 12-branch fashion retailer in Dubai had month-end closing taking 3 full days — manual reconciliation between LS Central POS and Business Central financials. The finance team dreaded it every month. Inventory counts were off. Promotions weren't posting correctly.
Rebuilt the POS-to-GL posting logic, fixed the promotion engine configuration, and automated the reconciliation. Month-end close now takes 4 hours — done by lunchtime on the 1st. Inventory variance dropped to under 0.3%.
A Riyadh restaurant group with 8 locations needed ZATCA Phase 2 e-invoicing compliance — their previous partner had quoted 6 months and a large fixed fee. Their BC was heavily customized NAV-era code. They also needed Talabat and HungerStation order sync that had never worked reliably.
ZATCA Phase 2 live in 6 weeks, including Fatoora portal onboarding and cryptographic stamp validation. Delivery platform integration rebuilt from scratch — orders now sync within 45 seconds of placement with automatic kitchen routing.
A mid-size FMCG distributor operating across two countries was running NAV 2015. Their partner had told them a BC upgrade would require a full re-implementation — 12 months and a budget that wasn't feasible. Data was messy: duplicate vendors, open entries going back years, mixed currencies.
Designed a phased upgrade using data upgrade codeunits — cleaned the vendor/customer master first, migrated in stages, went live on BC 2023 in 14 weeks. Zero data loss. All historical transactions preserved and reconciled to the cent across both entities.
All stories are representative of real project types. Client names and identifying details withheld by default — available under NDA for qualified prospects.
Certified. Verified. Accountable.
Microsoft-certified across Business Central, Finance & Operations, Azure, and Power Platform — with active LS Retail and ZATCA compliance expertise.
The Principles I Won't Compromise On
Not a values statement. These are the specific rules I follow on every project — things I've been burned by when they slipped, and never let slide again.
Everything in writing — always
Scope, changes, decisions, known risks — all documented before work begins and updated as the project moves. If it wasn't written down, it wasn't agreed. This protects you as much as it protects me.
I say no to work I can't do properly
If a project needs skills or bandwidth I don't have right now, I say so on the discovery call. I'd rather lose the work than deliver something below standard. You'll hear "I can't do this" from me — very few consultants will say it.
Diagnose before I propose
I don't send a proposal for a system I haven't understood. The discovery call isn't a sales call — it's a working session where I ask the questions needed to give you an honest assessment. If I need more information, I'll say so before quoting.
Bad news travels fast — to you
If something unexpected comes up mid-project — a hidden complexity, a data integrity issue, a timeline risk — you hear about it immediately, not at the end. I'd rather have an uncomfortable conversation early than a crisis late.
Your system data stays yours
I don't share client data, system architecture, or business information with third parties — ever. No case studies without permission. No screenshots in portfolios. NDAs on request, but the same standard applies regardless.
Build for your team, not just for go-live
A system that works on launch day but that your team can't use or maintain is a failed project. I design with handover in mind — clean code, documented decisions, and training that actually sticks. You shouldn't need me forever.
What I Actually Work With Daily
Not a marketing list. These are the tools open on my screen every day — the ones I know inside out from 12+ years of real projects.
What Clients Say After Go-Live
From system rescues to full implementations — feedback from the people who were in the room.
"Our LS Central system was a complete mess before Mahmoud came in. He diagnosed the issues fast, fixed the POS slowdowns, and rebuilt our promotions module properly. Night and day difference."
"We needed a Business Central upgrade with zero downtime — they delivered exactly that. Clean migration, no data loss, and the team kept us fully informed at every single step."
"The payment gateway integration was complex — three platforms, custom workflows, live orders. MR ERP handled it with precision. It's been running flawlessly for over 8 months now."
"We had a failed BC implementation from another partner. Mahmoud came in, diagnosed what went wrong in two days, and had us live within six weeks. Exactly what we needed."
"ZATCA Phase 2 was a deadline we couldn't miss. He delivered the full e-invoicing integration — XML signing, clearance, QR codes — ahead of schedule and with proper documentation."
Book a free 45-minute discovery call — no commitment, no pitch.
⚡ Book Your ConsultationNames anonymised at client request · References available on request
Questions About Me Specifically
The questions prospects ask after reading the services page — about how I actually operate, not just what I offer.
I'm the primary consultant on every engagement — you work with me directly from the first call through go-live. For large implementations that need parallel workstreams, I work with a small network of trusted specialists I've collaborated with for years. If that's the case, I tell you upfront. I never hand off a project to someone you haven't met without your knowledge.
English and Arabic — both fluently. All technical documentation, code comments, and proposals are in English by default. Client-facing training, user manuals, and workshops can be delivered in Arabic where that serves the team better. System interfaces and reports can be configured in either language, or bilingual where BC supports it.
Client system details are confidential by default — I don't share screenshots, code, or architecture from past projects without permission. What I can do: describe the type of work in detail on a discovery call (anonymized), share the specific technical approach I'd use for your situation, and connect you with past clients willing to give a reference if the engagement warrants it. The impact stories on this page are representative of real project types.
Yes — and I consider it a core part of any implementation, not an optional add-on. I design training around your team's actual roles: what the warehouse team needs to know is different from what finance needs. I also produce written quick-reference guides your team can use after I'm gone. Remote training via Teams or on-site — depends on what works for your team.
Every project ends with a handover package: documented solution design (what was built and why), configuration notes for any BC/LS settings changed, AL code in your repository with clear naming, and a short written guide for your internal team or partner to maintain the system going forward. The goal is that you're not dependent on me to keep things running.
Yes. Many clients come to me without an active partner — either they've never had one, or they've parted ways with a previous one. I can handle the full engagement independently: implementation, development, training, and ongoing support. For Microsoft licensing specifically, I'll advise you on the right approach — whether that's through a CSP partner or direct, depending on your situation.
Yes — if you have an internal BC administrator or developer, I'm happy to work alongside them and upskill them during the project. I can also run dedicated technical training sessions covering AL basics, debugging, and system administration. The outcome I want is for your team to be capable of handling routine work independently, with me available for the complex stuff.
I work with both — but I give startups an honest assessment first. Business Central has a minimum viable scale: if you're pre-revenue or under 5–10 users, BC may be more system than you need right now, and I'll say so. For startups that are past that point and need a proper ERP foundation, I can scope an implementation that's appropriately lean and grows with you. I'm not going to sell you a full enterprise rollout if you need a sensible starting point.
Availability & How to Reach Me
Updated regularly. No vague "contact us" — here's the actual picture right now.
Let's Talk About Your ERP.
No sales pitch. No generic demos. A real conversation about your specific situation — and what it would take to fix it.