Alessio Tresanti writes and speaks about procurement technology, especially how autonomous systems could handle routine purchasing and give procurement teams more time for strategic work.
Most useful for explaining autonomous procurement and how routine purchasing could free procurement team capacity.
Best for
Procurement technology company running a thought leadership webinar on autonomous procurement and team capacity.
Not for
A paid product endorsement campaign with scripted demos, product claims, guaranteed pipeline, and published rate card.
Key takeaways
Automation handles stable, standard workflows; autonomous procurement responds and adapts to real-world situations.
Procurement teams do not lack strategy; they lack people free for thousands of small purchases.
Most procurement technology is the same product with an AI banner, they argue.
Check first: Confirm documented audience data on procurement roles and seniority, plus recent attendance or reach.
Main ideas
Automation follows the process; autonomous procurement adapts to the situation · Procurement's real constraint is capacity, not strategy · Most procurement technology is the same product with an AI banner
Alessio Tresanti writes and speaks about procurement technology, particularly the shift from software that assists people doing purchasing work to systems that can carry routine purchasing tasks through to completion.
Their posts connect that shift to a practical problem: small purchases consume procurement teams’ time while strategic work waits.
Their work is useful to follow for a clear account of why adding AI features to familiar tools may differ from changing who—or what—does the work.
Tresanti makes an abstract technology debate concrete by tracing what changes in a procurement process.
In their DPW Amsterdam post, they argue that many products still reflect the assumption that people do the work while software helps them see, route, clean, or store information.
They contrast that with systems that could find suppliers, obtain quotes, negotiate, apply policies, coordinate across teams, and place purchase orders, leaving people to handle exceptions and relationships.
Their Gartner conference posts give the argument a human consequence: routine purchases take up capacity and leave strategic work waiting.
A keynote summary offers a concise distinction—automation handles stable, standard workflows, while autonomous systems respond and adapt to real-world situations.
One short post urges procurement leaders to evolve but does not name the topic, so it adds little detail on its own.
Together, the fuller posts show their distinctive contribution: explaining autonomous procurement through both the work a system might take on and the organizational capacity that could free up.
Alessio Tresanti's public arguments circle one idea: procurement software is moving from helping people do the work to doing the work itself.
Read more
They call that shift autonomous procurement and contrast it with automation, which only fits stable, standard workflows.
The priority behind the argument is capacity — teams that know what they would do with more hours but have nobody to run the thousands of small purchases that fill the week.
They are skeptical that most vendor AI claims change anything, because the products were built on the assumption that a person does the work and software helps that person see, route, clean, or store it.
The constructive version is software that takes a request and finishes it, while people stay in charge of exceptions and relationships.
Automation follows the process; autonomous procurement adapts to the situation
Tresanti draws a line between two things that are often sold as one.
Read more
Automation works in stable, standard workflows.
What they call autonomous procurement responds and adapts to real-world scenarios—a different capability, not a better dashboard.
The distinction is their core definitional claim and the framing they use to explain how procurement organizations can scale beyond what their headcount allows.
Tresanti made the contrast the main takeaway of a keynote at Gartner's procurement conference in San Diego, reporting almost 2,000 attendees. At DPW Amsterdam, Rivio ran a session with customers titled Automation vs Autonomous Systems, described as the difference that matters for scaling a procurement organization.
Procurement's real constraint is capacity, not strategy
Tresanti argues that procurement teams do not lack a strategy: most know exactly what they would do with more hours.
Read more
The blocker is that nobody is free to run the thousands of small purchases that eat the week, so strategic work waits and tail spend goes unnegotiated year after year. They make capacity the practical case for autonomous purchasing.
Ahead of Gartner's first Procurement Conference in San Diego, Tresanti named capacity as the conversation most worth having and invited procurement leaders attending the event to reach out.
Most procurement technology is the same product with an AI banner
Reflecting on DPW Amsterdam, Tresanti described the noise in procurement tech as thick enough that a buyer cannot easily tell which vendors are worth a conversation.
Read more
They sorted nearly every vendor into seven familiar groups — vendor master data, spend analytics, contract lifecycle management, intake and orchestration, full source-to-pay suites, sourcing, and tail spend — plus a wave of startups building prompts.
Their pointed claim is that stripping away the AI branding leaves most products looking as they did five years ago: they were built on the assumption that a person does the work and software helps that person see, route, clean, or store it.
AI was added on top as a feature.
Tresanti lists the visible changes and treats them as real but shallow: intake forms that autofill themselves, a chatbot in the corner that summarizes a contract, a dashboard that writes its own caption.
The constructive half of Tresanti's argument is that the meaningful change is software taking a request and completing it: finding suppliers, getting quotes, negotiating, enforcing policies, orchestrating across teams, and placing the purchase order.
Read more
People stay in charge of what matters — exceptions and relationships.
They note this does not fit any of the seven vendor categories, because those categories describe what humans used to do, split into tools.
Ask Tresanti how people in procurement are expected to evolve beyond handling exceptions and relationships.
In the same post-event analysis, Tresanti contrasts a world where software helps a person see, route, clean, or store work with one where software finds the suppliers, negotiates, enforces the policies, orchestrates across teams, and places the order.
This is the clearest starting point for the question, “What does autonomous procurement mean beyond adding AI features?”
Read more
It shows how Tresanti frames the market and why familiar category labels obscure the real change.
Tresanti writes that they returned from DPW Amsterdam confused by the noise in procurement tech.
They sort most vendors into seven familiar categories: Vendor Master Data, Spend Analytics, CLM, Intake & Orchestration, Full S2P Suites, Sourcing and Tail Spend, alongside hundreds of startups building prompts.
The core argument: remove the AI banners and most products look much as they did five years ago, because they assume a person does the work while software helps them see, route, clean or store it.
The real shift, Tresanti says, is software that takes a request through to completion: finding suppliers, getting quotes, negotiating, enforcing policies, coordinating across teams and placing the purchase order.
People remain responsible for exceptions and relationships.
For brands planning a campaign
For a thought leadership webinar on autonomous procurement and team capacity, this post offers the sharpest contrast: AI as a feature layered onto human-run workflows versus a system that owns the work. It can frame the discussion around workflow ownership, exceptions and relationship management rather than vendor categories.
This answers the question, “How does Tresanti define automation versus autonomous procurement in a live talk?”
Read more
It gives the short version of the distinction developed in the fuller posts.
Tresanti reports an audience of almost 2,000 for a keynote at the Gartner procurement conference in San Diego.
The talk distinguishes automation from AI augmentation, which Tresanti calls autonomous procurement.
Automation works in stable, standard workflows; new autonomous systems respond and adapt to real-world scenarios.
For brands planning a campaign
Evidence that the automation-versus-autonomous framing has reached a large procurement audience. For a webinar, it offers a concise definition and an event-backed hook.
This answers the question, “Why should procurement leaders care about autonomous procurement?”
Read more
It names the practical problem plainly: capacity, small purchases and unnegotiated tail spend.
Tresanti says they will attend Gartner’s first Procurement Conference in San Diego with the Rivio team, and that capacity is the conversation they most want to have.
The post argues that procurement teams do not have a strategy problem: most know what they would do with more hours.
What they lack is someone to handle the thousands of small purchases that consume the week, leaving strategic work waiting and tail spend unnegotiated year after year.
Tresanti invites procurement leaders attending the event to reach out.
For brands planning a campaign
Directly supports a webinar brief on autonomous procurement and team capacity.
The post identifies a concrete pain point: routine purchases consume hours while strategic work waits.
That can shape the webinar’s problem statement and audience invitation.
This answers the question, “What live format does Tresanti use to explain autonomous systems to procurement teams?”
Read more
It shows the event-session model, collaborators and scaling angle.
Tresanti announces that Rivio will be in Amsterdam with Simone Bruni and Jacopo Gallucci at booth #58, and invites people to the Tech Safari: AI-Native Procurement session from 02:15 PM to 03:00 PM on Thursday, October 1. Run with customers, the session covers Automation vs Autonomous Systems and why the distinction matters for scaling a procurement organization.
For brands planning a campaign
Shows how Tresanti and Rivio use customer-backed event sessions to explain autonomous systems. For a webinar, it suggests a panel or customer-story format and shows how they present the automation-versus-autonomous message to procurement teams scaling their operations.
This answers the question, “How does Tresanti signal urgency for procurement teams?”
Read more
Open it after the fuller posts; the topic is not named in the text.
A short post calls a topic “super important” for procurement leaders and says teams will need to evolve for the coming wave. Ask for the topic and event details before using it to support a webinar.
For brands planning a campaign
Too thin to carry a webinar angle on its own. It can support a point about teams needing to evolve if the missing topic is named later, but the fuller DPW and capacity posts should lead.
Event-anchored formats and short reflective posts4
Automation versus autonomous procurement2
Capacity, not strategy, is procurement's constraint1
Procurement technology market noise and vendor categories1
Software that finishes the request1
Automation versus autonomous procurement
Tresanti returns repeatedly to one distinction: automation handles stable, standard workflows, while what they call autonomous procurement responds and adapts to real-world scenarios.
Read more
They used the contrast as the main takeaway of a Gartner procurement keynote in San Diego and again as the theme of a customer session at DPW Amsterdam, framed as the difference that matters for scaling a procurement organization.
Conference keynote framing plus a customer-facing session, rather than a written explainer or tutorial.
For brands planning a campaign
This is the clearest spine for a thought leadership webinar on autonomous procurement.
Ask Tresanti to open with the automation-versus-autonomous distinction and walk through where each belongs, so attendees leave with a decision rule rather than a product pitch.
Build the rest of the session around the capacity problem that distinction is meant to solve.
Capacity, not strategy, is procurement's constraint
Tresanti argues that procurement teams do not lack a strategy: they know what they would do with more hours.
Read more
The blocker, in their account, is that nobody is free to run the thousands of small purchases that fill the week, so strategic work waits and tail spend goes unnegotiated year after year. They named capacity as the conversation they most wanted to have at a procurement conference in San Diego.
For brands planning a campaign
This gives the webinar its problem statement in the buyer's own terms. A session can start from unnegotiated tail spend and the hours it consumes, then show how autonomous purchasing changes that picture, and invite attendees to bring their own examples of work that keeps getting deferred.
Procurement technology market noise and vendor categories
Reflecting on DPW Amsterdam, Tresanti said the noise in procurement technology makes it hard for a buyer to tell which vendors are worth a conversation.
Read more
They sorted almost every vendor into seven groups, from vendor master data and spend analytics to contract lifecycle management, intake and orchestration, full source-to-pay suites, sourcing, and tail spend, plus startups building prompts. Their more pointed claim is that stripping away the AI banners leaves most products looking as they did five years ago, because AI was added as a feature on the older assumption that a person does the work and software helps that person see, route, clean, or store it.
Public post-event analysis written for a vendor-side audience, combining a category map with an argument about why products have not changed more.
The same post preserves the outside view Tresanti is arguing against: intake forms that autofill, a chatbot that summarizes a contract, a dashboard that writes its own caption. They treat those as real but superficial changes, a position a partner would have to answer.
For brands planning a campaign
A brand entering the webinar should expect this skepticism and meet it directly.
Position autonomous execution, not an AI badge on an existing workflow tool, and be ready for the question of which of the seven categories Tresanti describes you are claiming to replace or connect.
The category map is also a useful segmenting device for the invitation and the landing copy.
Tresanti's constructive claim is that the real shift is software taking a request and finishing it: finding suppliers, getting quotes, negotiating, enforcing policy, orchestrating across teams, and placing the purchase order.
Read more
People stay in charge of exceptions and relationships. They note this does not fit any of the seven vendor categories, because those categories describe what humans used to do, split into tools.
For brands planning a campaign
This is the natural webinar payoff and the part that can be made concrete with the brand's own product story. Ask for one end-to-end example, from request to purchase order, with the human exception path shown alongside it, so the session demonstrates the claim instead of asserting it.
Tresanti's public material is largely event-driven: keynote takeaways, booth and session invitations, and short posts telling procurement leaders which conversation to follow.
Read more
The posts are concise and argument-first, and the customer panel at DPW Amsterdam put them on stage with buyers rather than speaking only as a vendor.
A recurring pattern across Tresanti's posts rather than a single stated preference.
For brands planning a campaign
Tresanti is a fit for event-anchored formats: a webinar tied to a conference moment, or a session staged with a customer alongside them, will match how they already appear in public. Plan for a tight, argument-led narrative rather than a long written asset, and expect the strongest material to be conversational.
The posts center on Rivio, a procurement technology company Tresanti represents at industry events and speaks about on stage.
Read more
They describe the relationship as a partnership but don't specify whether Tresanti is an employee, owner, or commercial partner; ask for clarification. Gartner and DPW Amsterdam appear as conferences Tresanti attended or spoke at, not as brands they work for.
Rivio
Disclosed partnership
Tresanti appears at procurement events as part of the Rivio team and speaks about Rivio's approach.
Read more
Posts say they will be in Amsterdam with Rivio's team at booth #58 for a "Tech Safari: AI-Native Procurement," that Rivio will be at Gartner's first Procurement Conference in San Diego, and close a keynote post about autonomous procurement with the company name. Ask whether their relationship with Rivio is employment, ownership, or another arrangement.
Tresanti attended Gartner's first Procurement Conference in San Diego and describes a keynote there with almost 2,000 attendees on the difference between automation and AI augmentation.
Tresanti wrote a vendor-side analysis of DPW Amsterdam, sorting the procurement technology vendors seen there into seven categories and arguing that AI has so far been layered onto tools built around people doing the work.
Alessio Tresanti writes about procurement technology, with one argument running through their posts: software is moving from helping people do the work to doing the work itself.
Read more
They call that shift autonomous procurement and contrast it with automation, which fits stable, standard workflows.
Start with the DPW Amsterdam takeaway post on vendor categories and software that finishes the request, then read the Gartner keynote reflection on automation versus autonomous systems.
Conference and customer-session posts offer other entry points.
For adjacent perspectives, Sarah Toomey, Sameer Syed, CPA, and James Meads approach nearby subjects from operator, finance, and advisory angles.
Toomey works in sourcing and procurement, writing about AI-native source-to-pay and the friction of buying AI in the enterprise.
Read more
That overlaps with Tresanti's focus on autonomous procurement and the gap between AI branding and actual workflow change.
Toomey speaks from an operator and platform-leadership position at Levelpath, writing about a specific product launch and the day-to-day sourcing problem. Tresanti's posts focus more often on vendor-side market commentary and conference framing, mapping the wider vendor landscape rather than introducing one platform.
Syed writes about making AI change how work gets done rather than bolting it onto legacy processes, and describes AI deployment across procurement, finance, and accounting workflows.
Read more
That theme is close to Tresanti's argument that software should finish the request instead of helping a person process it.
Syed's vantage point is finance and accounting leadership inside Zip, with concrete internal examples such as month-end close skills and accrual automation. Tresanti looks outward from the procurement technology market, using conference takeaways and vendor categories rather than a finance team's implementation story.
Meads works in procurement technology, evaluates software, and asks where AI should be given authority and where a human should stay in the loop.
Read more
That question sits directly alongside Tresanti's distinction between automation and autonomous procurement.
Meads focuses more on advisory work and startup growth, writing about procurement technology targeting, sales, and open questions for procurement leaders. Tresanti advances a market thesis about autonomous procurement and vendor categories, primarily through conference keynotes and customer sessions.
For a webinar on autonomous procurement and team capacity, Alessio Tresanti’s LinkedIn posts are relevant: they discuss procurement automation, autonomous systems, and the time routine purchasing takes from procurement teams.
Read more
Their LinkedIn account showed 9,022 followers on October 7, 2026. Before booking, ask for documented audience data on procurement roles and seniority, plus recent attendance or reach for comparable procurement topics and formats.
The posts show no sponsorship or partnership offer from Alessio Tresanti.
Read more
They document conference activity: they appeared at Gartner's procurement conference in San Diego and at DPW Amsterdam as part of the Rivio team, speaking about autonomous procurement and team capacity, and endorsing a procurement-leaders conversation.
Posts name and tag Rivio colleagues, indicating an affiliation rather than a paid partnership programme.
No published sponsor policy, rate card, media kit, format list, or sponsorship inquiry route appears in the posts.
For a buyer planning a webinar partnership, ask directly about deliverables, disclosure practice, lead times, and the contact channel before committing budget.
A procurement technology company wants to run a thought leadership webinar on autonomous procurement and its impact on team capacity, and Tresanti is a strong fit for that brief.
Read more
This is not a subject they would be learning for the session; it is an argument they already make in public.
Their clearest distinction is that automation handles stable, standard workflows, while what they call autonomous procurement responds and adapts to real-world scenarios.
They used that contrast as the main takeaway of a Gartner procurement keynote in San Diego and again as the theme of a customer session at DPW Amsterdam, framed around scaling a procurement organization.
They also supply the problem statement a webinar needs, in the buyer’s own terms: procurement teams do not lack a strategy; they lack anyone free to run the thousands of small purchases that fill the week, so strategic work waits and tail spend goes unnegotiated year after year.
Capacity is the conversation they said they most wanted to have with procurement leaders at that conference.
The format matches how they already appear in public.
Their posts are event-anchored and argument-first, and the DPW session put them on stage with customers rather than speaking alone as a vendor—a ready-made model for a customer-backed webinar rather than a lecture.
Their DPW write-up also sorts almost every procurement vendor into seven groups, from vendor master data and spend analytics through contract lifecycle management, intake and orchestration, full source-to-pay suites, sourcing, tail spend, and startups building prompts.
That map can help segment the invitation and landing copy, and tells the host brand which question it will have to answer on stage.
The reservation is audience evidence, not topic fit.
The only available audience figure is a LinkedIn follower count of 9,022, observed on October 7, 2026; it describes account size, not who follows or how many people a webinar would reach.
Before committing, ask for procurement roles and seniority from an audience survey or another documented source, plus attendance figures for a comparable procurement session.
When to choose a specialist
A materially different need would be a paid product endorsement campaign: a vendor asking Tresanti to front a scripted demo, make specific product claims on camera, and deliver guaranteed pipeline, with the deal priced from a published rate card and supported by a documented history of disclosed sponsored placements.
Read more
Their posts provide no basis for pricing the work, establishing how disclosure would be handled, or assessing a history of paid placements: they include no sponsor policy, rate card, media kit, format list, disclosed sponsorship example, or inquiry route.
The second problem is positioning.
The same DPW post that makes them valuable on stage also makes them difficult to script: they argue that stripping away the AI banners leaves most procurement products looking the same as they did five years ago, because AI was added on top of the older assumption that a person does the work while software helps that person see, route, clean or store it.
Asking them to praise a product on the strength of its AI features would put them in direct contradiction with their published position—and the credibility the brand is paying for is the credibility of that argument.
The third problem is format.
Their public output is short, argument-led posts and live event sessions, sometimes with customers alongside them, not produced promotional assets.
A scripted endorsement campaign asks them to work against their natural register.
Finally, the only available audience number is a follower count of 9,022, observed on October 7, 2026, with no measured breakdown of procurement roles or seniority.
Account size does not establish who would see a sponsored message or act on it.
Before spending budget, settle commercial terms, disclosure practice, and audience composition directly with Tresanti; expect a refusal or a counter-proposal on format.
A worked campaign example
A worked angle for the good-fit brief: a 45-minute live session titled around the capacity gap, not the host’s product, with Tresanti making the argument and a customer supplying the proof.
Open with five minutes on the automation-versus-autonomous distinction, in the same short form they use elsewhere: automation runs stable, standard workflows; autonomous systems respond and adapt to real-world scenarios.
Spend the next ten minutes on the capacity problem in attendees’ own language: teams know what they would do with more hours, but nobody is free to run the thousands of small purchases that eat the week.
Then invite attendees to name one repeated purchase their team keeps deferring.
Give ten minutes to the difficult question they raised publicly after DPW Amsterdam: most tools look unchanged once the AI banners come down.
Let them ask the host brand which of the seven vendor categories it is changing and how; a session that asks this on stage is more useful than one that avoids it.
Reserve fifteen minutes for a single end-to-end example, from request to purchase order, covering the steps they describe: finding suppliers, getting quotes, negotiating, enforcing policy, orchestrating across teams, and placing the order.
Show the human exception path and relationship handoff alongside the automation rather than editing them out.
Close with five minutes on what a procurement team should change first.
Support assets should follow the same register: a short pre-event post, one idea per post, argument first, and invitation copy that lets recipients self-identify against the seven categories rather than a generic AI pitch.
Before booking, ask for documented audience roles and seniority and attendance figures for a comparable procurement session; settle the commercial terms and disclosure wording for any partner placement; and test whether the host’s product can withstand being asked which category it belongs to.
Attendees should leave able to state the automation-versus-autonomous distinction, name one category of deferred purchase on their own team, and describe the exception path in the demonstration.
Choose Sarah Toomey when the webinar needs an operator's view of autonomous procurement rather than a conference-stage framing.
Read more
Toomey's posts say they fell into sourcing more than fifteen years ago, built and ran procurement functions across tech, and now oversee procurement inside the finance team at Levelpath, which introduced an autonomous source-to-pay platform in a post dated 10 September 2026.
Their account of the launch describes routing requests, pulling supplier and contract data, checking policy, and moving work toward a decision autonomously.
The human work left over, they say, is relationships, negotiations, and judgment calls.
For a buyer whose session has to answer "what does my team actually stop doing," Toomey can describe internal rework, not just the product idea.
Their July 2026 post adds another thread for a webinar about autonomous procurement: buying AI is often the slowest and most expensive enterprise purchase, and the teams pulling ahead are building visibility to keep pace with the business while still knowing what they signed up for.
That speaks directly to capacity, explaining why adding reviews and stakeholders lengthens the cycle even when the technology works.
Toomey's public record here is thin and narrowly vendor-tied.
Only two saved posts are available, neither an event keynote nor a customer session, so there's little evidence of how Toomey performs in front of a large procurement audience.
The autonomous source-to-pay platform discussed is a competing product, and the argument is tied to that employer: a different vendor hosting the webinar would ask Toomey to make its case from a rival's platform.
Tresanti has a visibly event-anchored record and a named distinction between automation and autonomous procurement used on a keynote stage.
Toomey offers the operator's detail, but not the same stage history or independence from a competing suite.
Choose Sameer Syed when the webinar audience includes finance and accounting leaders alongside procurement, and the point to land is what autonomy does to controls, close cycles, and audit trails.
Read more
In two posts, one from June 2026 and one from September 2026, Syed describes seven months as chief accounting officer at Zip, a rearchitected internal workflow, named colleagues' automations, and an accrual automation launch.
It generates journal entries from purchase data already in the system and posts them to the ERP, with a human in the loop and a full audit trail on every calculation.
The same post says the organization expects more than forty AI use cases deployed by year end and describes deploying Zip's capabilities across procurement workflows.
For a webinar about autonomous procurement and team capacity, this offers a counterpart to a procurement-only session: automation's capacity gains show up as shorter closes and fewer manual accrual workbooks, while the governance question of where a human stays in the loop is answered from the control side rather than the sourcing side.
That pairing suits a session meant to convince a joint procurement-and-finance buying committee rather than procurement alone.
Syed's center of gravity is accounting and finance, not sourcing or category work, so a session on procurement team capacity would come from the finance seat and could leave procurement audiences without the operator detail they came for.
The two saved posts are internal-rollout accounts tied to one employer.
With no public event, keynote, or customer-session history, it's hard to assess how Syed holds a room or how a procurement-specific claim would land; ask for relevant speaking examples.
Tresanti's published position is squarely on procurement technology and the automation-versus-autonomous distinction, used on a conference stage and in a customer session.
Syed brings credibility on controls and close, but the session would need reframing around finance workflows to play to that strength.
Choose James Meads when the webinar needs someone who already spends the hour interrogating procurement software and can put the awkward question to the host on stage.
Read more
The saved posts show Meads working in procurement technology, researching and evaluating different types of procurement software, and speaking with procurement leaders at conferences and events about what AI should decide and where a human stays in the loop.
They describe agentic AI moving software from supporting the work to performing parts of it, and frame the opportunity around where value comes from, which workflows can safely become agentic, how governance and decision rights should work, and what capabilities organizations will need.
Meads also ran a panel webinar on AI-native procurement in October 2026, so the format is proven.
A separate post shows them considering how buyer targeting, ideal-customer clarity, and sales-team competence determine whether a lead converts.
For a session built on "which category is your product changing, and how," Meads is the better chair: someone who understands the buyer's task can press the supplier and draw out specifics.
Meads reads as an independent evaluator and commentator more than a practitioner running procurement, so a session about first-hand team capacity would have less lived detail than Tresanti's operator-facing conference material.
The public record also points in a competing direction: the panel webinar is with a named procurement platform, and the commentary is about how vendors sell, not a host brand's own product.
A sponsor hoping for a clean endorsement would get questions instead.
Tresanti already carries the automation-versus-autonomous distinction as a signature argument, whereas Meads brings the questioning and market read.
If the campaign needs a named thought-leadership voice rather than a moderator, Tresanti remains the closer fit.
Alessio Tresanti's LinkedIn posts here include five full texts: a reflection on a Gartner procurement conference keynote, a preview of the same event focused on team capacity, a DPW Amsterdam vendor write-up, an announcement of a Rivio customer session on automation versus autonomous systems, and one brief post about procurement teams needing to evolve.
The posts carry no publication dates, so no sequence or change over time is claimed.
The posts here include no transcripts, articles, longer written work, or event recordings, and do not identify signature books, shows, or earlier career roles, which remain open gaps for anyone searching the name.
Audience information is limited to a LinkedIn follower count of 9,022 observed October 7, 2026, which describes account size rather than who follows or acts.
The similar-creator comparisons draw on posts dated from July to September 2026.
The claims here are limited to these posts; where they do not say, such as the exact nature of the Rivio relationship or any sponsorship, rate card, or disclosure practice, this profile says so rather than assuming.