Salesforce Plans to Buy Braze, With Integration Still Undecided

Salesforce’s October 20 agreement to acquire Braze puts customer-messaging teams in a planning gap. Current contracts stay put, while the promised AI combination remains undefined. The deal values Braze at approximately $5.66 billion in enterprise value, but the product decisions customers need for planning remain ahead.

The companies expect to close in Salesforce’s fiscal 2028, which begins February 1, 2027. Braze says existing contracts and account teams stay in place while they remain separate companies. A signed acquisition agreement hasn’t changed who runs tomorrow’s campaign.

Bill Magnuson, Braze’s CEO and co-founder, framed the deal around the people using the platform. In the joint announcement, Magnuson said the company was founded on the conviction that:

“marketers and their creativity are a brand’s ultimate competitive advantage”

That’s an ambitious promise for a transaction whose practical value will depend on what a marketer can do across the combined products, and how much work it takes to get there.

The attraction is the customer response

Braze’s software responds to customer behavior, coordinating messages across channels including apps and email. Its AI capabilities help choose what to show and when. Salesforce wants those capabilities alongside its customer records and data products, with a closer connection between what a business knows about someone and the next message it sends.

Salesforce’s announcement presents Braze’s response to live customer activity as a reason for the purchase.

Consider a hypothetical retailer deciding what to send after a customer makes a purchase. A useful combination would let the campaign owner use that purchase information while honoring the customer’s messaging choices. An AI recommendation is only useful if the right information arrives and the resulting action follows the brand’s rules.

That example describes the operating requirement, not a delivered integration. Salesforce and Braze haven’t established that the proposed combination eliminates the work of connecting those systems. Both companies have a commercial interest in presenting the deal’s potential favorably.

Customers still have separate products

The merger agreement filed with the SEC is dated October 19. It provides for $47.50 in cash per Class A share, subject to closing conditions including shareholder approval and regulatory clearance. October 20 was the public announcement, not completion.

Those dates matter to a marketing team negotiating its next year of software. The most concrete customer commitments appear in Braze’s publicly filed communications: existing contracts continue, and the companies operate independently until close. The filing describes possible future product combinations as undecided.

A buyer can acknowledge the potential without making an operating plan depend on it. Any proposal to simplify the team’s setup needs to identify a working connection and the conditions for using it. A future owner on a slide doesn’t establish which subscription will pay for that connection.

This is related to the problem behind Hightouch’s acquisition of Strata: the person responsible for marketing results still needs the data and tools to work together. Corporate ownership can change which integrations a supplier prioritizes. It doesn’t, by itself, prove a campaign team has fewer handoffs.

An integration can also erase what customers chose

Rafael Beckenkamp, a senior MarTech solution architect at APPLY, raised the customer-choice issue in a public response to the agreement. Beckenkamp asked how much integration could happen:

“without losing what made the products good independently.”

APPLY provides marketing-technology services, so this is an implementation practitioner’s view with a commercial interest in the work. It isn’t an independent finding about the future combined product.

The concern deserves space alongside the sales pitch. A customer may have selected Braze to fit an existing data system. Making a tighter Salesforce connection useful to another customer needn’t mean imposing the same setup on both. The eventual product choices will show how much flexibility survives.

There is a credible benefit on the other side. A good integration could make information easier for marketers to use without a separate technical request. Our recent CustomerLake reporting described a CRM team building audiences and sending them to Braze. That is the kind of specific work an acquisition’s promises should eventually be judged against.

For now, customers can separate their renewal decision from an unbuilt product plan. Keep current requirements in the contract discussion. When a proposed combined capability becomes available, ask the supplier to demonstrate one existing campaign with the team’s own approved data. The evidence is whether the campaign owner can finish that work under the promised terms.

Follow the changing ownership of marketing software in the state of the AI martech stack.