[BidClub_]
The a16z Show · · 36 min

The State of AI: Models, Moats, and the Consumer Renaissance

Anish AcharyaJen Kha

YouTube
TL;DR
  • Anish Acharya plants his flag in the "many winners" camp on frontier labs. In the last 2 weeks, xAI went "from not even being a real contender on the model side to being one of three" — a two-horse race became three — while Anthropic's apparent dominance gave way to OpenAI's excellent 3 months (new models, the Codex harness, and the ChatGPT desktop app), with multiple labs growing despite each other's successes. Jen adds the tradeable overlay: X is an imperfect weather vane but an early indicator of developer sentiment; Claude is taking token-usage pushback, and Anthropic is going public later this year.
  • The under-discussed macro scenario isn't the bubble — it's "what if we're insufficiently optimistic?" B200 per-hour prices are rising even though it is a non-cutting-edge GPU and compute is normally deflationary, which "points to very constrained supply and essentially infinite demand." On SaaS: February's 30–40% drawdown was overselling and many names are back up 40%, but with SBC distortions now visible it's "accelerate or die."
  • Most moats survive abundant low-cost intelligence — but the integration moat is at risk. Network, scale/distribution, and brand effects are "as good as they've ever been" ("no amount of coding agents is going to make Nike not Nike"), while coding agents make SAP-style integration dramatically better and raise an "existential question" for SIs and GSIs.
  • Token spend rationally splits by bounded versus unbounded upside. For sales and product, "it's economically rational to pay almost any price for a model that's even 1 IQ point smarter" — "your Fable 5 or your Gro or your GPT56"; for finance, "you can't close the books 10 times better than accurately," so open-weight models plus reinforcement learning may be the Pareto-efficient choice. Models aren't commodities: neurotic, literal GLM 5.2/5.3 versus open, presumptuous Kimi K3 — organizations need both minds.
  • Labs are vertically integrating down into inference, not up into apps — inverting the early-2025 panic. Anthropic's legal "plugin" (just collections of long prompt files) sparked a panic in which Thomson Reuters and other legal names traded down, but inference workloads are homogeneous and scalable while the app layer is idiosyncratic and OpEx-heavy; and in a multi-model Pareto-frontier world, labs have a harder time capturing "100% of your gross margin."
  • The consumer's quarter may finally be here, but "we're in the DOS era of AI" awaiting its Windows. Open-weight models are making AI software dramatically cheaper and more performant (Jen's own X-timeline app cost $250 to onboard a new user), there's still no AI-native app store, and consumers are excited to try and pay for new software — Anish compares the moment to Christmas 2009 with the iPhone, except consumers may now pay $200 a month.
  • The investing posture has hardened around live product and technical founders. It's now "disqualifying to not be showing a live product in a pitch at any stage"; founders skew "less MBAs, more researchers"; and per Ben at the offsite, "the biggest risk in the past was the ideas were too big and now the biggest risk is that the ideas are too small." New business formation is at an all-time high outside a peak moment during COVID — the 25-year-old who would have been a YouTube creator now builds neighborhood SaaS.
Digest · the substance, structured for research

1. Grok Bots buys the jeans — and the macro says demand is effectively infinite

  • The opening anecdote that frames the episode: Anish mostly wears Frame jeans, photographed his current pair, told Grok Bots overnight "don't spend more than $500 and get it done," and woke up to a researched, purchased, in-transit pair — same fit, different wash, bought with his credit card. His read: "the defining characteristic of Grok Bots is resourcefulness," and the next unlock comes from resourcefulness plus product architecture consumers understand.
  • On the winner question, he's "many winners": xAI went from non-contender to one of three in 2 weeks; Anthropic went from seeming dominance to OpenAI's excellent stretch — exceptional new models, the Codex harness, and a "very well done" ChatGPT desktop app — with specialization diverging and multiple labs growing. Jen's caveat: X is an imperfect "weather vane" but an early indicator of developer sentiment, Claude faces token-usage pushback, and Anthropic goes public later this year.
  • The bubble case is "fully discussed"; the out-of-distribution topic is insufficient optimism. Evidence: B200 per-hour prices rising even though the non-cutting-edge GPU is normally part of a highly deflationary market — "essentially infinite demand and highly constrained supply."
  • The SaaS whipsaw as market psychology: after February's 30–40% drawdown, a16z said software was oversold; many names recovered 40% ("I'm not quite sure what we collectively accomplished"). Software is only 8–12% of enterprise spend, so the upside of vibe-coding your own payroll or CRM is low and the downside "essentially unlimited" — but the tide has receded on SBC-distorted economics, and those companies must "accelerate or die."

2. Moats mostly survive; token spend splits by bounded vs. unbounded upside

  • Working from 7 Powers, Anish argues most moats are untouched by abundant intelligence: "no amount of coding agents is going to make Nike not Nike," and Instagram's power was never the app's complexity. For him, the most obvious exposed moat is integration — SAP is so complex that even migrating from one version to the next can be existentially risky, and SIs/GSIs face an existential question about their value as the integration point.
  • The rational enterprise architecture: alpha-creating functions (product, sales, engineering, research) get frontier tokens because upside is unbounded — pay almost any price for 1 more IQ point, "your Fable 5 or your Gro or your GPT56." Supporting functions have bounded upside: "the best way to close the books is accurately. You can't close it 10 times better than accurately." For those use cases, open-weight models with reinforcement learning can make sense on the Pareto-efficient cost curve.
  • Jen surfaces Decagon founder Jesse Zhang's post that for many startups open source is "actually the only option" — for localization, training, and fine-tuning, not just cost. Anish's addition: reinforcement learning on a specialized problem and its reasoning traces builds compounding domain advantage, with Harvey seeing strong results in legal. The trade-off is lost generality — fine for legal or customer support.

3. Models are not commodities — and labs integrate down, not up

  • His Big Five framing: there are "autistic models" — GLM 5.2 and 5.3 are "very literal and they'll only do exactly what you told them" — versus Kimi K3, "open and presumptuous and creative." You can't be both highly open and highly neurotic; accounting may want neuroticism, while design may want openness, so organizations need multiple minds.
  • The legal-plugin panic as case study: Anthropic's plugin — "a ZIP of skill files… just long prompts" — prompted a panic in which Thomson Reuters and other legal names traded down dramatically. But instead of integrating up, labs have integrated down into inference and compute, where homogeneous workloads allow enormous scale; the app layer's idiosyncratic pricing, packaging, and buying behavior make it "OpEx-heavy" for labs.
  • Specialization is already visible in harnesses: OpenAI's new GPT models and desktop app are a strong product container for knowledge work; Claude Code, terminal UI and all, is oriented to software engineering. Aggregation can beat any single lab — the Expedia metaphor: Cursor uses a frontier model for planning and a lesser one for execution; creative tools combine ElevenLabs (voice and music) with Black Forest Labs (video and creative direction); research can run the same query adversarially through models with non-overlapping training data and then use another model to converge. Labs are structurally limited to providing their own in-house models, while an application aggregator can provide best of breed.

4. Apps productize the intelligence primitive; loops are the enterprise unlock

  • The core analogy: intelligence is a primitive like cloud, and just as Salesforce turned the AWS cloud primitive into CRM, "you really need Harvey to turn that into an economic outcome for the legal industry." Credit unions illustrate the idiosyncrasy — most don't want to halve headcount; they want to double it while remaining economically performant.
  • Agent demystified: "just a model in a loop with tools and memory." The coding loop — bug reported, reproduced, fix generated, verified, shipped autonomously if low-risk — extends to price optimization and procurement, up to the business loop where the model proposes, "I think we need to open a branch in Tijuana."
  • Marc's line is "industries, not markets": the coding primitive spans Claude Code exposing "the raw horsepower" to developers, up to Replit abstracting for the non-coding small-business owner — all variations of pricing, productization, and packaging. On whether labs will squeeze the app layer: in 2023's one-model world "the labs would just take 100% of your gross margin over time"; with many options across the Pareto frontier, they have a harder time doing that.

5. The consumer renaissance: DOS era, personal agents, and Town's compounding memory

  • What held consumer back: consumers don't love paying for software while AI carries real marginal costs of distribution and engagement — Jen's X-timeline app cost $250 to onboard a user, making a mass-market free product hard to support; open-weight models are now changing that with lower costs and better performance. There's no AI-native app store, so distribution looks like Web 2.0, not mobile; and "we're in the DOS era of AI… we're going to need the Windows."
  • What's working: coding agents for the "digitally native entrepreneur" — the YouTube-creator moral panic reframed as kids wanting to build internet businesses, now able to build $100K–$1M/year "mom-and-pop SaaS," not venture-backable but "very cool for the country." Personal agents are moving from OpenClaw's January "Homebrew Computer Club" energy into consumer software such as Grok Bots and ChatGPT Work.
  • His consumer definition: if you can't justify sales-led acquisition, usually around a $15K ACV, it's consumer — the plumber counts. Entertainment will be massive (Character was arguably an entertainment company; Asian short-form drama is starting to come over): "most people want to spend time, not save time."
  • The broader personal-agent model is a set of life loops — family, friendships, money, and health — in which changing information leads to decisions, agency, execution, and another iteration. OpenAI is focused on health and finance, while startups are working on shopping; Anish expects a dramatic quality-of-life improvement, with 80% of the surplus delivered to the mass market.
  • Town (Alex Rampell's investment) as the memory-compounding pattern: day 1 it's a new hire; by day 30 it makes excellent assumptions from soaked-in context — showing up as retention and per-customer pricing power. Jen says her professional inbox is at zero but her personal inbox has about 20,000 messages; Town surfaces what matters, scrubs subscriptions, and is starting to self-improve by showing the credit cost of routines and how to save credits.

6. Economics, founders, and where the capital goes

  • The consumer whitespace includes AI in "the emotional, interpersonal domain": you can talk to Claude, OpenAI, or K3 "and feel feelings," after "40 years of technology that boosted our intellect… but nothing that spoke to our humanity." Startups can pursue products that labs and big tech are not culturally set up to build, such as a companion that disagrees with you or uses sexual innuendo. Consumers are excited to download new software and, unlike the 99-cent era, Anish says they are willing to pay $200 a month.
  • Funding posture: mostly no pre-revenue bets — "it's disqualifying to not be showing a live product in a pitch at any stage these days because it's so trivial to build stuff"; the work is extrapolating from statistically significant sales and product against price and implicit risk, with small "pre-everything" call options for talented, experienced teams. The old wisdom that too much seed capital wrecks companies is becoming more nuanced: a focused $100M can deliver a different value proposition than $20M — a better problem than fintechs "indirectly subsidizing their customers through weak underwriting."
  • Founder archetype shift: "less MBAs, more researchers" — lower business sophistication, dramatically higher technical sophistication, which is "upstream of all the good things"; business sophistication can be taught and observed, while technical sophistication typically cannot. Ben's offsite line: the biggest risk used to be ideas too big; now it's ideas too small.
  • For existing SMBs, the old channels remain, but founders increasingly need an original network effect — word of mouth — because Instagram, TikTok, and X make it difficult to build a new distribution channel on top of an existing one. The most interesting segment is new business formation, at an all-time high and highest outside a peak moment during COVID: "not the 55-year-old plumber… a 25-year-old building SaaS for their neighborhood or their high school."
Jen Kha

To help me break down all things around this incredible abundance, I'm going to bring up Anish Acharya.

Anish Acharya

Hi.

Jen Kha

Awesome. Awesome. Awesome. Hey, Anish. Anish and I were at the GP offsite earlier this week, and he shared with me that he's already running Grok Bot and has purchased a bunch of jeans for him. Anish, do you want to drop what you purchased?

Anish Acharya

True story. Yes. So, I'm going to reveal an important secret—protected IP—which is that I mostly wear Frame jeans. Frame is a great brand, and Grok Bots are an awesome product.

Actually, I'd say the defining characteristic of Grok Bots is resourcefulness. I went to bed a few nights ago and said, “Hey, buy me a pair of jeans that are inspired by these.” I took a photo of my current jeans, said, “Don't spend more than $500, and get it done,” and went to sleep. I woke up in the morning, and it had researched and found a pair with the same fit and a different wash, used my credit card, purchased them, and they were on the way.

I think that's going to be something that we see more and more of. We already have the capabilities, and now a lot of the unlock will come from resourcefulness, as well as product architecture delivered in a way that most consumers can understand.

1. Who Wins the AI Model Race in Three Years?

Jen Kha

Awesome. Awesome. Awesome. I told my team that I'm going to set my bot to finally take care of the pile of things I've been promising my husband I'm going to sell for the last 2 years. That is the project for this weekend.

Anish, we asked the question earlier: Which one of today's AI leaders will be the clear winner 3 years from now? What's your take?

Anish Acharya

I'm a many-winners guy, and I see I'm in good company with many of you. If you look at what's happened in the last 2 weeks, xAI went from not even being a real contender on the model side to being one of 3. We essentially went from a 2-horse race to a 3-horse race.

Even more broadly, over the course of the year, we went from Anthropic feeling like they were so dominant they could do no wrong to OpenAI, which has just had an excellent 3 months. The new models are exceptional. The new Codex harness and ChatGPT desktop app are very well done, and we're seeing the specialization of these labs in different directions.

They're both growing like crazy despite each other's continued successes. xAI is doing well, and open-weight models are doing well. So, I'm definitely in the many-winners camp.

Jen Kha

Yeah, it's interesting to see the sentiment also on X, which is not always a perfect weather vane for the future, but it's often an early indicator of at least where developer sentiment is. There's been a lot of pushback from Claude users recently in terms of token usage, and developers tend to be fair-weather fans on these things. They'll go where the latest, greatest, and very best model isn't.

2. What's Next in the Frontier of Intelligence

Over the last 6 to 8 weeks in particular, I think we're going to see some very interesting traction in terms of the flow of activity. Obviously, Anthropic is going public later this year, and there's a lot of keen interest in this.

With that, it brings us straight into the topic of discussion today: Where and what is next in the next frontier of intelligence?

Anish Acharya

Amazing. Thank you, Jen. Let me tee this up for everybody. Please hop in if you've got questions.

Let's first cover the macro and what's happening at a market level. Then we're going to hop into the application layer broadly and talk through why applications are the productization of the intelligence primitive. Finally, let's talk about the consumer. With the launch of Grok Bots and a few other products, it's actually been a very fun couple of weeks in consumer.

Hopefully, our dear friend Leopold doesn't mind me poking a little fun at him here with “Situational awareness, please. Next.”

Look, I think the case for this being a bubble is over-discussed, or at least fully discussed. I think the out-of-distribution topic that's less discussed is: What if we're insufficiently optimistic?

If you look at some of the underlying indicators, what they point to is essentially infinite demand and highly constrained supply. Things like B200s, which are non-cutting-edge GPUs, going up in price on a per-hour basis are very strange. Normally, we see these things be highly deflationary, and it points to very constrained supply and essentially infinite demand.

We're thinking and talking a lot about what's the informed case for optimism here, given some of these second-order indicators.

The SaaS bubble—or the SaaS whipsaw—was an interesting peek into market psychology. Back in February, when we saw a 30% to 40% drawdown in a bunch of SaaS names, we said that the market had oversold software. Lo and behold, here we are: Many of those names are back up 40%.

I'm not quite sure what we collectively accomplished, but I'll tell you what we said then, which is still true today: For the enterprise, software spend is 8% to 12%. It's just not a huge proportion of spend. So, the upside to vibe-coding your own payroll or CRM is not particularly high. The downside is essentially unlimited.

There are obviously all kinds of compliance implications of not getting things like payroll right. Most enterprise software today demands a level of precision that just isn't afforded by coding agents.

The one thing that has happened, though, is that the tide has receded. A lot of SaaS companies had a ton of SBC and things that distorted their economic performance. I think that's very much visible now, and they're going to have to accelerate or die.

So, it's less bleak for the SaaS market than perhaps we all collectively thought for a few months there, but there are still some existential questions to address.

There's been a huge discussion of moats. Are there any moats? There are no more moats. It's very funny because if you actually study moats, which I think are most famously codified in the book *7 Powers*, the vast majority of moats are not affected by abundant, low-cost intelligence.

When you think about network effects, scale effects, which show up in distribution, and brand effects—which we tend to discount in Silicon Valley—these things are as good as they've ever been. No amount of coding agents is going to make Nike not Nike. The power of Instagram was never the complexity of building the Instagram app. Of course, it was the network behind it.

You actually think the majority of moats are as good as they've ever been and, of course, are still critical to building compounding value.

There are a couple of moats that are exposed. For me, the integration moat is the most obvious one. SAP is so famously complex to integrate into and out of that it's an existential risk even to migrate from one version of SAP to the next. Coding agents make this dramatically better.

I think there's a bit of an existential question for SIs and GSIs as to what their value will be when they've historically been this point of integration. So, I do think this moat is a little bit at risk. But for the other traditional moats, they persist and they're as important as they've ever been.

Jen Kha

Yeah, I think this is a really important concept. As you start to think about what the job functions in the enterprise are that are alpha-creating, it's typically product, sales, engineering, and research. Conversely, what are the job functions in the enterprise that are supporting other functions? “Administrative” is maybe too bleak, but legal, HR, finance, and so on.

We really think that the rational architecture—and the one that is emerging—is that for jobs that have unlimited upside, like sales or product, you always want to use frontier tokens. The reason for that is you just don't know what the value of the new product feature or closing a customer account is. It's effectively unbounded, and therefore it's economically rational to pay almost any price for a model that's even 1 IQ point smarter—your Fable 5 or your Gro or your GPT56.

Conversely, when you talk about something like finance, the best way to close the books is accurately. You can't close them 10 times better than accurately. As a result, you have this bounded-upside problem where it makes sense to use open-weight models with reinforcement learning for the Pareto-efficient cost curve.

3. Why Open Source Is the Only Option for Some Startups

Maybe before we move on from this one—because this is a big debate, and again, when Kimmy dropped a few weeks ago, there was a lot of consternation about this topic, given the relative cost, which was the focus of the discussion—our founder, Jesse Zhang from Decagon, dropped this great post about the fact that, in some respects, and for a lot of companies like Decagon, open source is actually the only option.

It's not just cost. It's that they can actually localize it, train it, and fine-tune it. Maybe unpack a little bit of that configuration. Talk through the nuances there and why folks shouldn't be concerned, even though that is the case for startups, that there's a lot in the way of abundance around this topic.

Anish Acharya

Yeah. One of the big topics that we're seeing—or one of the big trends—is that there are comparative advantages of different models. The models often have areas of focus that are almost in tension with each other.

So you see a certain set of models that have a high degree of neuroticism. They’re sort of autistic models. GLM 5.2 and GLM 5.3 are great examples of this: they’re very literal, and they’ll only do exactly what you told them to do and nothing more. Then we’re seeing models like Kimi K3 that are much more open, presumptuous, and creative.

There are roles for both types of models in the organization, and often the shapes of those minds, if you will, are at odds with each other. That is one reason you actually want to have multiple models. Reinforcement learning is a really important point. If you actually have a problem that you can specialize the model around with your reasoning traces, you can start to create this compounding advantage in your domain for your customer base, where you’re able to shape the intelligence to be better than any general intelligence for your problem. I know Harvey has had some great results with this as well.

The trade-off of that kind of reinforcement learning is that you lose generality. If you have the best model fine-tuned for solving legal problems, it may not be great at solving theoretical math problems, and that’s okay for Harvey’s uses or in the case of Decagon’s customer support. This sort of open-weight specialization property is very unique and is one of the reasons our startups are selecting these models.

This is also a big topic. We’ve learned so much since January. We should really do this monthly, Jen.

Jen Kha

Yeah. I mean, honestly, there’s just so much changing.

Anish Acharya

So, in January and February, there was a lot of discussion, and it’s very idiosyncratic and interesting. Anthropic’s Claude released what is called a legal plugin. Plugins are just collections of skill files; you can think of them as a ZIP of skill files. Skill files are just prompts—long prompts. There was this huge panic, and all of a sudden Thomson Reuters and a bunch of other big legal names traded down dramatically.

But those were really just prompts. There was a lot of discussion about whether labs were going to vertically integrate up into the application layer. Instead, we’ve seen the very opposite: yes, they are vertically integrating, but they’re vertically integrating down into inference and compute. It’s actually logical now, in hindsight, because the workloads for inference are very homogeneous, so you can build enormous scale in one part of the value chain. Whereas when you think about the application layer, you’ve got so many idiosyncrasies and unique needs in terms of pricing, packaging, productization, and how the market wants to buy.

It’s actually a much more challenging and OpEx-heavy proposition to move into the application layer versus moving down into the inference layer. This is the point I alluded to earlier, which is this discussion of model commoditization. If you use the models every day, which I do—I hold myself to a standard of making something either small or big with every model that comes out—you start to appreciate the fact that these things are not commodities. They have comparative advantages at a domain level.

A great example is OpenAI’s new GPT models, which are just so good at knowledge work. The harness is also very well set up for knowledge work. If you’ve used the ChatGPT desktop app, you know what I mean. It’s very cool and interesting, and it’s the perfect product container—to use “harness,” I mean a product container like a browser—to do spreadsheets, slide presentations, written documents, and all of that type of work.

If you look at Claude Code, which many of you, I’m sure, have used, it’s oriented toward software engineering. It’s in a terminal UI. Everything from the small design decisions to the areas in which it specializes, like code planning and code testing, is oriented toward the software engineer. Both products make many trade-offs for their respective specializations.

So, one, you’ve got this domain-level specialization that’s already occurring. Then, two, as I mentioned earlier, you’ve got what I think of as the Big Five personality traits, if folks have studied that. You can’t be both highly open and highly neurotic. Sometimes, when you have an intelligence you’re applying to an accounting problem, you want neuroticism. When you’re applying it to a design problem, you want openness.

You actually have a need for both types of minds in the organization, which is why you would select something like a GLM 5.3 versus a Kimi K3. So, definitely not commodities in our view.

This is an important point. There are many product categories in which model aggregation delivers a greater-than-the-sum-of-its-parts outcome. A good metaphor for this is Expedia. It’s so much more useful to use Expedia than it is to go to United, then to Delta, then to Southwest. You just want a single place where you can benefit from seeing every airline’s inventory.

Similarly, in coding, we’re seeing this with Cursor a ton, where you want to use a frontier model for planning, for example, but then you can use a lesser model for execution. You really need to have one product harness, or sort of product architecture, that lets you use multiple models.

Creative tools are another great example, where you’ve got models that specialize in different modalities. You’ve got something like ElevenLabs, which of course is incredible at voice and music as well, and then you’ve got something like Black Forest Labs, which is doing such an excellent job in video and creative direction. The correct product is to bring all of these together into one shell.

Finally, there’s research and decisions. We see this all the time, where the models are often trained with non-overlapping data sets. You’re able to get more information by running the same query through many models adversarially and then having a separate model help you converge. This is a place where the application layer really shines, because labs are both incentivized and structurally only able to provide their own in-house models. You, as an application aggregator, can provide the best of breed.

Okay, let’s jump into the apps layer. The key point about the application layer is that intelligence is a primitive, just like buying cloud is a primitive. What does Salesforce do? It takes the AWS cloud primitive and turns it into CRM software that delivers an economic outcome for all of its customer segments. The same thing is true of the AI application layer.

It’s great to have the raw intelligence primitive, but you really need Harvey to turn that into an economic outcome for the legal industry. A similar example is credit unions, which are a really interesting market segment because they’re so idiosyncratic in how they want to buy products, how they want the product to be productized, and the shape of the ambition for their market.

Most credit unions don’t want to decrease their headcount by half. They want to double it, and they want to double it while having an economically performant business. It’s just a very specific way that they see the intelligence primitive playing out in their market segment, and the application layer’s opportunity is to be the one that delivers that.

This is a bit of an advanced concept, but I think it’s an important one. If you look at the way the evolution of AI use has gone, it’s gone from prompting models to putting models in loops. The term “agent” is overused, but an agent is just a model in a loop with tools and memory and a few other things.

A great example of this is coding. We’ve all seen this from software companies: a bug gets reported, it gets reproduced, a fix gets generated, and it gets verified. If it’s a low-risk fix, it gets integrated and shipped, and maybe the customer gets an email saying, “Your bug was fixed.” If it’s a high-risk change, perhaps a human reviews it. That way, every bug that actually gets reported to the enterprise now gets autonomously fixed through this coding loop.

As you start to take that idea and apply it to other parts of the business—things like price optimization and procurement—these are very natural business loops that can be fully automated by these models. Perhaps the most ambitious type of loop is the business loop: you make a change that’s very cross-cutting to the business, and the model comes back and says, “Hey, I think we need to open a branch in Tijuana.”

Now, the model can’t do that autonomously, but it can make a change at the surface level of the entire business, which is extraordinary. This is how enterprise automation is going to occur through AI. For me, coding has been, over and over again, an illustration of this.

4. One Dominant Personal Agent or Many Talking to Each Other?

Legal is another great example of an industry, not a market. This is something that Marc says, and he’s so right. If you look at intelligence as a primitive, let’s think now about coding intelligence as a primitive. All of these products are working in their respective areas of the stack.

Claude Code does such an excellent job of exposing the raw horsepower, so to say, to the developer, all the way up to Replit, which is a great abstraction layer for the average small-business owner who’s unfamiliar with code. These are variations of pricing, productization, and packaging for the coding and intelligence primitives, and all of them are working as a result. So, I think a big mental model shift for us is ensuring that we’re assessing these as industries, not necessarily simple markets.

Jen Kha

Okay, and consumers had a really cool couple of weeks. We've been saying for 3 years that this is going to be the consumer's quarter, but I think that this might be the consumer's quarter. Let's go into it.

The things that have actually held back consumers so far have been a couple of things. The first is that consumers don't love paying for software. We've learned this lesson over and over again. Unfortunately, unlike the sort of magic of software in the past, AI software has marginal costs of distribution and engagement, and the marginal cost can sometimes be very high.

I built an app I use to help me browse my X timeline, and it costs $250 to onboard a new user. So, if I'm a startup founder looking at a $250 CAC, even with a $0 onboarding cost, it's very hard to make a mass-market free product work. That is changing now because of open-weight models, which are dramatically cheaper and more performant.

The second is that we've never had an AI-native distribution channel. There's no App Store for AI. So, this actual product cycle for consumer looks more like Web 2.0, where you have to build the channel alongside the product, and less like mobile, where you have the central point of distribution for the entire ecosystem.

Then the final point, I think, is an important one: we're sort of in the DOS era of AI. For this technology and its capabilities to be fully embraced by consumers, we're going to need the Windows, so to say. I think there's just a ton of work to be done around product and design craft to ensure that consumers know how to consume all these magical new capabilities.

Two things are working. Coding agents are extraordinary, and I know they've been discussed. I think it's interesting to think about how they work for consumers. If you think of this concept of the digitally native entrepreneur, if you're not a programmer, the way that's historically shown up is that you're a YouTube creator.

There was a whole moral panic 10 years ago about how kids wanted to be YouTube creators, not astronauts. But I would interpret that instead as kids who grew up on the internet wanting to build businesses on the internet, and the only way to do it, again, was by being a creator. Now, with coding agents, you can build a software product that generates $100,000 of revenue a year or $1 million of revenue a year.

These are not venture-backable businesses, but it's a sort of mom-and-pop SaaS opportunity that's emerging, and I think it's very, very cool for the country.

Personal agents: we had this collective moment of excitement around OpenClaw in January, and it was an extraordinary composition of primitives, but it never really crossed over into consumer. It was sort of a developer-oriented thing, more of a Homebrew Computer Club kind of energy. We're starting to see, with the emergence of Grokbot and ChatGPT Work, personal agents being turned into software that consumers can use.

5. Redefining Consumer: When the Plumber Uses GrokBot

Anish, actually, do you mind just pausing on this before we go to the Town demo? You were a founder building in the last era of the consumer app experience, and when I even think about it, I'm like, gosh, how do you even define consumer today? The plumber who utilizes Grokbot to completely turn around their business end to end—is that consumer or is that enterprise? It's almost like a PLG movement, but it's coming from a consumer that then crosses over into enterprise.

Particularly, the last era of consumer applications was more towards entertainment as a way to monetize, so maybe unpack some of that, and particularly where you've been spending time as a part of that.

Anish Acharya

I mean, our simple rule is: if you cannot justify acquiring the customer through sales, which usually means a $15K ACV, you have to acquire them through marketing. We think of them as a consumer, which is most small-business owners. So, I think that plumber is definitely the consumer in our investing mind.

Entertainment is huge, and there are going to be a bunch of AI-native entertainment companies. I would argue Character was kind of an entertainment company. There's been a huge trend around short-form drama, mostly in Asia, and that's starting to come over here. Many of those are generative or generative-assisted.

I think entertainment is going to be massive. Most people want to spend time, not save time, and consumers are not that interested in productivity. So that's definitely going to happen, and it's probably worth a separate deep dive.

I think Town, for folks who have used it, is just such a magical experience. This is the No. 1 piece of advice I give to everybody—friends, family, folks in the industry: please just use the products, because it's so easy to build intuition when you see how they change day to day.

Town is an investment our partner Alex Rampell made. It's a really extraordinary productivity product, and you see how the compounding improvement of the product through memory advantages it over time. The first day you use a product, it doesn't know you that well. It's sort of like a new hire who's just getting up to speed.

By day 30, it's able to make excellent assumptions on your behalf because it has soaked in 30 days of context, memory, and skills. This is a pattern that we're seeing more and more: the compounding value being delivered to the end customer showing up as retention in the business and showing up as pricing power on a per-customer basis.

6. Town Demo: Personal Agents & Managing Chaos

Jen Kha

Yeah, this is a great one, because folks can utilize Town for their personal use case. It's a free trial; they give you, I think, something like 40 credits to start, or something around there, so you can see, once you plug in your personal email, how productive it actually is. On the professional front, I'm always at inbox zero. On the personal front—

Jen Kha

My inbox is like 20,000. David George is probably cringing on the inside here just because it's unacceptable. However, personal-life things are common. If you email me at my personal address, I will never respond to you.

However, I plug my email into Town, and I don't even check anymore. If there's something important, Town will surface it to me. It also does all the scrubbing of subscriptions and all the things that it can optimize, and it's starting to self-improve. It'll send you emails where it says, “Hey, this routine is costing this much; here's how you could actually save your credit spend.”

So, it's this unlock into what starts on the productivity side and, to your point, maybe people won't pay for that personally. But once it starts to get locked in and then expand in terms of the remit, you're like, “Okay, I'll pay whatever X bucks,” just because it helps to manage my life and I can put it on autopilot.

Anish Acharya

Yeah, it's such a great point, Jen. My mental model for this is just an experienced employee, a tenured employee versus a new hire. The new hire may be brilliant and may even cost less than a tenured employee, but we all know the value of a tenured employee. They're just able to make great assumptions on behalf of the organization and you.

This is a little philosophical, but I think this is where it all goes. Just as we talked about coding loops and business loops for the enterprise, we think there's a set of loops that are informally defined that really lay out a consumer's life. Think of family, friendships, money, and health. These are all areas where you have changing information, decisions, agency, execution, and then the loop continues.

We're starting to see some of these loops emerge around self-improvement. Health and finance are the 2 areas that OpenAI is focused on. We've seen a bunch of startups working on shopping, but we think that the way this ends up playing out is a dramatic quality-of-life improvement for the consumer, and that really follows the shape of past product cycles, where 80% of the surplus is delivered to the mass market.

Jen Kha

Maybe just going back to the last slide, there's a question here. When you think about these personal-agent examples, whether it be Town or Ethos, et cetera, they all point to one assistant having context, but it seems like there are many different options.

Do you think it'll end up being one dominant platform for this personal aspect of your life, such as time management? Or will it be like an operating system where you have many agents talking to each other and configuring on the back end?

Anish Acharya

The comparative vantage point kind of comes to mind. I think the characteristics you want from your CFA are different from the ones that you want from your party planner. The surface area is so broad that I think, yes, there's overlapping bits of context.

I think Grok Bots has done a nice job of illustrating this in product: you have many bots that are pointed in slightly different directions, and they all coordinate to deliver a globally optimal outcome.

7. Apps vs Model Companies: Who Captures the Value?

Jen Kha

There are a few questions. I'm going to go back to topics you've covered earlier. If the application layer captures economic outcomes, how do you think about the competition from the model companies, and what will allow value accretion to happen downstream? Are companies at the app layer able to compete with the frontier labs going after that particular market?

Anish Acharya

I mean, I think so. Again, I think we're underestimating the complexity of product, pricing, packaging, and how the end customer wants to buy.

The way that a teenager wants to consume the intelligence primitive is different from the way a marketing executive at a credit union wants to consume it. It's very heterogeneous. So to me, it just makes less sense for the labs to move up to the apps layer than to move down to inference.

That permission point is an interesting one. I think if we lived in a world of 2023, when it was one model to rule them all, it wouldn't even matter if you had permission, because the labs would just take 100% of your gross margin over time. But now, because you've got many options at all points on the Pareto frontier, the labs have a harder time actually doing things like that.

Jen Kha

Awesome. There was a question just on traction. Do you fund anything where there's no revenue at this point, given how quickly people have been making progress, or is it extremely difficult?

Anish Acharya

We try not to. I certainly have spent less time on that strategy. Look, I think the basket is mostly investments that are showing some signs of working. Certainly from a product-velocity perspective, that used to be something we measured pretty carefully. It's disqualifying not to be showing a live product in a pitch at any stage these days, because it's so trivial to build stuff.

So almost everything we're seeing is showing signs of some sort of breakout. My model is somewhat simplistic: once you have statistically significant sales and product, if we extrapolate from there, do we like the price that we have to pay to be a part of it and the risks that we're taking implicitly? I'd say that's the majority of the work that we do. We look for very talented, experienced folks, and we do take a small call option, which looks like a pre-everything round, but that's not the majority of what we do.

Jen Kha

When you think about the competitive landscape on the consumer side—this has been unloved for so long—are you seeing this reversion, given it's clear that apps are sort of this next layer of value creation? The model layer has been somewhat set, and I say that with a huge asterisk, because there might be new algorithmic breakthroughs, folks coming out from left field, as we have in the portfolio as well. But do you feel like the competitive dynamic is shifting more toward applications?

Anish Acharya

100%. It's sort of a renaissance for being a consumer builder because you've got this extraordinary primitive that you can work with. By the way, we now have a primitive that can operate in the emotional, interpersonal domain. You can have a conversation with Claude or OpenAI or K3 and feel feelings. We've had 40 years of technology that really boosted our intellect and productivity, but nothing that spoke to our humanity.

So it's a whole different technology surface, and it's very wide. I think there are a set of products that labs are just not culturally set up to go after, and big tech isn't set up to go after them either. Think about launching a companion product at Google that may disagree with you, that may have sexual innuendo in it. These are things that a thousand committees at Google are designed to prevent.

So startups have areas where they're uniquely capable. And then, finally, the consumer is excited to download new software, excited to pay for it. It's like Christmas 2009 with the iPhone. People want to try new apps, but unlike the 99-cent days, they're willing to pay $200 a month. So it's sort of a renaissance for consumer builders, and, yeah, I think things have changed.

Jen Kha

Anish, dropping Birkin bag–framed jeans. I had no idea you were such a fashionista. This is like your butt is helping you get up to C-suite here, my friend. Uh, for a guy secret is a good steward of capital. Okay, that's all that I am.

Anish Acharya

For a guy I only see in quarter-zips, I'm just saying.

8. Who's Actually Building Apps Today? Founder Archetypes

Jen Kha

Okay, maybe one question for you on the founders, because I don't know if you remember this conversation. This is probably 5 years ago or so, when most of the founders you saw had more diversity in their backgrounds, in part because the software and technology were way more sophisticated. So you had a lot of program managers spinning out of Google, for example, and starting a company. What are the types of founders you see building apps today? Do they tend to lean more technical, more researcher-derived? Are they product managers? What kind of archetype are you seeing in at least the early innings of apps coming out of the woodwork?

Anish Acharya

Yeah. Less MBAs, more researchers, and they both have their strengths and weaknesses. I think the business sophistication of the founders we're seeing today is lower, but the technical sophistication is dramatically higher, and the technical sophistication is upstream of all the good things that happen. Business sophistication can be taught and observed, but technical sophistication typically cannot.

So we're definitely seeing a much more technical, earlier-career founder, but the things they're doing are extraordinary because they don't have any preconceived notions about what's possible. And so much of what holds back senior founders that don't quite get to the other side of this product cycle is that they're not close enough to the technology, and they've got an idea that's rooted in the past of what the ceiling is.

I think the best thing about these young founders is they assume everything is possible. We are at an offsite where Ben was saying that the biggest risk with ideas in the past was that they were too big, and now the biggest risk is that the ideas are too small. But I think that's illustrative of the different founder archetypes.

9. Why Giving Founders Too Much Money Isn't Fatal Anymore

Jen Kha

Yep. And maybe on that similar thread, it used to be that if you gave a founder too much money, it would wreck the company, because the founder almost always has way too many ideas and is a visionary and doesn't have the talent to land all those ideas commensurately. We're seeing a whole new paradigm on that. Maybe unpack that idea a little bit more, because it was such a huge theme of the offsite.

Anish Acharya

Yeah, for sure. This was a historic wisdom. Why didn't we give every seed company $20 million, $50 million, or $100 million? It wasn't just the risk-reward, but rather, typically, the constraining factor was that they just didn't have enough talented people to work across $20 million of product surface at the same time. They really had to focus on 1 idea at a time, and the capital was a great way to enforce that focus.

What we're now seeing is that you could make different sorts of product and model trade-offs through more or less capital. And there is a case for a company that raises $100 million, uses it productively and in a focused way, and is able to deliver a different value proposition than the very same team would be able to do with $20 million.

So I think that, again, just as we talked about the fog of war around margins, this question of what is the optimal seed-round size and how much capital can you put to work effectively is a much more nuanced topic. It's sort of an embarrassment of riches, but I'd rather have this problem than the problem we had 5 years ago, which is: “Hey, my fintech company is indirectly subsidizing its customers through weak underwriting, and we don't know the path home.”

Jen Kha

Yeah. Yep. Yeah. The Chris Dixon model, which is: You always want the problem of supply, not of demand. Right now, we have to fix the supply part, right? But the demand is so abundantly there that undoubtedly the supply part will get fixed.

10. Go-to-Market for Startups Selling to SMEs

Maybe I'll close on this one last question for Anish. Double-clicking on the theme of sector adoption of AI, unlike large enterprise, the friction of adoption is much less because they require less change management. I agree with much of that, but not all. Small and medium-sized businesses sometimes have more habit change that you have to work through.

But the question is: how do you see the go-to-market playbook for startups targeting SMBs, and has that changed in the age of AI?

Anish Acharya

For existing SMBs, I think it's the same channels through which you historically reach them. I actually think one of the interesting things about marketing in the age of AI is that all of the existing networks have been so trained on the methodology of building new networks that they're very careful to ensure no one does it on their network. Instagram, TikTok, and X—it's very hard to build a new distribution channel off the backs of an existing one.

So what founders have to do is actually build a product that has the original network effect, which is word of mouth. We're definitely seeing more of a focus on word of mouth. The old channels for reaching them are still there.

I actually think the most interesting segment of the market, though, is new business formation, which is, by the way, at an all-time high. I think it's the highest it's been outside of a peak moment during COVID. These are people who would have never otherwise been business owners. It's not the sort of 55-year-old plumber; it's a 25-year-old who previously would have been a YouTube creator and now is building SaaS for their neighborhood, their city, their high school, or whatever else it is.

Jen Kha

Yep. Yep. Awesome. Well, thank you so much for listening. It's always great to have you on. Now, I know you're a fashionista, and we're going to be clipping that endlessly on the socials. But thank you for that. And if folks have any questions, you know where to find Anish. We'll follow up here on some of the questions we weren't able to get to as well.