Forward-deployed engineering for customer support.

An engineer to choose your support AI and make it work in your helpdesk. Sierra, Decagon, Intercom Fin, and your helpdesk's own AI all publish strong case studies. We put a senior engineer on your team who tests them on your tickets, picks with you, and does the integration, escalation, and QA work that decides whether the numbers hold.

  • Free 14-day pilot
  • On a company laptop, inside your network
  • We train your team
  • Vendor-agnostic
  • You own the code

Bring a 90-day ticket export from your helpdesk.

What is already working, and what it took.

Three published results. The first shows the careful version, and the last shows what happens when volume is the only goal.

Sierra × WeightWatchers
~70%

WeightWatchers' Sierra agent contained nearly 70% of cases in its first week, with CSAT above 4.5 out of 5.

Sierra agent ~70%
Cases contained without a person, week one
What it took

Started on a small slice of app traffic. Connected to internal systems so it could take actions. IT and security attacked it with adversarial prompts before launch.

Intercom × Synthesia
55%

Intercom's Fin resolved 55% of Synthesia's support conversations while monthly requests grew from 40,000 to 316,000.

April 2024 40,000
August 2024 316,000
Monthly support requests, April vs August 2024
What it took

The team estimated it would otherwise have needed to grow to 150 people. It handled the growth without growing the support team.

OpenAI × Klarna
2.3M

Klarna's OpenAI-based assistant handled 2.3 million conversations in its first month, two-thirds of its customer service chats.

Before 11 min
AI assistant under 2 min
Time for a customer to resolve an errand
What it took

In May 2025 Klarna's CEO said quality had suffered and that the company would hire more human agents. Volume alone was not the finish line.

Figures as reported by the vendor or customer at the linked source. They are not OpenNash results.

Someone on your side, with a laptop and the authority to decide.

WeightWatchers started on a slice of traffic and had IT and security attack the agent before launch. Klarna later said quality had suffered. The difference is the work around the product. Our engineer takes that on, with a helpdesk admin seat, billing access, and a weekly review with your QA lead.

DecisionWhat we look atOutcome
Sierra, Decagon, Fin, or a custom buildPer-resolution price at your volume over three years, how many tickets need actions in billing or orders, and who owns the knowledge base and test set afterwards.A written comparison with the cost at your volume.
Which ticket class goes first90 days of tickets grouped by intent, with volume, handle time, and reopen rate.A ranked list. You choose.
What the agent may do aloneRefund and credit limits, account changes, and legal or chargeback language.Rules written by your team, enforced in code, and tested on every release.
When it goes liveShadow-mode drafts compared with what your agents actually sent.Only after the pilot tests pass.

AI can do the work. Running it inside your company is the gap.

The deployment gap What AI can do rises steeply. Tickets answered by hand stays nearly flat, leaving a widening gap. A line for an OpenNash engineer rises from the bottom line toward what AI can do. the gap What AI can do OpenNash engineer Tickets answered by hand
OpenAI, Anthropic

Lab engineers

Built for their largest accounts, deploying their own models. OpenAI's deployment company launched with more than $4B. ↗

The product you bought

Vendor teams

Configure their own product, priced per seat or per resolution.

Independent

OpenNash

A small senior team, ex-Palantir, Meta, and Databricks. Any model, any vendor. Free pilot, then a flat monthly fee.

~15OpenAI engineers on site at one chip maker, 3-6 months to production
6 weeksof hands-on work for one tax schedule to reach 90% precision and recall
60% → 90%+on a telco's own production tests, over six months

Even OpenAI closes the gap with engineers in the room. Source: OpenAI, What FDE means at OpenAI, Oct 2026.

The first pilot: one tier-2 ticket class in shadow mode.

  1. Week 1We pull 90 days of tickets, group them by intent, and pick the first ticket class with your support ops lead.
  2. Day 14The agent drafts every reply for that class in shadow mode, and your agents compare the drafts with what they sent.
  3. Weeks 3-8Live on a share of traffic, then all of it, with helpdesk and billing writeback, QA scoring, and escalation paths.
  4. After launchWe run and improve it on a flat monthly fee, or your team takes it over. The next ticket class reuses the same test suite.

The day-14 test: one tier-2 ticket class in shadow mode

Written down with your team in week 1. The pilot is free, and it has to pass these before anything goes further.

$ run day-14 --suite cx-support-teams
T01A refund request inside policy gets a drafted reply that cites the policy line it relied on.
T02A refund above the agreed limit is drafted as an escalation with a one-paragraph summary.
T03A legal threat or chargeback mention is flagged for a person, with no drafted reply.
T04A ticket with no order number gets one drafted clarifying question. The agent does not guess the order.
T05A reopened ticket is handled with the full earlier conversation in context.

Example acceptance tests, not results from a customer deployment. Yours are written with your team.

Systems we work in

  • Zendesk, Salesforce Service Cloud, Intercom, Freshdesk
  • Stripe, Shopify, and billing systems
  • Confluence, Guru, Notion, help centers
  • Sierra, Decagon, or Fin, when one is chosen

Rules from day one

  • Shadow mode first. Nothing reaches a customer until the pilot passes.
  • Refund and credit limits are enforced in code, not in the prompt.
  • Every reply and action is logged with the knowledge source it used.
  • Code, prompts, and test cases live in your repository and stay with you.
Should we buy Sierra, Decagon, or Intercom Fin?

Possibly. We test them on the same set of your past tickets and price them at your volume over three years. If one wins, we do the integration and QA work. If none fits, we build, and you own the code and test suite.

Do we have to leave Zendesk or Salesforce?

No. Tickets, macros, and reporting stay where they are.

Who decides when the agent escalates?

Your team. We write the escalation rules with your support ops lead, turn each one into a test, and run the tests on every release.

Why you need one

Every result on this page needed engineers inside the company. We can be yours.

A senior engineer joins your team on a laptop you issue, tests the options on your data, and puts one customer support workflow into production in 4 to 8 weeks. It starts with a free 14-day pilot judged against test cases you agree in writing.

On your laptopWe work on a machine you issue, behind your VPN and SSO. We file the access tickets and chase them.
Next to your teamWe sit with the people who do the work and build around how they actually work.
IndependentWe do not work for any model company or software vendor, so we test the alternatives and tell you what we would buy.
SeniorEngineers who have shipped production systems at Palantir, Meta, Databricks, and Global 2000 companies.

After launch, we run and improve the workflow on a flat monthly fee, or your team takes it over. The code, tests, and runbook are yours either way.

Bring a 90-day ticket export from your helpdesk.