Every company will have a Head of AI within 24 months.
> A $90m national nonprofit engaged an AI transformation partner to automate its back-office finance operations with custom agents. They're using finance as a pilot, with plans to expand into events and campaigns if successful.
> An elementary and high school are exploring custom AI modules to better serve students through more personalized learning and support (may or may not be powered by our team).
> A 1,500-person logistics company with a large internal engineering team has spent the last 18 months transitioning from software-first to AI-first. They have 4 people dedicated to AI transformation, are building MCP servers to connect their existing systems, and are even reconsidering software they built just 12–18 months ago.
> Over the last 6 weeks, we've spoken with a few dozen mid-market and enterprise companies scoping larger AI transformations, starting with custom agents to automate repeatable work across departments.
What's becoming clear is that this isn't something companies can delegate to an employee who happens to be good with ChatGPT. Someone needs to own the roadmap, understand the workflows, decide what gets built versus bought, and oversee deployments across the organization.
It's a matter of a couple of years before every organization either has its own internal AI team or engages a third party to act as one.
1
2
269
A meaningful portion of the custom AI workflows being sold to enterprises today will become obsolete long before the contracts they're attached to expire. Enterprises are being deceived by their vendors.
We recently had a conversation with a distributor of outdoor winter apparel about improving their procurement process. It's a highly seasonal business, where purchasing decisions depend on historical sales, fashion trends, inventory levels, supplier lead times, and, perhaps most importantly, the weather.
A colder winter generally means stronger demand. A warmer winter can leave the business holding substantial amounts of seasonal inventory that eventually needs to be liquidated at a discount. And because purchasing decisions are made well ahead of the season, the business is effectively committing capital against a forecast that may prove incorrect months later.
We discussed building a procurement agent that could incorporate these variables, continuously reassess demand projections, and help the team make better purchasing decisions.
The potential economic value was straightforward: fewer avoidable stockouts, less excess inventory, and reduced end-of-season liquidation.
But something else happened during the conversation that I found considerably more interesting.
_
The operator had recently connected their legacy ERP to ChatGPT, giving him the ability to retrieve and analyze information that previously required navigating an outdated system or asking someone on his team to prepare a report.
That relatively simple change opened up an entirely new set of possibilities in his mind.
As we discussed procurement, he began identifying other workflows across the business that could potentially be automated. Some were interesting opportunities for custom development. Others were tasks that existing AI tools could already handle reasonably well. And a few were capabilities that I suspect will become standard features of general-purpose AI products within the next several months.
This creates an interesting problem for enterprises investing in AI transformation.
> The market is moving quickly enough that the useful life of certain custom implementations may be considerably shorter than the procurement cycles and multiyear contracts through which they're being sold.
> A workflow that requires custom engineering today might be available through a standard model subscription six months from now. That doesn't necessarily make the original implementation a bad investment. If it creates sufficient economic value during that period, the investment can still be justified.
> But it changes the calculation considerably. I think enterprise AI investments increasingly need to be evaluated across three categories:
1. Build: Workflows that are sufficiently specific to the business, require meaningful integration across systems, and create enough economic value to justify custom development and ongoing maintenance.
2. Buy: Capabilities that existing software providers already deliver effectively, where custom development would add complexity without a corresponding economic advantage.
3. Wait: Capabilities that aren't yet reliable or readily available, but are likely to become commoditized quickly enough that the expected benefit of building them today doesn't justify the investment.
The third category is particularly important because it requires an implementation partner to occasionally recommend doing nothing. And that's not always an easy recommendation to make when your business earns revenue from implementations.
6
12
1,077
In conversation, an AI leader mentioned that “AI implementation in the enterprise, as a service” is a short-lived commercial opportunity.
(Respectfully disagree)
That would only be true if every single enterprise builds an in-house AI team. Nothing to do with how good the models (more precisely, the ease of building workflows) of the big labs become.
The question we’re all looking to get an answer to, regarding enterprise software: do we BUILD / BUY / WAIT?
Here’s what chatGPT has to say:
Grateful for all the new eyeballs on my content over the last 48 hours. Figured I'd share a bit about myself and my story:
> Born and raised in Montreal. Moved to NYC for university, where I majored in accounting.
> 3 years later, graduated with a double major (accounting & strategy), and the day after graduation, decided I didn't want to be an accountant. Took a complete 180 and did the next logical thing...
> Started reaching out to founders who had exited their companies, pitching them on this thing called “personal branding” (which, ~4 years ago, most had never really heard of!).
> Landed my first client through one of my very first outbound messages, the day after I graduated. Started freelancing as a ghostwriter.
> Went all-in. Spent 4 months serving a handful of clients myself, until I decided to bring on my first teammate (who's still with us today!) and gave the company a name: Notice Me(dia).
> Went on to serve 200+ executives, including leaders at some of the world's fastest-growing companies. Expanded our offerings, built an incredible team, and grew the agency to 7 figures in annual revenue.
> Throughout, I was fortunate to syndicate venture investments, invest directly in companies we'd worked with, and make lifelong friends with some of the coolest founders. We were essentially their fractional storytelling team, getting a front-row seat to how they hired, fundraised, sold, and built their businesses.
> Eventually decided it was time to take a shot at solving a completely different problem.
> September 1, 2026: Stepped away from my full-time CEO role at our content businesses (which are still running and growing faster than ever!).
> Raised a friends-and-family round, hired two of the smartest engineers I know, and got to work on what we’re building.
> Our first product used AI to analyze company spending and usage patterns, helping finance teams identify opportunities to save money.
> October 20: Made another 180. The more mid-market and enterprise companies we spoke with, the more we realized that the bigger opportunity was helping them implement AI across their operations, building custom agents around how their businesses actually work.
> Brought on our first cohort of businesses, started deploying agents, and are already planning expansions with several of them.
> Started sharing anecdotes, observations, and lessons from these conversations here on X. It's been hugely beneficial so far, both for meeting interesting people and challenging how I think about what we're building.
> Our vision has since expanded into building, operating, and securing the technology that runs an enterprise.
Still at the very beginning of this next chapter.
If you're new here, introduce yourself. Would love to meet more of you!
13
22
877
There's a lot of confusion among enterprise buyers right now about what AI software is actually worth paying for.
They don't know (a) which vendors to trust, (b) which products will still be relevant a year from now, or (c) whether they should be building these capabilities internally instead.
And the signals they historically relied on aren't particularly helpful. A company raising hundreds of millions of dollars tells you very little about whether its product will deliver value in your business.
We're seeing more companies hesitate to make decisions, even when they're convinced of what AI could do for them. There's a real fear of committing to the wrong solution in a market where the definition of a good solution keeps changing.
What to do?
Continuing on this point, enterprises are beginning to deploy custom AI agents across their organizations. The obvious Q then becomes: who's responsible for taking care of them, once deployed? Some thoughts:
An agent that works perfectly today could break tomorrow because an ERP changes its API, a supplier changes its invoice format, or an employee modifies an approval process. And unlike traditional software, an agent can continue operating while making mistakes. It might process 500 transactions incorrectly before anyone realizes something has changed.
We're moving toward a world where companies have dozens, eventually hundreds, of agents operating across finance, operations, sales, and other departments.
Someone needs to monitor their decisions, investigate failures, manage permissions, update integrations, and make sure they're still producing the intended outcomes. We've spent decades building an entire industry around managing enterprise IT infrastructure.
I suspect we're about to see something similar emerge around managing AI agents. We have managed IT, cyber, now we’ve been chewing on something called ‘Managed AI’. The opportunity may be just as large in keeping agents running reliably as in building them in the first place.
So to answer the Q:
(A) Either the company themselves (/their internal AI team),
(B) Or, their designated third-party, managed AI team.
Thoughts?
I've been thinking about what happens to enterprise SaaS over the next few years. A few scenarios:
1. SaaS companies become the infrastructure for their own replacements.
The optimistic scenario for incumbents is that they expose their products through APIs and MCP servers, allowing agents to operate their software on behalf of employees. But there's an interesting risk here: once the agent becomes the interface, the customer no longer needs much of what made the application valuable in the first place.
The vendor retains the database and transaction engine, while the agent owns the workflow and user relationship. That's a very different position to negotiate pricing from.
2. Enterprises realize they've spent decades adapting themselves to software that was never built for them.
Historically, buying an imperfect SaaS product was still cheaper than building and maintaining a custom one. That assumption is becoming less reliable. If a company can retain a handful of engineers to build applications around its actual processes, the economics of paying seven figures annually for software that requires endless workarounds start looking questionable. Especially when much of the functionality is only used by a fraction of the employees paying for seats.
3. The best SaaS businesses may become the worst businesses to sell AI to.
If an incumbent automates 80% of the work its customers perform inside its product, it could destroy a substantial portion of its own seat revenue. The customer wants fewer people doing the work. The vendor wants more people paying to access the software. That creates a genuine incentive problem. Some incumbents will successfully move to usage or outcome-based pricing. Others may be financially better off slowing down the very automation their customers want.
4. The cost of building software falls, but the cost of owning it becomes the deciding factor.
Generating an application is becoming cheap. Keeping it secure, integrating it with changing systems, maintaining permissions, handling exceptions, and supporting it for years is another matter. This could produce a strange outcome: companies build far more software internally, only to discover that maintaining hundreds of custom applications creates a new kind of technical debt. The winners may be the companies that figure out how to make custom software disposable rather than permanent.
5. Enterprise software stops being sold primarily to the people who use it.
Today, a large part of enterprise software distribution depends on convincing employees and department heads that a product will improve how they work. But if agents increasingly choose which tools to call, where to retrieve information, and how to execute tasks, the buying criteria change. Interface quality, onboarding, and user experience become less important for certain categories. Reliability, permissions, interoperability, and cost per completed task become much more important. Some products with terrible interfaces but excellent underlying infrastructure could become more competitive, not less.
_
A company could keep its core systems, replace much of the software employees interact with, build its own workflows, and reduce its seat count dramatically.
And the software vendors could find themselves processing more transactions than ever while capturing less revenue per customer. That's the tension I find most interesting: AI could make enterprise software more useful while making large parts of the enterprise SaaS business model less valuable.
12
32
2,877
Enterprise buyers are being asked to make multiyear commitments to AI products whose capabilities could be commoditized within months.
Funding rounds, impressive demos, and customer logos don't tell you whether a product will remain differentiated. It's becoming increasingly difficult to distinguish a durable software business from a feature that hasn't reached the foundation models yet.
Buyers are genuinely scared about this.
3
2
2,022
Vertical SaaS has historically been attractive because every industry has unique workflows that horizontal software doesn't handle particularly well.
But what happens when building software around those workflows becomes dramatically cheaper?
A distributor, manufacturer, or logistics company might have spent years looking for software that accommodates its specific processes.
Now it can potentially build agents directly on top of its ERP, without buying another application.
The irony is that the more specialized a workflow is, the more attractive custom development could become.
Particularly when the software vendor is charging a premium precisely because there aren't many alternatives.
_
We experienced some of this firsthand at our stealth co.
Our first product analyzed company spending alongside software usage and other operational data to identify opportunities to save money.
The more we tried to make it work horizontally across industries and company sizes, the more we realized how differently businesses operate, even when they're trying to solve what looks like the same problem. We eventually pivoted from building one product for thousands of companies to building custom AI workflows around how each company actually operates.
It's an interesting position to arrive at after a month month trying to build the exact opposite.
I've been thinking about what happens to enterprise SaaS over the next few years. A few scenarios:
1. SaaS companies become the infrastructure for their own replacements.
The optimistic scenario for incumbents is that they expose their products through APIs and MCP servers, allowing agents to operate their software on behalf of employees. But there's an interesting risk here: once the agent becomes the interface, the customer no longer needs much of what made the application valuable in the first place.
The vendor retains the database and transaction engine, while the agent owns the workflow and user relationship. That's a very different position to negotiate pricing from.
2. Enterprises realize they've spent decades adapting themselves to software that was never built for them.
Historically, buying an imperfect SaaS product was still cheaper than building and maintaining a custom one. That assumption is becoming less reliable. If a company can retain a handful of engineers to build applications around its actual processes, the economics of paying seven figures annually for software that requires endless workarounds start looking questionable. Especially when much of the functionality is only used by a fraction of the employees paying for seats.
3. The best SaaS businesses may become the worst businesses to sell AI to.
If an incumbent automates 80% of the work its customers perform inside its product, it could destroy a substantial portion of its own seat revenue. The customer wants fewer people doing the work. The vendor wants more people paying to access the software. That creates a genuine incentive problem. Some incumbents will successfully move to usage or outcome-based pricing. Others may be financially better off slowing down the very automation their customers want.
4. The cost of building software falls, but the cost of owning it becomes the deciding factor.
Generating an application is becoming cheap. Keeping it secure, integrating it with changing systems, maintaining permissions, handling exceptions, and supporting it for years is another matter. This could produce a strange outcome: companies build far more software internally, only to discover that maintaining hundreds of custom applications creates a new kind of technical debt. The winners may be the companies that figure out how to make custom software disposable rather than permanent.
5. Enterprise software stops being sold primarily to the people who use it.
Today, a large part of enterprise software distribution depends on convincing employees and department heads that a product will improve how they work. But if agents increasingly choose which tools to call, where to retrieve information, and how to execute tasks, the buying criteria change. Interface quality, onboarding, and user experience become less important for certain categories. Reliability, permissions, interoperability, and cost per completed task become much more important. Some products with terrible interfaces but excellent underlying infrastructure could become more competitive, not less.
_
A company could keep its core systems, replace much of the software employees interact with, build its own workflows, and reduce its seat count dramatically.
And the software vendors could find themselves processing more transactions than ever while capturing less revenue per customer. That's the tension I find most interesting: AI could make enterprise software more useful while making large parts of the enterprise SaaS business model less valuable.
No, enterprises are NOT vibe coding each SaaS tool they’ve procured. BUT, before (1) every renewal, and (2) every new proposal they’re reviewing, one of the very first Qs theirs teams are asking internally is: how much time and capital would it take to build something like this, custom for us?
The biggest benefits of spending 3 years out of college building a personal branding agency for executives (which is still running and growing faster than ever):
1. Most importantly, learned how to serve. How to listen, understand what someone needs, and consistently deliver beyond expectations.
2. Got a front-row seat to how exceptional executives hire, fundraise, negotiate, and creatively close some of the biggest logos on earth. We were essentially their fractional storytelling team. Imagine the stories we pulled out of the vault.
3. Built relationships with people I otherwise would've had no business being in a room with. And learned that access means very little unless you actually have something valuable to contribute.
The monetary component was the least important of all that came from the experience …
Hill I'm willing to die on:
Agencies are great for getting your first $250k liquid in the bank and thats about it...
(Yes regardless of what they $100m/mo online gurus tell you, $250k is A LOT of money to go bootstrap a Saas and Ecom brand)
After you do this you should instantly begin pivoting to a business model that is more scaleable, ideally 1000+ customers.
Saas is great because you can scale to thousands of monthly recurring customers with low startup costs if you whitelabel or do something simple that serves a deep need within a unsophisticated industry.
Ecom is great because you can serve millions of customers as long as your fulfilment is dialled in.
Agencies are only good for:
1. Getting marketing & sales skills.
2. Build your business acumen.
3. Putting enough liquid cash in the bank to go do something seriously BIG.
Obviously there are outliers, but I've met way more happy & healthy Saas and Ecom guys than agency owners in the past 2 years.
At some point you have to see the truth in why that is.
1
5
439
I've been thinking about what happens to enterprise SaaS over the next few years. A few scenarios:
1. SaaS companies become the infrastructure for their own replacements.
The optimistic scenario for incumbents is that they expose their products through APIs and MCP servers, allowing agents to operate their software on behalf of employees. But there's an interesting risk here: once the agent becomes the interface, the customer no longer needs much of what made the application valuable in the first place.
The vendor retains the database and transaction engine, while the agent owns the workflow and user relationship. That's a very different position to negotiate pricing from.
2. Enterprises realize they've spent decades adapting themselves to software that was never built for them.
Historically, buying an imperfect SaaS product was still cheaper than building and maintaining a custom one. That assumption is becoming less reliable. If a company can retain a handful of engineers to build applications around its actual processes, the economics of paying seven figures annually for software that requires endless workarounds start looking questionable. Especially when much of the functionality is only used by a fraction of the employees paying for seats.
3. The best SaaS businesses may become the worst businesses to sell AI to.
If an incumbent automates 80% of the work its customers perform inside its product, it could destroy a substantial portion of its own seat revenue. The customer wants fewer people doing the work. The vendor wants more people paying to access the software. That creates a genuine incentive problem. Some incumbents will successfully move to usage or outcome-based pricing. Others may be financially better off slowing down the very automation their customers want.
4. The cost of building software falls, but the cost of owning it becomes the deciding factor.
Generating an application is becoming cheap. Keeping it secure, integrating it with changing systems, maintaining permissions, handling exceptions, and supporting it for years is another matter. This could produce a strange outcome: companies build far more software internally, only to discover that maintaining hundreds of custom applications creates a new kind of technical debt. The winners may be the companies that figure out how to make custom software disposable rather than permanent.
5. Enterprise software stops being sold primarily to the people who use it.
Today, a large part of enterprise software distribution depends on convincing employees and department heads that a product will improve how they work. But if agents increasingly choose which tools to call, where to retrieve information, and how to execute tasks, the buying criteria change. Interface quality, onboarding, and user experience become less important for certain categories. Reliability, permissions, interoperability, and cost per completed task become much more important. Some products with terrible interfaces but excellent underlying infrastructure could become more competitive, not less.
_
A company could keep its core systems, replace much of the software employees interact with, build its own workflows, and reduce its seat count dramatically.
And the software vendors could find themselves processing more transactions than ever while capturing less revenue per customer. That's the tension I find most interesting: AI could make enterprise software more useful while making large parts of the enterprise SaaS business model less valuable.
Our team recently spoke with the Head of AI Transformation at a 1,500-person logistics company with an engineering organization of roughly 100 people. The company has been operating for 60 years, spent the past two decades building out its proprietary software capabilities, and has been actively preparing for the transition to AI over the last 18 months.
A few particularly interesting observations from our conversation:
_
1. They're preparing to transition from software-first to AI-first, and reconsidering what they've already built.
Over the past 20 years, they've invested heavily in developing software to support their logistics operations. But with the pace at which AI capabilities are advancing, they're now questioning whether certain applications and features developed as recently as 12–18 months ago will remain necessary in their current form.
Their dedicated AI team currently consists of four people, but the longer-term intention is to redirect more of their existing engineering resources toward AI development.
2. They're pursuing a fundamental technological transformation without wanting to cause a fundamental organizational disruption.
Despite the ambition, their immediate priority isn't replacing existing systems, restructuring departments, or requiring employees to adopt entirely new workflows. Instead, they're building infrastructure, including MCP servers, that allows AI applications to interact with their existing systems and make operational information more accessible to employees.
In a logistics business of this size, information relevant to a single decision can be distributed across multiple systems, email threads, and departments. Retrieving it often requires employees to coordinate with one another, manually consolidate records, and reconcile information before they can act.
3. They're using AI to conduct process discovery without relying exclusively on employee interviews (probably the most interesting part of our conversation).
One of the biggest constraints in enterprise AI implementation is understanding how work actually gets done. Traditionally, that means interviewing employees, surveying departments, and spending considerable time documenting workflows.
Beyond being time-consuming, this process can introduce organizational friction. Employees may be reluctant to disclose inefficiencies, describe their responsibilities differently from how they're actually performed, or become concerned about why their work is being scrutinized in the first place.
Their approach is to begin with the operational evidence that already exists.
By analyzing historical emails, system activity, transactions, and interactions between departments, they can reconstruct how information moves through the organization, identify recurring processes, and understand where manual intervention or delays occur.
Rather than relying entirely on what employees say they do, they can develop an initial picture of what actually happens, then work with employees to validate the findings and understand the context behind them. This can make discovery substantially faster and less disruptive, while potentially revealing patterns that wouldn't surface through interviews alone.
_
I suspect this balance between technological ambition and organizational continuity will become one of the defining challenges of enterprise AI transformation.
3
70
792
We're finding that one of the biggest barriers to enterprise AI adoption is company leaders labeling themselves as “non-technical.”
For a long time, that distinction mattered. It determined what you could build and what you needed someone else to do for you.
That's changing very quickly, but the way people think about their own abilities hasn't caught up. A lot of folks are ruling themselves out before they've even tried.
3
64
303
We just deployed an AI procurement agent for a food distributor. What made the engagement interesting was that the company's president had already been using AI extensively to inform purchasing decisions, but the procurement process itself remained largely manual.
BACKGROUND:
He's non-technical, runs a busy operation, and had taken it upon himself to connect Claude with the company's historical sales data, Excel worksheets, and SAP records. He was using that information to generate purchasing recommendations for his team, who had historically relied heavily on experience and anecdotal judgment.
THE CHALLENGE:
The challenge was that procurement in food distribution involves considerably more than forecasting demand. For every SKU, the team needs to account for historical sales, seasonal demand fluctuations, current inventory, shelf life, supplier lead times, and projected sales. And because much of their inventory arrives in shipping containers from suppliers around the world, purchasing decisions must also account for how to fill those containers economically.
These variables are interdependent. Ordering more of one product might improve container utilization but increase the likelihood of liquidation as expiration dates approach. Ordering less might preserve working capital but create stockouts or require more expensive shipments later. A product with relatively modest historical sales might warrant a larger order ahead of a seasonal demand spike.
The consequences of getting these decisions wrong were material. The business was regularly liquidating five to six figures' worth of inventory each month as products approached expiration. Meanwhile, the president was spending his own time analyzing data and preparing recommendations to compensate for gaps in the existing process.
OUR WORK:
We spent a week in their office with the procurement team, mapping the workflow from beginning to end and identifying the information and decision criteria involved at each step. The resulting agent evaluates the relevant purchasing variables daily, determines whether a purchase order should be proposed, and, when appropriate, recommends what to order and how to allocate products across a container. The procurement team reviews the recommendation, makes any necessary adjustments, and approves it before the agent submits the PO to the supplier.
The immediate operational benefit is roughly a day of procurement work that can be taken off the team's plate. But the more consequential opportunity is improving the quality and consistency of the purchasing decisions themselves.
If the system can reduce unnecessary inventory accumulation, avoid preventable stockouts, and improve container utilization, the financial impact can extend well beyond the labor involved in preparing purchase orders. Those outcomes will need to be measured over subsequent purchasing cycles.
One of the more interesting things we're learning through these deployments is that the cost of executing a business process and the economic consequences of the decisions within it can be vastly different. In this case, generating and submitting a purchase order is relatively straightforward. Determining the right purchase order, across hundreds of interacting constraints, is where much of the value sits.
And that's an important distinction when evaluating where AI can create meaningful economic value inside an enterprise.






