The Deal: Pipedrive Buys Its Top-Rated Marketplace App
Pipedrive, the Estonia-founded CRM vendor that now serves more than 105,000 companies across 180-plus countries, announced on 5 August 2026 that it has acquired Outfunnel, a sales-and-marketing automation startup also founded in Estonia, in 2018. Financial terms were not disclosed. Outfunnel had been the highest-rated app on Pipedrive's own Marketplace, used by more than 500 businesses to sync customer data in real time between CRMs - including Pipedrive, HubSpot and Copper - and marketing platforms such as Mailchimp and Klaviyo.
Four Outfunnel team members are joining Pipedrive as full-time employees, including co-founders Andrus Purde and Markus Leming. Purde is returning to Pipedrive in a consultant role; his brother Urmas was one of Pipedrive's five original founders, so the acquisition folds a set of Estonian founders back under one roof. Outfunnel had previously raised 2.4 million US dollars (roughly 2.1 million euros) in pre-seed funding.
Why Pipedrive Wants This Built In, Not Bolted On
Pipedrive chief executive Paulo Cunha did not frame the deal as a routine tuck-in. "A CRM that doesn't connect with your marketing tools is only solving half the problem," he said - a direct admission that Pipedrive's core product had a real gap, one a third-party app had been quietly closing for years. Outfunnel co-founder Andrus Purde put the same point from the other side: "Joining forces with Pipedrive gives us the opportunity to help solve that problem at scale."
The stated plan is to rebuild Outfunnel's core sync capabilities as native features inside Pipedrive itself, over the coming months, not immediately. Existing Outfunnel customers keep working without disruption during the transition. That timeline detail matters: an independent app that used to ship on its own release schedule now moves onto the acquirer's roadmap, at the acquirer's pace.
Analysis: A Popular Marketplace App Is a Takeover Candidate, Not Just a Nice-to-Have
On deal size alone this looks minor: undisclosed terms, roughly 500 customers, a startup that had raised barely more than two million dollars. But the mechanism behind it generalizes well beyond Pipedrive. Platforms that run their own app marketplaces tend to absorb whichever third-party app becomes the most-used answer to a real gap in the core product, turning an independent vendor relationship into an internal feature the platform fully controls. The pattern has played out across major SaaS ecosystems - Salesforce's AppExchange, Shopify's App Store, HubSpot's App Marketplace - each has, at points, seen a category-defining partner app pulled in-house once its function proved too load-bearing for the platform to keep depending on an outside company to provide it.
The signal in this deal is precise enough to reuse elsewhere: Outfunnel was not a minor utility, it was the top-rated app in its marketplace category, and Pipedrive's own chief executive publicly named the gap it filled as unsolved by the core product. Top-rated-in-category, combined with a platform admitting that exact gap as a weakness, is a checkable pair of conditions - on any marketplace, for any app a business currently depends on.
What This Means If You Run Core Workflows Through a Marketplace App
For any company syncing data, billing or compliance workflows through a third-party app on Pipedrive, HubSpot, Salesforce or Shopify, the practical expectation is that once an acquired feature goes native, it typically lands bundled into one specific paid tier rather than shipping free across every plan, because the acquirer needs to recover a real, if undisclosed, purchase price. Existing Outfunnel customers should watch Pipedrive's tier structure as the native rollout lands over the coming months; undisclosed terms today says nothing about what the eventual pricing model will look like.
The practical check for any owner: is your most business-critical marketplace app the top-rated app in its category, and has the platform's own leadership ever described the workflow it covers as a gap in the core product. If both are true, treat that dependency as a single-supplier risk rather than a settled vendor relationship - keep the underlying data exportable, avoid building custom logic that only works against that one app's API, and assume the deal you signed up for is not the one you will have in twelve months.
Read next: Dassault Will Pay $200m More Only If the AI Earns It | Prefect Bought the Other Orchestrator on Your List
