Hi {{FIRST_NAME|readers}},
The acquisition press release dropped on a Thursday.
By Friday, the LinkedIn posts were already calling it a "game changer."
Nobody had seen the combined product yet. Nobody had asked about the new org chart. Nobody had talked to a single customer running both tools in production.
That's the thing about ProcureTech press releases. They're written like endings. "We're thrilled to announce..." "This positions us to..." "Together, we will..."
It's the same energy as a Go-Live celebration. Cake in the break room. A VP giving a speech. A team photo for the internal newsletter.
And then Monday morning hits. The approvals are routing to the wrong people. The data isn't flowing. Finance is asking why the new tool doesn't match what they saw in the demo.
That's because your Go-Live isn't the ending. It's the beginning. The real work starts the next day. Anyone who’s gone through this feels it in their soul…
Press releases work the same way. They announce the intention. What follows is what matters.
That’s why we don’t usually cover them here…
BUT a big one dropped this week… And we have questions… (If only for the teaching moment)
Onwards!
📰 In this week’s edition:
📄 Source-to-Pay Process: A Practical Guide for Enterprise Indirect Procurement Teams (sponsored)
🌙 Coupa's Tonkean Acquisition. Game Changer or Smoke and Mirrors
📢 This week’s “Must Reads”
📋 3 procurement jobs that caught our eye
Note: Some of the content listed above is only available in the email version of this newsletter. Don’t miss out! Sign up for free to get the next edition.

Coupa's Tonkean Acquisition. Game Changer or Smoke and Mirrors?
Three years ago, I compared buying a Source-to-Pay system to buying an old, renovated house (list of all acquisitions for 5 top Source-to-Pay Suites).
The house looks great during the tour (demo). New kitchen. Fresh paint. Open-concept living room.
But behind the walls? Load-bearing structures from previous owners. Plumbing that was "good enough" at the time. An extension that doesn't quite connect to the original foundation.
You don't find this stuff during the open house. You find it six months after you've moved in, when you try to renovate the bathroom and discover that the pipes run through a wall you can't touch.
I bring this up because Coupa just added 4 new impressive wings to their house (or maybe they’re just going to be sheds..? Let’s wait and see).
And they've been busy renovating over the years...
The acquisition timeline:
Pre-IPO (2006-2016):
1 → Xpenser: Expense management
2 → ZenPurchase: Procurement collaboration
3 → TripScanner (2015): T&E
4 → InvoiceSmash (2015): Invoice digitization
Post-IPO (2016-2022):
5 → Contractually (2016): Contract collaboration
6 → Spend360 (2017): AI spend classification
7 → Riskopy (2017): Supplier risk
8 → Deep Relevance (2017): AI fraud detection
9 → Trade Extensions (2017): Sourcing optimization
10 → Simeno (2017): Catalog search & management
11 → DCR Workforce (2018): Contingent workforce / VMS
12 → Acquiire (2018): Real-time catalog search
13 → Hiperos (2018): Third-party Risk Management
14 → Exari (2019): CLM
15 → Yapta (2020): Travel rebooking
16 → Executive Travel App (2020): Corp Travel Tech
17 → ConnXus (2020): Supplier diversity
18 → BELLIN (2020): Treasury management
19 → LLamasoft (2020): Supply chain design
20 → Pana (2021): Travel booking
Post-Thoma Bravo acquisition (2023-present):
21 → Cirtuo (2025): AI-powered category management
22→ Scoutbee (late 2025): AI supplier discovery
23 → Rossum (May 12, 2026): Intelligent document processing
24 → Tonkean (May 21, 2026): Agentic intake & orchestration
That's 24 acquisitions over 20 years (If I didn't miss any...). This is a house that has been renovated many, many times.
But the last four are worth singling out. Four acquisitions in roughly 18 months, each one addressing a genuine gap in Coupa's platform.
On paper, it's a masterclass in strategic M&A. Coupa now has category intelligence, supplier discovery, document processing, and workflow orchestration layered on top of their core S2P network.
And the Tonkean piece, specifically, makes a lot of sense. Tonkean brings 250+ native connectors (a slew of which are already for Coupa), a no-code workflow builder, multi-agent orchestration, and (critically) experience beyond pure procurement (pun intended) in legal, HR, IT, and finance.
Coupa's own intake & orchestration product, launched just last year, was improving fast but still catching up to best-of-breed competitors (I'm guessing it’s never going to be mentioned ever again after this acquisition 😅).
This deal should accelerate the modernization timeline significantly.
So yes, these last 4 acquisitions are a big deal for Coupa's competitive positioning.
Here's the irony, though.
Coupa now has the exact same problem you have if you're running multiple systems in your own enterprise ProcureTech stack.
A sourcing tool that doesn't talk to your CLM. A spend cube that lives on a different planet from your P2P suite. An SRM tool that has never heard of your ERP. And if you have multiple ERPs? You know this hell intimately.
None of them are written on the same code base. You spend half your time being the human integration layer between tools that were each sold to you as "the platform."
The only difference? Coupa's core business is making sense of messes like this. And they also, just like leading procurement teams, have acquired Intake & Orchestration capabilities to help “connect the tubes” 😅 So, if anyone can pull off these integrations, they are certainly a contender...
The question is whether being a contender turns into "actually pulled it off."
Given Tonkean’s “raison d’être” is integration/orchestration between different systems, is it going to be the glue that's supposed to pull the above pieces together? Does this mean it should be more of a Tonkean + Coupa situation than Coupa + Tonkean?
(Tonkean the hub, all other Coupa apps the spokes?)
Given the press release is full of terms like “native integration”, “unified” & “united”, one would imagine so…
Everyone's talking about what Coupa + Tonkean means for the ProcureTech market.
Nobody's asking what it means for you, the buyer…
I've watched a horror movie with a similar beginning in the past...
SAP bought Ariba in 2012. Made sense on paper. Augment ERP procurement processes with a best-of-breed procurement suite and business network. I was excited for the possibilities.
Six, seven years later, Ariba was still a separate org and a separate product, just sold via the same website... Integration to SAP ERP remained harder than catching a greased watermelon in a swimming pool... while blindfolded. 😅
(And I, a competent ProcureTech implementer, almost burned out trying to make the marketing work in real life.)
Note. 👆True fact… It’s actually a big reason why this newsletter exists… To try to spare you the future burnouts… 😅
13 years later, SAP announced they were rewriting Ariba from scratch.
That experience shaped a rule I now apply to every major ProcureTech acquisition:
Don't evaluate the combined capabilities. Evaluate the combined organization.
The questions tech-savvy procurement pros should be asking:
So, if you're a Coupa customer (considering becoming one), here's the list of questions I'd bring to your next conversation with your account team to validate this isn’t a cheap horror movie reboot… 😱
The answers will tell you if you're really getting any "synergies" from this new combined organization (I love a good synergy, don't you? 😅).
Sales & Go-to-Market:
→ How are Coupa and acquired sales teams going to market together? Integrated, unified, or will you now just have a Coupa rep sitting in on all the Tonkean, Rossum & Cirtuo calls, adding bodies, noise and complexity to the conversation?
→ How are sales incentives being drawn up? In the best interest of customers, or according to solution business units?
Delivery & Support:
→ How are delivery and customer success teams being cross-trained on each other's solutions to provide 1 seamless experience (given that's the undertone of all this M&A activity)?
→ What does the implementation methodology look like for the combined products? Is it one methodology or multiple methodologies stitched together?
→ Are Coupa's SI partners going to be trained on these new products/modules? Or do we need to add 3+ new specialized functional analysts to every end-to-end delivery project?
Product & Roadmap:
→ How are product teams being integrated to build one INTEGRATED roadmap, not two (or five)?
→ How is the org structure changing to ensure common objectives, language and culture between what used to be separate organizations?
→ How will data models, workflows, and process ownership actually be unified across both platforms? (Because in ProcureTech, integration challenges are almost never about features. They're about data models, operating models, user experience and adoption.)
Tonkean has its own data model (albeit a flexible one). Coupa has its own data model. Cirtuo, Scoutbee, and Rossum each have theirs. Getting five sets of data structures to behave as one coherent platform is not a press release problem. It's an engineering problem that can take years to solve well (if at all).
(It’s also why I ask if viewing it as Coupa on top of Tonkean instead of Tonkean on top of Coupa makes more sense?)
Why the System Integrator questions matter more than you think
Those delivery & support questions are important…
Most analysis is viewing this M&A activity through a functionality/capability lens… I think the more important question is “How is this ‘new Coupa’ (and its ecosystem) going to deliver client benefits at scale?”
Traditionally, Coupa has mostly outsourced implementation to solution integrators (SIs). These SIs have built big consulting practices around Coupa. Coupa's position has long been "we don't want to be in the consulting business." (Fair enough, that’s the position of most software providers...) But that means the people designing your processes, configuring your workflows, and managing your change aren't Coupa employees.
The newer I&O-first players took advantage of this (Zip, Focal Point, Pivot, Vertice, ORO Labs, Tonkean, etc.)… They largely implement directly with clients. They have “Forward Deployed Engineer” roles in-house. SI partnerships are starting to develop for business analysis and configuration work as they scale, but nothing like the heavy functional and development consulting work that characterizes a typical Coupa (or “old guard” S2P Suite) implementation.
So, what happens now? Are existing Coupa SIs going to be trained on Tonkean's orchestration platform? On Rossum? On Cirtuo and ScoutBee? Is Coupa going to be doing solution architecture in-house more seriously? Will Tonkean's implementation teams be spun-off into Coupa's partner model? Or will there be a gap where nobody fully owns the end-to-end experience?
I’m sure the answer is going to be “a unified, ONE Coupa approach”, by the way…
But in a world with unlimited distractions, simplicity and focus are at a premium. And these 4 acquisitions have created a huge, complex set of questions that need concrete answers (and aligned action) before this vision can become reality.
The bigger point (and this applies to every ProcureTech decision, not just Coupa)
Once your "functionality bar" has been cleared when sourcing ProcureTech, you should be almost disinterested in solution capabilities...
I know that sounds counterintuitive. But hear me out.
At a certain point, features become table stakes. Every serious vendor clears the bar. The demo looks great. The roadmap slide is inspiring. The competitive matrix has green checkmarks everywhere you want them.
After that, the ONLY thing that matters is the vendor's ability to deliver the business outcomes you're actually looking for. And that ability comes from the business capabilities you develop when/while implementing their tools. Not the tools themselves.
If you’ve got a Ferrari in the garage but no driving license, you’re out of luck… (And, no, I don’t care if it’s an AI-enabled Ferrari 😅)
Ability to deliver has two components:
→ A technology component (consistently overrated). The platform, the connectors, the AI, the dashboards.
→ A domain-specific implementation component (consistently underrated). The people. The change management. The process redesign. The organizational readiness.
These two components are linked together by the processes you design, implement and support *with* the tools. That's where value is created. Not in the feature list.
So, when you see a headline like "Coupa acquires Tonkean," don't just ask "what new features does this give me?" Ask "does this combined organization have the people, the methodology, and the implementation depth to help me build the business capabilities I need, in context, without needing a PhD to navigate their organization and license structure?"
“Who gets me to business results on the shortest, straight(-ish) line?”
Don't get tickets to the functionality circus. You'll be entertained by the ROI illusionist. Popcorn will be available. But you won't have learned how to juggle anything…
Juggling is the core skill you need to be successful.
Juggling school with a proven juggling instructor is a better investment. 😅
What this means for the broader market
Our hypothesis on implications:
For existing Coupa customers: You now have a much stronger intake & orchestration story with your existing vendor. That's genuinely good news for your internal discussions. But, you’ll still need to push hard on the integration timeline (yes for product, but mostly for org structure!). Don't assume "acquired" means "integrated."
For organizations evaluating I&O solutions: Coupa just became a more serious contender, but the combined product (Coupa + Tonkean) works just as it did yesterday. And unless Coupa starts shutting other partners out, all the other solutions have their Coupa connectors as well… If you need something production-ready today, ask to see it working, not just demoed (yes, even if they are throwing in Tonkean for free!).
Free can turn out to be quite expensive…
For other S2P suites: The pressure just increased. They now face a Coupa with (on paper) best-of-breed orchestration capabilities layered into their suite. Perhaps we see more acquisition activity from competitors trying to keep pace in months to come? I’ll leave those predictions up to the real analysts…
For best-of-breed I&O vendors (Zip, Focal Point, Pivot, Vertice, ORO Labs, etc.): Selling against the Coupa + Tonkean combination is a new challenge, but the "we're already an integrated platform, they're still assembling" argument is a strong counter for the next 12-24 months while answers find the hard questions.
The 1 product with 0 acquisitions narrative surely stays compelling as well.
For the orchestration market more broadly: Further consolidation is surely coming unless the different players can find strong, durable differentiators providing a competitive advantage, if only for a slice of the total addressable market (TAM)…
The bottom line
Congratulations to all teams (and teams from previous acquisitions). These are smart deals on paper.
But the real work starts now.
(Just like the real work of digital procurement starts AFTER your Go-Live.) 😊
The coming months will reveal whether “unified, united and integrated” go from press release to practice. I sure hope they do.
Until the dust settles, getting strong answers (and proof!) to the questions above is required for diligent ProcureTech buyers who want the actual business outcomes they are looking for...
In the meantime, this is just another press release…
Disclosure: Zip, Pivot, Vertice, Focal Point, and ORO Labs are Pure Procurement content partners. Tonkean has been a content partner in the past. This piece represents our independent editorial perspective.
👀 In Case You Missed It…
The Last 3 Newsletters:
1/ The Day Nobody Came to Our eAuction
2/ P2P Requirements for Manufacturers, Distributors, and MRO-Heavy Operations
3/ The Master Procure-to-Pay (P2P) Functional Requirements List for Indirect Purchasing

Execution is the ability to mesh strategy with reality, align people with goals, and achieve the promised results.

2 other ways we can help this week:
Stop comparing apples to oranges. Most ProcureTech evaluations break down early because teams compare suites, point solutions, and hybrids as if they solve the same problem. This framework gives you a sharper way to read the market, structure your thinking, and build a technology stack around fit, integration, and business outcomes instead of vendor noise.
Grab it here.Make your implementation more likely to succeed. Procurement system rollouts rarely fail because of the software alone. They fail when the fundamentals get missed. This quick-reference poster highlights the success factors that matter most, from data quality and governance to team setup and change management, so your project stays focused on what actually drives results.
Grab it here.
See you next week {{FIRST_NAME|readers}},
— The Pure Procurement Newsletter Team
P.S. Please rate today’s newsletter.
Your feedback shapes the content of this newsletter.
