.svg)
From Grow With Braze Dubai 2025 to 2026: What we've built through the year
On 23 October 2025, CustomerIK's leadership stood on the Grow with Braze Dubai stage and asserted that a company's data foundation would decide 2026. A year on, we return to the same event as Gold Sponsor, this time with a year of built work behind the argument.
The stage, 23 October 2025
The session was called "From Data Chaos to Impact: How Real-Time Sync Transformed Media Engagement". Braze used the stage to talk about Braze Agent Console, Braze Decisioning Studio, Braze Operator. All three were about agents. What we talked about was the data those agents would need to act on.
People in the room already wanted real-time engagement. We asked the question underneath it: what has to be true about your data before real-time means anything at all.
What we've said since…
By December, our position had sharpened into something closer to a forecast than an opinion. We called 2025 a year of foundation, following it with a warning: "Your biggest threat in 2026 isn't a competitor, it's non-compliance." And a diagnosis: "If 2024 was about centralising data into a warehouse, 2025 was about democratising it." And we committed to CustomerIK's deepened focus on Braze and going "beyond implementation" to build "innovative products and solutions around Braze".
These, together, make a testable claim.
What we've built since…
We won't tell this as a company timeline. It wasn't linear. It happened as call and response: a position taken in public, then, months later, the things spoken about, built and running.
In February 2026, Abridge became a Braze Amplifier. It is an integration suite built for one job: moving Salesforce data into Braze without a bespoke project every time. In June, we shared results about an SFMC to Braze migration that ran on it.
By May 2026, a conversational analytics agent was running on our live accounts. A marketer asks a question in plain language. The answer comes back drawn from the warehouse and Braze together, with no SQL and no wait in an analyst's queue. It changed what marketers using it could ask, which made our point about democratising the warehouse real.
Seven months after the non-compliance warning, by July 2026, an integration layer went into production. It carries the systems that never make it onto a slide: hotel property management systems, airline reservation extracts, POS exports, SOAP-era CRMs, fixed-width files over SFTP. It runs inside the client's own cloud tenancy, so credentials and residency stay with them. The design goal behind it is to minimise what data ever leaves the client's systems at all.
By August 2026, CustomerIK became an official Databricks partner, positioned upstream of Braze. That moved the warehouse side of the work from something we recommend to something we build.
| Said | Gap | Built |
|---|---|---|
| "beyond implementation... innovative products and solutions around Braze" | Two months | Abridge, a live Braze Amplifier |
| "2025 was about democratising [the warehouse]" | Five months | A conversational analytics agent, in use on live accounts |
| "Your biggest threat in 2026 isn't a competitor, it's non-compliance" | Seven months | The integration layer carrying legacy systems into Braze |
| "we specialise in configuring... Zero-copy features" | Eight months | Official Databricks partner |
If you are assessing a partner, ask which position they took in public a year ago. Then ask what exists now because of it.
As we like to put it: most brands already have Braze. Only a few have figured out how to use it. The tool is only as powerful as the hands holding it.
May 2026, GWB Singapore
We were back on a Grow with Braze panel within months. This time in Singapore, on a panel called "Earned, Not Automated." The subject had moved from data chaos to something harder: how far AI should go before it stops earning trust and starts spending it.
Our answer stayed simple. Customers don't resist AI. They resist being treated like a data point. Restraint is a feature, not an absence of capability, and knowing when not to send matters as much as knowing when to.
We gave our teams a test. Run it before any AI-driven journey goes live: finish the sentence "we sent this because the customer..." If it ends with something the customer did, you're fine. If it ends with something you inferred about who they are, you've crossed from personalisation into presumption. The same test holds up in the GCC, where the first questions on any engagement programme are about consent and where data may sit, not about the creative. Know what you're allowed to do with someone's customer data, and do less than you're allowed to, not more.
Failure modes we see
- The consent question gets answered by the marketing team rather than by the people who own the data. That answer stands until someone senior asks for the basis.
- The event set is agreed late, so field mapping becomes a negotiation during cutover instead of a decision made before it.
- The pipeline runs one way. Attributes go in and nothing comes back. As our CTO puts it: "Without a return path, your models only ever see what customers did before you spoke to them. The pipeline works. It just never learns."
- Implementation practice reaches for what deploys fastest. The fastest thing to deploy is rarely the thing the client's data actually needs.
The order we would run it: settle what data may move and on what basis, agree the event set and mapping, build the return path in the same phase as the outbound one, then design the journeys. Journeys designed before the event set is agreed get rebuilt.
What to ask before you sign anything
Put these to any partner, including us.
- Where will the integration run, and who holds the credentials? If the answer is the partner's cloud, your data protection officer has inherited a third party.
- Which fields leave your systems, and who signed the list off? If nobody can produce the list, assume the answer is all of them.
- What happens to an event during an outage at either end? A queue that drops leaves a hole in a guest's history. You find those in a campaign, not in a log.
- Can your own team run the deployment without the partner? If not, you have bought a dependency alongside the capability.
Where we've done our hardest work
Travel and hospitality is where Braze implementation gets hard. Guest data lives in property management systems, reservation platforms and point-of-sale exports that were never built to talk to an engagement platform in real time. We've spent the past year solving that inside our clients' own systems, through the kind of technical integration most vendors would rather not take on.
That work is becoming another Braze Amplifier. More on that in October at GWB Dubai, 2026.
What was harder than expected
The hard part wasn't building what the December diagnosis called for. It was deciding when a piece of client work earns the word product. Abridge went from a sentence in December to a listed Amplifier in two months, because moving Salesforce data into Braze was one well-bounded job with a clear finish line. Other work took longer, because it had to prove itself inside a live account before we'd put a name on it. That's a slower way to build a product line than announcing one. It's also the only way we were willing to do it.
Back in the same room, 7 October 2026
We're back on 7 October 2026, at the Al Habtoor Grand Resort, Autograph Collection, in Dubai, for what Braze is calling The Resonance Revolution. Braze expects "200+ marketing, product, and customer engagement leaders." We'll be there for all of them.
Our CEO, Mitra Daram, is on the CxO panel from 17:45 to 18:10 GST, talking about customer expectations, trust and loyalty. Our team including Shekhar (Head of Growth & Strategy) and Mayank Khanna (The Braze MVP) is at the booth all afternoon, and this time we're bringing the Amplifier we've been building to show you.
CustomerIK is a Braze Solutions Partner.
Come to the booth, we would love to talk. Whether you are evaluating Braze, already running it, running the data behind it, or want to raise something else entirely, that is a good use of the afternoon. If a system you already own has a question you have not been able to answer out of it, that is a shorter route to something real than a demo of ours. You are also welcome to reach us directly before then.
Customer is King. Context is Kingmaker.
.svg)
