Applied AI and the LLM Adoption Curve

Apr 12, 2024
Applied AI and the LLM Adoption Curve
Interested in reading more?

Sign up for our Enterprise Weekly Newsletter.

We'll send you our top, curated content straight to your inbox (along with top industry news, events, and fundings).

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

There are two ongoing, but divergent trends afoot in enterprise software that are taking up a lot of airspace for companies building in Applied AI. Both are catalyzed by the emergence of Large Language Models (LLMs), and while these trends might not be so different from how software companies have historically been founded, given that all eyes are on AI, they feel more palpable today than ever before:

  1. A reimagination of traditional software
  2. Unlocking new workflows for greenfield use cases

The divergence in these two use cases boils down to LLMs and its power to democratize access to AI and machine learning capabilities. LLMs are turning the traditional applied AI market on its head. While full stack machine learning was once a competitive advantage for teams of highly trained PhDs, it is now just an API call away.

For example, back when I was a Product Manager at Hyperscience, it took us years to acquire the raw training data needed to build proprietary models that beat out traditional optical character recognition (OCR) techniques for document extraction. Today, generally available LLMs and other task specific models can abstract away the need to spend significant time and money building out these workflows all out of the box.  

As a result, every company is now an AI company, fostering a new ethos in how products are built.

Emerging Themes in AI-Native Companies

Startups are building AI-native products from the get-go in hopes of either disrupting traditional incumbents with more powerful and productive software, or leveraging AI/ML to build products for net-new use cases once overlooked for being too technically challenging. As a result, we’re seeing products that unearth new experiences and modalities for human: machine interaction.

The New Playing Field In Applied AI
A Reimagination of Traditional Software
Category Traditional Software New Player
Automation
Lead Generation
Content Marketing
Legal e-Discovery
Unlocking New Workflows for Greenfield Use Cases
Category New Player
Coaching for Field Sales
Code Completion
Video Creation
Clinical Transcription

But even as many companies across both categories have captivated users and quickly grown in popularity, not all that shimmers is gold:

  1. There are fewer barriers to entry in application software today than ever before
  2. This leads to more competition as ideas are commoditized
  3. No company leveraging third-party LLMs has any inherent competitive advantage
  4. As a startup, speed and sales execution is the best way to win another day (and hopefully build towards a moat) and keep fighting  

Competition Is Heating Up in The Race for Applied AI Dominance

As the price to develop and integrate applications with AI/ML drops, so do the barriers to entry, leading to a sea of competitors across both existing and net new use cases.

While we already knew that no startup idea is truly unique, we’re seeing an influx of founders scanning the market to find use cases they can attach AI capabilities to. To this extent, we’re seeing a concentration of companies emerge across the different functions of sales, marketing, code generation, API generation, video generation, and many more use cases. Not to say these companies won’t be successful, but founders need to be aware of the number of new entrants trying to capitalize on the same AI paradigm shift.

Applied AI Remains Highly Competitive Across Verticals
The Reimagination of Traditional Software
Category Players
Automation
Sales
Content Marketing
Legal e-Discovery
Unlocking New Workflows in Greenfield Use Cases
Category Players
Coaching for Field Sales
Code Completion
Video Creation
Clinical Transcription

In the past generation of SaaS companies, those that entered competitive markets aimed to differentiate from the pack by expanding their product surface area to own more of the workflow or by creating a unique GTM motion:

  • For example, our portfolio company Dialpad operates in the highly competitive Unified Communications (UCaaS) space against incumbents like Avaya and RingCentral. In the early days, Dialpad introduced a modern communications product that emphasized the importance of an enhanced user experience. Paired with faster development cycles than sleepy incumbents, the company ate away at incumbent market share, and crossed the $200M+ ARR mark back in 2023.
  • Similarly, our portfolio company Socure did the heavy lifting to build an enterprise grade product from day one. This enabled them to authentically build trust with early adopters like Bank of America. By landing several bulge-bracket banks early in their GTM journey, their base ML-model continuously improved and the company had a stronger story for each net-new customer pitch within the Fortune 500 customer segment.

However, today, many AI-native companies are taking a different route: they’re going after niche wedges in big markets, seeking to capture key customer data that will over time help improve their product’s value as they aim to automate more and more of the customer’s workflow and show customers more value relative to the competition. On top of that, many AI-native companies are aiming to differentiate on the model level by leveraging techniques like Retrieval Augmented generation (RAG), finetuning models with specific datasets, or by daisy chaining LLMs & SLMs together for a specific business need.

The only problem? It’s almost exactly what every AI-native company I meet brings up: start with accessible models, add customer data to refine model outputs, and over time acquire enough data through your unique workflow to create your own model, and finally have true competitive advantage by owning the data layer.

To that point, every applied AI company falls somewhere on what I’m calling the LLM Adoption Curve:

Work-bench

V1: Closed-Source LLM: Companies leverage out-of-the-box LLMs to demonstrate validation for their use case. This works good enough for basic tasks and workflows with a human in the loop

V2: LLM + RAG: As the use case gets more customer validation, experienced product builders leverage existing data to improve model inference via retrieval augmented generation (RAG)

V3: Fine Tuned LLM: As customer validation scales, startups seek to optimize model cost and performance by fine tuning an existing model based on the specific use case

V4: Fully Custom LLM: Over time, companies seek to acquire enough data to build their own model trained on relevant customer data and use these models to better serve customer’s use cases and beat out the competition

While the above looks like a great strategy in theory, in practice the competition is heating up and sees a similar future for their products.

To determine how to truly differentiate AI companies from the growing herd, here are a few key questions I’m thinking about:

  1. When is the right time for startups to churn off of generally available LLMs and make their own models?
  2. Is there a future where generally available LLMs like GPT-5, Claude 4, or DBRX-2 will  be good enough that companies don’t need to RAG, fine tune, or even build their own?
  3. Can companies even survive long enough to build their own models? Our portfolio company Dialpad built DialpadGPT off of 5 billion minutes and 10+ years of proprietary customer data.
  4. Many startups are aiming to unseat scale-ups, not even true legacy incumbents. So, how do scaleups and incumbents pivot to add their own AI twist?
  5. How can companies better evaluate build vs. buy frameworks at their target ICP to better understand if there’s real venture-scale opportunity here?
  6. How do agents impact all this?
  7. Investing in a net-new AI startup going head-to-head with an incumbent with distribution sounds like a losing battle. In the future, do companies need to own enough of the data and workflow layer from the outset to train their own model and become a proprietary player? Or will models be so generalizable that you don’t need to?

As we continue to dig into these questions, we’re eager to speak with more founders, practitioners, and builders in the category. And if you’re an early stage startup building in the future of AI, I’d love to hear from you!

TOPICS
Research
SHARE