Salesforce that matches how your team sells, not how a template assumes

Salesforce is a platform more than a product. You license clouds (Sales, Service, Marketing and others), then shape them with objects, fields, page layouts, record types, flows and permission sets. Most failed rollouts fail here, not on licensing. Someone enabled every feature, copied a demo layout, and left reps with forty fields to fill per lead.

We start from your sales motion: how a lead is qualified, who quotes, who approves a discount, what a renewal looks like. From that we design the smallest data model that supports it. Standard objects are used wherever they fit, because they keep reporting and upgrades simple. Custom objects are added only for things Salesforce does not model, such as a site survey, a tender submission or a framework agreement.

Expect 8 to 16 weeks for a single-cloud org with one or two integrations. A multi-cloud rollout with several business units, or heavy custom logic, takes longer, and we say so at scoping rather than mid-build.

Salesforce supports Arabic as a user language, and records can hold Arabic text in any field. The work is in the details: quote and contract templates with correct right-to-left layout, Arabic picklist values that match your terminology, names stored in both scripts so search finds them either way, and Hijri or Gregorian date handling where your contracts need it.

Customer data in a CRM is personal data, so the Personal Data Protection Law (PDPL) applies to what you store, why you store it and where it goes. Before go-live we map which fields hold personal data, set field-level access, record consent where you rely on it, and agree a retention rule. Salesforce infrastructure regions and the cross-border transfer rules in the PDPL regulations both change, so we confirm the current position with your legal adviser during scoping instead of assuming it.

If you invoice through a ZATCA-integrated ERP, the CRM should never become a second source of invoice truth. We pass won deals to the ERP and read invoice status back.

Moving data is usually the longest hidden task. Legacy exports carry duplicate accounts, contacts with no company, and free-text fields holding what should be three separate values. We profile the data first, agree a cleaning rule set with you, run a trial load into a sandbox, and only then load production. You review counts and a sample of records at each step.

Integrations are where the CRM stops being an island. The common ones are ERP for orders and invoices, e-signature for contracts, WhatsApp Business for conversation history, and a data warehouse for reporting. We build against documented Salesforce APIs and keep each integration idempotent, so a retry never creates a second order.

Adoption is a delivery item, not an afterthought. We train by role, run a hypercare period after go-live, and review login and record-update patterns together after the first month. If a screen is being ignored, we change the screen.