This content originally appeared on HackerNoon and was authored by Ishan Pandey
\
The Procurement Software Market Doubles to $17 Billion by 2031. Spendflo Just Built the Operating Model for the Tier Growing Fastest.
\ Spendflo launched Flo AI, an autonomous procurement workforce structured around three agents that share context end-to-end: Flo Procure (intake to PO), Flo Contracts (redlines and renewals), and Flo AP (invoice match to payment). Spendflo leads with $3.2 billion in spend processed across 200-plus customers since founding. The thesis is that procurement is restructuring around a new role: the procurement engineer.
https://www.youtube.com/watch?v=ZSwAwuLbq20&embedable=true
\
A $10 billion category, splitting in three
The global procurement software market sits at $9.81 billion in 2025 and is projected to reach $17.11 billion by 2031, at a 9.76% compound annual growth rate (Mordor Intelligence). Other estimates cluster in the same band: Fortune Business Insights puts it at $8.89B in 2025 growing to $20.75B by 2034 at 9.7% CAGR. The category is large, growing at roughly twice the rate of B2B SaaS overall, and structurally splitting in three.
\ Procure-to-pay holds 62.81% of category spend. Contract lifecycle management is the fastest-growing module at 9.01% CAGR. The SME segment within procurement is expanding at 9.77% CAGR, slightly faster than enterprise. None of these are exotic numbers. They are the standard signature of a category mid-restructuring.
\
Spendflo's target band, $50 million to $1 billion in revenue, is the only band where the category math forces a structural rethink. SaaS application count scales 16x from SMB to enterprise. Procurement headcount scales 34x. The widest gap sits in the middle. A lower-mid-market company managing 75 apps with 2.5 FTEs is mathematically running an enterprise-scale problem with an SMB-scale team.
\ Three things are happening across this $10 billion category simultaneously, each on a different timeline.'
\ The enterprise tier is retrofitting AI onto legacy platforms. SAP launched its Joule AI copilot inside Ariba in January 2026. Coupa committed $150 million to autonomous procurement agents the same month. Oracle acquired Determine for $1.2 billion in December 2025 to fold contract management into the Fusion ERP suite. Workday added embedded supply-chain finance in November 2025. These are defensive moves by incumbents who already own the $1B+ enterprise segment and are not under structural pressure to rebuild.
\ The intake orchestration tier is consolidating. Zip, named a Visionary in the 2026 Gartner Magic Quadrant, sits on top of existing P2P and ERP systems to fix the unstructured intake layer. It is a wedge into the procurement function rather than a full replacement.
\
\ \ The SaaS-buying-services tier is now eight years old. Vendr has raised $156 million and built a $5 billion benchmark dataset. Tropic reports $13 billion in benchmark data. Sastrify, Zylo, and Vertice round out the cohort. These are mid-market focused but narrow to software spend specifically, and most still rely on human-in-the-loop negotiation services that do not scale with zero marginal cost.
\ Spendflo's bet is not that it competes with any one of these tiers. It is that none of them serve the mid-market the way a native-agentic, intake-to-pay system would. That is a real claim, and it is the one most coverage of the announcement will miss.
\
The vision: rebuild beats retrofit
Every procurement software vendor in May 2026 is talking about AI agents. The question that matters is whether they are building agents or bolting them on.
\
The median requisition-to-PO cycle is 55 hours, per Procurify's 2026 Procurement Benchmark. APQC's data shows top performers reaching five hours. The 50-hour gap is the procurement category's accumulated tax on coordination. Workflow automation has cut that tax by roughly half over the past decade. Agentic systems claim to cut it by another order of magnitude. Vendor claims should be treated as ceilings, not commitments, but even halfway to the claim resets the operating model.
\ If those claims hold, the question becomes architectural. A system that adds an agent to a 1995-era e-procurement workflow does not deliver the same result as one designed around the agent from the beginning. Spendflo positions itself as the second. So do Omnea and Order.co. SAP, Oracle, Coupa, Workday, and Ivalua are mostly the first.
\
The market does not always reward the architecturally cleaner product. The history of enterprise software is full of challengers that lost to incumbents with deeper integrations and higher switching costs. SAP Ariba and Coupa have those moats at the enterprise tier. They do not yet have them at the mid-market tier, which is the structural reason the mid-market is where new entrants get to compete in the first place.
\
The friction the mid-market actually pays for
The economics are not vague. The friction the mid-market pays for is measurable, and it does not show up in the procurement software P&L. It shows up in EBITDA leakage downstream.
\
The breakdown is roughly this. Of every dollar of mid-market procurement budget, fifteen cents leaks to manual coordination, eight to approval delays, twelve to maverick spend, five to renewal slippage, and ten to inactive licenses. By the time the dollar converts to negotiated value, half of it is gone. The composition is illustrative, the underlying numbers are not. Cledara puts inactive seats at 30 to 40 percent. Gartner puts shadow IT at 30 to 40 percent of total IT spend. Simfoni puts the mid-market EBITDA gap against enterprise procurement effectiveness at 5 to 10 percentage points.
\ Five to ten EBITDA points is the latent budget Spendflo is selling against. For a $200 million revenue mid-market company at a 15% EBITDA margin, recovering five points of margin is roughly $6 million a year. That is not a marketing figure. That is the financial size of the problem, and it is the only number that needs to clear for the buy decision to make CFO-grade sense.
\
The competitive geometry
The right comparison for Spendflo is not Coupa. It is the next-generation cohort fighting for the same $50M-$1B band.
\
The cohort exists because of one number. Net-new SaaS subscriptions added per month went from 53 to 401 between April 2025 and March 2026, per Cledara. A 7.5x acceleration in eleven months. No procurement team gets 7.5x bigger to match. Someone will win this band, and the candidates in May 2026 are:
\ Spendflo, with its agentic intake-to-pay positioning. Zip, with intake orchestration moving down from enterprise. Vendr, expanding from SaaS-buying-services with its new AI negotiation agent Ruth. Tropic, with the largest pricing-benchmark dataset in the cohort. Procurify and Precoro at the SMB-mid-market boundary. Ramp, Brex, and Airbase coming up from the finance-side. Coupa and SAP Ariba for any mid-market customers willing to absorb enterprise complexity.
\ The defensible features in this cohort will not be the agents themselves. Every player will ship agents within twelve months. The defensible features are which vendor sees the most contracts per category, which integrates with the broadest set of mid-market ERPs, and which captures the procurement engineer hire as the design partner before the role hardens into convention.
\ Spendflo's $3.2 billion in processed spend is real, but it is smaller than Vendr's $5 billion in benchmark data or Tropic's $13 billion. The difference is scope: Spendflo's data spans intake, contracts, and AP across all spend categories, while Vendr and Tropic see negotiation-stage data on software spend specifically. Whether a deeper but narrower dataset beats a wider but shallower one is the empirical question the next 24 months will resolve.
\
The role is the leading indicator
\
\ The most underrated tell in the entire announcement is the role naming itself. Roles do not get named into existence. They get named after the work has been visibly happening for eighteen months and three or four companies realize they are hiring for the same thing under different titles.
\ Bloomberry's analysis of 1,000 GTM engineering job posts found GTM engineer postings grew 205% year on year through 2025. Apollo's data shows them climbing from 1,400 in mid-2025 to over 3,000 by January 2026. Median compensation sits at $127,500, with senior leads at AI-native companies clearing $250,000.
\
\ Apply the same compensation logic at half the GTM curve's speed, and a senior procurement engineer would clear $150-200k within 24 months. The point is not financial. It is structural signaling. When a category names a role, the vendors who hire for that role get the design feedback loop. Vendors who do not ship features the category will not adopt.
What the demand side actually shows
The simplest and most under-appreciated data point in this entire analysis: AI tools went from 8.8% of new SaaS purchases in April 2025 to 26.4% in March 2026, per Cledara. A tripling in eleven months in a category that usually moves single digits a year. Every AI tool is a new vendor relationship, a new contract, a new compliance check, a new renewal. The procurement team that handled 25 SaaS apps at the start of 2025 is processing 35+ by mid-2026 with the same headcount.
\
\ Four numbers condense the entire investment thesis: apps per FTE, requisition wait, EBITDA leakage, AI tool share growth. None of these is correctable with a bigger team or another point tool. Each compounds the other. That is what makes the mid-market band the structurally most attractive segment in the procurement software category right now, and it is why Spendflo will not be the only vendor making this bet.
\
The bet worth tracking
What separates this from a routine product launch is the alignment of category structure, technology maturity, and capital flow.
\ The procurement software category is real and large. The mid-market band within it is structurally underserved. The technology that closes the gap has matured in the last eighteen months. The role that operates the new system has been named. The competitive cohort has assembled. Coupa has committed $150 million. Oracle has spent $1.2 billion on Determine. SAP has put Joule into Ariba. The capital is flowing through the whole category.
\ Spendflo is one of perhaps four or five companies that will reach a real position in this band by 2028. The interesting question is not whether Flo AI works. It will work in some form. The interesting questions are which vendor accumulates the most learning loops over the next eight quarters, which hires the most procurement engineers as design partners, and which ships the integrations that let mid-market CFOs replace three vendors with one.
\ The procurement category is splitting. Spendflo just made its bet on which fragment will reconsolidate first. That is the bet worth tracking.
\ Don’t forget to like and share the story!
\ \
:::tip HackerNoon has reviewed the report for quality, but the claims, opinions and analysis herein belong to the author. This author is an independent contributor publishing via our business blogging program. #DYOR
:::
\ \
This content originally appeared on HackerNoon and was authored by Ishan Pandey
Ishan Pandey | Sciencx (2026-05-14T13:47:46+00:00) Built on $3.2 Billion in Processed Spend: Inside Spendflo’s New AI For Managing Enterprise Spend. Retrieved from https://www.scien.cx/2026/05/14/built-on-3-2-billion-in-processed-spend-inside-spendflos-new-ai-for-managing-enterprise-spend/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.