Gradient Labs

Otto is an autonomous agent that reasons through a customer's problem and completes it, and the founders are explicit that they were not building an assistant. It interprets a query, follows a procedure written in natural language, calls the institution's systems and takes the action. That might be freezing a card, opening a dispute or running a due diligence check. Without the models nothing remains. A deflection bot pointing at a help center is precisely the incumbent approach the company was founded to move past.

The product is autonomy forward and the company does not pretend otherwise. It describes fully autonomous agents rather than assistants and aims for minimal human intervention while the agent freezes cards, files disputes and runs due diligence checks. The control architecture is real and specific. Procedures are authored by the institution in plain English, guardrails execute on every turn and are counted, and tool exposure is deliberately constrained per procedure.

The platform is described as fully auditable. The human boundary is missing. There is no stated escalation threshold, no confidence level that forces referral, and no described route by which a person reviews an action before it lands on a customer's account.

Performance is stated as a curve rather than a headline. Resolution runs roughly 60 percent on day one, rising to 80 to 90 percent as a deployment matures. That admits the system starts imperfect, and it gives a buyer a number to hold it to during a pilot. Guardrail execution volume with an associated quality score gives an operational measure of how often controls engaged. Procedures written in plain English are readable by a compliance officer without vendor assistance. Absent are model documentation, error analysis, independent evaluation and any stated support for a customer's own validation.

Customers are named across several financial models, including a major money transfer business, digital banks, a savings and investing platform, an insurance provider and a lender, with more than twenty active customers and European bank deployments.

Performance is published as a maturity curve rather than a best case, at roughly 60 percent resolution on day one rising to 80 to 90 percent in mature deployments, with satisfaction above 80 percent across deployments and 98 percent at the top, and the company states its agents beat human teams on both satisfaction and quality scores.

One deployment is quantified in operational detail: more than 500,000 customers served at a European digital bank with nine million guardrail executions and a 98 percent quality score. Revenue reached a million pounds within five months of launch, and a European bank's venture arm co led the funding.

The safety architecture is described concretely and measured. More than twenty compliance guardrails run on every turn. One deployment reports nine million guardrail executions alongside a 98 percent quality score, a published count of how often the guardrails actually fired. A second design choice is explained rather than assumed. Each procedure exposes only the one or two tools it needs rather than the full toolset, deliberately narrowing the agent's option space to raise accuracy.

The company also delayed launch by fourteen months to build against internal quality benchmarks. What is absent is independent validation of any of it, and any statement on whether customer conversations inform model training.

The agent holds live customer conversations, reads account data and acts on accounts, which places it inside the most sensitive part of a bank's customer relationship. The company discloses that it fails over across multiple cloud and model providers, so conversation content can traverse several third parties by design. A SOC Type II certification is stated. The framework beneath it is not published. There is no privacy policy detail on conversation handling, no retention schedule, no subprocessor list and no statement on how customer data is bounded when it reaches an external model provider.

A SOC Type II certification is stated explicitly on the product site and framed as banking grade data handling. That names a standard and a level rather than gesturing at unspecified certifications. The surrounding surface is absent. There is no trust center, report request path, stated audit period or scope, and no second framework such as ISO 27001, which European bank customers would ordinarily expect alongside it.

Gradient Labs supplies technology and holds no authorization, the expected posture. Its domain credibility is direct, since the founding team led data science and machine learning across customer operations and financial crime at a licensed digital bank before starting the company. The agent operates inside regulated processes, running customer due diligence and handling payment disputes, both of which carry defined obligations.

The platform is described as preconfigured for consumer protection laws. The framing stays at the level of global regulations generally, and the specific instruments it was built against are not named.

Satisfaction and quality scores are aggregate measures of whether customers were pleased, not measures of whether they were treated evenly. The agent operates across voice, text and email in the United States and Europe, so speech recognition is exposed to variance by accent, dialect and impairment. The consequences are decisions rather than routing: a dispute filed or refused, a card frozen or left active. Nothing public breaks resolution or escalation rates down by language, accent or customer segment, and no fairness testing or accessibility analysis is published.

Outcome based pricing creates alignment rather than liability: the vendor earns on resolutions, so unresolved or reopened cases cost it revenue, which is a real incentive but not a commitment to bear the consequences of being wrong. Guardrails and auditability let an institution reconstruct what the agent did. Neither reaches the customer.

No accuracy guarantee, no remediation term, and no described route for someone whose card was frozen in error or whose dispute the agent declined, which matters more here than in advisory products because the agent takes the action rather than recommending it.

Gradient Labs acknowledges that multiple external model providers sit in the path, disclosed through a failover design spanning several cloud and model suppliers. The durable workflow engine underneath is named openly through a published case study. What is not disclosed is which providers, under what terms, or what they retain. There is no subprocessor list, so a bank knows its customer conversations reach several third parties without being able to identify them.

The integration position is the product's central claim, and it is correct. Most agents stop at the help desk. This one also connects into the financial systems where the work actually completes, which is what allows it to freeze a card rather than describe how to. It runs as a layer over the major helpdesk platforms or an in house one, and connects by interface, file upload or inside existing tools.

It is built on a named durable workflow engine, so a conversation can persist across hours or days and retry reliably. Failover spans multiple cloud and model providers, an availability design that is rarely described.

Delivery is cloud hosted with deliberate failover across multiple cloud providers, serving customers in both the United States and Europe. Conversation data therefore moves between regimes and between providers as a matter of architecture rather than exception. No hosting regions, residency options, transfer mechanisms or subprocessor locations are published. The multi provider design widens that gap, since the set of systems touching a customer conversation is not fixed.

The pricing model is published even though rates are not. Charging is outcome based on resolutions rather than seats or conversations, so the vendor is paid when the work actually completes. That tells a buyer the shape of the commitment and aligns the commercial interest with the operational one. Independent reviewers note the trade offs plainly. There is no self serve trial, the process is entirely sales led, and a resolution based bill can be hard to forecast as volumes move.

Coverage spans banks, fintechs, lenders, insurers, wealth management and crypto businesses across the United States and Europe, and the functional reach is wider than customer service alone, taking in back office investigations such as disputes and due diligence plus proactive outreach. Named customers cover digital banking, money transfer, savings and investing, insurance and lending.

The boundary is the function rather than the sector: this is customer and back office operations, with nothing addressing underwriting, capital markets, treasury or credit decisioning, and no credit union material.