Salesforce Is Paying Nearly 16x More for Braze Than CPQ: Here's What That Means for Revenue Cloud Hiring

In December 2015, Salesforce agreed to buy SteelBrick, the company whose product became Salesforce CPQ, for about $360 million.

On October 20, 2026, it agreed to pay about $5.66 billion for Braze, a customer engagement platform. That's nearly 16 times as much.

Even adjusted for inflation, it's about 11 times as much. Different decade, different market. But if you work in quote-to-cash, it's hard not to read that gap as a ranking: marketing gets the billion-dollar checks, and your team gets a migration.

We think that's the wrong read. Look at what else Salesforce has bought since June and a different pattern shows up. It's buying both ends of the revenue line, and the team that owns the middle is about to get a bigger job. And the people who can do that job are already hard to find.

What Salesforce actually bought

Braze runs real-time messaging for big consumer brands across apps, websites, email, SMS and WhatsApp. It serves about 2,770 customers, including Canva, Instacart, Equinox and Venmo. Its AI layer, BrazeAI, personalizes each message.

Salesforce plans to use Braze to strengthen Marketing Cloud. One analyst told TechTarget that Marketing Cloud's revenue has been softer in recent quarters. The deal still needs shareholder and regulatory approval and is expected to close in Salesforce's fiscal 2028, which runs February 2027 through January 2028. Salesforce hasn't published a combined roadmap yet.

Braze is also part of a bigger buying spree. Here are six deals Salesforce has announced since June:

Contentful and Listen Labs prices come from CMSWire; the rest are from Salesforce.

That's about $10.8 billion in disclosed prices for content, service and engagement alone. Only one of these deals touches quote-to-cash, and it's one of the two without a price tag.

Salesforce is buying both ends of the revenue line

Put m3ter and Braze side by side and the shape is clear.

At the back end, m3ter will bring usage metering and rating natively into Revenue Cloud's product suite, so companies that charge by consumption can track usage, price it, and bill for it through Salesforce instead of a separate tool. The first capabilities are targeted for the first half of 2027. At the front end, Braze reacts to what customers do as they browse, buy and use a product.

In the middle is everything your team owns: the product catalog, the price, the quote, the contract and the asset. Salesforce didn't buy that layer this time. It built it. Revenue Cloud is API-first and native to the core platform, built for selling through partner, ecommerce, self-service and in-product channels, not just a rep's quote screen.

You could argue that's the real lesson of SteelBrick. CPQ stayed a managed package on top of Salesforce until Salesforce rebuilt quote-to-cash natively and, in 2025, put CPQ into end-of-sale. The middle of the revenue line turned out to be too important to leave bolted on.

Every offer needs a price

Here's where it gets practical. BrazeAI's job is deciding which offer each customer sees, and when they see it. Compare the Market, a UK insurance comparison site, is one example. It uses Braze's AI to decide which renewal message each car insurance customer gets and when it arrives. The company reported a 9% lift in renewal conversions over its usual approach, later rising to 17%, according to CMSWire.

That's a marketing AI working a renewal.

In Revenue Cloud, a renewal isn't a campaign. It happens on the asset, which is where the platform handles amendments, renewals and cancellations. When an engagement agent offers a customer a discount to renew, someone on your Revenue Cloud team has to make sure:

• the price comes from your pricing procedure, not a campaign field
• the discount respects the approval rules finance signed off on
• the renewal lands on the asset correctly, so the next amendment and the next invoice calculate the way they should

Salesforce made a similar argument at Dreamforce in September. According to Atrium's recap of the Revenue Cloud keynote, Salesforce's message was that AI alone can't run revenue, because revenue can't be "probably right." Atrium's takeaway: AI can recommend a discount, and Revenue Cloud enforces the rules.

That isn't a job for marketing ops. We made the same point about AI-built quoting tools in a recent article: let AI assist the people who price, but never let it set prices on its own.

A fair caveat: Braze is built for high-volume consumer brands, and most Revenue Cloud work is still B2B. But the line is blurring. Salesforce pitches Revenue Cloud for self-service and in-product selling, and Braze's customer list includes subscription businesses like Canva and Equinox. And none of this integration exists yet. We're describing where the work is heading, not a feature you can turn on Monday.

Your Revenue Cloud team just got a bigger job

For the past couple of years, the CPQ migration has dominated the Revenue Cloud hiring conversation. Companies have needed people who can read an old CPQ org and rebuild it the right way. That hasn't gone away. Salesforce says about 15% of Revenue Cloud Advanced customers are companies that migrated from CPQ, and plenty of CPQ orgs haven't made the move yet.

But the job description is growing. Here's how we see the shift:

The consultant who fits all three columns is rare. CPQ veterans know the first. Newer Revenue Cloud consultants know the second. Almost nobody has shipped the third, because it barely exists yet.

And the competition for those people is about to get tougher. Talent is part of what Salesforce is buying, too: its investor presentation lists Braze's "deep mobile and data engineering talent" among the deal's benefits. West Monroe's Alex Torgerson told TechTarget the deal's value "hinges entirely on integration…and customer migration." Once these products come together, customers will need people to implement them. That's six deals since June, each adding work across Data 360, Agentforce and the rest of the platform.

At the same time, the CPQ migration wave is still building. At Dreamforce, Salesforce announced a Migration Assistant, planned for December, that moves configuration as well as data. That should get more companies moving, and a tool doesn't replace the design work. The few senior architects who understand both data and revenue will be pulled in two directions.

Our prediction: the hardest Salesforce hire of 2027 won't be an AI specialist. It'll be a Revenue Cloud architect who can talk to the data team.

Why we might be wrong

The other side deserves a fair hearing, because it isn't a crazy argument.

Since June, Salesforce has agreed to spend about $10.8 billion on content, service and engagement companies. It hasn't spent anything close to that on the middle of the revenue line. Executive attention tends to follow money. Meanwhile, CPQ sits in a maintenance phase with no new features coming. If you're a CPQ consultant, it's fair to wonder whether quote-to-cash is losing the room.

There's also a warning in here for Marketing Cloud teams. Salesforce bought SteelBrick, ran it as its own product for years, then built a native replacement that requires a full re-implementation. Braze's CEO says the company will keep building as Braze, and Salesforce hasn't said what happens to Marketing Cloud's existing tools. Nobody knows whether Braze follows the CPQ path. CPQ teams just know what that path looks like.

Here's why we still land where we do. Acquisition dollars show where Salesforce needed to catch up, not what it considers core. Marketing Cloud had a gap, and Braze had been competing hard against it. It took almost a decade, but quote-to-cash is where Salesforce chose to build natively rather than keep relying on a managed package. And the more offers an engagement platform sends, the more it matters that your product catalog, pricing and asset records are clean.

What to do about it

If you run RevOps or own the Salesforce budget:

1. Give RevOps a seat at the table when marketing evaluates engagement tools. If marketing is buying AI that makes renewal or upgrade offers, decide up front who sets the limits on those offers. Every price and discount should come from your pricing procedures and approval rules, not a campaign setting.
2. Treat your product catalog and asset data as shared infrastructure. Every engagement agent will read it. A messy product catalog used to mean slow quotes. Now it means wrong offers, sent at scale. That's one more reason to clean up during your migration instead of lifting and shifting.
3. Line up your architect before demand spikes. The Braze deal won't close until 2027, but demand for senior Salesforce architects won't wait for it. Scope your migration's discovery phase while the people who can lead it are still available.
4. Ask interview questions that go beyond CPQ. Two questions worth adding: "If a customer accepts an upgrade offer inside our app, how would you make sure they get the same pricing and discount rules a sales rep would apply?" and "Walk me through what happens to the customer's asset, contract and next invoice when they upgrade mid-term." The answers will tell you quickly who has only done CPQ.

If you're a CPQ or Revenue Cloud consultant:

• Look beyond the quote. Learn how pricing gets called through APIs and by agents, how assets drive renewals, and how usage gets rated.
• Learn enough Data 360 to hold your own with the data team. That conversation is coming to your projects.
• Keep your CPQ experience front and center. Clients still need people who know why the old org was built the way it was. We laid out how to make the move in a recent guide.

Conclusion

The price gap isn't a verdict on quote-to-cash. It's a sign of where Salesforce needed to catch up. What matters for your team is what happens after the deal closes: more channels making offers, more agents asking for prices, and more pressure on the product catalog, pricing and assets underneath.

That work lands on Revenue Cloud teams. The companies that staff for it early will spend 2027 building. The rest will spend it competing for the same handful of architects.