Sierra Pricing

Sierra approaches enterprise AI pricing around outcomes rather than traditional software seats. Instead of tying the commercial model primarily to licenses or messages, Sierra generally charges when an AI agent completes an agreed business result, such as resolving a support request or completing another measurable customer workflow.

The model is straightforward in principle, but enterprise budgeting still depends on the details written into the contract. Buyers need to understand what counts as an outcome, how unresolved or escalated interactions are handled, when consumption pricing applies, and which channels, integrations, and workflows are included.

Key Takeaways

• Sierra centers pricing on completed outcomes, with billing linked to agreed results rather than standard seat-based software access
• Public dollar rates are unavailable, so enterprise pricing requires a custom commercial proposal
• Outcome definitions are central to cost modeling, because the contract determines which completed interactions become billable
• Blended pricing is possible, including consumption-style treatment for interactions that do not map cleanly to a measurable business outcome
• Maven AGI provides a published starting reference, with AWS Marketplace listing a 12-month enterprise contract minimum of $25,000 and final pricing based on scope, complexity, and resolution volume

What Sierra Means by Outcome-Based Pricing

Sierra's commercial model starts with a different question from traditional SaaS pricing: what business result did the AI complete?

A billable outcome can vary by workflow. Examples include:

• Resolving a support conversation
• Saving a cancellation
• Completing an upsell
• Completing a cross-sell
• Achieving another contractually defined valuable outcome

The specific result is established between Sierra and the customer rather than being defined by a universal public rate card.

That distinction matters because two organizations can use the same platform while paying against different outcome definitions.

A support organization may focus on successfully resolved requests. A retention team may define value around saved cancellations. A commerce workflow may connect billing to an upsell, cross-sell, or another measurable action.

Outcome Criteria Come Before Cost Modeling

Before estimating annual spend, buyers need a contractual definition of success.

Questions to resolve include:

• Which event officially completes an outcome?
• Which system records that completion?
• Does an outcome require the entire workflow to finish?
• How are repeat contacts treated?
• What happens if a customer reopens the same issue?
• How are abandoned conversations classified?
• How are disputed outcomes reviewed?

These definitions determine the billable unit and therefore matter as much as the negotiated rate itself.

Human Escalation Is Treated Separately

Sierra's pricing materials state that when a case needs to escalate, there is no charge in most cases.

That wording makes the individual agreement important. Procurement teams should confirm exactly when escalation removes an interaction from outcome billing and how partial completion is treated.

Human support also remains an important part of the operating model for situations requiring judgment, empathy, exceptions, or sensitive communication.

Where Consumption and Blended Pricing Enter the Model

Outcome-based pricing is Sierra's central commercial approach, but Sierra also acknowledges that some work does not map neatly to an attributable business outcome.

In those situations, the company can use consumption-style or blended pricing.

Routing and greeting interactions are one example. The AI may perform useful work without completing a distinct end-to-end business result, making conversation volume a more practical billing unit.

An enterprise proposal can therefore contain different commercial logic across different workloads.

Buyers should determine whether each part of the proposed deployment is:

• Outcome-based
• Conversation-based
• Consumption-based
• Covered by another commercial unit
• Combined into a blended structure

This is especially relevant when a deployment spans multiple customer journeys rather than one narrowly defined support use case.

Five Questions That Shape a Sierra Pricing Model

Sierra does not publish one standard formula that applies to every enterprise. The economics are shaped by how the deployment is designed.

1. What Outcomes Are Being Purchased?

The first question is not simply how many conversations the organization receives. It is which completed results will count as billable outcomes.

A clearly attributable customer-service resolution is different from a greeting, routing interaction, partial workflow, or escalation.

That distinction establishes the foundation for the commercial model.

2. How Often Will Those Outcomes Occur?

After defining an outcome, buyers need to estimate how often the AI is likely to produce it.

Useful inputs include:

• Monthly interaction volume
• Seasonal peaks
• Eligible support volume
• Expected growth
• Current escalation patterns
• Issue categories
• Repeat-contact rates

These assumptions should be tested against actual customer-service data rather than a generic automation target.

3. Which Interactions Sit Outside Outcome Pricing?

A deployment may include work that is valuable but difficult to attribute to one discrete result.

Those interactions should be identified before signing the agreement so finance teams know which workloads use outcome pricing and which use another billing structure.

4. Which Channels Are in Scope?

Sierra supports customer interactions across voice and digital channels, including chat, email, SMS, WhatsApp, and other supported surfaces.

Channel scope matters because an enterprise may begin with one customer journey and later expand into additional interaction types.

The proposal should make clear whether commercial terms change as channels are added.

5. How Will Outcomes Be Audited?

Outcome pricing works best when both sides can see how the billable event was determined.

Buyers should establish:

• Where outcome data is recorded
• Which system acts as the source of truth
• How exceptions are reviewed
• What reporting accompanies invoices
• How disputed outcomes are handled
• Whether definitions can change during the contract

This turns outcome pricing into a measurable operational model rather than an abstract commercial concept.

What the Sierra Contract Supports Beyond Pricing

The billing model should be evaluated alongside the platform used to create those outcomes.

Agent Studio

Sierra's Agent Studio gives teams a workspace for configuring and managing AI agents.

Capabilities include:

• Agent instructions
• Knowledge
• Customer journeys
• Guardrails
• Actions
• Tools and dynamic data
• Integrations
• Escalation behavior

Sierra also provides visibility into agent decisions and tool activity so teams can examine behavior during development and optimization.

Enterprise Integrations

Sierra currently documents more than 40 prebuilt integrations through Agent Studio, along with support for custom integrations.

These connections can link agents with:

• Knowledge systems
• Systems of record
• Contact-center infrastructure
• Customer data
• Business applications

The integrations allow an agent to retrieve context and perform supported actions rather than limiting interactions to informational responses.

Cross-Channel Deployment

Sierra's current product supports voice, chat, email, WhatsApp, and other digital channels, with the company positioning its agent as a consistent customer-experience layer across surfaces.

Its product materials also state that deployments can launch in weeks.

Actual implementation timing will depend on the organization's workflows, integrations, knowledge readiness, security requirements, testing process, and rollout scope.

Sierra's Enterprise Scale

Sierra has expanded rapidly since its launch.

In May 2026, the company announced a $950 million funding round led by Tiger Global and GV, pushing its post-money valuation above $15 billion. Sierra also said more than 40% of Fortune 50 companies were customers at that point. TechCrunch funding report

The company had previously reached $100 million in annual recurring revenue in 2025 and later said it added another $100 million in ARR within two additional quarters. Sierra growth report

Those figures provide context for Sierra's position in the enterprise AI-agent market, although they do not determine the pricing of an individual customer contract.

Security and Governance

Enterprise procurement also needs to evaluate the controls surrounding the AI deployment.

Sierra's current security program includes ISO/IEC 27001 and ISO/IEC 42001, along with additional security, privacy, and regulatory controls documented through its Trust Center.

Security requirements should be assessed against the organization's own data classification, industry, geography, workflows, and integration architecture.

The NIST AI framework provides a vendor-neutral reference for evaluating AI governance alongside vendor-specific controls.

How Maven AGI Approaches Resolution Economics

Maven AGI uses resolution volume as a central commercial input while providing a published starting reference through AWS Marketplace.

The current AWS Marketplace listing shows Enterprise Custom Pricing starting at $25,000 for a 12-month contract. Final pricing is based on:

• Expected scope
• Complexity
• Volume of resolutions

AWS describes a resolution as a customer query handled end to end without human intervention.

Maven's commercial model sits within a broader enterprise AI platform built around completing customer requests across existing systems.

Key elements include:

• One reasoning engine: Maven's agent platform applies shared reasoning, knowledge, and policy logic across chat, email, voice, and web
• 100+ integrations: Maven integrations connect with support, CRM, knowledge, data, commerce, communications, and telephony systems
• Existing-stack connectivity: Maven operates across established help desks, CRMs, knowledge sources, telephony platforms, and internal systems
• CX-team control: Agent Designer tools support simulations, testing, evaluations, behavioral configuration, monitoring, and ongoing improvement
• Cross-system actions: Agents can retrieve information and carry out approved actions across connected enterprise systems
• Human escalation: Complex exceptions, sensitive conversations, and work requiring judgment can move to human teams with relevant context
• Enterprise governance: Maven's trust and compliance program includes ISO/IEC 42001, ISO/IEC 27001, SOC 2 Type II, PCI DSS Level 1, and additional security and privacy certifications or assessments

This creates a pricing discussion centered on how much customer work the AI can complete end to end within the organization's operating environment.

Outcome Pricing and Resolution Pricing Are Not Identical

Sierra's outcome model and Maven's resolution-oriented pricing framework both connect commercial terms to completed work, but the measurement unit should not be assumed to be identical.

An outcome can represent different business results depending on the Sierra contract.

A Maven resolution, as described through AWS Marketplace, is a customer query handled end to end without human intervention.

That means buyers should avoid comparing labels alone.

A useful evaluation should ask:

• What event creates the billable unit?
• How is completion verified?
• Are escalations excluded?
• What happens with reopened issues?
• Which channels are included?
• Which integrations are required?
• What ongoing platform capabilities are included?
• How does the unit connect to customer-service performance?

Maven's resolution measurement guide also distinguishes true resolution from simply preventing an interaction from reaching a human queue.

A Practical Contract Evaluation Framework

Instead of trying to convert every vendor into the same pricing terminology, enterprise teams can evaluate the commercial proposals against the same business workload.

Establish the Baseline

Measure current:

• Interaction volume
• Resolved cases
• Escalations
• Repeat contacts
• First-contact resolution
• Channel mix
• Peak periods
• Cost per resolved request

Define AI-Eligible Work

Identify which requests can reasonably be completed autonomously and which should remain human-led.

Human teams remain particularly important for:

• Sensitive customer situations
• Complex exceptions
• Relationship management
• Judgment-intensive work
• Policy exceptions
• High-risk decisions

Test the Billing Definition

Use real interaction samples to determine how the vendor's commercial unit behaves.

A useful pilot should make it possible to answer:

• Was the customer's underlying request completed?
• Was human intervention required?
• Did the customer return with the same problem?
• Did the AI perform the required system action?
• Would the interaction become billable under the proposed agreement?

Include the Full Operating Scope

The commercial evaluation should also account for:

• Implementation
• Integrations
• Voice and telephony
• Testing
• Monitoring
• Governance
• Professional services
• Contract minimums
• Overage treatment
• Renewal terms

This creates a more useful comparison than relying on an isolated unit rate.

Why Maven AGI Fits Enterprise AI Evaluations

Maven gives enterprise buyers a published pricing starting point while connecting the commercial model to end-to-end customer resolution. The platform combines this resolution focus with integration, governance, testing, and human escalation capabilities designed for production customer-service environments.

For teams evaluating enterprise AI economics, Maven provides:

• A public pricing reference: AWS Marketplace currently lists a $25,000 minimum for a 12-month custom enterprise contract
• Resolution-centered measurement: Pricing considers the volume of customer queries the AI resolves end to end
• A unified agent architecture: The Maven agent platform uses one reasoning layer across supported channels
• Broad system connectivity: 100+ integrations connect the AI with the systems customer-service teams already use
• Ongoing CX ownership: Agent Designer lets teams test, evaluate, monitor, and refine agent behavior over time
• Enterprise-grade governance: Security controls span AI governance, information security, privacy, payment security, and independent audits or assessments
• Human-centered escalation: Human employees remain part of the service model for sensitive, nuanced, or exception-driven work

Production results add context to those capabilities. Maven's K1x customer story reports that Agent Maven resolves 80% of tickets, almost always in under three minutes. Maven's current site separately reports that K1x went live after a one-week integration and reached 80% autonomous resolution within six weeks.

Those results reflect K1x's individual environment and implementation rather than a universal expected outcome.

For buyers comparing AI-agent economics, Maven brings pricing, autonomous resolution, enterprise integrations, CX-team control, governance, and human escalation into one operating model.

Frequently Asked Questions

Does Sierra publish standard pricing?

Sierra publicly explains its outcome-based pricing model but does not publish standard enterprise dollar rates. Buyers need a custom proposal that defines the relevant outcomes, commercial units, deployment scope, and contract terms.

What counts as a billable outcome with Sierra?

The definition depends on the customer agreement. Examples can include a resolved support conversation, saved cancellation, upsell, cross-sell, or another contractually defined valuable outcome. The agreement should establish the qualifying event and how it is measured.

Does Sierra always use outcome-based pricing?

No. Sierra says outcome-based pricing is its primary approach, but consumption or blended pricing can be used where an interaction does not map cleanly to an attributable business outcome. Routing and greeting interactions are examples that may use conversation-based pricing.

How does Maven AGI define a resolution for pricing?

The AWS Marketplace listing defines a Maven resolution as a customer query handled end to end without human intervention. Final contract pricing is based on expected scope, complexity, and resolution volume.

What does Maven AGI include beyond its pricing model?

Maven combines resolution-oriented commercial inputs with its AI agent platform, 100+ integrations, Agent Designer, cross-channel reasoning, governed enterprise knowledge, approved actions, security controls, and contextual escalation to human teams. This lets buyers assess pricing alongside the technology and operating model used to resolve customer requests.