Digital Transformation, Jordan

Why the roadmap starts with processes, data and people

Jordanian SMEs come in many shapes: family distributors selling to pharmacies and groceries, software and outsourcing firms billing foreign clients, contractors, clinics and regional offices. Their systems problems look different on the surface, yet the root is often the same. Each department keeps its own version of customers and items, approvals happen by phone or message, and reports are assembled by one trusted person at month-end.

Software cannot fix that by itself. If the item list has duplicates, an ERP will carry them into every invoice sent to the tax system. If nobody owns the customer master, a CRM becomes another list. My opening stage therefore settles three things: how core processes should run, which manager answers for each master list, and which day-to-day behaviors have to shift, such as where quotations are prepared, who may alter a price and how stock adjustments are approved.

People come into it early because adoption decides whether the investment pays back. I talk to the staff who do the work, not only to managers, and note where resistance is likely and why. That information shapes the order of the roadmap as much as any technical dependency. The general method is described on my digital transformation consulting page; this page is about applying it in Jordan.

Jordanian drivers that shape the order of work

Several local developments affect what should happen first. I treat them as planning inputs and refer legal and tax questions to your advisors.

• Electronic invoicing. The national e-invoicing system means invoice data quality now has direct consequences. Companies that rushed a connector onto weak master data often need a cleanup stage before any larger ERP decision. Which transactions fall in scope is a question for your tax advisor.
• Payment modernization. Instant transfers through CliQ and bill payments through eFAWATEERcom give customers more ways to pay. Each channel needs a matching rule in finance so receipts can be identified and reconciled without manual detective work.
• Government services moving online. As ministries move registrations and filings onto portals, a firm that tracks its permits, renewals and staff papers in one register spends less time scrambling before deadlines.
• Data protection. Jordan's personal data protection law affects how customer and employee data is stored, shared and accessed. Your legal advisor should confirm obligations; the roadmap makes sure each stage asks the right questions.
• Skills market. Jordan has a strong pool of technical talent, and competition for it, including from Gulf employers, is real. Plans that depend on one internal developer are fragile.

These drivers help rank stages by risk and value. None of them should be allowed to choose the platform on its own.

Putting ERP, CRM, dashboards and the website in order

A good roadmap gives each stage its own payoff while preparing the next one. For a Jordanian SME a sensible default order is the one below, adjusted to what the baseline reveals:

1. Master data and invoicing discipline. Clean items, customers and tax codes so e-invoices stop bouncing and reports can be trusted.
2. Core ERP decision. Decide whether the existing accounting package can be extended or whether an ERP is needed, then select on evidence. The ERP consulting for Jordan page and the ERP selection page cover this.
3. CRM and sales process. Bring quotations, tenders, field visits and follow-ups into one system linked to the ERP. See the Jordan CRM page.
4. Automation and integration. Connect banks, payment services and the e-invoicing interface, then automate reminders and approvals once data is stable.
5. Management reporting. Dashboards fed from the systems of record, in dinars and dollars where both matter.
6. Website and lead engine. Search visibility, campaign tracking and inquiry capture tied into the CRM, which matters most for firms selling to the Gulf or beyond. My SEO work for Jordan picks this up.

The order can change. A service exporter with clean finance may start with CRM; a distributor with chaotic stock may need warehouse discipline before anything else. The roadmap explains each choice so it can be revisited when circumstances change.

Cash, checks and resilience in the operating model

Many Jordanian businesses still collect a large share of revenue in cash or post-dated checks, especially in distribution and retail. A transformation plan has to work with that reality rather than assume every customer will move to electronic payment soon. The practical question is how to give finance and management the same visibility over cash and checks that they would have over bank transfers.

At roadmap level, I look at where money enters the business, who handles it, when it is recorded and how it is matched to invoices. The plan then decides which stage tackles each gap: a process change for drivers and collectors, a CRM view so sales reps see outstanding balances, or an ERP feature for managing a check portfolio. Detailed design of those controls is covered on the Jordan process consulting page, so here the focus is order and ownership.

Resilience matters too. Branches and warehouses need to keep trading when an internet link drops, invoices must still reach the tax system once the connection returns, and backups should be tested, not assumed. I ask each vendor how their system behaves under those conditions and record the answers. I also look at key-person risk: if one employee holds all the passwords or knows how the connector works, the roadmap includes documenting that knowledge before anything else changes.

Who steers, who builds, and where AI fits

Transformation needs an owner inside the company. I help set up a small steering group, usually the general manager, finance and operations, meeting online on a fixed rhythm with a written decision log. Each stage gets a named business owner who signs off scope, test results and adoption, not just the vendor's completion note.

My role is independent. Implementers and vendors in Amman and across the region build and support systems, and the roadmap relies on them. I sit on your side: defining needs in writing, holding bids up against the plan, confirming that what was promised gets delivered and making sure the ERP, CRM and website projects do not contradict one another. Licenses and configuration are their business, not mine, and my fee comes from you alone.

AI earns a modest, governed place in the plan. Useful early uses include reading supplier documents for human review, drafting routine Arabic or English replies for staff to approve and summarizing long service histories. Each needs rules on data, review and accountability. I do not recommend AI as a substitute for clean processes or as a stage of its own. The engagement runs remotely in English, during Jordanian working hours, with Arabic training material produced or reviewed by your own bilingual people. Visits happen only by arrangement. Background reading: the Jordan overview and my guide to building a roadmap.