Matt Leta works on enterprise AI transformation, focusing on getting AI into real business workflows, measuring results, and building systems that combine people, models, and processes.
Matt Leta is useful for turning enterprise AI promises into practical workflow tests with finance validation and accountability.
A manufacturing operations consultancy executive briefing for operations, engineering and finance leaders.
Consumer electronics sponsored social posts paid against media kit, rate card and reach targets.
Check first: Confirm audience data from comparable briefings and whether sponsorship terms and inquiry route exist.
Matt Leta writes about making enterprise AI useful in real operations.
Leta turns broad AI promises into practical tests for operators: Can the workflow deliver value within weeks?
Matt Leta’s posts return to one central claim: enterprise AI succeeds when companies redesign real work, measure results, and build clear human oversight around changing models.
They favor short implementation cycles over long plans and urge leaders to test whether data, workflows, and decision ownership are ready.
Leta argues that AI projects should deliver a working result quickly, with a value measure Finance can verify.
Each cycle should earn the case for the next, rather than depend on a distant transformation plan.
Leta describes a 12-week project to ship and track work across 40 solar projects. The post reports more than 20,000 work hours reduced annually and says later three-month cycles built on the first project’s results.
In Leta’s view, an agent can make a broken process run faster without making it better.
They point leaders to workflow design, connected data, and the human effort required to check an agent’s output.
Leta describes a company whose CRM had not synced with its customer-experience platform for 11 months, warning that placing an agent over disconnected data does not fix the underlying plumbing. In another post, they say time spent checking an agent’s work can erase its time savings.
Leta asks who owns decisions, who reviews agent work, and who can stop an agent when something goes wrong.
They treat oversight as part of how a system operates, not a policy added after deployment.
Leta asks companies to name the person responsible for a “kill switch” if an agent goes wrong. They also describe assigning a senior expert to review agent work and tying part of a fee to value checked by the client’s finance team.
Leta argues that businesses should not rely on one employee’s judgment or lock themselves into one model provider.
The procedures, roles, and feedback around AI should let businesses change tools without losing control of their work.
Leta’s test: imagine the person behind an important weekly decision leaving, or the model being replaced.
Want a concrete example of how Leta moves from a broad transformation plan to a first working result?
This post follows Nextpower’s shipping-and-tracking workflow across 40 solar projects, then reports results from its first 12-week cycle.
Rather than map every workflow before starting, the example focuses on one high-friction task and puts a platform in the hands of logistics teams and customers.
For an executive briefing, this case shows how to select a focused starting workflow, define a result and decide what evidence should justify the next phase. The post reports the figures but does not independently verify them.
Wondering how to judge an AI agent beyond its apparent speed?
This post makes the time a person spends checking its work the central test, using a planner’s reorder or a buyer’s freight booking as examples.
Leta contrasts a one-hour task that takes six minutes to review with one that takes an hour to check: in the latter case, even a perfect agent saves no time.
A speaker session could use this test to help operations leaders identify tasks where agents may save time and where human review remains a bottleneck. Ask attendees to estimate task time and review time before discussing automation.
Considering an enterprise AI purchase?
This post explains how disconnected data can undermine an AI product, using the example of a company whose CRM had not synced with its customer-experience platform for 11 months.
The post links a vendor’s reported finding about disconnected business data to an example of a personalization contract.
Use this in a vendor-evaluation briefing: ask what data and workflow dependencies need fixing, who owns them, and whether the vendor’s diagnosis is independent of its proposed sale. Ask for evidence supporting the post’s figures and customer anecdote.
Looking for Leta’s broader view of how people and AI should work together?
This post argues against treating a single powerful model as the whole system and suggests testing whether an important decision still works when a person or model changes.
The post frames reliable AI as a combination of people, models and business-specific processes, including rules and feedback.
Use this test to open a discussion about decision ownership, documented procedures and model dependence. It helps executive audiences distinguish a model demonstration from an operating system the business can maintain.
Leta argues that AI work should start with a specific business workflow and produce a result Finance can verify.
They point to short delivery cycles, early working systems, and one measured outcome per cycle, rather than long strategy phases or adoption metrics. Examples include a manufacturer’s 12-week project and a solar-project logistics workflow.
Leta's posts turn the argument into a practical test: identify a workflow, measure its starting point, and ask whether the result is fast enough and valuable enough to fund the next step.
A speaker briefing could focus on how executives choose a first workflow, set a credible value baseline, and decide whether results justify the next cycle.
Leta warns that agents can accelerate a broken process instead of fixing it.
Their examples connect AI readiness to workflow design, usable operational data, and the human work required to check an agent’s output. They also apply this lens to CRM adoption and engineering workflows.
Leta makes broad claims concrete with diagnostic questions: Is data connected?
Useful for a session on operational readiness that helps leaders find process and data problems before approving an automation project.
Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5
Leta asks who owns AI decisions, who can stop an agent, and who checks its work.
They connect executive accountability to practical controls and describe human review as part of an agent system, not a separate afterthought.
Leta uses pointed questions and contrasts board-level responsibility with the controls and operating structures actually in place.
A suitable executive briefing could examine decision ownership, escalation paths, review responsibilities, and how governance should change before an organization scales agents.
Leta favors systems that coordinate people, models, processes, and feedback rather than relying on one model or a fixed vendor stack.
They argue that model choice will change quickly, so businesses should preserve the ability to switch tools and keep control of their own operating rules.
Leta tests resilience by asking whether a key decision would still be handled consistently if a person left or a model changed.
A technology strategy session could help leaders discuss vendor dependence, model switching costs, and which operating procedures need to remain specific to their business.
Leta comments on company announcements, investment, and market research, then redirects attention to what changes inside a business: workflows, decision speed, engineering work, costs, or accountability.
Examples include BMW’s management structure, Salesforce’s product direction, and investment in engineering-focused AI.
This approach could support an executive briefing that separates headline claims from the operational questions leaders need to answer. For a neutral, comprehensive review of each announcement, ask for that explicitly; these posts offer Leta’s interpretation.
Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5
Matt Leta describes building Future Works around enterprise AI projects delivered in short cycles and tied to measurable outcomes.
They also share a client example involving NextPower.
Owned business
Leta says they built Future Works as an operating system for AI transformation, using senior experts and AI agents in twelve-week cycles.
They describe the company’s approach as delivering working projects against value measures set with clients’ finance teams.
Client
Leta describes work with NextPower on shipping and tracking across photovoltaic projects.
They say the first cycle took twelve weeks and that the work continued in successive three-month cycles.
Matt Leta's posts are field notes on why enterprise AI programmes stall and what to do instead.
They take a headline — a vendor study, a funding round, a layoff announcement or a survey of CEOs — and ask what must change inside a real operation before the claim becomes true.
Both write from inside firms that build AI systems for enterprise clients, rather than advise them, and both ask whether a system can work for the people who use it.
Dosapati describes shipping inference infrastructure for AI companies and configuration, quoting and analytics tools for operators in healthcare, manufacturing, financial services and energy.
Dosapati focuses on what gets built and on helping founders turn stalled ideas into tested prototypes, with little attention to governance or how clients measure value. Leta, by contrast, writes about delivery cycles, finance-approved value baselines and who owns the kill switch: running a programme rather than building a first working product.
Blonski argues that enterprises cannot bolt AI onto a legacy software stack and that architecture, not adoption metrics, will decide the outcome.
They challenge Gartner's claim that domain-specialist agents from Salesforce, SAP and ServiceNow are the only secure route to autonomous operations, arguing that the technical reasons for domain-specific data models have gone. Leta makes a compatible point: an agent running on disconnected data does not fix the plumbing; it just moves faster through the same broken pipes.
Blonski argues as a vendor for replacing named legacy SaaS contracts, citing figures such as a 50 to 70 percent total cost of ownership reduction, and closely tracks industry analyst positions.
Holley builds posts much like Leta: opening with a specific scene inside a company, describing what went wrong, then closing with a question that helps leaders test their own situation.
Examples include a strategy review where sales, finance and operations each had a different definition of priority, and a weekly metrics review where a warning indicator went ignored for eleven weeks because it did not roll up to corporate. Both write for people responsible for operations and top-level decision-making.
Holley writes about lean manufacturing and executive alignment.
Of the two things a buyer needs — how many people the creator reaches and who they are — the posts here answer the first only partially and the second indirectly.
The only measured audience figure is a LinkedIn follower count: 17,128, observed 9 October 2026.
17,128
Matt Leta's LinkedIn account · 2026-10-09
Leta’s posts do not include a sponsorship package, media kit, rate card, branded-content terms or official partnership inquiry page.
They do describe how Leta’s firm, Future Works, structures paid client work: short delivery cycles, a named person accountable for each agent fleet and part of the fee tied to value the client’s own finance team verifies. Brands and agencies should ask whether sponsorship terms and an inquiry route are available.
Work is scoped and shipped in twelve-week cycles, with each cycle expected to pay for the next, rather than on a multi-year roadmap that promises results at the end. Matt Leta says most enterprise AI roadmaps run three to five years and argues for a shorter rhythm.
A third of the fee, Leta says, is tied to value the client’s own finance team verifies at the end of each cycle. The client sets the baseline, so buyers need an internal figure they are willing to stand behind.
Every fleet of agents has a named senior expert who reviews the work and signs off. Buyers should plan for one accountable counterpart, not a rotating delivery team.
Systems route by intent rather than locking to a single model provider, allowing clients to switch to the best model each month and keep the resulting savings. Buyers should ask what it would cost to leave a provider.
Leta says the firm builds trust through certifications, cybersecurity and conduct, as well as its delivery record. Buyers with procurement or security reviews should expect those steps to be part of the engagement.
A manufacturing operations consultancy wants Leta for a 60-minute executive briefing and Q&A for roughly 40 operations, engineering and finance leaders at mid-size manufacturers.
The topic: why AI programmes stall and what the first twelve weeks should look like.
A consumer electronics brand wants eight sponsored social posts over a quarter, paid against a media kit with a rate card, audience demographics, a discount code and reach targets.
The creator would front the product to a broad buyer audience.
Worked campaign angle for the manufacturing operations consultancy's executive briefing.
Working title: “Twelve weeks or three years: what actually decides whether AI pays for itself.”
Pre-read (one page, sent a week ahead): the three tests Leta uses—value appears in weeks, the finance team signs off on the number, and each cycle pays for the next.
Session outline, 60 minutes:
0–10 minutes — The gap.
10–25 minutes — The three tests, each with a manufacturing example: short cycles instead of a multi-year roadmap; one measurable outcome per cycle, with the client's finance team setting the value baseline; and accountability, including who checks the agent's work.
25–40 minutes — The review-time test and the kill switch.
40–50 minutes — Live exercise.
50–60 minutes — The next cycle.
Handout: the one-page three tests and the room's decision-latency counts.
Do not build the session around a neutral comparison of AI vendors or a general market review.
End with one question for the room: what would have to be true for your finance team to sign off on the next cycle? It leads directly into the consultancy's follow-up conversation.
If the consultancy needs a speaker to cover a builder's view of shipping AI systems — inference infrastructure, a quoting tool that collapses a multi-step manufacturer workflow into one dashboard, natural-language analytics for non-technical staff, and persistent engineering agents — Siva Dosapati's material is closer to an inside-the-build account.
The AI20 Labs posts describe work at both the infrastructure and enterprise ends, including a manufacturer's distributor network and an engineering organization. Choose Dosapati when the session needs a hands-on product and venture perspective rather than an operational field-note framing.
Leta's posts focus mainly on company and service promotion, with less sustained argument about why complex transformations stall than their other material.
If the briefing's centre of gravity is enterprise software cost and architecture — replacing legacy SaaS, cutting total cost of ownership, challenging vendor roadmaps such as Gartner's domain-specialist position, and linking AI-first systems to CIO and CFO priorities — David Blonski's material is more directly relevant.
The posts argue for a single AI-first system of record across ITSM, procurement, CRM and HRIS, cite 100,000-plus layoffs attributed to AI, and make the case for cutting the legacy SaaS stack. Choose Blonski when the client meeting is really about legacy platform renewal, software spend, or governance across enterprise systems.
The posts are positioned around Elementum AI, so the argument is tied to a vendor replacement thesis rather than neutral category analysis.
If the consultancy wants the room to confront why operational improvement and lean programmes fail before AI enters the picture — conflicting executive priorities, metrics reviews that change no decisions, and plant managers serving multiple masters — Daryl Holley's posts speak directly to that leadership failure.
The material is written from a lean and manufacturing leadership seat and gives the briefing a management-alignment frame that an AI-focused speaker can miss. Choose Holley when the executive briefing should start with operating discipline and decision rights, not with AI models or vendor choices.
Holley's posts contain no AI transformation material: no AI deployment, governance, agent, or model discussion.
Editable Markdown templates for planning a campaign with this creator.
