A decision record

Should a mid-market B2B SaaS company replace 30% of its customer support volume with AI agents in 2026?

Verdict

No. The 30% target is built on a denominator nobody has verified.

Your ticket data is likely 25 to 40 percent noise from duplicates and re-contacts, which means the CFO's $1.5M savings projection is modeled on phantom volume. Automating 30 percent of a number that is itself 30 percent inflated means spending real capital to process tickets that should not exist in the first place.

Run a 30-day ticket hygiene sprint staffed with support reps and a product team member, then launch a narrow AI pilot (10 to 12 percent of volume) on billing lookups, password resets, and license key retrieval, with a hard kill switch tied to CSAT and escalation thresholds.

Advisory panel

Six advisors. Four lenses, two synthetic roles.

Each advisor reasoned independently. Their conviction is tracked round to round. Resilient positions are listed first.

The deeper story

The Trial of the Unsayable Decision

An organization that already knows what it is going to do but cannot say so out loud, because saying it out loud would make someone accountable for the human cost. So it hires a room full of brilliant people to generate enough noise that the decision appears to emerge from process rather than from power. Every advisor's drama is a scene in this trial.

Causal Layered Analysis synthesis. What is CLA?

Action plan

What to do this week, this month, this quarter.

  1. This week Line-item cost decomposition

    Before evaluating any AI vendor, pull a line-item breakdown of total support spend. Labor, tooling, platform licenses, infrastructure. Separate headcount growth from non-labor growth across the last four quarters. If you are over 10% of revenue on support, know exactly where the overage lives.

  2. Days 1 to 30 Ticket hygiene sprint

    Pull your top three support reps and one product team member into a 30-day audit. Deduplicate re-contacts. Tag misrouted tickets. Identify the real denominator before automating anything. Most mid-market SaaS support queues carry 25 to 40 percent noise.

  3. Days 31 to 90 Narrow AI pilot on deterministic flows

    Launch a 10 to 12 percent of volume pilot on billing lookups, password resets, and license key retrieval. Hard kill switch tied to CSAT and escalation thresholds. Clean data, defensible business case, compliant rollout path within 90 days.

Surviving assumptions

What the debate did not refute.

  • Support volume likely contains 25 to 40 percent duplicate, re-contact, or misrouted tickets.
  • The $1.5M savings projection is modeled on unverified total volume.
  • The parallel-pilot window may be closing; sequential cleanup cedes short-term ground to faster competitors.
  • Compliance overhead on escalations is not priced into the CFO's model.

Forecasts

What Manwe expects to happen.

  • Launching a 30% automation target without first completing a ticket hygiene audit will automate 8 to 12 percent of total volume against duplicate, re-contact, or misrouted tickets, producing inflated deflection metrics that mask flat or worsening actual resolution rates through Q4 2026.

    82% confidence
  • Regardless of which path leadership chooses (broad rollout vs. narrow pilot), the company will not achieve the CFO's $1.5M annualized cost savings target within the original 12-month window. Realized savings by April 2027 will be under $600K after accounting for implementation and escalation overhead.

    78% confidence

Read the full record

Six rounds of debate, every source, every risk, the full action plan.

The showcase above is the executive summary. The complete decision record, with every debate round, every source cited, every risk surfaced, and the full 90-day action plan, lives in the public archive.

Run your own

One real decision. One Manwe run.

Download the Mac beta and turn one hard question of your own into advisors, evidence, dissent, and a decision record like this.