For twenty years (more?) enterprise procurement teams have been trapped in a false choice: pick a single, monolithic “suite” and sign up to never change it or stitch together best-of-breed point tools (loads of great features but who wants to teach their teams how to use 11 different platforms?).
With AI this seems to be changing, but can you build your own or is this a false economy. To make you laugh, take a look at this from X:
Now, give it some careful thought… Are you building a tailored solution or an expensive black box of technical debt?
Recent market signals, like the recognition of procurement orchestration platforms in Gartner’s 2026 Source-to-Pay Magic Quadrant, show that the real battleground has moved from product category labels to architecture and an organisation’s ability to compose capabilities. Zip’s appearance as a Visionary in that report is a clear marker of that shift.
Here’s what that means in practice and how procurement teams are changing the ways they think and buy in 2026:
The missing ingredient was a strong orchestration layer
The old choice assumed the procurement platform product did most of the work but in practise this meant that whenever there was a manual over-ride or exception it just couldn’t go through the platform at all so all efficiencies and benefits were lost
In reality, what procurement needs is a way to orchestrate people, policies, systems and specialist tools so they behave like a single coherent suite while keeping the speed and innovation advantage of point solutions you can buy for specific skills (AI negotiation being a perfect example).
Orchestration layers don’t just pass data between systems. Modern orchestration understands intent: it applies policy, routes work, normalises messy inputs, and coordinates human + agent action so workflows can be part computer, part human if and when needed.
Agentic AI + orchestration will let you build your own suite
Two technical trends make this possible now:
- Agentic AI is technology that can understand messy (or at least less perfect) data inputs and independently execute multi-step tasks, using the tools people use. This lets teams automate entire sourcing flows, including identifying and executing savings via negotiations, rather than just generate a suggestion for you to follow.
- Developer-friendly agent platforms and tools (for example, Anthropic’s Claude Code and similar agent tooling) mean engineering teams can rapidly create connectors, adapters and small orchestrations without waiting years for vendor roadmaps.
Combined, those changes mean teams can assemble a “suite” around their own priorities: pick best-of-breed components where you need specialist capability (e.g., advanced negotiation, analytics, e-signature, supplier risk) and use orchestration and agents to make it behave like a single product.
Three practical implications for procurement buyers
- Stop asking “suite or best-of-breed?”
Start asking: “Which platform gives us the best foundation to grow our ecosystem?” Look for flexible orchestration, open connectors, built-in governance and evidence they can safely run agentic workflows at scale.
- Prioritise architecture and product velocity over pedigree
A legacy vendor with a long roadmap but rigid internals will slow you down. Modern architecture (event-driven APIs, intent-aware orchestration and agent support) matters far more than a checkbox list of modules.
- Design for the “Agent Architect”
Procurement teams will increasingly need people who can design how AI agents, humans and systems cooperate, not just administrators who configure fields. Consider hiring or training “agent architects” who can translate commercial intent into guarded, audit-friendly agent workflows.
What orchestration done right could do for you
I’m afraid I am starting to sound like an advert for orchestration platforms – sorry about this – but the truth is we see it first-hand here at Nibble, our clients want to get started or scale with AI negotiations but they can’t endlessly gather the data and insights manually, that effort alone erodes the ROI of the negotiation.
The same must be true for hundreds of opportunities for procurement, particularly the now we frequently see procurement needs to be aligned to the strategic aims of the business – being able to evolve to these with agility is increasingly important to CPOs.
When orchestration is done right you get:
- faster time-to-value (build and iterate in days, not quarters),
- better data capture (negotiation back and forth, supplier responses, enforcement)
- a clearer route to autonomous outcomes (e.g. agents executing repeatable work autonomously within safe guardrails).
Where specialised skills like AI negotiation fit in
Orchestration decides when and how a workflow runs. Specialist tools, like Nibble, execute one high-value job inside that flow: safe, repeatable, accountable. Think of orchestration as the conductor and a negotiation engine as the soloist: the conductor sets the score and hands off at the right moments, the soloist delivers the outcome and hands the result back for enforcement downstream.
That separation is powerful. Orchestration makes it safe and repeatable to call a negotiation engine at scale; a specialist engine makes sure those negotiations actually move commercial outcomes. Together they let you build a suite that’s both bespoke and operational.
Final thought: don’t let a vendor roadmap dictate your strategy
If your digital strategy is still constrained by a legacy vendor’s three-year plan, you’re designing to someone else’s timetable. The Build-Your-Own-Suite era gives teams a choice: conform to a vendor’s cadence, or own an operating model that evolves with your business.
If you want to start small, focus on one high-value orchestration flow (e.g., renewals or basic service RFQs). Use that as your beachhead opportunity and you’ll quickly learn where autonomy helps, where human oversight matters, and how to turn orchestration into a real competitive advantage.
