By Adam Wessling · CMO, Speya (formerly Find My Factory) · 2026-04-23
TL;DR
For twenty years, the big bet in procurement technology was that one enterprise suite would own every workflow from requisition to payment. That bet has quietly unwound. In 2026 the category attracting the fastest growth and the most budget is not the monolithic suite. It is the intake-and-orchestration layer — tools like Zip, Payflows, and Ramp that sit in front of the existing stack, capture every procurement request at the point of origin, and route it to the right approval path, sourcing strategy, and system of record. This article explains what intake-and-orchestration is, who the category leaders are, why the shift is happening now, and where supplier intelligence fits into the new architecture.
What intake and orchestration actually means
Every procurement request starts the same way. Someone in the business needs to buy something. Legal needs a new tool. Marketing wants to run an event. Engineering needs a CAD component. Today, that person goes to a procurement inbox, a Slack channel, a spreadsheet, or — still, often — walks over to someone’s desk.
Traditional procurement treated this intake step as noise. The real work started later, inside the P2P system. The problem is that by the time the request reaches the P2P, the policy decisions are already made. Category choices, preferred vendors, approval routes, compliance gates, all of them were either skipped or improvised upstream. That is where maverick spend comes from. That is why an estimated 35% of enterprise procurement spend is off-contract. That is why a procurement leader can read a clean ERP dashboard and still not know what their company is actually buying.
Intake-and-orchestration inverts the design. Intake is a standardized gateway — a form, a portal, a chat flow — that every procurement request goes through. Orchestration is the logic that routes the request: to the right approver, to the right category manager, to the right sourcing tool, to the right supplier shortlist, to the right system of record, to the right contract template. Both sit in front of the existing procurement stack, not inside it.
Why the shift is happening now
Three forces arrived at the same time and made this category inevitable.
Non-procurement sourcing volume. By 2027, an estimated 40% of all sourcing activity will be conducted by people who do not sit in the procurement function, marketing teams buying their own tools, finance teams running their own RFPs, engineering teams adding their own SaaS. Traditional P2P was designed for a procurement analyst. It is incomprehensible to a marketing manager. Intake flows are designed for the non-procurement requester first, which is the only way that volume ever gets captured.
AI agents that actually work. For a decade, “AI in procurement” meant recommendation engines that no one trusted. The current generation of AI agents can actually execute workflow steps, drafting RFI text, extracting data from supplier responses, routing requests based on content, and flagging policy exceptions. Orchestration tools are the natural home for these agents because orchestration is itself a workflow problem. The agent does not replace procurement. It removes the manual routing that procurement used to do.
Suite fatigue. Enterprise procurement teams spent the last decade rolling out monolithic suites and have lived through the cost. Long implementations, high license fees, difficult upgrades, and — quietly — user frustration. The market response has been a move away from replacement and toward layering: keep the ERP or P2P as the system of record, add a better front end, add better intelligence, and never again commit to a 36-month rip-and-replace.
The category leaders
Three companies are most associated with the intake-and-orchestration shift in 2026.
Zip. The category-defining brand. Zip built the first purpose-built intake-and-orchestration product and has led on the workflow graph, approval routing, and non-procurement UX. Strongest with finance-adjacent procurement, marketing SaaS intake, finance tool approvals, AP-adjacent workflows. Zip does not compete with the ERP; it sits in front of it.
Payflows. European-focused, strong on policy enforcement and tail-spend control. Where Zip leans finance-adjacent, Payflows leans procurement-native. Compliance-heavy industries (financial services, life sciences) frequently pick Payflows for the deeper policy engine.
Ramp. Coming from the corporate card and spend-management side, Ramp has extended into intake as a natural adjacency. Strongest when the primary pain point is card spend rather than contract spend. The fit is best for mid-market companies that never fully adopted a P2P to begin with.
Each of these companies is adding AI agents for intake classification, supplier shortlist recommendation, and approval acceleration. None of them — and this is the important point — is trying to be a supplier intelligence platform. They are the workflow layer.
What the numbers say
The operational case for intake-and-orchestration is not theoretical. Three numbers are quoted consistently in 2026 industry reporting:
Companies that digitized procurement intake have reduced off-contract expenditure by an average of 35%.
Orchestration has increased visibility into spending for 55% of procurement leaders who have deployed it.
By 2027, an estimated 40% of sourcing activity will be conducted by non-procurement staff — which is precisely the audience traditional P2P was never designed to serve.
Taken together, those three numbers describe the economic wedge. Intake-and-orchestration pays for itself on the off-contract-spend reduction alone. The visibility lift and the non-procurement coverage are structural gains that compound over time.
Where supplier intelligence fits
Here is the architecture question procurement leaders are asking in 2026: if intake-and-orchestration is the new front end, and the ERP or P2P is still the system of record, where does supplier intelligence live?
The answer is that supplier intelligence is a third layer, and it is the layer that feeds the other two.
Orchestration tools know how to route a request. They do not know which suppliers you should invite to respond. P2P systems know how to issue a purchase order. They do not know whether the supplier has a new ESG issue, has been recently acquired, or has dropped below the financial-stability threshold your risk policy requires. The supplier intelligence layer is what provides those answers.
A working 2026 procurement stack looks like this:
Intake and orchestration layer (Zip, Payflows, Ramp) — captures the request, routes it, drives approvals.
Supplier intelligence layer (Speya, and a small number of comparable specialists) — provides the AI-vetted supplier shortlist that the orchestration tool routes the request to, and provides the continuous monitoring data that feeds compliance attestation.
ERP / P2P layer — the system of record for purchase orders, invoices, payments, and accounting entries.
Each layer has a clear job. No layer pretends to own the whole stack. That is why all three layers are compatible in a single enterprise deployment.
“The procurement leaders I talk to in 2026 have stopped asking whether they should replace their P2P. The question now is which of the three layers to upgrade first, and in what order. For most teams, the answer is the supplier intelligence layer, because you cannot route requests well if you do not know which suppliers to route them to.” — Adam Wessling, CMO, Speya (formerly Find My Factory)
A decision framework
If you are trying to figure out where your team actually needs to invest, use this three-question triage.
Question 1: Do you know what your company bought last quarter and from whom? If the answer lives across three spreadsheets, your problem is visibility, and an orchestration tool solves it first. Start with intake.
Question 2: Do you know which of your current suppliers represent the biggest compliance or financial risk? If the answer is “we would need to run a manual review,” your problem is supplier intelligence, and the continuous-monitoring gap is the critical one. Start with a supplier intelligence layer.
Question 3: Do you spend more time arguing about approval routes than executing sourcing events? If yes, your problem is workflow, and orchestration is the right fix.
Most teams answer yes to more than one of these questions. That is fine. The architecture above is additive, each layer can be adopted independently and connected later. The mistake is trying to solve all three with a single monolithic suite.
A note on language
The 2026 shift is also a language shift. Terms like “source to pay” and “procure to pay” carry the implicit assumption of a single continuous workflow inside a single system. The new vocabulary — intake, orchestration, intelligence layer — carries a different assumption: that procurement is a set of connected but distinct layers, each of which can be upgraded independently. If your procurement transformation deck still opens with a source-to-pay value chain, it is selling the last decade’s architecture.
FAQ
Is intake-and-orchestration a replacement for a procurement suite? No. Orchestration tools sit in front of the ERP or P2P. They complement the system of record; they do not replace it. Intake-and-orchestration deployments work alongside an existing procurement suite.
How is intake-and-orchestration different from a procurement ticketing system? A ticketing system captures requests. An orchestration tool captures the request and then routes it, to an approval path, to a sourcing strategy, to a supplier shortlist, to a policy check, to the right system of record. The routing logic is the difference.
Who should own the intake-and-orchestration rollout. Procurement, finance, or IT? In most successful rollouts, procurement owns the business logic (categories, policies, preferred suppliers) and IT owns the integration surface (ERP connections, SSO, security). Finance is typically the biggest internal stakeholder after procurement.
Where does supplier intelligence fit in the architecture? Supplier intelligence is a third layer. Orchestration knows how to route requests. P2P knows how to issue POs. Supplier intelligence knows which suppliers to consider, which to monitor, and which to replace. All three layers are needed; each can be adopted independently.
What is the biggest mistake teams make adopting intake-and-orchestration? Starting with the tool selection instead of the workflow design. Intake flows are as good as the upstream policy logic encoded into them. If the underlying category strategy is incoherent, the orchestration tool will just route incoherence faster.
How does Speya work alongside orchestration tools today? The current pattern is CSV or Excel export from Speya into the orchestration or procurement system, where the AI-vetted shortlist becomes part of the routing input. Continuous supplier-monitoring signals are delivered by email or surfaced in the Speya dashboard. A direct API for deeper integration is on our roadmap.
About the author. Adam Wessling is CMO at Speya, a European supplier-intelligence platform used by enterprise procurement teams at IKEA, PwC, Deloitte, EY, Ahlsell, and Stark Group. He writes about AI-driven supplier discovery, procurement operations, and European regulatory compliance. Connect on LinkedIn.