ERP and CRM for MENA: connect the operation, scope each market.

Start with the markets and entities you actually operate

A regional ERP evaluation needs more detail than a MENA label. List each entity, branch, warehouse, currency, document language, and integration. Identify who owns the accounting records and which teams share customers, suppliers, products, or stock.

Use a separate acceptance checklist for each jurisdiction. An invoice, payroll run, tax export, or payment integration that works in one country is not proof that it meets the requirements of another. Ask for the evidence relevant to your own configuration.

Evaluate agents alongside your ERP workflows

Tellency agents can read business records, create and update data, and execute supported workflows across modules. Use a representative request to inspect the selected records, required inputs, resulting document, permissions and execution log. Include an approval decision and an action the agent is not permitted to perform in your acceptance checks.

For a business operating across MENA markets, use an illustrative request that crosses sales, purchasing and finance. Specify the company, location, currency and responsible roles before testing the agent. Agree country-specific outputs, language and integrations individually rather than treating the region as one configuration.

• AI-native ERP and cross-module agents →
• Tellency as an Odoo alternative →

Trading and distribution: follow stock and balances

Start with a supplier order that arrives in two deliveries and then moves between locations. Tellency implements stock-transfer approval, shipment, receipt, and posting stages. Demonstrate the discrepancy path and inspect the inventory and finance records with your team.

For products with expiry dates, test lot capture, expiry monitoring, and configured notifications. Confirm units, valuation, landed-cost requirements, shipping services, and customs-related documents individually rather than assuming they are included in a general inventory module.

CRM: make the sales handoff visible

Tellency implements lead imports, duplicate handling, ownership, qualification, conversion, and opportunity pipeline stages. Use an actual enquiry and show how the salesperson hands over a customer commitment to operations and finance.

AI-assisted lead scoring includes a model-based path and a rules fallback. Evaluate how your team reviews and uses the score; it is not a promise of predictive accuracy or improved conversion. Record the language, communication channels, and third-party connections your sales process requires.

Country evaluations, with a wider MENA scope

Start with the UAE and Saudi Arabia guides below. For Qatar, Bahrain, Kuwait, Oman, Egypt, Morocco, or another MENA market, bring the specific entity, reporting, document-language, payroll, and integration requirements to discovery. This regional page does not claim a local office, local customer base, or a certified configuration in every country.

Arabic, French, and English screen and document requirements should be demonstrated explicitly. Confirm templates, right-to-left behaviour where needed, and the roles that will use them. A regional marketing page is not evidence that a language pack or statutory submission service is available.

• ERP and CRM in the UAE →
• ERP and CRM in Saudi Arabia →

Agree the implementation and total cost

Bring your current systems, approximate users and locations, sample documents, product list, open balances, and integration requirements. Agree data mappings, reconciliation, permissions, training, and acceptance before setting the cutover date. Use anonymised records during the initial evaluation.

Tellency platform pricing starts at $79 USD per user per month. Included modules, migration, deployment, integrations, support, and AI usage charges must be confirmed in a proposal. Around eight weeks is a typical planning reference; the agreed schedule depends on scope and readiness. Managed cloud and self-hosted deployment options should be assessed alongside data-location and operating responsibilities.

• Implementation checklist →
• Deployment and security review →