Arena: Market Conditions Before Braze
Product and marketing teams at consumer-app businesses · 2011 · United States first, then global
Disconnected workflowsEnabling technology shift
Smartphone apps gave consumer businesses a direct channel to their customers, but product and marketing teams had little infrastructure for using what people did in an app to decide what to tell them. Email systems kept their own customer profiles, and push-notification tools handled one channel at a time, so most marketing ran channel by channel and campaign by campaign B1. Tying product events, consent and messages together took custom engineering or several products that did not share data. Messages mostly went out on a schedule, not while a customer was active B2 B3.
How each step happened
Step 1 of 5 · 2011–13
Engagement SDK inside the app: live behavior triggers messages
Braze, founded as Appboy in 2011, put the marketing system inside the customer's app. Its first software development kit (SDK), code a company builds into its own app, recorded what each user did there and could respond through four channels: push notifications, email, an in-app news feed and slide-up messages BRZ-1 B2. Email tools held profiles apart from the product and push tools handled one channel each B1. With the SDK, a message could follow from what a customer had just done, while that customer was still in the app B2 B3.
The bet was that apps would become a main channel between brands and their customers. Bill Magnuson had watched Android emerge while at Google and said he "couldn't shake the feeling that the entire world was changing on the back of mobile" B3. He built for a market that was not there yet: from 2012 to 2015 most mobile software companies served game makers BRZ-1. Placing code in the app gave Braze two things it would reuse at every later step: a live record of behavior and a delivery path it controlled.
Rivals Iterable was founded in March 2013 as an email platform for smaller companies that could not use the large marketing clouds IT1; in February 2015 it was still an email product, with push notifications among its plans BRZ-4. Salesforce and Adobe sold broad marketing clouds that could add mobile channels to their existing campaign tools B1.
Enabling technology shift
Step 2 of 5 · 2011–21
Its own stream processor, with the decision made before the channel
The data system behind the SDK was built from the start, which is why this step's dates overlap the first; Magnuson described its design in 2021. Apps produced far more events than email programs, so Braze wrote its own stream processor to handle mobile scale BRZ-2. The fiscal 2026 annual report describes the result: each event is processed in context as it arrives, and segments, the groups of users a marketer targets, update in real time as data comes in B1. The report contrasts this with batch processing, which it calls easier to scale but held back by its design B1.
The second choice was an abstraction layer over messaging. The system decides what to say to a customer before it chooses the channel that carries the message BRZ-2. That separation made personalization work across channels: a marketer's rule responds to what the person did, not to which tool holds their address. A new channel then needs only a new delivery path, not a new decision engine, which made the next step cheap.
Rivals Iterable's early product ran trigger-based email campaigns off customer behavior BRZ-4. A Braze implementation partner's Iterable-to-Braze migration guide names journey logic and real-time personalization among the limits that move teams to Braze R8. Salesforce and Adobe offered their own cross-channel orchestration B1.
Novel ArchitecturePersonalization
Step 3 of 5 · 2013–26
New channels ship through the SDK already in the app
Because the SDK already sat in customers' apps, Braze could ship new channels and message formats through it. The annual report says that embedding new messaging features in the SDKs lets Braze deploy them with little or no additional effort from customers B1. One product holds customer profiles, event ingestion, journey design in its Canvas editor and delivery across push, email, in-app messages, SMS and other channels B1. A single event can change several messages without a handoff between channel tools.
The company renamed Appboy to Braze in 2017, dropping the mobile-only suggestion of its first name B2. By fiscal 2026 its SDKs ran in iOS, Android, web, connected-TV and Unity game apps, and data moved both ways: Cloud Data Ingestion pulls records from customers' data warehouses, and Currents streams Braze events back out to them B1. Each addition widened the job Braze did for customers who had installed it once, and gave them a reason to spend more, the subject of the next step.
Rivals Iterable added channels one at a time: push and SMS by January 2016, in-app messages in December 2016 and WhatsApp in 2024 IT12 IT11 IT3. Its warehouse import, Smart Ingest, built with Hightouch, became generally available in May 2024 IT8 IT3.
PlatformizationEnd-to-End Workflow
Step 4 of 5 · 2013–26
Large brands expand users, channels and products
From hobbyists to brand marketers
Braze's March 2012 public beta drew 1,000 signups, mostly hobbyist developers, and almost none became customers BRZ-1. Between 2013 and 2015 it turned to professional mobile marketers at established brands; retailers were among the first large accounts, because engaging customers in real time sold more goods BRZ-1. These buyers had large audiences and several channels, which suited what the product already did. Direct sales, implementation partners, security work and global infrastructure carried it into larger companies B1.
Pricing that grows with the customer
Braze sells subscriptions based on an upfront commitment to a number of monthly active users (MAUs), the customer's end users who engaged in the past 30 days, and to message volume; customers who go over pay for the excess or buy a higher tier B1. Braze reports that once the platform is deployed, customers typically add MAUs, channels and use cases and buy more products B1. At the 2021 public listing, 41 customers paid more than $1M a year and net dollar retention, a year-old customer group's spend now against a year earlier, was 125% BRZ-6. In fiscal 2026, 333 customers paid $500,000 or more a year, and existing customers supplied 65.5% of revenue growth on revenue of $738.2M B1.
Rivals Iterable aimed at companies too small for the large marketing clouds IT1. It reached a $2B private valuation in 2021 BRZ-8 and more than $200M in annual recurring revenue in early 2024 IT5; in July 2025, still citing that figure, it named a Salesforce executive chief executive to expand its enterprise business BRZ-9.
Usage-Based Pricing
Step 5 of 5 · 2019–26
Switching costs
The SDK from step 1 became the lock-in. In March 2026 Magnuson said over 90% of customers use the Braze SDK and 80% use Currents to send data to their other systems BRZ-5. Leaving means pulling code out of a company's apps, instrumenting them for a new vendor and rebuilding every template and journey; one implementation partner puts an Iterable-to-Braze move at 8 to 16 weeks R8. The longer a customer runs journeys on Braze's event stream, the more there is to rebuild.
The barrier slows departures without stopping them. Net dollar retention fell from 125% at the listing to 109% in fiscal 2026, which Braze attributes to customer turnover and renewals at lower subscription levels BRZ-6 B1. What keeps accounts is the route from step 3: the SDK that makes Braze hard to remove is also how each new channel reaches customers without new work.
Rivals Iterable customers face the same rebuild, and partner guides document moves from Iterable to Braze R8. Braze listed nine migrations from legacy platforms in the fourth quarter of fiscal 2026 BRZ-5.
Switching costs