Sierra didn’t build an Agent Data Platform because it wanted more product surface to sell. It built one because an agent platform valued at over $15 billion, already running inside over 40% of the Fortune 50, still couldn’t act on a customer’s order or account from raw CRM and billing records alone. That gap is where Atlan enters the story, not as a Sierra competitor, but as the governed context layer underneath it and its closest rivals, Salesforce Agentforce, Intercom Fin, Decagon, Ada, and Zendesk AI. Sierra itself, launched publicly in February 2024 by former Salesforce co-CEO Bret Taylor and former Google VP Clay Bavor, charges when its agent achieves an agreed outcome rather than per seat, a bet that only pays off if the agent can reach data good enough to resolve something real.
Sierra’s own product roadmap is the clearest evidence for that positioning. The company built an Agent Data Platform specifically because raw, scattered customer records across CRM, billing, and order systems were never usable by an agent on their own; Sierra’s own framing describes it as unifying “everything your company knows about a customer” into one layer. Atlan connects to that same MCP-native ecosystem through its own MCP server, carrying the lineage, ownership, and business-term definitions that a customer-facing agent needs but that no single vendor’s platform natively holds.
- Ghostwriter: Sierra’s agent-building agent
- Agent Studio: the no-code layer for building and managing agents, with 40+ pre-built integrations
- Horizon: long-horizon agents that pursue a goal across days and weeks
- Context Engine: memory, signals, and personalization, fronting the Agent Data Platform Sierra launched in November 2025
- Enterprise Data Graph: Atlan’s lineage, ownership, and certification layer for what Sierra’s own context layer doesn’t ingest
| Sierra: Quick Facts | |
|---|---|
| What it is | Conversational AI agent platform for enterprise customer service |
| Founders | Bret Taylor (ex-Salesforce co-CEO, founder of Quip, ex-CTO of Facebook), Clay Bavor (18 years at Google, led Google Labs) |
| Funding/valuation | $950M raised May 2026, led by Tiger Global and GV, at a valuation of over $15 billion |
| Pricing model | Not published. Outcome-based, contracted per deal, with consumption pricing offered for routing and greeter interactions |
| Key customers | Airtable, Chime, ADT, WeightWatchers, Sonos, SiriusXM, Redfin, CarMax, SoFi, Rocket Mortgage and roughly 25 more named on sierra.ai/customers |
| Core components | Ghostwriter, Agent Studio, Horizon, Context Engine, Insights, Explorer, Channels |
| Compliance | SOC 2 Type II, ISO 27001, ISO 42001, AIUC-1 and PCI DSS Level 1 Service Provider |
What is Sierra?
Sierra is a conversational AI agent platform built to let enterprises deploy customer-facing AI agents rather than scripted chatbots. Sierra’s own About page describes Taylor as the former co-CEO of Salesforce, founder of Quip, CTO of Facebook and co-creator of Google Maps, and Bavor as an 18-year Google veteran who led Google Labs and started the company’s AR/VR effort. Sierra dates itself from its public launch: “we launched in February 2024,” it wrote when announcing $100 million in ARR.
Sierra’s growth since has been fast even by AI-startup standards. Sierra hit $100 million in ARR seven quarters after that February 2024 launch, then reported over $150 million in ARR entering its third year in February 2026. In May 2026 it announced it was raising $950 million from new and existing investors, led by Tiger Global and GV, at a valuation of over $15 billion, up from the $10 billion valuation on the $350 million round Greenoaks led in September 2025. That trajectory is a genuine data point for how enterprises use AI agents at scale, not just a funding headline.
Sierra says it serves over 40% of the Fortune 50, and its own customer index names roughly 35 companies including Airtable, Chime, ADT, WeightWatchers, Sonos, SiriusXM, Redfin, CarMax, SoFi and Rocket Mortgage. Sierra sizes that base directly: “one in four of our customers has revenue over $10 billion and 50% over $1 billion.” Sierra’s current product surface is Ghostwriter (an agent-building agent), Agent Studio (no-code build and management), Horizon (long-horizon agents), Context Engine (memory, signals and personalization), Insights, Explorer and Channels. Agent OS remains Sierra’s developer platform term and Agent SDK its developer layer, though neither is a top-level product page today. Agent Data Platform, launched November 2025, is the memory layer that Context Engine now fronts, and it carries most of the weight in this page’s argument. Sierra sits in the same competitive lane as Salesforce’s Agentforce 360, Intercom Fin, Decagon, Ada, and Zendesk AI, each a vendor-native AI agent platform built to be the default place its customers deploy conversational agents.
How does Sierra’s AI agent platform work?
Sierra’s architecture layers a “constellation of models” under a supervisor, with a separate context layer responsible for unifying what the agent knows about a specific customer. Each layer below handles a distinct part of how an agent decides what to say and whether it’s allowed to say it.
The constellation of models
Rather than routing every request through one monolithic LLM, Sierra assembles agents from “15+ frontier, open-weight, and proprietary models, depending on the job to be done”, the same layered pattern described generally in how AI agents work. Sierra names none of the providers behind those models. It does publish the failover behavior: the platform “automatically switches between LLM providers to optimize your agent’s performance and maintain service continuity.” Agent OS is Sierra’s term for the platform tying that constellation together, and its “Agent OS 2.0” framing describes the evolution as moving from answers to memory and action, not just single-turn responses.
The supervisor architecture
Sierra’s supervisors are real-time guardrails that review each response as it is generated, verifying facts, enforcing policy and redirecting conversations before the agent replies. In Sierra’s own words, a supervisor is “a Jiminy Cricket for each agent that sits on its shoulder and keeps it honest.” That’s a genuinely credible piece of engineering, and it’s worth naming clearly here because the rest of this page returns to a distinction the supervisor doesn’t resolve on its own: catching a bad response is different from governing what customer data an agent is allowed to reach in the first place.
Context Engine and the Agent Data Platform
Sierra introduced the Agent Data Platform to unify “everything your company knows about a customer… across sessions, channels, and systems” into one layer an agent can query, built because agents were “forgetting almost everything they learned the moment the conversation ends.” On Sierra’s product site today that function is fronted by Context Engine, which covers memory, signals and personalization and integrates with systems of record. Sierra has published no rename notice, so both names are still in circulation. Either way, the admission is the same: raw, scattered enterprise data isn’t usable by an agent without a unification step first, the same gap context engineering exists to close one layer below any single agent vendor.
Horizon and long-horizon agents
Sierra’s 2026 roadmap moved past single conversations. Horizon, launched July 2026, is “a platform that enables agents to pursue long-horizon goals, like originating a loan or getting prior authorization for a healthcare procedure”, work that runs across days and weeks rather than one session. A week later Sierra acquired Takeoff, a long-horizon agent runtime operating in lending and healthcare. The longer an agent’s goal runs, the more it depends on customer, account and policy records staying consistent the whole way through, which is a governance question before it is a runtime one.
Agent Studio, Agent SDK and what Sierra publishes about integrations
Agent Studio gives non-technical teams a no-code way to build and manage an agent’s behavior. Sierra publishes 40+ pre-built integrations into third-party knowledge bases, systems of record and contact centers, configurable directly in Agent Studio, with the Agent SDK as the extensibility path for proprietary systems. What Sierra does not publish is which 40+ systems those are. It names no CRM, no ticketing platform and no contact-center vendor in its public integration material, and docs.sierra.ai is login-gated, with sign-in terms stating access is granted “solely to evaluate” the products. So an enterprise cannot confirm coverage for the specific systems it runs without a sales conversation, and the context an agent needs about a customer’s order or account still has to be reconciled against enterprise data the company controls.
The Agent Data Platform can be read as Sierra’s own acknowledgment that raw, scattered customer data isn’t usable by an agent without a unification step, though Sierra would likely frame it as forward-looking product design rather than a gap being closed. Either read points at the same underlying job: unifying context Atlan’s context layer also does one level below the agent itself, across systems no single agent vendor holds.
| Aspect | Traditional scripted bot/IVR | Sierra’s agent architecture |
|---|---|---|
| Resolution approach | Fixed decision trees, keyword matching | Constellation of models reasoning over intent |
| Escalation logic | Hard-coded rules, frequent dead ends | Supervisor-checked handoff to a human when scope is exceeded |
| Context handling | Session-only, no cross-channel memory | Context Engine unifies memory and signals across sessions and channels |
| Pricing basis | Per seat or per message | Per agreed outcome, with consumption pricing for routing interactions |
| Update cadence | Manual script edits | Continuous model and policy updates via Agent Studio |
Sierra's Context Engine already unifies session and channel memory. What it doesn't resolve on its own, definitions like "resolved," cross-system lineage, and systems outside the 40+ integrations Sierra never names, is where an external MCP server picks up.
Get the CIO's guide to context graphs
See the four-layer architecture data leaders use to give agents like Sierra's context beyond their own platform, from metadata foundation to agent orchestration.
Get the CIO GuideWhat is Sierra’s outcome-based pricing model?
Sierra does not publish pricing. There is no pricing page on sierra.ai and no dollar figure appears anywhere on its site. What Sierra does publish is the model: “you pay only when the software achieves specific, valuable outcomes”, counted as resolved conversations, ecommerce purchases or memberships saved, with criteria agreed upfront per contract. Sierra qualifies the escalation case rather than exempting it outright: if a case needs to be escalated, “in most cases, there’s no charge.” It also offers a consumption model where outcome pricing doesn’t fit, since “routing or greeter-style interactions may align better with consumption-based pricing, where payment is based on conversation count, regardless of the outcome.” Third-party estimates of what a Sierra contract costs circulate widely, most of them published by vendors selling against Sierra, and this page holds off on repeating any of them until Sierra confirms a figure directly. Practitioner skepticism persists about whether “resolved” is defined consistently across contracts, and what happens when the same customer issue recurs days later.
A pricing model built entirely on “resolved” only holds up if every system involved, the agent, the billing platform, and the human team that handles escalations, agrees on what “resolved” actually means. That’s a governed-definition problem, not a pricing problem, and it’s the exact gap Active Ontology is built to close before an agent acts on a term whose meaning shifts depending on who you ask. Teams evaluating what a resolution-based model costs at scale should model it the same way they’d model the cost to run AI agents at scale on any platform, since resolution volume, not seat count, drives the bill.
Sierra’s enterprise use cases: where it delivers results
Sierra’s clearest published results come from subscription and account-servicing workloads, and voice became its biggest channel early.
Subscription and cancel-flow handling (WeightWatchers)
WeightWatchers’ Sierra agent contained roughly 70% of cases in its first week at a 4.6 CSAT, the most concrete customer proof point Sierra publishes. That’s the kind of deflection enterprise-ready AI agents are meant to produce once a company trusts them with real subscription and cancellation conversations, not just demo scripts.
High-volume account servicing (ADT)
ADT’s Sierra agent handles 1.2 million customer inquiries a month, a scale that puts real pressure on how well the agent’s context about a specific account and service history stays consistent across every interaction. Sierra publishes per-customer outcome figures like this rather than a single platform-wide resolution rate: an 80% resolution rate at Airtable, 70%+ at Chime, 4x conversion at Rocket Mortgage.
Voice as the primary channel
Sierra acquired the voice-agent company Receptive AI in March 2025 and said at the time that voice had already become its biggest channel, having been available only since the previous October. Sierra now deploys one agent across chat, voice, email and SMS. The same scaling questions apply here as in how to scale AI agents from POC to production, and the same context dependency many enterprises hit when they extend agents beyond support into AI agents for sales.
What Sierra’s own material leaves an enterprise unable to check?
Two things an enterprise needs before it signs are absent from everything Sierra publishes, and both are verifiable gaps in the public record rather than claims about the product’s quality.
The first is integration coverage. Sierra publishes the count, 40+ pre-built integrations, and never the list. No CRM, ticketing system or contact-center platform is named anywhere in its public integration material, and docs.sierra.ai sits behind a login whose terms state that access is granted “solely to evaluate” the products and that “all Sierra Products are confidential.” A buyer running a fifteen-year-old billing system or a regional contact-center suite has no way to establish, from public material, whether it is one of the 40+ or a build.
The second is cost. Sierra publishes no pricing page and no dollar figure, so finance cannot get a directional number without a sales conversation. The model itself is published in detail and is genuinely coherent. The price is not.
Neither gap is evidence that the platform is weak. Sierra’s own trust posture cuts the other way: it holds SOC 2 Type II, ISO 27001, ISO 42001 and PCI DSS Level 1 Service Provider certification, added AIUC-1 in September 2026, a standard built specifically to test how agents actually behave, and routes payment data through dedicated PCI-certified infrastructure that “never touches Sierra’s core platform, LLMs, or persistent storage.” That is a stronger published governance boundary than most vendors in this category offer.
Sierra’s own 2026 product direction shows where the remaining work sits. The company shipped Agency, secure sandbox infrastructure for its agent-building tools, and Agent Studio Experiments, a framework for A/B testing agent behavior against resolution rate and churn reduction. In the Agency launch post, Sierra’s engineering team wrote plainly that the hardest part of building great agents stopped being the model and became everything surrounding it, a genuine admission that a capable model and good guardrails were never going to be the whole story. Sandboxing, release governance and behavior A/B testing are real, useful infrastructure. They solve a different problem than governing what an agent is allowed to know and say about one specific customer’s order or entitlement, a distinction covered more broadly in AI agent accuracy and in AI agent risks and guardrails.
The governed-context gap this section describes is exactly what an external context layer addresses, one level below any single agent vendor’s guardrails, the same argument covered in securing multi-agent systems in the enterprise and in AI agent governance broadly, and in AI agent access control for the specific case of an agent taking real actions like issuing a refund.
Check your context readiness before you scale
Most conversational agent rollouts stall on data readiness, not the reasoning engine. Run through the checklist enterprises use to spot gaps before scaling past a pilot.
Assess Your ReadinessHow does Sierra fit into an enterprise AI agent stack?
Evaluating Sierra alongside other conversational agent platforms means checking connector coverage and context governance before committing, not just which model sounds most fluent in a demo. Every platform in Sierra’s competitive set, Salesforce Agentforce, Intercom Fin, Decagon, Ada, and Zendesk AI, faces the same evaluation questions once an agent needs data the vendor’s own platform was never built to hold.
Before committing to a context strategy for any of them, ask whether it reaches data the vendor’s own context layer doesn’t already hold, who resolves what “resolved” or “entitled to refund” means before an agent acts on it, and what happens when the platform needs a system it doesn’t natively connect to. Getting these answers right is what separates agents that hold up under how to build an AI agent tech stack planning from the ones that stall once they meet real customer data instead of a clean demo, the same pattern covered in how to make AI agents context-aware.
| Criterion | Why it matters | What to look for |
|---|---|---|
| Native connector coverage | Sierra publishes 40+ pre-built integrations and names none of them | A context source that reaches data across the estate, not just one vendor’s integration list |
| Context governance & definition consistency | Outcome-based pricing depends on a shared definition of “resolved” | A certified semantic layer resolving one definition per term |
| Pricing transparency | Sierra has no pricing page and publishes no dollar figure | Clear, auditable pricing tied to a verifiable outcome |
| Guardrails vs. governed context | Supervisor guardrails check behavior, not data scope | Policy enforcement checked at the point the agent acts on a specific record |
| Cross-system reach beyond CRM/helpdesk | Context Engine unifies session and channel memory, not every SaaS tool | An open, MCP-compatible context source alongside the Agent SDK |
Sierra’s rapid customer growth also raises the same operational question every fast-scaling platform faces: how to build an AI agent harness robust enough that adding volume doesn’t mean adding risk, and why more teams are treating why AI agents need an enterprise context layer as a prerequisite rather than an afterthought once an agent is handling thousands of real customer conversations a day. The enterprise context layer question isn’t specific to Sierra; it recurs across Gemini Enterprise and AWS Bedrock for enterprise agents too, and how to implement an enterprise context layer for AI walks through the same evaluation regardless of which vendor’s agent sits on top.
How Atlan approaches context for agents like Sierra
Atlan doesn’t compete with Sierra, and never enters the customer-service conversation itself. What Sierra’s own context layer shows is that a conversational agent is only as trustworthy as the context it can reach about the specific customer, order, account, or policy in question. That context lives across the enterprise’s actual systems of record, CRM, order management, billing, entitlements, not inside any agent vendor’s own platform, Sierra’s included, the same systems-of-record dependency covered for AI agents generally.
Atlan’s MCP server gives any agent, including a Sierra agent wired up via its own Agent SDK, a governed way to query business context, definitions, lineage, ownership, access policy, rather than reasoning over raw, ungoverned exports from a CRM or data warehouse. What Is Atlan MCP? covers the mechanism directly, building on the broader Model Context Protocol standard and how MCP delivers business context to any compliant agent. The Enterprise Data Graph carries lineage and ownership across every connector in the stack, which matters directly for the “does this agent’s answer about a customer’s order actually match what’s true in the system of record” question practitioners already raise in reviews. Active Ontology resolves what a business term means, “resolved,” “active subscriber,” “entitled to refund,” before an agent acts on it, the same context graph discipline that separates a governed definition from a generic knowledge-graph lookup, directly relevant given Sierra’s own outcome-based pricing depends on a shared, auditable definition of “resolved.”
No internal or public source ties Atlan directly to a Sierra deployment, and none should be fabricated here; no Sierra-specific case study exists yet. The architecture claim stands on its own: any agent can query Atlan via MCP, the same real technical relationship regardless of which customer-facing agent vendor a company picks, whether that’s Sierra or an internal knowledge assistant built for employees rather than customers. Teams preparing for this kind of integration should also review how to prepare enterprise data for AI agents and how to connect enterprise data sources to LLMs securely, since Sierra’s own Agent SDK pattern mirrors the same custom-connection work either way.
Real stories from real customers: governed context for customer-facing agents
The MCP-native pattern this page describes for Sierra isn’t specific to any one CX vendor. Atlan’s own MCP server and Enterprise Data Graph already run in production at enterprises solving the same shared-vocabulary and context problem outside any single agent platform.
"We're excited to build the future of AI governance with Atlan. All of the work that we did to get to a shared language at Workday can be leveraged by AI via Atlan's MCP server…as part of Atlan's AI Labs, we're co-building the semantic layer that AI needs with new constructs, like context products."
Joe DosSantos, VP of Enterprise Data & Analytics, Workday
"Atlan is much more than a catalog of catalogs. It's more of a context operating system…Atlan enabled us to easily activate metadata for everything from discovery in the marketplace to AI governance to data quality to an MCP server delivering context to AI models."
Sridher Arumugham, Chief Data & Analytics Officer, DigiKey
See **Context Agents** live
Watch how a governed context layer connects CRM, billing, and order systems, and everything outside them, to AI agents in real time, across systems and vendors.
Watch a Live DemoWhy Sierra’s own roadmap makes the case for an external context layer
Sierra is a real, credible platform, not a thin wrapper on a foundation model. The WeightWatchers containment rate is a genuine production result, and the supervisor architecture is a genuinely sophisticated piece of guardrail engineering. None of that is in dispute.
What’s worth noticing is what Sierra built alongside those wins: the Agent Data Platform and the Context Engine that now fronts it, Agency, and Agent Studio Experiments all exist because a capable model and good behavioral guardrails were never going to be enough on their own. Sierra would likely frame all of them as product maturity rather than an admitted gap, and either read still lands on the same fact: a well-funded, purpose-built agent platform still had to build infrastructure specifically to unify customer context, because the conversation layer and the context about a specific customer’s order or account are two different problems that don’t collapse into one vendor. Behavioral guardrails and governed context-and-scope control are related but distinct disciplines, not the same one wearing two names. As Sierra’s sandbox and behavior-testing tooling matures further, the open question shifts from whether the agent sounds confident to whether its answer matches what’s actually true in the systems of record it can’t see directly, the same test that applies to Salesforce Agentforce and every other vendor-native agent platform in this category, not just Sierra.
FAQs about Sierra
1. Who founded Sierra AI?
Sierra was founded by Bret Taylor, former co-CEO of Salesforce, founder of Quip, CTO of Facebook and co-creator of Google Maps, and Clay Bavor, who spent 18 years at Google, led Google Labs and started Google’s AR/VR effort. Sierra launched publicly in February 2024 as a platform for enterprises to deploy customer-facing AI agents rather than scripted chatbots.
2. What is Sierra AI used for?
Enterprises use Sierra to deploy conversational AI agents for customer service, most commonly subscription and account servicing, cancellation handling, and high-volume support inquiries. Sierra deploys one agent across chat, voice, email and SMS, and said in March 2025 that voice had already become its biggest channel.
3. Is Sierra AI the same company as Sierra Wireless or Sierra Nevada?
No. Sierra AI, launched publicly in February 2024 by Bret Taylor and Clay Bavor, is a conversational AI agent platform for enterprise customer service. Sierra Wireless is an IoT connectivity company and Sierra Nevada is an aerospace and defense contractor; neither is affiliated with Sierra AI.
4. How much does Sierra AI cost?
Sierra does not publish pricing. There is no pricing page on sierra.ai and no dollar figure appears anywhere on its site. Sierra publishes only the model: you pay when the agent achieves an agreed outcome, and in most cases there is no charge when a case is escalated to a person. Sierra also offers consumption-based pricing for routing and greeter-style interactions where outcome pricing does not fit, so confirm the rate directly with Sierra.
5. What is the “supervisor” model in Sierra’s architecture?
Sierra’s supervisors are real-time guardrails that review each response as it is generated, verifying facts, enforcing policy and redirecting conversations before the agent replies. Sierra calls a supervisor “a Jiminy Cricket for each agent that sits on its shoulder and keeps it honest.” It is a behavioral quality-control layer, distinct from governing what customer data the agent is allowed to see.
6. Does Sierra AI integrate with Salesforce, Zendesk, or Shopify?
Sierra publishes 40+ pre-built integrations into third-party knowledge bases, systems of record and contact centers, configurable in Agent Studio, with the Agent SDK as the extensibility path for proprietary systems. Sierra does not publish which 40+ systems are covered, and docs.sierra.ai is login-gated, so an enterprise cannot confirm coverage for a specific CRM or ticketing platform without a sales conversation.
7. How is Sierra AI different from Agentforce or Decagon?
Sierra is a standalone, vertical customer-service agent platform with outcome-based pricing, while Agentforce is bundled into Salesforce’s CRM and priced on consumption credits. Decagon, Ada, and Zendesk AI compete in the same customer-service lane with their own pricing and connector models.
8. How does Atlan connect to an agent platform like Sierra?
Atlan connects through its own MCP server, which a Sierra agent wired up via its Agent SDK can call as an external, governed context source. The Enterprise Data Graph and Active Ontology give that agent lineage, ownership, and consistent definitions that Sierra’s Context Engine does not natively hold.
Sources
- About Sierra, Sierra
- Sierra Just Hit $100M in ARR, Sierra (November 2025)
- Year Two in Review, Sierra (February 2026)
- Better Customer Experiences, Built on Sierra, Sierra (May 2026)
- Constellation of Models, Sierra (December 2025)
- Sierra Agent OS 2.0: From Answers to Memory and Action, Sierra (November 2025)
- Confidence in Every Conversation, Sierra (October 2025)
- Introducing Agent Data Platform, Sierra (November 2025)
- Context Engine, Sierra product
- Agent Studio, Sierra product
- Agent SDK, Sierra product
- Horizon, Sierra (July 2026)
- Sierra Acquires Takeoff, Sierra (July 2026)
- Outcome-Based Pricing for AI Agents, Sierra
- Trust and Reliability, Sierra product
- Sierra Achieves AIUC-1 Certification, Sierra (September 2026)
- Sierra Acquires Receptive AI, Sierra (March 2025)
- Agency: Secure, Scalable Sandboxes for Agents, Sierra (July 2026)
- Sierra Customers, Sierra
- How WeightWatchers Embraces AI to Engage Members with Empathy, at Scale, Sierra customer story
- ADT Customer Story, Sierra
- Sierra Documentation (login-gated), Sierra
