CloudAvant
News Analysis · Market Intelligence · For Operations & Support

Salesforce Signed Five Acquisitions in Five Months. None of Them Need Your Attention Yet.

Salesforce signed five acquisitions between mid-June and early November 2026, and as of this writing not one of them has a confirmed, verified close. The useful move isn't reacting to any single deal - it's documenting contracts, renewals, and integration ownership before a vendor's merger timeline forces the question.

CloudAvant Team9 min read

What you’ll learn

  • Five deals since mid-June 2026 - Fin, Loops, Braze, Rune Technologies, Cresta - with a combined reported value over $12 billion, and none confirmed closed as of 9 November 2026.
  • Only one of the five (Rune Technologies, folded into the defence-focused Missionforce unit) is genuinely irrelevant to a typical commercial Salesforce customer - the other four touch Service Cloud, Agentforce, Marketing Cloud, or Tableau directly.
  • A situation-by-situation table for what to actually do now, depending on which of these tools you already run or are evaluating a competitor to.
  • Why five deals in five months reads as a coherent strategy, not noise - and why that still isn't a reason to act today.

Salesforce's 2026 acquisitions run to five deals in under five months: Fin in mid-June, Loops in mid-October, Braze eight days later, Rune Technologies nine days after that, and Cresta four days after that. We've already covered what the Braze deal means for Marketing Cloud customers in detail. This piece is about the other four, and the one thing all five genuinely have in common: not a single one has a confirmed, verified close as of this writing, and none of them need your attention yet - your own contracts and renewal dates do, which is exactly the groundwork a Salesforce Health & Roadmap review starts with before touching anything else.

The short answer

No product feature from any of these five deals has shipped to a customer yet. Three of the five (Loops, Rune, Cresta) are expected to close sometime between now and spring 2027; Braze can't close before February 2027; Fin's status is genuinely disputed in public reporting, which is covered below. If you don't run Service Cloud, Agentforce, Marketing Cloud, or Tableau, only one of these deals is worth even a glance - Rune Technologies is a defence-logistics acquisition with no bearing on a commercial Salesforce org. If you do run one of those products, the action isn't to wait for Salesforce's roadmap; it's to know your own renewal dates and integration ownership well enough that whatever Salesforce announces next doesn't surface a question you hadn't already answered.

Salesforce's five 2026 acquisitions: what's confirmed, and what isn't

DealSignedWhat it's forPriceClose status (9 Nov 2026)
Fin (formerly Intercom)15 Jun 2026Text-based AI customer-service agent, positioned alongside Agentforce~$3.6B (Salesforce-disclosed)Disputed - see below
Loops12 Oct 2026AI analytics that explains metric changes; folds into TableauUndisclosedExpected early Nov FY27 - not independently confirmed closed
Braze20 Oct 2026Real-time customer engagement; folds into Marketing Cloud, Data 360, Agentforce$47.50/share, ~$5.66B enterprise valueNo earlier than Salesforce FY28 (1 Feb 2027) - needs a shareholder vote and regulatory clearance
Rune Technologies29 Oct 2026Frontline military logistics software; folds into the Missionforce defence unit~$375M (reported, unconfirmed by Salesforce)Expected Q4 FY27 (by end Jan 2027)
Cresta2 Nov 2026Voice AI for contact centres, paired with Service Cloud~$2.7B (reported by The Information, unconfirmed by Salesforce)Expected Q1 FY28 (roughly Feb-Apr 2027)

The Fin entry needs a caveat the others don't. Salesforce's own June announcement said the deal was signed, with closing expected in the fourth quarter of its fiscal 2027 (November 2026 to January 2027) subject to regulatory approval - standard language for a signed-but-not-closed acquisition. A separate report says Salesforce stated the acquisition completed on 10 September 2026, with Fin operating inside Salesforce AI Labs. The two accounts don't reconcile cleanly, and we could not confirm a completion through a primary Salesforce newsroom post or SEC filing in this review. Treat Fin's status as unresolved, not as closed, until your own account team confirms it in writing.

The pace is the actual story

  1. 15 Jun 2026

    Fin signed

    The oldest of the five, and the one with the most disputed status today.

  2. 12 Oct 2026

    Loops signed

    Four months after Fin, with no public link drawn between the two deals.

  3. 20 Oct 2026

    Braze signed

    Eight days after Loops.

  4. 29 Oct 2026

    Rune Technologies signed

    Nine days after Braze - the only deal outside the commercial CRM/CX line.

  5. 2 Nov 2026

    Cresta signed

    Four days after Rune - the third deal in two weeks.

Three of those five signatures landed in a two-week window. That's the detail worth sitting with before reacting to any one of them individually: a single acquisition is a bet on one product gap; five in five months, three in two weeks, is a buying pattern. Reading the pattern is more useful than reacting to any single headline in it.

Why so many, so fast

Line the four commercial deals up by channel and the logic is legible: Fin covers text-based service conversations, Cresta covers voice ones, Braze covers outbound marketing engagement, Loops covers explaining what happened in the data afterward. Salesforce reported Agentforce annual recurring revenue passing $1.5 billion in its fiscal second quarter, up 240% year over year - company-reported, not independently audited, but consistent with buying coverage for every channel a customer conversation can arrive through, rather than building each natively from scratch, the way Salesforce once did with ExactTarget and MuleSoft. What that strategy doesn't resolve is whether Fin, Cresta, and the existing Agentforce Service agent end up as one coherent platform or three adjacent SKUs a customer has to stitch together - unresolved in every deal here, Braze included. Rune Technologies doesn't fit this pattern at all; it's a separate bet on defence and national security, where Salesforce says that business is growing 80% year over year, and it says nothing about the CX acquisitions beyond confirming Salesforce has capital for more than one bet at once.

Who should care now, and who genuinely shouldn't yet

Your situationRecommended approach nowWhy
Evaluating a voice-AI vendor for your contact centre this quarterAsk Salesforce directly whether Cresta will be a bundled Service Cloud capability, a separate SKU, or sold alongside Fin as two front doors - and get the answer in writingThe announcement itself leaves this open; a vendor you're about to sign a multi-year contract against should not be left guessing on your behalf
Running Tableau and weighing a build vs. buy on AI-narrated analyticsHold any in-house build until Loops' actual close and feature plan are publicUndisclosed price and an unconfirmed close mean there's no committed timeline to build against yet
Already a Fin (Intercom) customer with Salesforce elsewhere in the businessGet written confirmation of the deal's actual status from your account team before assuming either outcomePublic reporting disputes whether this one has even closed - don't let an unresolved fact become a planning assumption
In defence, government, or national-security logistics, using or evaluating MissionforceThis is the one deal worth tracking directly - read Salesforce's own Missionforce materials, not general CX coverageRune Technologies sits in a different business line with its own buyers, budgets, and procurement rules
A standard commercial Salesforce customer not evaluating any of these specific tools this yearDocument your renewal dates and integration map; otherwise, nothing requires actionNone of the five deals changes your current contract, support, or roadmap before a close date that's still months out in every case

What to actually document between now and whichever close date applies to you

  1. List which of Fin, Loops, Braze, Rune, or Cresta actually touches a product you run or are evaluating - most organisations will find the honest answer is zero or one, not all five.
  2. For the one that does apply, pull your current contract's renewal date and term length before any negotiation, not during one - the same discipline we've recommended for the Braze deal specifically applies to any of these.
  3. If you're mid-evaluation of a competing vendor (a voice-AI platform, an analytics-narration tool), ask that vendor directly how they expect the Salesforce acquisition to affect pricing or feature parity before you sign - their answer is also a data point.
  4. Put a direct question to your Salesforce account team in writing for any deal that applies to you: does this affect our current contract, our next renewal, or our existing integrations - and if the honest answer is 'we don't know yet,' get that in writing too.
  5. Set calendar reminders for the close windows that matter to you: early November 2026 for Loops, end of January 2027 for Rune and for Fin's disputed Q4 FY27 window, February 2027 for Braze, and roughly February to April 2027 for Cresta.

What to avoid doing prematurely

  • Don't sign a competing multi-year vendor contract purely out of uncertainty about where Fin, Cresta, or Loops will land - uncertainty cuts both ways, and a rushed contract locks in the downside without the upside.
  • Don't assume Agentforce Service, Fin, and Cresta are already one product with one roadmap - the announcements leave that question open, and 'the acquisition closed' is not the same claim as 'the products are merged.'
  • Don't treat an undisclosed price (Loops, and the disputed figures for Rune and Cresta) as evidence the deal is smaller or less serious than the ones with public numbers - undisclosed terms are common in tuck-in acquisitions regardless of strategic weight.
  • Don't let 'nothing changes for now' from any vendor substitute for a written answer specific to your own contract - it's accurate about today, not a commitment about the product you'll be using once a deal actually closes.

From the field

CloudAvant has sat on the other side of exactly this situation: migrating a newly acquired Mastercard subsidiary off SAP C4C onto Salesforce Service Cloud, under a deadline set by the acquisition itself rather than by anyone's product roadmap. What that work made clear is that 'nothing changes for now' always has a quiet expiration date - someone eventually has to decide which system owns which record, re-paper which contracts, and migrate which data, and the organisations that struggle most are the ones who hadn't mapped their own systems before the deadline arrived, not the ones using the 'wrong' technology. Salesforce's own acquisition targets, and their customers, are about to run a larger version of the same exercise - which is exactly why documenting your own footprint now costs nothing and pays off regardless of which of these five deals ends up mattering to you.

Frequently asked questions

Has the Fin acquisition actually closed?

Unclear. Salesforce's original announcement pointed to a close in its fiscal Q4 2027 (November 2026 to January 2027); a separate report says Salesforce stated the deal completed back in September 2026. We couldn't reconcile the two through a primary source, so if this deal matters to your organisation, ask your account team for written confirmation rather than relying on either public account.

Is the Rune Technologies deal relevant to a typical commercial Salesforce customer?

No, unless your organisation operates in defence, government, or national-security logistics. Rune folds into Missionforce, a distinct Salesforce business unit with its own customers (reportedly already deployed with the US Army and Marine Corps) and its own procurement track. It tells you about Salesforce's capital allocation, not about anything changing in Sales Cloud, Service Cloud, or Agentforce.

Does any of this affect Marketing Cloud or Account Engagement specifically?

Only the Braze deal touches Marketing Cloud directly, and we've covered what that means in detail separately. No public statement from either deal mentions Account Engagement (formerly Pardot) either way.

What we're advising clients right now

The advice doesn't actually change based on which of these five deals you're watching: know what you're running, who owns each integration, and when each contract is up, before a vendor's acquisition timeline forces the question on its own schedule. If a Salesforce Health & Roadmap assessment hasn't been run against your current Service Cloud, Marketing Cloud, or Tableau footprint, a five-deal quarter is a reasonable prompt to close that gap - not because any single acquisition demands urgency, but because the ownership and renewal questions it raises were worth answering regardless of who Salesforce buys next. Get in touch if you want a second opinion before your next renewal conversation.

The bottom line

Five acquisitions in five months is a coherent strategy - buying coverage across text, voice, marketing engagement, and analytics narration faster than building each natively - not evidence of chaos. But a coherent acquisition strategy on Salesforce's side still isn't a reason for urgency on yours. Act when a contract renewal, a competing-vendor decision, or an actual shipped product gives you a reason to. A press release isn't one of those three things, no matter how many of them land in the same month.

Not sure which of your contracts or integrations these deals actually touch?

Written by CloudAvant Team - Senior Salesforce consultants and architects with hands-on enterprise delivery experience across Sales Cloud, Service Cloud, Experience Cloud, and complex multi-region implementations. More about CloudAvant.