Romain Libeau is a founder of Pivot, a procurement software company. The posts describe Pivot’s work on AI-native procurement software and focus on how data, system architecture, and implementation costs affect the value of procurement technology.
Romain Libeau is most useful for practical buyer tests on procurement AI claims, data readiness, and total cost.
Best for
A procurement technology vendor selling on data readiness, faster implementation, or total cost of ownership.
Not for
A legacy suite launching an autonomous-procurement campaign led by agent count or AI branding.
Key takeaways
AI in procurement is capped by the foundation, not the model.
Subscription fees are about 23% of modeled three-year Coupa costs.
Agent washing warns buyers against paying extra for autonomy they do not need.
Check first: Confirm recent post-level results, audience composition, and sponsorship availability before contacting them.
Main ideas
AI in procurement is capped by the foundation, not the model · Most of a procurement software bill is not the subscription · "Agent" is a vocabulary problem before it is a technology problem
Romain Libeau is a founder of Pivot, a procurement software company.
They write about whether procurement technology—especially AI—solves real problems and delivers value.
A recurring point is that new features cannot compensate for weak data, fragmented workflows, or costly implementation.
Their posts offer buyers practical questions to ask before they invest.
Libeau turns procurement-tech hype into buyer tests.
In a post about AI agents, they ask whether a product offers genuine autonomy or simply automation under a new name, and warn buyers against paying extra for autonomy they do not need.
In another, they challenge the upbeat interpretation of a report in which 17% of respondents said they saw clear returns from procurement technology and AI, pointing to data quality, adoption, integrations, and workflows as constraints on results.
They also make enterprise software costs more concrete: citing a commissioned Coupa study, they note that subscription fees account for about 23% of its modeled three-year costs, with implementation, deployment, training, and ongoing management making up the rest.
Some posts make a direct case for Pivot’s AI-native approach, reflecting their perspective as the company’s founder.
Romain Libeau writes as founder of Pivot, a procurement software company, and returns to one argument from several angles: procurement AI is limited by the data and system architecture beneath it, not by the models.
Read more
They also argue that buyers routinely misjudge the cost of procurement software, much of the current "agent" market is repackaged automation, and products become incumbents far faster than their founding dates suggest.
The posts share a format — a short, humorous, counterintuitive opener, a specific number or example, then a route to a longer read, panel or calculator.
The recurring focus is buyer-side scrutiny of claims, not enthusiasm for new labels.
AI in procurement is capped by the foundation, not the model
Libeau treats procurement AI as a systems problem, not a model problem.
Read more
Responding to a State of AI in Spend finding that 17% of procurement, finance and IT leaders see clear ROI from their procurement technology and AI investments, they read the figure as a scoreboard, not a group to imitate: after two years of agent and autonomous-procurement launches, most respondents still cannot point to clear returns.
The reasoning is that AI cannot manufacture clean supplier data, create adoption, reconcile fragmented workflows or repair bad integrations and missing context.
Stacking more agents on the same foundation does not change the outcome.
They make the same case from Pivot's history: starting during the AI era, they say, allowed the company to connect directly to the system of record and keep data structured, giving AI the context to do work rather than merely perform well in a demo.
They acknowledge that the models are improving; the criticism is about what they are plugged into.
The 17% ROI figure, the list of things AI "can't" do — clean supplier data, adoption and fragmented workflows — and the claim that Pivot had an advantage because it was built when AI was already part of the equation.
Most of a procurement software bill is not the subscription
Libeau argues that buyers compare licences when they should compare total cost.
Read more
Drawing on a Coupa-commissioned study that models roughly $24M in costs over three years, they note that only about 23% goes to Coupa fees, with the rest split between implementation, planning and deployment, and training and ongoing management.
These costs are neither hidden nor surprising, they argue, but they matter when calculating ROI: returns should be measured against everything invested to deliver value, not just the subscription.
They frame this as a habit inherited from legacy enterprise software that buyers rarely question.
The post itemises about $7.5M for implementation, $5.4M for planning and deployment, and $5.5M for training and ongoing management out of roughly $24M over three years. It notes that the study was commissioned by the vendor being examined and points readers to a coupon ROI calculator Pivot built.
"Agent" is a vocabulary problem before it is a technology problem
Libeau argues that the language is moving faster than the tools: assistants became agents, agents became superagents, and every automation is one rebrand away from being called autonomous.
Read more
They borrow Gartner's term "agent washing" for a market flooded with rebranded automation, then spell out three buyer risks: paying a premium for agentic vocabulary, buying autonomy when plain automation would do the job, and starting with an agent before looking for a problem to solve.
Their question for buyers: does the problem actually call for an agent, or did the hype make the choice?
Ran Shapira of Lemonade, Joël Collin-Demers of Pure Procurement, and Pivot's Marc-Antoine Lacroix were announced separately as panellists discussing what agent washing looks like and where an agent genuinely made sense.
The post lists three buyer risks. Other posts strike the same note, mocking the "agent, superagent, digital workforce" launch cycle and describing fifty agents and newly promoted AI governors failing to rescue a stretched product.
Hypergrowth turns a young disruptor into an incumbent ahead of schedule
Libeau argues that legacy status no longer takes decades; sometimes six or seven years is enough.
Read more
They describe scope creep from an original idea: more products, services, packaging, specialists and AI branding than the software was designed to carry.
They credit the first generation of orchestration tools with solving a genuine procurement problem by giving employees a cleaner place to start and procurement a better way to coordinate requests.
Then hypergrowth knocks down the load-bearing walls, stretching the architecture and embedding complexity.
Their practical advice to buyers: a recent founding date, polished interface or fleet of new AI roles will not rescue an ageing foundation, so examine what sits beneath the modern story.
The argument also has a self-interested edge: it comes from a newer company.
The post's central image: software that still looks young, built on a foundation with "lower back pain, a mortgage, and strong opinions about the way we've always done it". It also quips that a product can be too young to rent a car and somehow old enough to become the incumbent.
Every argument routes the reader somewhere concrete
Libeau's recurring format: a counterintuitive or self-deprecating opening, one argument developed in short paragraphs, a specific number or named example, and a clear next step — a full read, event registration, calculator or product site.
Read more
Humour is the entry point, not the payload. The posts serve as doorways to longer assets, such as a study walkthrough, panel or interactive tool, rather than as complete pieces on their own.
A post opens, "POV: you realize the subscription might be the cheapest part of your procurement software," and ends with a ROI calculator.
An event post names its panellists and includes a registration link.
Another post narrates a film opener and points to the company's new site: "the subtitles explain me."
Answers the first question a newcomer to procurement software faces: does the word "agent" tell you what a tool can do?
Read more
It is the clearest short statement of the position Libeau returns to across the other posts.
The post starts from the observation that everyone now has an agent, then asks what they mean by the word.
It cites Gartner’s term "agent washing" for rebranding ordinary automation as autonomy, and lists three ways the confusion costs buyers: paying a premium for agentic vocabulary, buying autonomy when plain automation would do the job, and choosing an agent before finding a problem for it to solve.
It closes by pointing to a discussion with Ran Shapira of Lemonade, Joël Collin-Demers of Pure Procurement, and Pivot’s Marc-Antoine Lacroix about where an agent genuinely made sense.
For brands planning a campaign
A procurement software company could use this as the frame for a piece on how to interrogate agent claims during a vendor evaluation. Libeau supplies the vocabulary test; a practical checklist for buyers would be the collaborator’s contribution.
Answers how far procurement AI has got, using a published statistic rather than a vendor claim.
Read more
It offers a useful reality check before readers turn to more promotional material.
Cites a State of AI in Spend report finding that 17% of procurement, finance, and IT leaders report clear ROI from their procurement technology and AI investments.
Rather than treating the 17% as a group to copy, the post reads it as a scoreboard problem: after two years of agent and autonomous-procurement launches, most respondents still cannot point to clear returns.
The argument is that AI cannot manufacture clean supplier data, drive adoption, or reconcile fragmented workflows, bad integrations, and missing context—and that adding more agents to the same foundation changes nothing.
For brands planning a campaign
Works well alongside the standard AI-procurement narrative. A vendor could pair the statistic with practical material on data readiness and integration as prerequisites for an AI rollout to deliver returns.
Answers the cost question directly with public numbers, which is rare in this category.
Read more
Newcomers get a concrete sense of where the money goes.
Points out that, for legacy procurement software, the licence is often the smallest budget line.
It draws on Coupa’s own commissioned study, which models roughly $24M in costs over three years, of which about 23% is Coupa fees.
The rest is itemised: $7.5M for implementation, $5.4M for planning and deployment, and $5.5M for training and ongoing management.
The post notes that these costs are neither hidden nor surprising, and argues that ROI must be measured against the whole outlay, not just the subscription.
For brands planning a campaign
A foundation for a total-cost-of-ownership comparison. The linked calculator is Pivot’s own asset, so a partner would need to build or license a comparable tool to reuse the argument.
Explains why so much procurement software feels dated despite recent founding dates, and gives readers a checklist of what ages a product: expanded scope, a thicker commercial model, services, and a growing org chart.
Read more
Argues that legacy status can arrive in six or seven years, not decades, when an original idea is weighed down by more products, services, packaging, specialists, and AI branding than it was designed to carry.
It describes first-generation orchestration tools that solved a real procurement problem—a cleaner place for employees to start and a better way for procurement to coordinate requests—before hypergrowth knocked down the load-bearing walls.
The software still looks young; the foundation has aged.
A recent founding date, polished interface, or fleet of newly promoted AI governors will not rescue it.
For brands planning a campaign
A useful narrative frame for content about platform sprawl and the hidden cost of expansion, helping buyers look past interface polish and founding-date marketing.
Explains what "AI-native" means in practice, from someone building that way.
Read more
This post states the product thesis the others circle around.
Against the backdrop of a Pivot video, the post argues that procurement software is racing to become AI-native without reckoning with its inherited architecture.
Agents, copilots, superagents, and governors still have to work with the system underneath them, so adding more changes the org chart more than the capability.
The claim is that Pivot started in the AI era, connects directly to the system of record, and keeps data structured—allowing AI to do work rather than just perform in a demo.
For brands planning a campaign
A natural anchor for a collaboration about architecture readiness for AI in procurement. A partner would need to bring independent evidence; the supporting detail is in Pivot’s own marketing assets.
Format: short argument posts that route to longer reads and live events5
AI value in procurement is capped by the data and architecture underneath it3
Agent washing: separating autonomy from automation with a new label3
Total cost of ownership: the subscription is rarely the real number1
Hypergrowth turns a young disruptor into an incumbent ahead of schedule1
AI value in procurement is capped by the data and architecture underneath it
Across several posts, Libeau argues that procurement AI is limited by the systems it runs on, not by the models.
Read more
Reacting to the State of AI in Spend finding that only 17% of procurement, finance, and IT leaders see clear ROI, they treat the figure as evidence that two years of agent launches have not fixed clean supplier data, adoption, fragmented workflows, or missing context.
The foundation, they argue, decides how far AI can go.
A separate post draws on Pivot's own history: starting in the AI era let the company connect directly to the system of record and keep data structured, giving AI the context to do work rather than just look good in a demo.
A post about an international blockbuster film opens with a joke about the risk of letting a French founder narrate the opener, then turns to procurement software racing to become AI-native without reckoning with the architecture it inherited.
Reframes a widely circulated industry statistic, then supports the argument with concrete obstacles—data quality, adoption, and integrations—instead of a product pitch.
Libeau concedes the models themselves are improving; the criticism targets the systems they plug into.
For brands planning a campaign
Build around this argument when selling data readiness, clean integrations, or a system of record that AI can act on. It also suits content contrasting foundation-first implementation with agent add-ons.
Total cost of ownership: the subscription is rarely the real number
One post walks through a Coupa-commissioned study modelling roughly $24M in costs over three years, of which only about 23% is Coupa fees.
Read more
The rest breaks down, as cited in the post, into about $7.5M for implementation, $5.4M for planning and deployment, and $5.5M for training and ongoing management.
Libeau argues these costs are neither hidden nor surprising, but matter when calculating ROI: the value delivered relative to everything invested to get there.
The post closes by pointing to a Coupa ROI calculator the team built.
Uses a vendor's commissioned cost study to make a buyer-side ROI argument, then gives readers a tool to run their own numbers.
The study was commissioned by the vendor being examined.
For brands planning a campaign
A vendor selling faster implementation or lower ongoing management costs can join this argument directly. The topic lends itself to interactive assets, such as calculators or cost-breakdown worksheets, rather than a standard explainer post.
Agent washing: separating autonomy from automation with a new label
Libeau argues that vocabulary is moving faster than technology: assistants become agents, and agents become superagents.
Read more
They cite Gartner's term "agent washing" for a market flooded with agent-washed products.
The post lists three buyer risks: paying a premium for agentic vocabulary, buying autonomy when automation would have done the job, and starting with an agent before working backwards to find a problem for it to solve.
Other posts develop the same theme: one mocks the agent, superagent, digital workforce, and "one model away from sentience" launch cycle; another describes fifty agents and newly promoted AI governors failing to rescue a stretched product.
Uses a third-party analyst term to anchor the critique, lays out buyer risks in a short list, then hosts a live panel where named practitioners unpack where an agent actually made sense.
For brands planning a campaign
Best fit for a company differentiating honest automation from agent-hype competitors, or for an event or webinar built around a named guest panel. A concrete product comparison will keep the framing from becoming another complaint about vocabulary.
Hypergrowth turns a young disruptor into an incumbent ahead of schedule
One post describes legacy status arriving in six or seven years rather than decades: an original idea burdened with more products, services, packaging, specialists, and AI branding than it was designed to hold.
Read more
Libeau credits the first generation of orchestration tools with solving a real procurement problem, then describes hypergrowth knocking down load-bearing walls until the architecture strains, complexity settles in, and marketing gets handed a launch date. The conclusion is aimed at buyers: a recent founding date and polished interface will not rescue a stretched foundation, so look beneath the modern story.
Uses an extended architectural metaphor—load-bearing walls, lower back pain, a mortgage—to make an abstract switching-cost argument concrete, then turns it into a buyer checklist.
For brands planning a campaign
Works for a challenger positioning against a bloated incumbent, but the argument is self-interested from a newer company. Ask for named product evidence or a buyer-facing audit to support it.
Format: short argument posts that route to longer reads and live events
The posts follow a consistent shape: a counterintuitive or self-deprecating opener, short one-line paragraphs, a specific number or example, and a route out—a link to a full read, registration for a panel with named guests, or a calculator.
Read more
Examples include a POV-style opener about the subscription being the cheapest part of procurement software, a statistic reaction, and an event invitation naming practitioners from Lemonade, Pure Procurement, and Pivot. Humour serves as an entry point, not the payload, as in the post about being too young to rent a car and old enough to become the incumbent.
For brands planning a campaign
A brand working with Libeau should expect a short, provocative post that drives readers to a longer asset, event, or tool rather than a standalone explainer. Campaign planning should fund the destination asset, not just the post.
Romain Libeau writes as a founder of Pivot, a procurement software company, making it the clearest business relationship stated in the posts.
Read more
Other named brands appear as comparators, research sources or guests at a Pivot-hosted session. Ask for confirmation before treating any of them as clients, sponsors, affiliates or investment partners.
Pivot
Owned business
Libeau describes Pivot as a company they helped start, writing that they have believed in its approach “since we started Pivot.”
Read more
They say Pivot began in the AI era, connecting directly to the procurement system of record. The post points readers to a new Pivot site explaining that position; a later post describes building a Coupa ROI calculator with the same first-person framing.
Coupa appears in a cost comparison, not as a partner or client.
Read more
Libeau cites a Coupa-commissioned study modelling roughly $24M in three-year costs, about 23% of which is Coupa fees, and says Pivot built a calculator so buyers can work out their own return. No commercial relationship between Libeau and Coupa is stated.
Libeau names Lemonade as the company whose representative, Ran Shapira, would join a session on agent washing—the practice of rebranding ordinary automation as autonomous agents.
Read more
The post invites readers to the event; no commercial agreement between Libeau and Lemonade is stated.
Libeau lists Joël Collin-Demers of Pure Procurement as a fellow panelist on the same agent-washing session, alongside Lemonade’s Ran Shapira and Pivot’s Marc-Antoine Lacroix.
Read more
The posts show a shared speaking engagement, not client, sponsorship or partnership terms.
Romain Libeau writes as a founder of procurement software company Pivot, building a running argument rather than a stream of product news.
Read more
Start with their reaction to the State of AI in Spend finding that 17% of procurement, finance and IT leaders see clear ROI, and the Coupa cost breakdown: together, they lay out the core position that AI's ceiling in procurement depends on the data, integrations and system of record underneath it, while the subscription is usually the smallest line in the bill.
Then read the posts on agent washing and hypergrowth turning a young disruptor into an incumbent, which address vocabulary and switching costs.
The posts typically open with a short, often self-deprecating line, make one argument, cite a specific number or named example, and point to a longer read, a panel with named guests or a calculator.
Follow those links to explore the argument beyond the post itself.
Blonski makes the same structural argument as Libeau: AI's value depends on the enterprise architecture beneath it, not the model or agent on top.
Read more
Both write short, direct posts that name legacy SaaS vendors and push buyers beyond vendors' own framing of what AI can do.
Blonski writes from a broader enterprise-software position, covering IT, CRM, HR and procurement, and goes further into claims about where separate AI bills leave buyers, drawing on analyst coverage. Libeau stays within procurement, anchoring the argument in buyer ROI and implementation cost rather than the whole enterprise stack.
Barendrecht writes about the same procurement and spend-management market as Libeau, including how the category is valued and how companies adopt AI.
Read more
Both are operators in procurement software, bringing a seller's view of where the market is heading.
Barendrecht posts event and team-building updates, including an annual summit recap and an argument for joining a go-to-market team; market observations come through reported conversations. Libeau builds standalone arguments around a statistic, a vendor cost study or a critique, offering analysis rather than an event record.
Thorson writes about scaling a B2B company and how growth stalls when founder-led selling does not become team-driven, overlapping with Libeau's argument that hypergrowth quietly ages a company.
Read more
Both draw on their operating histories and see people and relationships as what automation cannot replace.
Thorson focuses on supply-chain partnerships and go-to-market leadership, drawing on more than thirty years of experience in career and practice updates. Libeau focuses on the software itself, its cost and architecture, with more contrarian, number-led writing.
Audience evidence for Romain Libeau is thin and mostly indirect.
Read more
The only measured figure is a LinkedIn following of about 30,560, recorded on 8 October 2026.
That establishes reach on one channel, not who follows them or how many people see any given post.
Five posts published between 13 August and 9 September 2026 show the readership their work addresses.
The subjects are procurement technology economics and AI claims: a State of AI in Spend ROI statistic, Coupa's three-year cost breakdown, agent washing, and legacy procurement software outgrowing its own architecture.
The vocabulary — implementation cost, system of record, deployment, procurement leadership — points to procurement, finance, and IT staff who buy or operate these systems.
For a content-marketing collaboration, ask for recent post-level results on the topics and formats you would commission, using the ROI and agent-washing posts as comparators, and an audience report or survey covering job function, seniority, and geography.
Romain Libeau's posts promote Pivot's own products and content rather than paid placements for other brands.
Read more
They link to Pivot's new site, a Pivot-built Coupa ROI calculator, an article on legacy software and hypergrowth, and a webinar registration for a session with guests from Lemonade and Pure Procurement.
The posts include no sponsorship policy, media kit, rate card, audience specification, or partnership inquiry route.
Ask directly about sponsorship availability, scope, deliverables, disclosure, and timing; the LinkedIn profile linked on this page is the only visible public contact point, but it is not a verified partnership channel.
A procurement technology vendor that sells on data readiness, faster implementation, or total cost of ownership is a strong fit for Romain Libeau.
Read more
Brief: ask them to write or co-create a short argument on why procurement AI results stall without clean supplier data, structured records, and integrations that let AI act.
Decision: yes.
Their posts already make that case repeatedly.
The 17% ROI post argues that AI cannot manufacture clean data, adoption, or reconciled workflows.
The AI-native post says agents and copilots still have to work with the system underneath them, and that starting in the AI era let Pivot connect directly to the system of record and keep data structured.
The Coupa post reframes ROI around the full cost of implementation, planning, deployment, training, and ongoing management rather than the subscription alone.
Those are the exact arguments a foundation-first procurement vendor would want in market.
Libeau's audience appears to include procurement, finance, and IT practitioners, matching the posts' vocabulary and examples.
The format also fits: short, pointed posts that route readers to a longer read, a tool, or a named-practitioner discussion.
Before committing, ask for recent post-level results on comparable topics and audience composition; follower count alone cannot show whether the right professional roles read a sponsored post.
Commercial terms and deliverables would need to be negotiated directly.
When to choose a specialist
A legacy enterprise procurement suite that wants to launch an autonomous-procurement campaign led by agent count, AI branding, or an expanding agent org chart would be a poor fit.
Read more
Libeau's posts directly undercut that positioning.
The agent-washing post says the vocabulary is moving faster than the technology, cites Gartner's term for rebranding automation as autonomy, and lists the risks of paying a premium for agentic vocabulary and buying autonomy where plain automation would do the job.
The hypergrowth post says fifty agents and newly promoted AI governors will not rescue a stretched foundation.
The site post opens by mocking the agent, superagent, digital workforce, and one-model-away-from-sentience launch cycle.
A sponsor whose core claim is that more agents equal more autonomy would be buying content that criticises that claim.
The mismatch is not fixable with a campaign rewrite because the conflict runs through Libeau's strongest posts.
A general AI thought-leadership campaign with no procurement-specific product or buyer decision attached would also be a poor fit.
Libeau's posts are consistently anchored in procurement software economics, implementation, and buyer choices.
Stripped of that context, the argument loses the concrete numbers and practitioner detail that make it useful.
There is no documented sponsorship policy, media kit, rate card, or published partnership package, so ask Libeau to confirm availability, terms, scope, disclosure, timing, and deliverables before pursuing a paid placement.
A worked campaign example
Campaign angle: The 83% problem: what has to be true before procurement AI returns anything.
The sponsor is a procurement platform that can show implementation speed, clean data handling, or lower ongoing management cost.
Step one: Libeau opens with the 17% ROI statistic and rejects the builders-versus-laggards frame.
The post says two years of agent launches have not fixed clean supplier data, adoption, fragmented workflows, or missing context.
Step two: a companion buyer asset turns the argument into a working tool.
A data-readiness checklist or a total-cost-of-ownership worksheet would follow the pattern of the Coupa ROI calculator, but the sponsor would need to build or license that asset.
Step three: a live or recorded conversation with a named practitioner follows the agent-washing post's pattern of testing where an agent actually made sense.
Step four: route readers to the sponsor's product page, demo, or brief.
The angle needs sponsor-specific details to avoid becoming another opinion post: implementation costs, integration detail, or a named customer example.
Libeau's posts show they can carry the argument and the short-post-to-longer-asset format.
No sponsorship package, rates, or disclosure terms are published; negotiate those directly.
If the sponsor cannot supply the concrete details, the campaign should not proceed on this angle.
Choose David Blonski over Romain Libeau when the campaign targets the legacy suite itself and the sponsor can put named customers and hard savings beside the claim.
Read more
Blonski's posts make the replacement case in vendor terms: cut the legacy SaaS stack, move that money into product and people, and attach an arithmetic claim—a stated 50-70% reduction in total cost of ownership—to named companies such as Sanofi, Under Armour, and Snowflake.
They hit the same procurement incumbents Libeau treats as architecture problems: Salesforce, ServiceNow, Coupa, Workday, and SAP.
They also add a pricing angle Libeau leaves implicit: agent tolls, consumption fees, data lock-in, and an executive quoted on agent-pricing upside.
If the campaign needs to argue that "the incumbent stack is a growing tax" and the sponsor can publish customer outcomes, these posts are closer to that argument than Libeau's readiness framing.
The tradeoff is who owns the argument and how it reads.
Blonski's replacement case is also Elementum AI's pitch, so a sponsor that is itself an enterprise suite may be buying criticism of its own category.
The posts are adversarial and formatting-heavy, which suits a demand-generation post more than an explanatory buyer asset.
Romain Libeau stays closer to what has to be true inside the buyer's own systems: clean supplier data, adoption, and reconciled workflows.
They are less bound to one vendor's product story.
Blonski also writes less about buyer-side readiness, so a sponsor selling implementation speed or data quality gets less usable material from the two posts than from Libeau's 17% ROI and Coupa cost posts.
Choose Beth Thorson when the buyer decision is about scaling a go-to-market motion rather than procurement software economics.
Read more
Thorson's posts cover the shift from founder-led selling to team-driven growth, the case for a supply-chain operating system that unifies data and automates execution, and the human side of adoption: AI and automation simplify workflows, but people still carry relationships, innovation, and retention.
A sponsor that needs a first-person operator voice gets a longer career anchor here: more than 30 years leading growth at major logistics companies, a firm Thorson founded, and a newly announced VP of Strategic Partnerships role at Auger.
Romain Libeau's product-economics posts do not offer that.
The tradeoff is topic overlap.
Thorson's posts do not touch procurement AI ROI, total cost of ownership, or vendor architecture, so a campaign built around "AI results stall without clean data and integrations" would have to be rebuilt around scaling, supply chain, or people.
The posts offer less inspectable evidence, with no cost tables or product-level close readings, and lean on announcement and advice framing.
A sponsor wanting numbers would lose the concrete detail Romain Libeau supplies.
Choose Arie Barendrecht when the campaign goal is field presence with procurement leaders rather than a written argument.
Read more
Barendrecht's posts sit inside the procurement software world at Omnea and read as event and audience work: a London summit with named procurement, finance, and operations leaders; a summary of how practical the AI conversation has become; and a framing of supplier spend as a $5 billion lever rather than a $10 million one.
The line—go after the spend you control and not just the cost of running your own function—is a usable campaign hook for a spend-management sponsor.
Barendrecht also writes to hiring, with an open call for sales engineers, account executives, and growth associates in New York.
The tradeoff is depth and reuse.
Both posts are largely event and recruitment updates, so they offer little close product or ROI reasoning a sponsor can turn into an article.
The spend-lever framing appears as a line quoted from another speaker rather than a developed argument.
Romain Libeau's posts carry a repeatable structure—a statistic, a rejected frame, a list of what AI cannot fix—that a content sponsor can build a series on.
Barendrecht fits event co-marketing, community access, and hiring-side messaging better than a written buyer asset.
Romain Libeau’s five complete LinkedIn posts cover procurement AI, software ROI, implementation and total cost of ownership, agent terminology, and the growth history of Pivot.
The posts do not say when they were published; titles and previews are not posts.
The title and description make no claims beyond the page’s overview, ideas, relationships, discovery and fit sections.
The posts here do not include earlier posts, other channels, engagement or audience data, biographical sources, or sponsorship terms.
Those gaps limit this profile to a starting set of documented topics rather than a full survey of Libeau’s public work.
Related creator comparisons help distinguish Libeau’s focus inside procurement software and buyer-side scrutiny, but they are not the subject of this profile.
