CRM Consultant, Jordan

Agencies and distributors selling on behalf of principals

Many Jordanian trading companies are the local agent or distributor for foreign manufacturers. That changes what the CRM must do. The principal often wants a regular report on pipeline, key account coverage and lost business by product line, sometimes in its own format. If the CRM only knows customers and deals, that report is rebuilt by hand every time.

I design for the principal relationship from the start:

• Products carry the brand and principal, so pipeline, quotations and won business can be reported per principal without manual tagging.
• Forecast fields separate committed orders from expected tenders, because principals plan production against each differently.
• Competitor and lost-reason fields use a short controlled list that the principal's report can summarize.
• Sharing rules keep a team handling one principal's range away from another principal's pricing where agreements require separation.

Customers are structured as a hierarchy where it matters: a pharmacy chain with branches, a hospital group with several purchasing units, a wholesaler with sub-dealers. Each level gets an owner, so a sales manager can see coverage by governorate and channel rather than a flat list of names.

Whether a principal can demand access to your customer data, and on what terms, is a contractual and legal question for your counsel. The CRM design simply makes it possible to give exactly what the agreement allows and nothing more.

Tenders from hospitals, ministries and international organizations

Tenders are a separate sales motion in Jordan with their own rhythm. Public hospitals, ministries, universities and international or donor-funded organizations publish requirements with fixed closing dates, clarification windows and often a bid guarantee. Missing one date can lose the business regardless of price.

I give tenders their own pipeline rather than mixing them with routine quotations. A typical structure:

• Identified: the tender is logged with its source, buyer, closing date and an owner.
• Bid decision: a recorded go or no-go with reasons, so management can see which opportunities were declined and why.
• Preparing: technical and commercial documents in progress, principal pricing requested, any guarantee arranged with finance.
• Submitted: the bid value and validity period recorded.
• Awarded or lost: the result, the winning price where published and lessons for next time.

Reminders before clarification and closing dates go to the owner and the sales manager. A won tender usually becomes a framework or supply agreement that generates repeated orders in the ERP, so I link the agreement to those orders and delivery against awarded quantities can be tracked.

The tender pipeline also feeds principal reports, since many principals want to know which tenders their products are entered in. For how one platform handles medical sales coverage, see my Zoho CRM notes for Jordan.

Field visits, cash and post-dated checks

Field sales in Jordan often mix selling and collecting. A representative visiting a pharmacy, grocery or workshop may take a new order and collect a payment in cash or a post-dated check in the same visit. If CRM and ERP do not share that picture, reps chase orders from customers already over their limit, and finance cannot tell which checks are still in a rep's hands.

I keep the roles clear. Receipts, checks and customer balances belong in the ERP, which handles their accounting and clearing. The CRM shows what the rep needs before and during the visit:

• Open invoices, overdue amounts and the credit limit, refreshed from the ERP.
• Post-dated checks already received and their due dates, so a rep does not ask twice.
• A collection task when finance flags an overdue account in the rep's territory.
• Visit notes and orders captured on a phone, synced when coverage allows.

Where reps carry stock on vans, order entry and invoicing usually happen in the ERP's own mobile or route-sales tool, with the CRM limited to planning and account history. Forcing van sales through a CRM creates a second stock record that never matches.

Dinar amounts carry three decimals, so the handoff is tested to confirm quotation and invoice totals agree exactly. The invoice itself, with general sales tax and preparation for the national e-invoicing system where it applies, comes from the ERP as your tax advisor directs. My integration consulting page for Jordan covers how that link is built.

Messaging, marketing contacts and personal data

Customers in Jordan expect to reach their salesperson on WhatsApp, and most deals involve some messaging. The commercial risk is that order history and promises live on personal phones. The compliance risk is that contact lists built from those phones are later used for promotional messages nobody agreed to receive.

My design separates three kinds of contact. First, business conversations: company numbers, a connector to the CRM where one has been tested and justified, and a simple logging rule otherwise. Second, operational messages: order confirmations, delivery notices and payment reminders to existing customers. Third, marketing: campaigns and broadcasts that need a recorded basis for contacting each person.

Jordan has enacted personal data protection legislation, and foreign principals or international clients may add their own requirements through contracts. Your legal counsel decides what those mean for you. I then put their guidance into the CRM as origin and consent fields, opt-out handling that spans channels, export permissions limited to named roles and a review routine for dormant records.

Hosting belongs in the same conversation. I ask each CRM vendor where your data would be stored, how backups and exports work and which subprocessors are involved, and pass the written answers to counsel. Getting those answers before signing is far easier than retrofitting them after the team has loaded a large contact base.

Choosing a CRM in Jordan without a vendor in the room

Jordanian companies usually hear about CRM from whoever is selling them something else: the ERP implementer offering its sales module, a regional vendor offering a standalone product, or a marketing agency recommending the tool it already uses. Each suggestion may be sound, but none is neutral.

I compare options against the sales motions mapped earlier. A distributor whose quotes depend on stock and principal price lists may be best served by the CRM inside Odoo, ERPNext or Dynamics 365 Business Central. A services firm selling abroad may prefer Zoho CRM or HubSpot for email and pipeline work. A subsidiary of an international group may be required to use Salesforce or Dynamics 365. Scoring covers process fit, Arabic output, mobile use, ERP integration effort, admin capacity and licensing model.

Adoption is designed in, not trained in afterward. I keep mandatory fields few, build a view for each role, and agree the handful of reports management will review weekly: pipeline by principal and channel, tender deadlines, account coverage by governorate and overdue balances on active deals. When managers run the meeting from the CRM, the private spreadsheets fade.

Sessions run online, and any visit happens only if we arrange one in advance. Related reading includes the Jordan ERP consultant page, the Zoho CRM and Salesforce comparison, my CRM consulting service and the Jordan hub.