Speaking twice at Dreamforce · Sept 15-17 →

Financial Services

Regional bank, UAE

The first week is in the org, reading what already exists. Named with permission.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

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. Open rates sat in the low teens. 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 number we will stand behind is the one they measured: opens moved from the low teens into the mid-40s. We will not invent a revenue multiple for the same work.

What changed

What we will stand behind.

  1. 01Open rates moved from the low teens into the mid-40s once journeys used the same profile as the branch.Financial Services
  2. 02Cross-sell stopped going out as a list that ignored what the branch already knew.Financial Services
  3. 03The marketing team owns the journeys after handover.Financial Services

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.

Ours looks like this

We work in banking and fintech and right now, leads go cold before anyone replies.

Industry
Problem

Brief: Financial services. Journeys ignore what the branch knows. An agent on a named process. A reviewer on the exceptions.