Software / AI

A six-month check-in on the SaaSpocalypse: "The Ghost of Software Present"

Building on the application-layer debate from last edition, Devin Mathews of ParkerGale looks back on the six months since his Christmas Carol themed "The Ghost of Software Future" article at the start of the SaaSpocalypse.

  • His argument then was that the gloomy narrative had skipped a few steps in the journey. SaaS was being priced as though AI had already replaced it, when most of us knew the likely path would be messier, just like other major technology (r)evolutions. His hunch was that AI would quickly get absorbed into the tech stack, Systems of Record would keep handling the boring, critical work companies must do, and many incumbents would harness AI's intelligence rather than get run over by it. Of course, many software companies would either ignore the Ghost's premonition or fail to execute.

  • For much of the spring, his position that enterprise software would domesticate AI looked wrong. As of recently, while you can still find a headline to convince your priors, whatever they may be, the IGV software ETF finished August up about 7% on the year.

  • This is a long article (estimated 22-minute read), and the conclusion is far from AI being much ado about nothing to software valuations. It's nuanced and open-ended, but to try to summarize a few of the key points:

    • The foundation models may be the thing getting commoditized, not software.

    • Hence the argument that enterprise software does not have to win the model war. It sits downstream of the labs, so cheaper and better intelligence (closed, open, or Chinese) all can help it.

    • Four years and hundreds of billions after ChatGPT, he still cannot point to a single foundation-model company that has displaced an enterprise system it was supposed to make obsolete.

    • The real fight is over layers, a debate Geoffrey Moore opened in 2011 (yes, 2011!): Systems of Record (authoritative, exact, boring) versus Systems of Engagement (the pretty, collaborative layer).

    • Generative AI made engagement cheap, so now the argument is value moving again to the System of Action, the layer that actually executes the work. E.g., AI can plan your trip, but Booking.com will still complete the transaction, settle payment, and handle the mess.

    • The distinction he keeps returning to is intelligence versus authority. Incumbents start with authority (state, permission, process, audit) and must acquire intelligence; AI challengers start with intelligence and must earn authority one integration, permission, and liability clause at a time. Whoever closes that gap first can own the System of Action.

    • On the fundamentals, there are individual winners and losers, not a category wipeout.

    • The risk he actually worries about is erosion, not replacement. A Guggenheim survey of 150 large enterprises found only 5% to 8% expect full AI-native replacement of core systems over one to three years, but about a third expect significant cuts in functionality (read: the logo may stay, but the invoice may shrink or stay flat at renewal).

  • The closing image: legacy Systems of Record are a handmade scabbard that most incumbents have let rust, with no sword to put in it. AI-natives were born holding the sword but have nowhere to sheathe it. "AI will not destroy enterprise software. It will destroy a great many enterprise software companies that fail to exploit the position they're in."

  • In the article, his firm also released its AI Resilience Scorecard and a companion Claude Skill publicly, scoring a company on Source of Truth, Workflow Depth, Uniqueness, Pricing, and AI Stance.

  • For a more alarmist companion on exactly where erosion (or replacement) could bite, OnlyCFO catalogs the 10 biggest threats to SaaS, as told through his seat as a CFO overseeing spend.

The Ghost of Software Present, Devin Mathews, PE Funcast

Another SaaSpocalypse post-mortem (if we can call it that yet), concluding the market is still looking for durability over growth.

FPE scored 27 public business-application software companies seven months after the SaaSpocalypse, rating each on a durability framework of four Cs:

  • Consequential (is it a system of record whose data takes precedence, and what breaks if it is wrong or unavailable?), Coordinating (how many people across how many departments depend on it), Codified (is compliance, security, and audit embedded, is it named in written procedures?), and Compounding (does its value grow over time through data, network effects, or domain insight?).

  • The headline finding, in the author's words: "At this point in the cycle, the market is paying more for durability than for headline growth. Durability explains 63% of the variance in ARR multiples, vs. 29% for forecast growth."

  • The median 'higher durability, higher growth' company is down just 3% year to date, whereas the median low durability company is down 27%.

  • Interestingly, they also conclude that growth and durability appear to be statistically independent of each other.

What "openness" means once your customers bring their own AI agents.

This article picks up on a different theme in the last edition: systems of record needing to become AI harnesses, showing what it may look like with a real example in property management software.

  • For a decade, "openness" in property management software meant how many third-party tools you integrated with and how good (and how expensive) your API was. Yardi has historically charged providers upwards of $25,000 for access, RealPage has offered a marketplace many find lacking, and AppFolio has kept fewer than 70 integrations so that they can own their core workflows rather than rent them out.

  • AI is changing what "openness" may mean. As property operators start doing actual work inside models like Claude, openness becomes less about access and more about agency. In the AppFolio CTO Matt Baird's own words: "The most open platforms are not the ones with the most connectors anymore. They are the ones that give customers the most freedom to shape how this new intelligence layer operates within the context of their business."

  • AppFolio's approach is a bidirectional MCP connector that puts Claude in conversation with AppFolio's own agent, Realm-X, agent-to-agent. The customer drives it with their own model, and the harness executes inside AppFolio under its rules. The analogy provided in the piece is that it is the difference between handing a contractor the keys and every document versus calling the property manager, describing the outcome, and trusting them to execute it within the rules.

  • As AppFolio sees it, this allows operators the best of both worlds: the intelligence of a best-in-class generalist model combined with the sector-specific understanding and guardrails of the property management platform. While a generalist model can read a database and reason an answer, harnesses add value by actually understanding the core business.

  • This technological shift is interesting in the context of AppFolio's position in the market. Much of the company's traditional customer base sits in the smaller and middle-market tier, comprised of multifamily operators who do not employ a CIO to hand-pick point solutions and who cannot bankroll the multimillion-dollar systems integrators that large institutions lean on to stitch a stack together. AppFolio is betting that its technology can help smaller operators keep pace. By drawing on shared training data and capability, a middle-market multifamily manager can effectively rent a data-and-automation moat it could never build alone, which turns the consolidated platform into less of a threat to the small operator than a lifeline against the giants' in-house advantage.

  • The article ends with an open question that the above point begs. If high-quality reasoning with industry context becomes a commodity, it remains to be seen how managers will continue to differentiate. "That is a serious question, and I do not know the answer yet."

Deep Dive: AppFolio, Brad Hargreaves, Thesis Driven

If you believe in what AppFolio is doing, you may agree with Garry Tan of Y Combinator, who put it recently "either you die a system of record or you live long enough to become a domain-specific harness." Regardless, if you enjoyed the AppFolio piece, or are just curious about the harness idea, another worth a skim is a ConTech roundup on the AI model becoming a commodity.

Reflections

Nabeel Qureshi on how to actually understand things, which AI has made both easier to do, and to skip over.

His premise is that intelligence is as much a set of virtues (honesty, patience, the will to keep going) as it is raw processing speed.

  • The trait that separates the smartest people he has known is refusing to stop at an answer they do not really understand, no matter how many others accept it. It takes energy, a "compulsive unwillingness to lie to yourself", and being unafraid to look stupid.

  • As famed scientist Richard Feynman says, the first rule of science: do not fool yourself, and you are the easiest person to fool. As others more commonly say, this is why writing is important. Writing forces clarity, as it's harder to fool yourself when you sit down to write about it and it comes out all disjointed and confused.

  • Unfortunately, many people don't actually try to understand topics in a deeper way. Many schools almost train us not to question too deeply, else you fall behind. Just learn the algorithm, plug in the numbers, and pass your exams. Speed is of the essence. In this way, school kills the "will to understanding" in people.

  • His countervailing advice to people trying to understand something is: go slow. Read slowly, think slowly, really spend time pondering the thing.

  • For example, Bill Gates structures his famous "reading weeks" around an outline of important questions he's thought about and broken down into pieces. e.g. he'll think about "water scarcity" and then break it down into questions like "how much water is there in the world?", "where does existing drinking water come from?", "how do you turn ocean water into drinking water", etc., and only then will he pick reading to address those questions. This method is far more effective than just reading random things and letting them pass through you.

  • Relatedly, there are some mantra-like questions that can be helpful to ask as you're thinking through things. Some examples: But what exactly is X? What is it? Why must X be true? Why does this have to be the case? What is the single, fundamental reason? Do I really believe that this is true, deep down? Would I bet a large amount of money on it with a friend?

  • Personally, I am concerned that with AI, many people will skip to the answer rather than leverage AI to work through such questions more easily than ever before.

How To Understand Things, Nabeel S. Qureshi

Podcasts

One I listened to this stretch.

Liberty Mutual's CIO on two nuances of investing permanent capital.

  • Investment hygiene. With no third-party capital to answer to, Vlad Barbalat argues Liberty can hold to what he calls "investment hygiene": doing the right thing rather than the expedient one. The caveat he adds is that permanence cuts both ways. It can breed complacency, and "we can make long-term decisions others can't" too easily becomes an excuse for results that simply are not working. Which brings him to...

  • One year vs. three to five. Long-term decisions still need to be built from sensible short-term results. Every business is stuck with an annual calendar, and one-year results matter to stakeholders, even though we all recognize anything can happen in a single year. His answer is to hold both truths at once: stay honest about the calendar year, but put yourself and more of the organization more explicitly on the hook for three-to-five-year targets.

Charts

I always love seeing the update of this chart year over year. Every asset (software or not) has its ups and downs, something obvious yet often lost in the moment.

Asset class returns, Mr Family Office, X

Quick Shares

On slowing down and remembering that most things don't matter. Being busy can actually be a form of laziness; being selective, i.e., doing less, is the path of the productive.

An article, with a twist, on why some investors may be better off saying "I don't know".

The End of a Golden Era for Investors, Ben Carlson, A Wealth of Common Sense

Ben Horowitz on Making Yourself a CEO (P.S. check out his book, The Hard Thing about Hard Things).

On the one question Antonio Gracias asks of his CEOs year after year: what is the constraint of the business?

On a nice counterpoint to the Horowitz piece above: "hire great people and get out of their way" is only half the job, and may not be quite right.

An interesting example of some of the limitations AI still has, told through someone's advice on how to get world-class design out of AI instead of the generic default.

How to turn your AI into a world-class designer, Anshu Chimala, Lenny's Newsletter

From The Vaults

A piece from my vault of favorites, that happened to re-cross my feed recently.

Charlie Munger's operating system for a life that works.

Drawn from Munger's 2007 USC Law commencement address (worth the read!), which Farnam Street collects into a few core ideas including but not limited to:

  • To get what you want, deserve what you want.

  • Attain fluency on the big multidisciplinary ideas of the world and use them regularly.

  • Learn to think through problems backwards as well as forward. Invert, always invert.

  • Be reliable. Unreliability can cancel out the other virtues.

  • Avoid intense ideologies. Always consider, and know, the other side as carefully as your own.

  • Avoid being part of a system with perverse incentives.

  • Learn to maintain your objectivity, especially when it’s hardest.

  • You’ll be most successful where you’re most intensely interested.

  • The highest form which civilization can reach is a seamless web of deserved trust.

The Munger Operating System: How to Live a Life That Really Works, Farnam Street (P.S. if you enjoy this, also check out a more business-focused Munger recap A Dozen Things I've Learned from Charlie Munger about Moats, Tren Griffin)