<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a" -->

---
title: a16z just bet $47M that Salesforce is the wrong shape...
description: Lightfield raised a $47M Series A led by a16z, positioning itself as a CRM built from the ground up for AI agents rather than humans, arguing that Salesforce...
canonical: https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: a16z just bet $47M that Salesforce is the wrong shape for AI agents | daily.dev
og:description: Lightfield raised a $47M Series A led by a16z, positioning itself as a CRM built from the ground up for AI agents rather than humans, arguing that Salesforce...
og:url: https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a
og:image: https://api.daily.dev/og/posts/BZLl1bA7A.png
og:image:alt: a16z just bet $47M that Salesforce is the wrong shape for AI agents
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# a16z just bet $47M that Salesforce is the wrong shape for AI agents

**[Trends](https://daily.dev/sources/trends)** · 2 min read · 0 upvotes · 0 comments

## Summary

Lightfield raised a $47M Series A led by a16z, positioning itself as a CRM built from the ground up for AI agents rather than humans, arguing that Salesforce and HubSpot's data models are structurally mismatched for agentic workflows. Its product continuously models each customer from calls, emails, and meetings, then runs agents for pipeline scoring, meeting prep, call summaries, and follow-ups, configurable via prompts and accessible through API, MCP, and CLI. Developers reacted enthusiastically, framing incumbent CRMs plus bolted-on agents (Salesforce Agentforce, HubSpot Breeze) as fundamentally limited by human-shaped data. The open question is whether enterprise buyers will actually switch CRMs, a notoriously sticky software category.

## Content

Lightfield closed a $47M Series A led by a16z, and the framing around it is more interesting than the funding number.

The core argument: every AI agent workflow built on top of Salesforce or HubSpot is sitting on a foundation that was never designed for agents. Those systems were built for humans to manually log things, search things, and hand things off by talking to each other. When you drop an AI agent into that stack, it inherits all the same context gaps that made human handoffs painful. The meeting prep agent doesn't know what the follow-up agent promised yesterday. You've automated the work and kept the problem.

Lightfield's answer is to rebuild the record layer from scratch. Every customer interaction — calls, emails, meetings, Slack threads — gets pulled into a continuously updating model of that customer. The key detail is the interface: every record is readable *and* writable through API, MCP, and CLI. That's not a CRM with an API bolted on. It's a data layer that agents can actually work from without a human in the middle translating.

The reaction in developer circles has been mostly positive, with a few people flagging that this is a bigger idea than it looks. One take that's circulating: "If AI agents are going to make business decisions, they need an accurate model of the business first." That's the real pitch — not better CRM features, but a world model for the business that agents can read and write against.

The skeptic's version of this story is that it's a well-funded bet on a specific architecture (MCP, agent-native records) that hasn't proven out at scale yet. The optimist's version is that Salesforce's $300/seat pricing and $100k+ admin overhead is a sitting target, and the first CRM that agents can actually use without human babysitting wins the whole market.

Co-founder Keith Peiris is positioning CRM as the beachhead, with the obvious implication that a continuously-updating business world model doesn't have to stop at customer records. Whether that expansion happens or whether this stays a niche tool for agent-heavy sales teams is the open question.

## Questions this post answers

### What is Lightfield and how is it different from Salesforce Agentforce or HubSpot Breeze?

Lightfield is a CRM built from scratch for AI agents rather than humans, having raised a $47M Series A led by a16z. Unlike Salesforce's Agentforce or HubSpot's Breeze, which layer agents on top of human-designed data models, Lightfield continuously builds a customer context model from calls, emails, and meetings, and exposes every record via API, MCP, and CLI for agent access.

_Developers weighing agent-native tools versus retrofitted incumbents can follow CRM and AI agent shifts on daily.dev._

### Why do AI agents underperform when added on top of existing CRMs like Salesforce?

Agents underperform because they are fighting an underlying data model designed for humans, not machines, so they lack enough structured context to reason over a full customer relationship. Lightfield's pitch is that context itself is the product: without a reasoning-ready history of interactions, an agent is effectively just autocomplete wrapped around a CRM login.

_Teams debating whether to bolt AI onto legacy systems or adopt agent-native tools can track this reasoning on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 8 comments across x (as of 2026-09-11).

**TL;DR:** Replies engage mostly with the 'business world model' framing, debating whether it's a genuinely new coordinate system for agents or just a richer CRM graph dressed up in bigger language.

**Sentiment:** 25% positive · 45% mixed · 30% skeptical

**The case for**

- The CRM-first approach is seen as pragmatic, grounding the world-model concept in a place businesses already operate.
- Some frame the business world model as a useful new coordinate system for coordinating complex agent work.

**The pushback**

- A CRM only records the path taken, not counterfactuals, so it may lack what's needed to actually be a 'world model'.
- Getting an agent to pull the right slice of context into each run is seen as harder than building the model itself.
- Skepticism about whether the system truly rolls state forward (e.g. predicting future deal/quarter moves) or is just a queryable CRM graph with a new label.

**By community**

- x (mixed): Replies are split between viewing the business-world-model framing as a genuine advance and doubting it's more than a relabeled CRM graph, with one reply questioning whether it can even qualify as a world model without counterfactual reasoning.

**Hottest debate:** Whether the 'business world model' is conceptually distinct from a CRM graph or just marketing language for the same thing.

**Open questions**

- Does the model actually roll state forward to simulate outcomes like closing a deal or next quarter's moves, or does it just let an agent query a richer graph?
- Can an agent reliably pull the relevant slice of the model into context on each run, rather than the data merely existing?

**Highlights**

> @omarsar0 @lightfld a world model has to answer what would have happened if you had not made the call. a crm only records the branch you took. without the counterfactual there is nothing to roll out, just a very detailed history
> — [unpaidneuron on x · 1 points](https://x.com/unpaidneuron/status/2098194538875809832)

> @omarsar0 @lightfld Building the model is the easy part - proving the agent actually reads the relevant slice into context each run is harder. Even a simple session profile file hits this: presence isn't usage. A full business world model just scales that gap up.
> — [MaximTitarenko on x](https://x.com/MaximTitarenko/status/2098172243486367891)

> @omarsar0 @lightfld does their world model actually roll state forward, close this deal and next quarter moves, or is it a richer CRM graph the agent queries?
> — [ethereaglehq on x](https://x.com/ethereaglehq/status/2098175782107361654)

> @omarsar0 @lightfld The CRM-first angle is smart Starting where businesses already live makes the world model practical instead of abstract
> — [Blum\_OG on x](https://x.com/Blum_OG/status/2098169031090110588)

**Source threads**

- [x](https://x.com/omarsar0/status/2098168545393701327) · 0 points · 6 comments
- [x](https://x.com/trikcode/status/2098320776889839751) · 1 points · 2 comments

## Similar posts on daily.dev

- [How Agentforce Lead Nurturing Agents Generated $100M\+ Pipeline](https://daily.dev/posts/how-agentforce-lead-nurturing-agents-generated-100m-pipeline-slcgsquqk) · Salesforce Engineering · 1 upvotes · 0 comments
- [Lightsage raises $4M to build the growth stack for software’s newest customer](https://daily.dev/posts/lightsage-raises-4m-to-build-the-growth-stack-for-software-s-newest-customer-yimygilu2) · The Next Web · 1 upvotes · 0 comments
- [Reimagining the CRM: Salesforce as a UI, Snowflake as the Brain](https://daily.dev/posts/reimagining-the-crm-salesforce-as-a-ui-snowflake-as-the-brain-kj8tmoluh) · Snowflake Community · 0 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#venture-capital](https://daily.dev/tags/venture-capital), [#mcp](https://daily.dev/tags/mcp), [#salesforce](https://daily.dev/tags/salesforce), [#crm](https://daily.dev/tags/crm)

[View this post on daily.dev](https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"a16z just bet $47M that Salesforce is the wrong shape for AI agents","url":"https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a"},"datePublished":"2026-09-09T16:36:47.636Z","dateModified":"2026-10-15T02:22:20.731Z","description":"Lightfield raised a $47M Series A led by a16z, positioning itself as a CRM built from the ground up for AI agents rather than humans, arguing that Salesforce...","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,venture-capital,mcp,salesforce,crm","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"a16z just bet $47M that Salesforce is the wrong shape for AI agents"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a16z-just-bet-47m-that-salesforce-is-the-wrong-shape-for-ai-agents-bzll1ba7a#faq","mainEntity":[{"@type":"Question","name":"What is Lightfield and how is it different from Salesforce Agentforce or HubSpot Breeze?","acceptedAnswer":{"@type":"Answer","text":"Lightfield is a CRM built from scratch for AI agents rather than humans, having raised a $47M Series A led by a16z. Unlike Salesforce's Agentforce or HubSpot's Breeze, which layer agents on top of human-designed data models, Lightfield continuously builds a customer context model from calls, emails, and meetings, and exposes every record via API, MCP, and CLI for agent access. Developers weighing agent-native tools versus retrofitted incumbents can follow CRM and AI agent shifts on daily.dev."}},{"@type":"Question","name":"Why do AI agents underperform when added on top of existing CRMs like Salesforce?","acceptedAnswer":{"@type":"Answer","text":"Agents underperform because they are fighting an underlying data model designed for humans, not machines, so they lack enough structured context to reason over a full customer relationship. Lightfield's pitch is that context itself is the product: without a reasoning-ready history of interactions, an agent is effectively just autocomplete wrapped around a CRM login. Teams debating whether to bolt AI onto legacy systems or adopt agent-native tools can track this reasoning on daily.dev."}}]}
```

