The wrong product against the wrong workflow
Salesforce sells the restaurant industry on Customer 360, on the Loyalty Management product, on the Marketing Cloud Engagement surfaces, and on the broader Data Cloud architecture. The pitch is that the enterprise gets a unified customer record, personalised marketing communication, AI-driven loyalty intelligence, and the connection to the broader Salesforce ecosystem the global enterprise's stack runs on.
The pitch sells well in the boardroom. The pitch lands less well at the operations level, because the workflows that Middle East restaurant chains actually run against their customers are not the workflows the global enterprise CRM was built to support. The unified customer record is harder to build at a Middle East F&B chain than the product's templates suggest. The loyalty programme structure does not match the regional family-dining, corporate-account, and festive-cycle reality. The marketing-communication cadence operates against the Arabic-and-English bilingual baseline the Salesforce surface handles imperfectly. The aggregator-channel reality — Talabat, Careem Food, Noon Food, Deliveroo — sits outside the Salesforce data model and feeds in through integrator-led configuration.
The category is moving. The restaurant-native CRM products — SevenRooms, Toast, the dedicated F&B-loyalty specialists — are competing against Salesforce on the operations-first vertical capabilities. The owned-architecture alternative is competing on the multi-year economics and the brand-level capability the enterprise builds. This piece is the REFORGE pattern for the Middle East F&B business running Salesforce today.
What the actual customer workflow contains
The F&B chain's customer relationship runs against four structural surfaces.
Identity and unification. The customer arrives through the POS at the outlet, the own-app, the aggregator order, the call-centre order, the reservation surface, the loyalty enrolment at the table. Each touchpoint has a different identity primitive — phone number, app account, aggregator profile, loyalty card, reservation booking. The unification work is the work the standard CRM struggles with at the chain's volume.
Loyalty mechanics. The tier structure, the earn-and-burn ratios, the cross-brand recognition for the multi-brand business, the family-account dynamic, the corporate-account spend, the festive-promotion overlay, the partner-redemption integration with the airline and hotel loyalty programmes the regional consumer holds. The standard Salesforce Loyalty Management template is configured against the generic mechanic library. The Middle East enterprise's actual mechanic mix is a configuration project that compounds across the renewals.
Personalisation and communication. The pre-visit communication, the order-suggestion at the point of order, the post-visit follow-up, the win-back campaign for the lapsed customer. The communication operates in Arabic and English, against the cultural-and-festive calendar, at the appropriate formality register. The standard Marketing Cloud surfaces handle the multilingual operation; the Arabic-first capability is improving but is not the architectural primary.
Customer service and recovery. The complaint handling, the case management, the social-media channel, the recovery offer at the point of dissatisfaction. The standard Service Cloud module handles this, with the loyalty-and-CRM integration through the standard Salesforce data model.
The enterprise running Salesforce against this workflow is paying per-record commercial rates against a customer base that scales with the outlet count, the channel mix, and the brand portfolio. The integrator's configuration work on the unification, the loyalty mechanic, and the multilingual communication is the largest line on the Salesforce-related retainer at most enterprises.
What the alternative architecture looks like
The replacement is not another vendor's CRM. It is the deliberate building of a customer-data substrate the enterprise owns, with workflow surfaces on top that respect the structural reality of the F&B business's customer relationship.
The substrate has three components.
The customer-data layer. The unified customer record, the cross-touchpoint identity, the loyalty profile, the visit history, the order history, the communication history, the consent record. The data lives on infrastructure the enterprise operates, with the cross-touchpoint identity resolution running against the enterprise's actual identity-primitive mix. The aggregator-channel data integrates as a first-class input.
The loyalty engine. The tier rules, the earn-and-burn mechanic, the cross-brand recognition, the family-account dynamic, the corporate-account workflow, the partner-redemption integration — each as a configurable workflow the loyalty team operates without integrator-led release cycles.
The communication and personalisation surfaces. The pre-visit and post-visit communication, the personalisation at the point of order, the win-back campaign — each running against the customer-data layer through the enterprise-owned communication infrastructure. The Arabic-and-English bilingual operation is the architectural primary.
The agent layer absorbs the synthesis work. The customer-recognition agent identifies the customer across touchpoints. The loyalty-mechanic agent runs the personalised redemption recommendations. The recovery agent surfaces the dissatisfaction signal and prepares the structured recovery action.
The REFORGE sequence
The sequence runs as workflow-led sprints. The Salesforce footprint shrinks at each sprint.
Sprint one — the customer-data layer migration. The customer records, the loyalty profiles, the visit-and-order history migrate to the owned substrate. The Salesforce instance continues to operate during the parallel-run period. The aggregator-channel data integrates into the owned layer as a first-class workflow.
Sprint two — the loyalty engine. The tier rules, the earn-and-burn mechanic, the cross-brand recognition, the family-account dynamic move to owned software reading from the customer-data layer. The Salesforce Loyalty Management module retires at the next renewal.
Sprint three — the personalisation and communication surface. The pre-visit and post-visit communication, the win-back campaigns, the personalisation at the point of order move to owned software. The Marketing Cloud module retires.
Sprint four — the customer-service workflow. The complaint handling, the case management, the social-media channel move to owned software. The Service Cloud module retires for the F&B workflow.
The Salesforce footprint at the end of the sequence is residual. The enterprise owns the substrate the brand-level customer relationship runs against.
The Middle East dimension
Three dimensions matter at a Middle East F&B business.
The aggregator-channel data integration. The owned customer-data layer ingests the aggregator data as a first-class input rather than as an integrator-led configuration on top.
The family-account dynamic. The Middle East F&B customer base operates against the family-account reality more than the global average. The owned loyalty engine handles this directly.
The festive-cycle promotional intensity. The Ramadan, Eid, National Day, and broader festive cycle drives disproportionate share of the enterprise's customer engagement. The owned communication infrastructure operates against the cadence the brand team designs.
The saasinator perspective
Restaurant loyalty is not generic CRM. The Salesforce commercial model is built against the generic CRM workload. The economics flip in the enterprise's favour when the enterprise owns the substrate the brand-level customer relationship runs against.
What to bring to the diagnostic
Bring the Salesforce module breakdown, the integrator retainer, the aggregator-channel inventory, the loyalty-programme economics, and the brand-level communication cadence. The diagnostic is ten working days. The output is the sprint recommendation, the architecture sketch, and the first-quarter scope. Book a diagnostic at /diagnostic.