You got the Ada demo. The Playbook builder was slick, the Reasoning Engine handled multi-step flows better than you expected, and the sales rep walked you through an impressive library of pre-built connectors. Then they sent the proposal.
No pricing on the website. No ballpark on the call. Just a custom quote that lands somewhere between "we need to think about this" and "this is going to require a board conversation."
This post exists because that information gap is deliberate, and buyers deserve the math.
Ada is a legitimate product. It's also genuinely good at what it does. But "genuinely good at standard customer support" and "right for your business" are different questions, and the answer depends on factors Ada's sales process is not designed to surface.
What Ada Actually Does Well
Let's start with credit where it's due.
Ada's Playbook builder is the most non-technical-friendly conversational flow tool available in this market. A support manager with no engineering background can build a working return authorization flow, a billing inquiry handler, or a subscription cancellation deflector without filing a single engineering ticket. That matters for teams where CX and engineering don't share priorities.
The Reasoning Engine - Ada's term for their AI logic layer - handles conditional multi-step processes better than most chatbot platforms that preceded it. It can check account status, apply business rules, and escalate based on calculated outcomes rather than keyword triggers. Ada's platform applies agentic reasoning to common support scenarios in ways that hold up under real volume.
Ada also supports over 50 languages and maintains pre-built integrations covering Salesforce, Zendesk, ServiceNow, Shopify, and most major CRMs. For teams with standard tech stacks, that out-of-the-box connectivity removes weeks of integration work.
The result: Ada is genuinely fast to deploy for standard customer support. Weeks to production, not months. For teams that need AI deflection running now on conventional support scenarios, that speed advantage is real and the Playbook tooling reduces dependence on engineering backlogs.
The Pricing Problem Nobody Models Until Year Two
Ada does not publish pricing. This isn't unusual for enterprise software, but the structure of how Ada charges creates a dynamic that most buyers don't model until they're already contracted.
Reported pricing runs from $1.00 to $3.50 per conversation. Annual contracts typically start around $30,000 for mid-market deployments, with enterprise deals reaching $100,000 to $300,000+ per year.
The per-conversation model has one feature that doesn't show up in the demo: Ada charges for attempts, not outcomes.
If your AI handles a conversation successfully, you pay. If your AI fails to resolve the issue and escalates to a human agent, you still pay. The conversation happened; the meter ran regardless of resolution.
Here's what that looks like as adoption grows:
- Month 1: AI handles 5,000 conversations at $2/interaction - $10,000
- Month 6: Adoption expands to 25,000 conversations - $50,000
- Month 12: Full rollout reaches 60,000 conversations - $120,000
- Year 1 total: Potentially $500,000 to $1,000,000+ depending on volume ramp
Year 2 costs even more as adoption matures. The more your deployment succeeds, the higher your bill.
Total cost of ownership at scale looks very different than it does in the initial contract. Buyers modeling ROI at current volume routinely underestimate what they will owe after two years of successful adoption.
Compare that to a purpose-built custom deployment. The infrastructure cost is the same in month 1 as month 12 as month 24. The more successful your AI deployment becomes, the better your cost-per-resolved-issue gets - because the numerator (fixed cost) stays constant while the denominator (resolved interactions) grows. Volume success stops being a liability.
Configurable vs. Custom - The Conceptual Divide
This is the part that matters most, and it's the part that gets lost in platform demos.
Ada gives you a sophisticated set of adjustable settings: tone configuration, knowledge base connections, routing rules, conversation flow builders, escalation logic. These are real capabilities - and they're capabilities that every Ada customer shares.
You can configure what Ada offers. You cannot build what Ada doesn't offer.
When your business logic falls outside Ada's template library - which is extensive but finite - you have three options: work around the limitation with workarounds that degrade the user experience, wait for Ada's product roadmap to catch up, or accept that this particular workflow won't be automated.
Platform-based AI tools optimize for breadth and deployment speed. Purpose-built solutions optimize for depth and fit to specific business logic. Both are valid - they serve different problems.
Here's what that looks like in practice across industries where we see this most often:
Travel and hospitality: A hotel chain needs AI that integrates with their specific property management system, applies overbooking logic that differs by property (Miami has different revenue management thresholds than Denver during shoulder season), and escalates by loyalty tier in ways that go beyond "route to VIP queue." Ada's templates don't know that your overbooking protocol depends on day of week, seasonal demand index, and whether the next available date within 50 miles has inventory. That logic lives in your revenue management system - and it changes.
Telecommunications: A regional telecom needs AI that diagnoses network issues by pulling real-time data from their specific monitoring stack, cross-references planned maintenance windows, and offers technician dispatch based on the actual scheduling system - not a simulated dispatch that creates a ticket for a human to process later. That's not a configurable template; it's software that talks to four proprietary systems on a live basis.
Financial services: A wealth management firm needs AI that distinguishes between a Roth conversion question (answer it directly) and a trade request (require compliance review), routes based on the advisor's book of business, and logs the interaction in a format their compliance system can audit. Ada doesn't know your compliance workflow because your compliance workflow is specific to your regulatory posture, your custody arrangement, and your documentation requirements.
Healthcare: A multi-location wellness brand needs scheduling AI that handles 200 locations with different providers, service types, insurance panels, and availability rules that aren't consistent across locations. A configurable bot handles "book an appointment." Purpose-built software handles YOUR appointment logic across your specific inventory.
Organizations that start with platform solutions often commission custom builds within 18-24 months - not because the platform failed, but because the business grew into requirements the platform was never designed to serve. The platform was not wrong; it just had a ceiling.
The Ownership Question
Every year you run on Ada, more institutional knowledge about your customer interactions gets encoded inside their platform.
Your conversation logic - the playbooks you've refined, the escalation rules you've tested, the routing heuristics that took six months to calibrate - lives on Ada's servers. If you need to modify it, you use Ada's tools. If you want to export it, you get configuration files that don't run anywhere else.
Leave Ada, leave with nothing executable.
This isn't unique to Ada; it's the standard dynamic with any platform-as-a-service. You're renting access to infrastructure you don't control. The switching cost increases each year as more of your operational knowledge gets encoded in Ada's proprietary format. Your AI intelligence isn't yours.
Purpose-built software works differently. You own the code. It runs in your environment. If the consulting relationship ends, you keep everything: the codebase, the data, the logic, the institutional knowledge encoded in software you can read, modify, and operate independently.
Vendor lock-in is the TCO factor buyers underweight in initial purchasing decisions - the cost is not visible until you try to leave. Platform tools trade long-term flexibility for short-term deployment speed. The question is whether your AI capability is a commodity service or a competitive asset.
When Ada Is the Right Call
Being direct about this: Ada is the right answer for a meaningful portion of the market.
If you need AI customer support running in weeks, not months, and your use cases are conventional enough that Ada's template library covers 90%+ of your scenarios - Ada will probably deliver real value. The no-code Playbook builder is easier to use than most alternatives, and Ada's deployment support removes friction during rollout.
If your team has no engineering capacity and commissioning custom software development feels risky, Ada's managed platform removes that burden entirely. You get a product with an SLA, a support team, and a roadmap that someone else maintains.
If your conversation volume is modest and predictable - say, under 10,000 conversations per month and growing slowly - the per-interaction pricing may be manageable relative to deflection value. At $2/conversation and 5,000 monthly conversations, you're at $10,000/month. Whether that math works depends on what you're deflecting and what human agent time costs.
There is a useful distinction between tools that solve known problems (where platforms excel) and tools that need to encode your specific business context (where custom solutions excel). Ada sits firmly in the first category, and that is not a criticism - it is accurate positioning.
When to Build Instead
Custom AI agents make more sense when the calculus shifts in four ways.
Your workflows are industry-specific. If the reason you need AI involves logic that's specific to your business model, your compliance environment, or your operational context - rather than generic support patterns - you're outside the territory platforms were designed for. Configuring around that gap produces workarounds, not solutions.
You want predictable costs at scale. If your AI deployment is working well and volume is growing, that's exactly when platform costs accelerate. The more successful your deployment, the higher your bill. Custom deployments don't have that property - volume growth improves unit economics instead of degrading them.
Your AI needs to talk to your entire stack. Ada connects to common CRMs and support tools. If your AI needs to integrate with proprietary internal systems, specialized industry software, or real-time data sources outside Ada's integration library, you're doing custom engineering either way - the question is whether you own the result.
Ownership matters for your business strategy. If you're building AI capability that you intend to be part of your product, your competitive advantage, or your long-term operational infrastructure - renting access to someone else's platform is a different strategic bet than owning the software outright.
The tradeoff is simple: platforms reduce time-to-value but increase time-to-limit; custom solutions increase time-to-value but have no inherent ceiling. The right choice depends on where you are on that curve and where your ceiling is.
If you are solving a known problem that looks like what Ada already handles, Ada is worth evaluating. If you are solving a problem that is specific to how your business works, you will hit the ceiling eventually - the question is when, and whether you will own anything when you do.
Ada vs. OpenNash CX
If Ada's per-conversation pricing and platform ceiling are the reasons you are looking, here is how OpenNash CX compares directly.
| Ada | OpenNash CX | |
|---|---|---|
| Pricing | $1.00-$3.50 per conversation, $30K-$300K+/yr | $7,995/mo flat. Unlimited conversations, everything included. |
| Cost at 20K conversations/mo | $20K-$70K/mo | $7,995/mo |
| Architecture | Shared platform - configure what Ada offers | Single-tenant, built around your workflows |
| Scope | Standard support deflection + templates | Any workflow - support, ops, compliance, scheduling |
| Cross-system workflows | Ada's integration library, roadmap-dependent | 1,000+ native integrations, custom builds included |
| Channels | Chat, email, voice (platform-defined) | Voice, SMS, webchat, email, WhatsApp + 6 more |
| Human handoff | Escalation to helpdesk | Native agent workspace with full AI context |
| Ownership | Conversation logic lives on Ada's servers | You own the code, data, and infrastructure |
| Transparency | Reasoning Engine is a black box | Inspectable prompts, version-controlled procedures |
| Contract | Annual | Month-to-month, pause anytime |
| When contract ends | Configuration resets to zero | Keep everything |
The flat retainer reverses Ada's cost curve. With Ada, your bill goes up every time the AI succeeds. With OpenNash CX, $7,995/month covers unlimited conversations, every integration, every channel, and ongoing optimization.
How to Choose
Stay with Ada when: use cases are standard enough that templates cover 90%+ of scenarios, conversation volume is under 10,000/month and predictable, and you need to be live in weeks without engineering involvement.
Move to OpenNash CX when: workflows include industry-specific logic Ada's templates cannot model, per-conversation fees are approaching what a flat retainer would cost, you need AI across systems outside Ada's integration library, or you want to own the software you are paying to build.
Ada is not the wrong choice for everyone - it is the wrong choice for businesses whose AI is strategic rather than operational overhead. The question is which one you are.
See the full platform comparison on our Sierra vs Decagon vs OpenNash CX page, or talk to us to see what your volume would look like at $7,995/month flat.