Regional bank, UAE

Marketing Cloud sat apart from the branch's customer. Journeys now use the same profile. Clients asked not to be named.

Get the written assessment

Founded 2022 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks

The engagement

Three stops, quoted from the note.

Before
The week as it was
The branch already knew the customer; the campaign did not.
The week
What we built
Marketing Cloud journeys against a single customer profile: transactions, send-time, and a preference center the marketing team could run without us.
After handover
What stayed
After handover, their team edits the journeys.

Quoted from the note. The client is not named here.

Before, and the week

What the week looked like.

This was a regional bank in the UAE. They asked not to be named. They already had Marketing Cloud. That was not the problem.

Campaigns ran on lists. Transaction data never reached the journey. A customer who had just taken a product at the branch still got a generic cross-sell. The marketing team could not change a journey without calling the partner.

We connected the journeys to one customer profile: core transactions, send-time rules, and a preference center. The work was Salesforce, not an invented AI layer. After handover, their team edits the journeys. We did not stay to operate the desk.

The bank measured the change itself, and their figures stay theirs. We will not invent a number for the same work.

What changed

What we will stand behind.

Before

What changed

Marketing Cloud sat on one side of the bank. Transaction data lived on another.: Journeys ran on the same customer profile the branch used, so a customer who had just taken a product stopped getting the generic offer.
Cross-sell went out as a blast list.: Cross-sell stopped going out as a list that ignored what the branch already knew.
The marketing team could not change a journey without calling the partner.: The marketing team owns the journeys after handover.

Quoted from the note. The client is not named here.

Where the same work fits

The same week, other desks.

Example
Marketing head at a Dubai real estate developer
Today: Owners who just bought a unit still get the launch campaign.
After: Journeys read the same profile the sales team uses, so a new owner gets the handover messages instead.
Real estate
Example
Marketing manager at a Dubai hotel apartments group
Today: Long-stay guests get the same short-stay offer every week.
After: The journey reads the booking before it sends.
Hotel apartments
Example
CMO at a US software company
Today: The team cannot change a nurture journey without calling the agency.
After: The marketing team owns the journeys after handover.
For CMOs

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

The honest no

When we are the wrong partner.

The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

The other stories.

The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.

01Regional grocery retailerSales Cloud for account-based selling, POS integration for inventory visibility, and a mobile path for field reps.Retail 02Regional hospital networkMarketing Cloud patient journeys with SMS and WhatsApp reminders, plus education sequences tied to the condition, not a blast list.Healthcare 03Regional property teamSalesforce around how the deal actually moves: inquiry, viewing, offer, close. One record for the listing, the buyer, and the viewing.Real Estate 04Regional manufacturerSales and Service around quote-to-cash and installed-base work. ERP stays the source for the shop floor. Write-back with errors visible.Manufacturing 05Regional agriculture deskSalesforce around the process that already exists: inquiry, quote, delivery, service. Digital where the farmer already is.Agriculture