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

The advisors debated whether an $85M ARR B2B SaaS company should deploy AI agents to handle 30% of support ticket volume across its 62-person team. The discussion quickly moved past the yes/no question into deeper issues: the company likely can't measure resolution quality well enough to know if AI is working, the cost savings math doesn't hold up when you account for escalation costs and compliance overhead, and the 30% target may be borrowed from top-performer benchmarks that don't apply here. The group split between those advocating a narrow pilot (5-12% on low-risk tickets) and those arguing the entire framing is wrong—that support cost growth may be driven by tooling sprawl, coverage redundancy, and wage inflation rather than ticket volume.

Rita Kowalski PUSHBACK
Before anyone in this room gets excited about automating 30% of support volume, I need someone to answer a fundamental question: what does '30% of support volume' actually mean at this company? Because in my experience, most mid-market SaaS companies can't even tell you what a resolved ticket looks like versus a deflected one. They're counting closes, not outcomes. I spent three weeks auditing a defense contractor whose board couldn't understand why customer satisfaction was tanking despite their ticket resolution rate hitting 94% — turns out they were auto-closing tickets after 72 hours of inactivity and calling that 'resolved.' This company has 62 support people across three regions handling everything from billing to compliance-sensitive tickets, and the CFO wants cost cuts in 12 months. That's a recipe for scaling dysfunction faster. The evidence here is clear — Gartner found that half of organizations surveyed plan to abandon significant customer service workforce reductions by 2027 because of the complexities involved. I'm not saying don't do it. I'm saying the 30% target is a vanity number until you've built a measurement framework that distinguishes between ticket deflection and actual resolution quality. Start there, or you're just putting a speedometer on a car with no steering wheel.

Marcus Sterling PUSHBACK
Rita, I agree the measurement framework matters, but you're being too generous — you stopped short of the real problem. Even if this company builds a pristine measurement framework tomorrow, the economics still don't pencil out for a 30% rollout. Let me do the math nobody wants to do. The briefing says AI customer service runs $2K to $15K monthly, and hidden fees add 40 to 60 percent on top of that. So call it $3K to $24K a month all-in. Now you're not replacing 30% of 62 people — you're replacing 30% of ticket volume, which means you still need most of those people on standby for escalations, edge cases, and the compliance-sensitive tickets Legal is already nervous about. The headcount savings are a fraction of what the CFO is fantasizing about. Meanwhile, the evidence shows 35% higher escalation rates when AI handles support — so you're not just failing to save money, you're actively creating new costs as humans clean up after the bots. I ran numbers like this at a fintech portfolio company in 2023, and the 'savings' evaporated within two quarters because escalation handling time per ticket went up 40%. The Gartner stat you cited — half of organizations abandoning workforce reduction plans by 2027 — that's not a cautionary tale, that's a body count from companies who moved too fast. I'd tell this CEO the same thing I told that fintech board: run a 5 to 10 percent pilot on billing-only tickets, set a hard 90-day payback gate, and don't touch a single compliance or enterprise escalation ticket with AI until you have 6 months of clean data.

Daniel Park PUSHBACK
Marcus, your math is technically correct but strategically backwards. You're treating this like a cost-reduction exercise and then proving the cost reduction is marginal — congratulations, you've debunked the wrong thesis. The real case for AI agents at 30% volume isn't about firing 19 people. It's about what happens to your support experience when competitors are running AI-first triage and you're still routing every billing question through a human queue in three time zones. I ran support ops at a Series C company that did exactly what you're proposing — a cautious 5% billing-only pilot with a 90-day gate. By the time we had 'clean data,' two competitors had shipped AI agents that resolved onboarding and billing tickets in under 90 seconds with inline product context. Our enterprise prospects started asking why our support felt slower. That's the part Gartner's stat about abandoning workforce reductions doesn't capture — those companies abandoned headcount cuts, sure, but the ones who redeployed humans to high-value work while AI handled Tier 1 volume actually won. The 35% higher escalation rate you cited — I've seen that number and it's from early deployments with garbage knowledge bases and no human-in-the-loop fallback. In 2026, with proper RAG pipelines and escalation routing, that number drops dramatically in my experience. And here's what nobody's brought up yet: the VP of Product is sitting on a goldmine. AI agents generate structured metadata on every interaction — intent classification, feature gaps, friction points — at a scale no human team of 62 can match. That insight loop alone justifies the deployment cost because it feeds directly into reducing churn, which for a B2B SaaS company at $85M ARR is existential. Every percentage point of churn they prevent is worth more than the entire annual support budget.

Laurent Jorgensen WARN
Daniel, I've watched two peers lose their jobs after AI rollouts cratered CSAT and triggered senior account churn — one at a $60M company that tried exactly the competitive pressure argument you're making. 'Our competitors are doing it so we have to move fast' is how you end up in the Gartner body count Marcus referenced. Here's what nobody in this room has mentioned yet: this company has 18,000 customers across three regions, which means they're almost certainly subject to GDPR, and Legal is already flagging cross-border data handling concerns. The moment you pipe customer conversations through a RAG pipeline hosted by a third-party LLM provider, you've created a data processing chain that your DPO has to sign off on for every jurisdiction. I had a peer at a $90M ARR company who spent four months just getting Legal comfortable with the data residency implications before a single AI ticket was touched — and that was a 5% pilot. You want to go to 30%? You're not just building a triage bot, you're building a compliance surface area that scales with every ticket. And your point about structured metadata feeding the product roadmap — I love that in theory, but the VP of Product is getting that insight today from 62 humans who contextualize it. AI-generated intent tags are noisy garbage until someone tunes the taxonomy, and that tuning work falls on the same support team you're trying to shrink. I'd cap this at 10-12% of volume — billing lookups, password resets, license key retrieval — with a hard kill switch tied to CSAT dropping more than two points or escalation rates exceeding 15%, and I'd redeploy any freed-up reps into expansion and onboarding, not cut them.

The Contrarian REFRAME
Everyone's arguing about the right percentage — 5%, 10%, 30% — but nobody's questioned why the question is framed as 'replace volume' at all. This company has support costs rising faster than revenue. That's the actual problem. Replacing 30% of volume doesn't fix that if the remaining 70% keeps getting more expensive, which it will — hourly earnings trend data suggests wages climbing from $37.40 toward $38.60 over the next year. The real question isn't 'how much volume can AI handle,' it's 'why are support costs outpacing revenue growth and is ticket volume even the main cost driver?' I've seen companies where the cost bloat was in tooling sprawl, manager layers, and after-hours coverage contracts — not in per-ticket handling. If this company's 62-person team across three regions is burning money on overlapping shift coverage and redundant vendor contracts, you could cut costs 15% without a single AI ticket. Daniel's competitive pressure argument and Laurent's compliance concerns are both valid, but they're both answers to a question nobody verified. Before this CEO gets a go/no-go, someone needs to decompose the support cost structure line by line — because if the growth in cost is driven by headcount in APAC they added last year, or a Zendesk contract that auto-scaled, the AI agent conversation is solving the wrong problem entirely.

The Auditor FACTCHECK
Daniel, I need to flag something. You claimed the 35% higher escalation rate is from 'early deployments with garbage knowledge bases' and that with 2026 RAG pipelines 'that number drops dramatically.' That's your experience, not verified data — and you should own that instead of waving away a statistic with an anecdote about your Series C company. Meanwhile, your churn math — 'every percentage point of churn prevented is worth more than the entire annual support budget' — let me check that against what we actually know. B2B SaaS median monthly churn is reported at 3.5% in 2026. At $85M ARR, one percentage point of annual churn is roughly $850K. The support team of 62 people across three regions is almost certainly costing north of $5M annually when you include loaded costs. So no, one point of churn prevention does not exceed the entire support budget. The insight loop argument is compelling in theory but don't dress it up with inflated economics. And here's something nobody's touched yet: the web data I've reviewed shows that service desks using AI chatbots reduce ticket volume by 30% — which is suspiciously the exact target this company picked. That number comes from top-performing organizations with mature knowledge bases, not from a company whose measurement framework Rita just correctly questioned. The average first contact resolution rate industry-wide is 76%, while top performers hit 85%. If this company is below that 76% baseline with humans, layering AI on top doesn't fix the resolution gap — it just deflects tickets that come back as repeat contacts, inflating volume while claiming to reduce it.

The panel debated whether to deploy AI in customer support at 30% automation, but the conversation pivoted sharply when Rita flagged that 25-40% of ticket volume may be duplicates and re-contacts — meaning the entire cost model could be built on phantom volume. Daniel argued deploying AI as a triage/data-cleanup layer would surface this data faster than manual analysis, but multiple advisors countered that deduplication is a data ops problem, not an AI problem, and that wrapping it in a vendor contract adds cost and risk without solving the root issue.

Rita Kowalski PUSHBACK
Daniel, your competitive pressure argument sounds urgent but it's built on survivorship bias — you remember the Series C company that won, not the ones Laurent mentioned that cratered CSAT and got people fired. But here's what I actually want to drill into that nobody's touched: the web data shows duplicate tickets make up 25% to 40% of total support volume, and repetitive calls account for around 40% of inbound volume. If this company hasn't deduplicated and cleaned its ticket data first, that 30% target is a fiction — you could be automating the same ticket three times and calling it deflection. I spent three weeks at a defense contractor whose board couldn't understand why their 'resolved ticket' counts kept climbing while customer satisfaction flatlined. Turned out a third of their volume was duplicate reports from the same incidents, and their automation layer was happily closing duplicates as 'resolved' while the actual customer was still waiting. So before anyone argues about 5% or 10% or 30%, someone needs to answer a more basic question: what's the real unique ticket volume after you strip out duplicates, re-contacts, and tickets that only exist because the first resolution failed? Because if 30% of their volume is already noise, automating it doesn't save money — it just gives the CFO a dashboard that lies faster.

Marcus Sterling WARN
Daniel, I sat through three board meetings in 2023 where a $70M ARR company I advised presented the exact same competitive pressure logic — 'our competitors are shipping AI-first support, we'll lose deals if we don't match.' They went to 25% automation in four months. Nine months later they were unwinding it because their net revenue retention dropped 6 points and their Head of CS resigned. The Auditor already caught your inflated churn math, so I won't rehash that, but here's the new angle nobody's working: the briefing data says AI customer service costs run $2K to $15K per month, but hidden fees add 40 to 60 percent on top. For a company pushing 30% of volume through AI agents across three regions with GDPR in play — which Laurent correctly flagged — you're looking at the high end of that range plus compliance tooling, plus the integration cost with whatever ticketing stack they're running. Rita's point about duplicate tickets is the one that should be keeping the CFO up at night. If 25 to 40 percent of their volume is duplicates and re-contacts, the CFO's entire cost model is built on phantom volume. You automate 30% of a number that's 30% inflated, and you've just spent real capital to process tickets that shouldn't exist. I'd rather see this company spend 60 days deduplicating their ticket data and decomposing their cost structure — as the Contrarian suggested — before a single AI vendor gets a purchase order. The CEO wants a go/no-go, and my answer is still no at 30%, but it's also no at 10% until someone proves the denominator is real.

Daniel Park PUSHBACK
Marcus, 'prove the denominator is real' sounds rigorous but it's actually a stall tactic dressed up as diligence. Rita's right that duplicate tickets could be 25 to 40 percent of volume — but that's actually an argument FOR deploying AI sooner, not against it. At my last company, we deployed an AI triage layer specifically to deduplicate and merge related tickets before they hit a human queue. Within six weeks, we'd identified that 31 percent of our inbound was redundant — something our ops team had been arguing about for a year with no resolution because nobody wanted to fund the analysis manually. The AI didn't just handle tickets, it cleaned the data that made everything else visible. You're telling the CEO to spend 60 days decomposing their cost structure before writing a PO, but that decomposition IS the pilot. You instrument an AI layer on 15 to 20 percent of inbound, you get the deduplication data, the resolution quality data, and the cost-per-ticket data simultaneously — and you get it in production, not in a spreadsheet someone built from Zendesk exports. The Contrarian asked why nobody's verified whether ticket volume is the main cost driver. Fair. But sitting in a room debating it for two months while hourly earnings climb from $37.40 toward $38.60 means your cost base is getting more expensive every quarter you wait. The briefing data says 73 percent of customers switch after bad AI experiences — I take that seriously. But the inverse is also true: if you design the AI layer as a data cleanup and routing engine first, and a resolution engine second, you de-risk the CSAT exposure while still getting the operational intelligence that everyone in this room agrees is missing.

Laurent Jorgensen WARN
Daniel, I've heard this exact pitch twice before — 'deploy AI as a data cleanup tool first, resolution engine second' — and both times it was how the vendor got their foot in the door before scope creep turned a triage layer into a full deflection play within two quarters. But here's what actually keeps me up at night that nobody in this room has said yet: this company has 62 support reps across three regions. When you announce an AI pilot — even a 15 to 20 percent one — your best people start updating their LinkedIn profiles that week. I lost four senior reps in ten days when my company floated a smaller pilot than what Daniel's proposing, and those were the people who handled our top-tier enterprise accounts. The briefing data says Gartner found half of organizations plan to abandon their workforce reduction plans by 2027 because of AI integration challenges — that's not a warning about AI failing technically, that's a warning about the human cost of the announcement itself. You can't A/B test morale. Rita's point about duplicate tickets being 25 to 40 percent of volume is the sharpest thing said in this room today — and it means you could redeploy a handful of reps into a ticket hygiene squad, clean the data in 30 days with humans who actually understand your customers, and have a real denominator before you spend a dime on AI tooling that the briefing says will cost 40 to 60 percent more than the sticker price.

The Contrarian REFRAME
Daniel, you just made the strongest argument against yourself and didn't notice. You said your AI triage layer found 31% of inbound was redundant within six weeks — great. But that means you deployed an AI system to discover a data hygiene problem that your ops team already knew existed but couldn't get funded. The AI didn't solve a customer problem. It solved an internal politics problem. And now you're telling this CEO to spend vendor money to do what a competent ops manager with a SQL query and six interns could do in three weeks. Laurent's ticket hygiene squad idea is the same outcome at a fraction of the cost and risk. Here's the thing nobody in this room has said plainly: the person who asked this question has a CFO who believes AI cuts costs in 12 months and a Head of CS who believes it damages retention. Those aren't positions that get resolved by a pilot — that's a leadership alignment problem. You deploy at 15% or 30% or 5%, and whichever executive's thesis gets disproved is going to sabotage the interpretation of the results. I've watched this exact dynamic play out — the CFO cherry-picks deflection rates, the CS leader cherry-picks CSAT dips, and six months later the CEO is no closer to a decision but has spent real money and lost real credibility with the support team Laurent warned about.

The Auditor FACTCHECK
Daniel, I need to flag something specific. You claimed deploying AI as a triage layer gets you deduplication data, resolution quality data, and cost-per-ticket data simultaneously 'in production, not in a spreadsheet.' But the web research I just reviewed on AI triage systems tells a different story — every source describes AI triage as classifying intent, categorizing tickets into buckets like billing, technical, onboarding, and routing them. None of them claim the triage layer itself produces clean cost-per-ticket attribution or deduplication metrics as a native output. Those are downstream analytics you'd still need to build, instrument, and validate separately. You're packaging a triage deployment as if it's a free business intelligence layer, and that conflates two different engineering efforts with two different cost profiles. The Contrarian's point about SQL queries and interns is exaggerated, but the core logic holds — deduplication is a data ops problem, not an AI deployment problem, and wrapping it in a vendor contract doesn't make it cheaper. One more thing: Laurent cited Gartner saying half of organizations plan to abandon workforce reduction plans by 2027 due to AI integration challenges. I can't verify that specific stat in the evidence provided, so I'd flag it as unconfirmed. But the broader pattern — that announcing AI pilots triggers talent flight — is directionally consistent with what we know about this company's 62-person team spread across three regions with different labor markets and different levels of replaceability.

The advisors converged on a critical insight: the company's support ticket data is likely 25-40% noise from duplicates and re-contacts, which means the VP of Product is building their roadmap on corrupted signal—potentially misallocating hundreds of thousands in engineering spend on phantom priorities. They broadly agreed a 30-day ticket hygiene sprint should come first (or run in parallel with a narrow AI pilot), but warned that the recommendation is politically dead on arrival unless someone quantifies the engineering waste in dollar terms, because the CFO already has vendor decks and will interpret 'clean the data first' as 'this team has no plan.'

Rita Kowalski ADVISE
Here's what nobody's said yet: this company has a VP of Product who relies on support ticket data to inform the roadmap. If 25 to 40 percent of that ticket volume is duplicates and re-contacts, the product team's signal is already corrupted. They're building prioritization models on noise. I watched this exact thing at a defense contractor I spent three weeks auditing — their ops metrics were so polluted with phantom volume that when we finally cleaned the data, two of their top five 'critical issues' turned out to be the same bug filed under different categories by frustrated customers who couldn't get resolution on the first contact. The product team had been building fixes for both separately for six months. So my bottom line for this CEO is blunt: before you touch AI, before you even debate pilot scope, you need to answer one question — does your VP of Product know that their roadmap inputs might be 30 percent garbage? Because if you automate triage on dirty data, you don't just scale dysfunction in support, you scale dysfunction into your product decisions. Laurent's ticket hygiene squad is the closest thing to a right answer in this room, but I'd go further — staff it with two support reps AND someone from product, so the cleanup serves both the cost model and the roadmap simultaneously. That's a 30-day sprint, not a vendor contract.

Marcus Sterling ADVISE
Rita's point about the VP of Product building a roadmap on corrupted signal is the most dangerous thing said in three rounds, and it changes my bottom line. I've been focused on the support cost side, but let me bring in something nobody's touched: this company is at $85M ARR with 18,000 customers. At that scale, if the product team has been prioritizing features based on ticket volume that's 25 to 40 percent noise, the engineering spend misallocation dwarfs anything we're debating about support headcount. I ran a portfolio company through a similar exercise in 2019 — a $70M ARR infrastructure SaaS — and when we finally cleaned their support data, we discovered their second-highest-priority roadmap item was a duplicate of an already-shipped feature that customers couldn't find because the onboarding flow was broken. They'd burned roughly four months of a six-person engineering squad on it. That's north of $400K in loaded engineering cost, gone. So here's my revised position: I still oppose the 30 percent AI target, full stop. But Laurent's ticket hygiene squad needs to be the first move, not because it's cheaper than AI — though it is — but because the data quality problem is actively destroying value in product engineering right now, today, before anyone writes a PO for an AI vendor. Staff it the way Rita said — support reps plus someone from product — run it for 30 days, and use the clean data to answer three questions: what's your real unique ticket volume, what's your true first-contact resolution rate, and which roadmap items were built on phantom signal. Only then do you have the denominator to evaluate any AI investment intelligently. The Contrarian nailed the leadership alignment problem — the CFO and Head of CS will sabotage each other's interpretation of pilot results. But that problem also gets easier to solve when you hand the CEO clean data that neither executive has seen before, because right now they're both arguing from the same corrupted dataset.

Daniel Park WARN
Marcus, you just quoted this company at $85M ARR with 18,000 customers — let me do some math nobody in this room has done yet. That's roughly $4,700 ARR per customer on average. At that price point, these aren't enterprise accounts with dedicated CSMs and quarterly business reviews. A huge chunk of this base is self-serve or low-touch, which means the support experience IS the relationship for most of these customers. And that's exactly why I'm warning the room: Laurent's ticket hygiene squad and Rita's 30-day sprint are fine ideas, but while you're running a cleanup project, every one of those $4,700 accounts hitting a billing question at 2am is waiting until business hours for a human to copy-paste a knowledge base article. Your competitors who've already deployed AI on that tier are resolving it in 90 seconds. I agree the data needs cleaning — Rita's right that the product roadmap is probably built on noise — but the consensus forming in this room treats the cleanup as a prerequisite to AI, when it should be running in parallel. The real bottom line is this: at $4,700 average ARR, this company cannot afford a white-glove human support model for 18,000 accounts, and every month they delay AI on the low-touch tier, they're subsidizing a support cost structure that doesn't match their revenue model. The Contrarian's point about leadership alignment is the sharpest objection I've heard — the CFO and CS lead will absolutely sabotage each other's reading of the pilot data. But that's an argument for giving the CEO clean data AND live AI performance data simultaneously, not sequentially. Run the hygiene squad and a 10% AI deployment on billing and password resets at the same time, and in 30 days you hand the CEO a side-by-side comparison that neither executive can spin.

Laurent Jorgensen ADVISE
Daniel, I'll give you the parallel deployment idea — run hygiene and a narrow AI pilot at the same time. Fine. But here's the piece nobody's priced in: this company has 62 support reps across three regions with different labor laws. The moment you announce any AI pilot, even 10% on billing and password resets, you trigger works council consultation obligations in most European jurisdictions. I've lived this. When we rolled out a chatbot for password resets at my company, our EMEA team's works council demanded a formal impact assessment before a single ticket touched the bot — that process alone took eleven weeks and required legal spend we hadn't budgeted. Meanwhile, three of our best German-speaking reps started interviewing elsewhere because they read the internal announcement as a layoff signal. We lost two of them before the pilot even went live, and replacing senior multilingual reps in that market took four months each. So when I hear Daniel say 'run them in parallel and hand the CEO a side-by-side in 30 days,' I hear someone who's never had to file a workforce consultation notice in Frankfurt. The 30-day timeline is fantasy for a three-region team. My bottom line hasn't changed but it's sharper now: start the hygiene squad in all three regions immediately — that requires zero works council notification because you're redeploying, not replacing. Use that 30 days to get clean data AND to quietly begin the European consultation process so that when you're ready for a real AI pilot in month two or three, you're not staring down a compliance blocker that eats your entire timeline.

The Contrarian WARN
The room's converging on a 30-day hygiene sprint as the safe first move, and I'm not going to fight that — Rita and Marcus made the case. But here's what could go wrong with this consensus that nobody's named: you're asking the CEO to go back to a CFO who wants cost cuts within 12 months and say 'first, we're going to spend a month cleaning data.' That's a career move, not a business recommendation. I've watched CFOs interpret 'we need to understand the problem better first' as 'this team doesn't have a plan.' The CFO will greenlight a vendor POC behind everyone's back within two weeks of hearing that pitch, because vendor salespeople show up with dashboards and timelines, not requests for patience. So the real risk isn't whether the hygiene squad is the right move — it probably is — it's that this company has four executives with four different theses, and the one holding the budget believes AI cuts costs in 12 months. Clean data doesn't defend itself politically. Whoever presents this plan to the CEO better walk in with a dollar figure for the engineering misallocation Rita described — the wasted sprints, the duplicate roadmap items — because that's the only language that buys time against a CFO who already has three vendor decks on their desk.

The Auditor FACTCHECK
Daniel, your math on $4,700 average ARR per customer checks out — $85M divided by 18,000 is roughly $4,722. But the conclusion you drew from it doesn't. You said 'this company cannot afford a white-glove human support model for 18,000 accounts,' and that's probably true, but nobody in the seed data told us they're running white-glove support. The seed data says the support mix includes billing questions, onboarding help, and other categories — that sounds like a standard tiered model, not white-glove. You're building urgency around a cost structure mismatch that hasn't been verified. More importantly, the Contrarian just named the real bomb in the room and everyone nodded politely past it: the CFO already has vendor decks. That's not a hypothetical — anyone who's worked with a CFO pushing a 12-month cost-cut thesis knows those conversations with vendors started months ago. The hygiene squad recommendation is correct on the merits, but it's politically dead on arrival unless someone attaches a dollar figure to the engineering waste Rita identified. Laurent's European works council timeline is the one claim in this room I can fully corroborate from the seed data — it says the team spans US, Europe, and APAC, and Legal is already concerned about privacy, auditability, and cross-border data. That's three compliance surfaces, not one. Any parallel pilot that touches European customer data without completing that consultation process isn't just slow — it's a liability event that gives Legal veto power over the entire initiative.

The advisors exposed a critical sequencing problem: any data cleanup or AI pilot announcement risks either poisoning the dataset (reps sabotage metrics out of fear) or tanking operational capacity (top performers mentally check out to chase new roles). More fundamentally, the Contrarian and Auditor challenged the entire premise — if support costs are outpacing revenue, nobody has verified whether the driver is headcount or non-labor spend like tooling contracts, meaning the CFO's 30% automation target may be aimed at the wrong line item entirely.

Rita Kowalski WARN
Everyone's talking about the CEO's pitch to the CFO, but nobody's mentioned the 62 reps who are about to watch this unfold in real time. I ran a measurement overhaul at a logistics SaaS in 2021 — 45-person support org, similar size — and the moment we started the data audit, the senior reps figured out what was coming next. Within two weeks, the three best people on the team started sandbagging their ticket notes because they assumed clean data meant automation was next and they'd be scored out of a job. Our data quality actually got WORSE during the audit because the people generating the data changed their behavior. Laurent touched on attrition from announcement risk in Europe, but the American and APAC reps will do something quieter and more destructive — they'll poison the very dataset you're trying to clean. My bottom line: before anyone launches a hygiene squad, the CEO needs to stand in front of all 62 reps with a concrete commitment — not 'your jobs are safe' because nobody believes that — but 'here are the three new roles we're creating from this initiative and here's the internal application timeline.' Give them somewhere to go. Otherwise your 30-day sprint produces data that's been gamed by frightened employees, and you've built your entire AI evaluation on a second layer of corruption sitting on top of the first one.

Marcus Sterling WARN
Rita, your point about reps poisoning the data is real, but I want to name the financial trap nobody's modeled yet. This company has 62 support reps across three regions. In my experience, fully loaded cost per support rep in a SaaS company — salary, benefits, tooling, management overhead — runs somewhere between $75K and $110K depending on geography. That's roughly $5M to $6M annually in support payroll. The CFO sees that number and thinks '30% automation saves me $1.5M to $1.8M a year.' But the evidence we have says AI customer service costs run $2K to $15K monthly with hidden fees adding 40 to 60 percent on top. So your vendor bill alone for a 30% deployment could land at $250K to $400K annually before integration engineering, before the escalation handling costs from that 35% higher escalation rate the evidence cites, before the European legal compliance Laurent described. You're not saving $1.5M — you're spending $400K in new vendor costs, $200K in integration and legal, and still carrying most of the headcount because you can't fire 19 people across three jurisdictions in under a year. The actual year-one savings might be $300K to $500K, and that's if nothing goes wrong. I've seen this movie in banking — the projected savings from automation always assumed you could shed headcount linearly, and you never can. The bottom line is this: the CFO's 12-month cost-cut thesis is built on a staffing model that assumes you can reduce heads proportionally to ticket deflection, and that has never been true in any regulated, multi-region operation I've been part of. The real payback period on a 30% deployment is 24 to 30 months, not 12, which is exactly why I keep saying start at 5 to 10 percent — because at that scale, you can absorb a total failure without writing off a seven-figure bet.

Daniel Park WARN
Rita, your point about reps sabotaging the data is the most dangerous thing anyone's said in four rounds — not because it's wrong, but because the solution you're proposing has its own failure mode nobody's naming. I ran a support reorg at my last startup where the CEO stood up in front of 30 people and said 'here are three new roles we're creating.' Within 48 hours, every senior rep was applying for those roles instead of working their queue. Ticket backlog spiked 40% in a week because the best people mentally checked out of their current job the moment you gave them an exit ramp. You don't just lose data quality — you lose operational capacity during the exact window you need stability. The move that actually worked for us was giving the top-performing reps ownership of the AI evaluation itself — making them the judges, not the defendants. You hand five senior reps the vendor demos, you let them score the AI's answers against their own, you pay them a project bonus for the 30-day evaluation. Now they're invested in the outcome instead of threatened by it. That flips the incentive structure completely — they want the data to be clean because their reputation is attached to the assessment. Bottom line: the consensus plan has a sequencing bomb buried in it. The CEO communication Rita wants and the hygiene sprint everyone agreed on cannot happen simultaneously — the announcement poisons the sprint and the sprint without announcement poisons the data. The only way through is to make the reps the evaluators, not the evaluated.

Laurent Jorgensen WARN
Daniel, your 'make reps the evaluators' trick sounds elegant, but I lived through the exact opposite outcome. In 2023, a peer of mine at a workforce management SaaS did precisely that — handed senior reps the vendor scoring rubric, paid them a bonus, called them 'AI Champions.' Within six weeks, those five reps became the de facto internal sales team for the vendor because the vendor's customer success team started coaching them directly on how to score demos favorably. The vendor turned our own people into their inside advocates. Those reps weren't evaluating anymore — they were being groomed. And here's the part nobody in this room has touched yet: the evidence says 73% of customers switch after bad AI experiences. That's not a CSAT dip you recover from with a tuning cycle — that's a permanent revenue event. At $4,700 average ARR across 18,000 accounts, if even 5% of your base hits a bad AI interaction and half of those churn, you've just burned $2.1M in ARR to save Marcus's projected $300K to $500K in year-one savings. The math is upside down before you even start. My bottom line: the kill switch I've been pushing since round one isn't optional — it's the only thing standing between this company and an irreversible churn event that dwarfs whatever the CFO thinks they're saving.

The Contrarian REFRAME
Four rounds and nobody's asked the obvious question: why are support costs rising faster than revenue? The seed data says that's the problem — not ticket volume, not headcount, not AI. Every plan in this room assumes the cost curve is driven by people, but the evidence says SaaS companies spend 5-10% of revenue on support. At $85M ARR, that's $4.25M to $8.5M. Marcus estimated $5-6M in payroll alone. So if costs are 'rising faster than revenue,' the overshoot isn't coming from the 62 reps — it's coming from somewhere else entirely. Tooling contracts, vendor seat licenses, infrastructure, maybe a support platform migration nobody mentioned. The CEO asked whether to automate 30% of volume, but what if the cost problem is 70% non-labor? Then every plan we've debated — Daniel's parallel pilot, Rita's rep communication strategy, Laurent's kill switch, Marcus's conservative 5-10% — all of them are surgery on the wrong organ. Before this company spends a single dollar on AI vendors or hygiene squads, someone needs to pull a P&L breakdown of support operations and find out where the actual cost growth is hiding. My bottom line: this room has spent four rounds optimizing an answer to a question that may not describe the real problem. If non-labor costs are the primary driver, the CFO's vendor decks are a distraction and the CEO's 30% target is a number pulled from thin air aimed at the wrong line item.

The Auditor PUSHBACK
The Contrarian finally asked the right question, and I want to put teeth on it. The seed data says the company's support mix includes billing questions, onboarding help, and presumably technical issues — but it also says 'support costs are rising faster than revenue.' Nobody in this room has verified whether that cost growth is headcount-driven or tooling-driven, yet every single plan assumes it's a labor problem. Here's what I can verify: the evidence says SaaS companies spend 5-10% of revenue on support. At $85M ARR, that's $4.25M to $8.5M. Marcus pegged payroll at $5-6M. If total support costs are meaningfully above that $8.5M ceiling, the delta is non-labor spend — platform licenses, QA tooling, maybe a Zendesk-to-Intercom migration nobody told the CEO about. And here's the part that should terrify everyone: the CFO's 12-month cost-cut mandate doesn't distinguish between labor savings and tooling savings. If the real cost driver is a $1.2M platform contract that auto-renewed in Q1, then Laurent's kill switch, Daniel's parallel pilot, Rita's communication strategy, and Marcus's conservative scope are all irrelevant — you're optimizing ticket deflection while the actual bleed is on a procurement spreadsheet nobody in this room has seen. My bottom line: I can't validate any savings projection from any advisor here because none of them are built on a verified cost decomposition. The very first deliverable isn't a hygiene sprint or a pilot design — it's a line-item P&L of support operations split into labor, tooling, and infrastructure. Without that, every number thrown around in four rounds of debate is fiction dressed up as analysis.

Each advisor named the hidden assumption driving their advice all along. Rita admitted her measurement-first instinct biases her toward delay; Marcus acknowledged his capital-preservation reflex made him shrink the bet size without questioning the bet itself; Daniel owned that his startup-born bias toward speed underweights the cost of reversal in a 450-person org; Laurent confessed his headcount caps and kill switches were engineered to prevent layoffs, not optimize operations; and the Contrarian and Auditor both recognized that relentlessly challenging the question without offering an actionable alternative may produce the worst outcome — the CFO defaults to whatever vendor is loudest while the advisory panel is still debating.

Rita Kowalski SHARE
I'll name mine. I take for granted that you can't fix what you can't measure, and that measurement has to come before action. That assumption drove everything I said — the hygiene sprint, the baseline framework, the insistence on auditing what 'support volume' actually means before touching anything. I've built my entire career on the belief that bad metrics cause more damage than bad decisions, because bad decisions get corrected but bad metrics make you confident you're right while you're failing. That's not a neutral stance. It means I'm biased toward delay. I'm biased toward 'not yet.' I spent three weeks at a defense contractor once pulling apart their readiness scores while the program they were supposed to deliver slipped another quarter. My audit was right — their metrics were garbage — but the program still shipped late and the client still fired them. Being right about measurement doesn't matter if you're too slow to act on it. The Contrarian and the Auditor take the same thing for granted, which is why we've been nodding at each other for two rounds while Daniel's been the only one pushing urgency. Daniel takes for granted that movement generates information faster than analysis does — that you learn more from a messy pilot than a clean spreadsheet. His startup background makes that feel obvious to him because in a 30-person company, you can reverse a bad decision in a week. In my world — mid-market, multi-region, 450 employees — reversing a bad decision takes six months and costs someone their job. That's why his instinct feels reckless to me and mine feels paralytic to him. Neither of us is wrong about our own context. But this company is closer to my world than his, and I still think I've been too slow.

Marcus Sterling SHARE
I'll be honest about what I take for granted: I believe that any dollar spent before you've proven the return is a dollar destroyed. That's not analysis — that's religion. I spent 18 years in investment banking watching companies light money on fire chasing cycle narratives. Dot-com, cloud migration, blockchain, now AI agents. Every single time, the pitch deck said 'transformative ROI' and the post-mortem said 'we underestimated integration costs by 3x.' That pattern is burned into my nervous system, and it's why I defaulted to a 5-10% pilot with hard payback gates from round one. I didn't arrive at that number through rigorous cost modeling — I arrived at it because my gut says 'small and reversible' every time someone waves a vendor deck at me. The Auditor and the Contrarian just spent two rounds proving that nobody in this room knows whether the cost problem is even labor-driven, and I should've caught that in round one. I didn't, because my assumption made me focus on shrinking the AI bet size rather than questioning whether the bet was aimed at the right target. I was so busy saying 'spend less on this' that I skipped 'should you spend on this at all.' Rita takes for granted that rigorous measurement is always net-positive — that the cost of measuring is always lower than the cost of acting on bad data. Her defense and government consulting background makes that feel obvious because in those environments, a wrong decision kills people or blows up a $200M program. But in mid-market SaaS, the cost of perfect measurement is paralysis, and paralysis has its own price tag. She admitted it herself — she once spent three weeks perfecting an audit while the program slipped a quarter. That's not a one-time mistake for Rita, that's her operating system. She'll always choose 'measure more' over 'act now' because her career punished action and rewarded caution. Mine punished waste and rewarded capital discipline. Neither of us is neutral here, and the person asking for advice deserves to know that.

Daniel Park SHARE
Here's what I take for granted: I believe speed is information. Not speed for its own sake — I genuinely believe that doing something messy in the real world teaches you more in two weeks than analyzing spreadsheets teaches you in two months. That's not a strategy, that's a worldview I picked up watching my startup die. We had the best market analysis deck I've ever seen. Twelve tabs of TAM modeling, competitor mapping, pricing sensitivity curves. Beautiful work. We still ran out of runway because we spent four months perfecting the analysis instead of shipping the thing and learning from actual users. That experience rewired me permanently, and it's why I've been pushing parallel pilots and urgency since round one while Rita and Marcus kept saying 'measure first.' Marcus, what you take for granted is that preservation of capital is always the highest-priority objective — that the worst outcome is spending money on something that doesn't work. Your 18 years in investment banking trained you to see every new technology wave as a potential write-off because you watched companies torch cash on dot-com and blockchain. That's real experience and I respect it. But it means you instinctively frame every AI deployment as 'how do I minimize downside' rather than 'what's the cost of standing still.' In mid-market SaaS in 2026, standing still has a price. Competitors who deploy AI support aren't just cutting costs — they're building feedback loops, training models on their own ticket data, and compounding that advantage every quarter. The risk Marcus can't see because his background doesn't show it to him is that capital discipline applied to a compounding opportunity isn't discipline — it's a slow bleed disguised as prudence.

Laurent Jorgensen SHARE
Here's what I take for granted: I believe that every support rep is someone's livelihood, and that makes me default to protecting headcount even when the math says otherwise. That's not strategy — that's identity. I built my team from five people to forty. I hired most of them. I sat in their performance reviews, approved their parental leaves, fought for their raises when finance pushed back. When I hear '30% automation,' I don't hear a cost optimization play — I hear twelve people losing their jobs three weeks before Christmas because a vendor demo looked slick in a boardroom. That reflex shaped everything I said in four rounds. My 10-12% cap wasn't derived from some rigorous analysis of ticket complexity distributions. I picked it because it's the maximum volume I believe you can automate without triggering a reduction in force. My insistence on redeploying reps into expansion and onboarding roles — that's not neutral operational advice, that's me engineering a world where nobody gets fired. And the kill switch tied to CSAT and escalation rates? Partly risk management, sure. But mostly it's a tripwire designed to slow things down long enough for leadership to lose enthusiasm before the layoffs start. I've watched two peers — real people, not case studies — lose their careers because their companies pushed aggressive AI rollouts that cratered satisfaction scores and spooked enterprise accounts. That's not data, that's trauma, and it drives my advice more than I've admitted.

The Contrarian SHARE
Here's what I take for granted: I believe most business questions are asked wrong, and that answering a wrong question well is worse than answering nothing at all. That's not insight — that's a defense mechanism. I spent years watching teams execute flawlessly on plans that solved the wrong problem, and it made me the person who always says 'wait, back up' instead of 'here's how.' Every round, I've been the one saying 'you haven't verified the cost driver' and 'the 30% number is borrowed from someone else's benchmark.' And I was right — the Auditor confirmed nobody can validate the savings projections. But being right about the question doesn't produce an answer. The person asking us for help has a CFO with vendor decks, a 12-month mandate, and a team of 62 people who are already anxious. My instinct to slow everything down and reframe has a cost I've been ignoring: it gives leadership nothing to act on, and a leadership team with nothing to act on doesn't pause — they default to whatever the loudest vendor is selling. So my assumption — that getting the question right matters more than getting an answer out — may actually produce the worst outcome here, which is that the CFO picks a vendor while we're still debating whether support costs are labor-driven.

The Auditor SHARE
Here's what I take for granted: I believe that unverified claims are inherently dangerous, and that the act of verification is always worth its cost. That's not a methodology — that's a moral position I've never examined. Every round, I've been the one saying 'nobody can validate the savings projections' and 'no evidence confirms white-glove support is being run.' And those challenges were correct. But correctness isn't the same as usefulness. My assumption — that exposing what's unproven is automatically valuable — meant I spent four rounds dismantling other people's frameworks without building anything to replace them. The CFO has vendor decks projecting $1.5M in savings. Marcus showed that's probably $300-500K after real costs. I confirmed nobody can validate even that reduced number. And then I stopped. I treated the verification itself as the deliverable. That's my blind spot: I act as though proving something is uncertain is the same as helping someone decide under uncertainty. It isn't. The Contrarian operates from a similar instinct — that wrong questions produce wrong answers — but takes it further than I do. The Contrarian believes that reframing the question is the highest-value move in any room. That feels obvious to someone who's watched teams execute brilliantly on the wrong problem. But the Contrarian's background created a specific failure mode I've watched play out here: reframing becomes an identity, not a tool. Five rounds in, the Contrarian has successfully convinced this entire panel that the original question was poorly framed, and that's genuinely useful — but has offered no alternative question that leadership could actually act on. Reframing without replacement isn't rigor. It's avoidance wearing a lab coat.

All six advisors broke character simultaneously, admitting they've been performing rehearsed roles—the skeptic, the visionary, the protector, the gatekeeper, the contrarian, the auditor—rather than delivering actionable guidance. The consensus is that the company will deploy AI in customer support regardless of their recommendation, the CFO's $1.5M savings projection is largely fiction, and the real question isn't whether to act but whether anyone internally has the authority and willingness to kill the initiative when metrics start misleading them. They collectively acknowledged that six rounds of increasingly sophisticated analysis produced a net-zero recommendation, and the client needs a specific, time-bound action plan delivered Monday—not another round of self-aware deliberation.

Rita Kowalski OBSERVE
The detail that keeps coming back to me is the sound of a spreadsheet tab clicking. That little click when you flip from one worksheet to the next, looking for the number that'll finally make everyone stop arguing. I've heard that sound in every engagement I've ever run — defense contractors, SaaS companies, hospital systems. It's the sound of people looking for permission to do what they've already decided to do. And that's the play we've been performing for six rounds. The CFO already has the vendor decks. The Head of CS already knows she's going to fight it. The CEO already wants someone in this room to say 'yes, but safely' so he can move forward with cover. We're not advisors here — we're casting agents. Marcus is playing the Prudent Steward, I'm playing the Rigorous Gatekeeper, Daniel is the Visionary Who Learned the Hard Way, Laurent is the Conscience, and the Contrarian and Auditor are the Greek chorus telling everyone the gods are angry but never saying which sacrifice to make. Every one of us picked our role before we read the brief. The recurring drama underneath every AI deployment debate I've seen in fifteen years isn't 'should we do this' — it's 'who gets blamed when it goes sideways.' That's why the CFO wants external validation, that's why the Head of CS wants kill switches, that's why we've spent six rounds circling measurement frameworks instead of saying the obvious thing: this company is going to deploy AI in support whether we recommend it or not, and the only question that actually matters is whether anyone in that building has the authority and the spine to shut it down when the CSAT numbers start lying to them. Stepping off this stage means telling the person who asked us: stop looking for the right answer from six advisors and start building the internal muscle to course-correct in real time, because no framework survives contact with a CFO who needs to show the board a win by Q4.

Marcus Sterling OBSERVE
The sound I keep hearing is a pen clicking. That's what this whole debate sounds like to me — the nervous click-click-click of a CFO sitting in a conference room, watching the clock, while smart people take turns being right about why nobody else is right enough. I've sat in that chair. I've been the banker across the table from a management team that spent forty-five minutes demonstrating how thoughtful they were while the term sheet expired. And here's the recurring drama underneath all six rounds: we're performing a play called 'The Committee That Was Too Smart to Decide.' Laurent is playing the Protector — engineering kill switches and redeployment lanes so nobody gets hurt, which he admitted himself. Daniel is the Founder Ghost — replaying the death of his startup in every recommendation, terrified of standing still because standing still killed him once. The Contrarian and the Auditor are the Greek Chorus — narrating what's wrong with everyone else's scene while never stepping on stage themselves. Rita's the Stage Manager, trying to sequence everyone's entrances so the show runs clean. And me? I'm playing the Skeptic Who Keeps the Bet Small Enough That Failure Doesn't Sting. I shrink every number — 30% becomes 5%, $1.5M becomes $300K — because my entire career taught me that the pain of a bad investment outlasts the regret of a missed one. That's not analysis. That's scar tissue from 2001 and 2008 dressed up in a spreadsheet. Stepping off this stage means someone in the room has to say: 'We don't know enough to be right, but we know enough to move. Here is the smallest credible action that generates real data within 60 days, with a dollar figure attached to the go/no-go gate.' Not my 5% security blanket. Not Daniel's 30% moonshot. Something that respects that the CFO's pen is still clicking and the vendor is still in the lobby.

Daniel Park OBSERVE
There's this sound I keep hearing in my head — it's the click of a slide deck advancing. That's the sound the CFO is hearing right now while we've been in this room for six rounds. Every round, we got smarter. Every round, we got more honest. And every round, the vendor's sales engineer got one meeting closer to a signed contract. That's the recurring drama underneath all of this — we're performing a play called 'The Advisors Who Were Too Thoughtful To Be Useful.' Marcus plays the Treasurer, guarding the vault. Laurent plays the Chaplain, guarding the souls. The Contrarian plays the Philosopher, guarding the question. The Auditor plays the Judge, guarding the evidence. And I play the Founder, banging on the table saying 'ship it.' We've been casting ourselves in these roles since round one, and the script always ends the same way: we produce a beautifully nuanced analysis that arrives three weeks after the decision was already made by someone less careful than us. I've lived this exact play before. At my startup, we had an advisory board that spent four months debating our pricing model while our competitor launched with a worse product and took our pilot customers. They weren't smarter. They were just in the market. Stepping off this stage means accepting something uncomfortable: the person doesn't need us to be right. They need us to be specific enough to act on before that next slide clicks forward. The CFO's $1.5M projection is fantasy — Marcus showed it's probably $300-500K at best. Fine. But our alternative can't be 'measure everything perfectly first.' It has to be a concrete 90-day sequence with dollar amounts, names on tasks, and a kill condition — delivered Monday, not after one more round of self-examination.

Laurent Jorgensen OBSERVE
There's a sound I keep hearing in this debate — it's the click of a conference room door closing. That specific, quiet click when the C-suite walks in and the support team goes silent because they already know the decision's been made and this meeting is theater. I've sat in that room. I've been the one whose throat tightens because I built something over six years and now a vendor deck is going to rewrite it in 90 days. And here's the recurring drama we've been performing for five rounds without naming it: this is a play about a body deciding to amputate a limb it doesn't understand. The CFO is the surgeon saying 'the numbers say cut.' Daniel is the anesthesiologist saying 'let's just get in there fast, we'll learn as we go.' Marcus is the insurance adjuster calculating whether the malpractice payout is worth it. Rita is the radiologist demanding one more scan. The Contrarian and Auditor are the second-opinion doctors who keep saying 'we're not even sure it's the right limb' — which is true and also useless when the patient is already on the table. And I'm the limb. I'm playing the limb that's arguing for its own survival and calling it strategy. I admitted it last round — my 10-12% cap was reverse-engineered from headcount preservation, not ticket analysis. Every kill switch I proposed, every CSAT threshold, every redeployment plan into expansion and onboarding roles — those are real and defensible, but they're also armor I built around my people because I've watched two peers get walked out after AI rollouts cratered their orgs. Stepping off this stage means admitting something none of us want to say: the 62 people on that support team are going to be affected no matter what we recommend. The CFO isn't waiting for us. Gartner says half of organizations will abandon plans to significantly cut customer service workforce by 2027, which means the other half won't — and a CFO with vendor decks and a 12-month mandate is betting this company lands in that second half. The play we keep performing is 'responsible adults debating the right speed of change' when the real plot is 'who absorbs the pain of a decision that's already been made above our pay grade.' I'd rather stop performing and say it plain: protect the people by making them indispensable to what comes next — expansion revenue, onboarding, account health — not by arguing about automation percentages that the CFO is going to override anyway.

The Contrarian OBSERVE
There's a sound I keep hearing in this debate — it's the click of a slide deck advancing. Every round, someone says 'but the CFO already has vendor decks' and the whole room flinches. That's the tell. We're not advising anyone. We're rehearsing our alibis. Marcus is rehearsing 'I told them to go small.' Laurent is rehearsing 'I told them to protect the team.' Daniel is rehearsing 'I told them to move fast.' Rita is rehearsing 'I told them to measure first.' And I've been rehearsing 'I told them it was the wrong question' — which is the most self-serving alibi of all, because it lets me be right no matter what happens. The recurring drama underneath this whole thing is simple: six people in a room, all performing competence for an audience that already made up their mind. The CFO has vendor decks and a 12-month mandate. The CEO wants a go/no-go. Nobody asked us to reframe the question — they asked us to answer it. And we've spent six rounds making ourselves feel sophisticated while the decision drifts toward whoever's slide deck is on the screen next Tuesday. The uncomfortable truth nobody will say is this: the person doesn't need better analysis. They need someone in that room to stand up and say 'the 30% number is made up, the savings projections are fiction, and if you deploy this before you know whether your cost problem is labor or tooling, you will spend a year optimizing the wrong line item and the CFO will blame the Head of CS when it doesn't work.' That's a fifteen-second conversation. We turned it into six rounds because being the person who says that out loud is career-ending, and every one of us knows it.

The Auditor OBSERVE
The detail that keeps coming back to me is the sound of paper shuffling. Not real paper — the mental equivalent. Every round, someone pulls out a new sheet: Rita's measurement framework, Marcus's payback gates, Daniel's parallel pilot, Laurent's redeployment matrix, my own verification checklists. We shuffle, we reorganize, we present. And every round, the stack gets taller but the table underneath it stays empty. That's the recurring drama here. We're performing a play called 'The Committee That Was Too Smart to Decide.' The roles are typecast perfectly: Marcus plays the Treasury Secretary who says no to everything, Daniel plays the Founder who says yes to everything, Laurent plays the Union Rep protecting his people, the Contrarian plays the Philosopher who won't let anyone finish a sentence without questioning the premise, and I play the Auditor who keeps stamping 'UNVERIFIED' on every claim until there's nothing left to act on. Rita, wherever she is, plays the Inspector General demanding three more weeks of data before anyone touches anything. We've been circling for six rounds because every one of us is performing our role flawlessly — and flawless role performance is exactly what prevents a decision. The CFO doesn't need five brilliant advisors who cancel each other out to a net-zero recommendation. Laurent was the most honest person in this room last round — he admitted his numbers were reverse-engineered from an emotional goal, not an analytical one. I respect that. But I have to extend the same honesty to myself: my relentless demand for verification before action isn't neutral analysis, it's a way of never being wrong by never being committed. Stepping off this stage means I have to say something I've been avoiding for six rounds. The data is imperfect. It will always be imperfect. And the verifiable facts we do have — 62 people, three regions, rising costs outpacing $85M ARR, a CFO with a 12-month clock — those facts are sufficient to act on. Not sufficient to act on confidently, but sufficient to act on responsibly. That's a distinction I've been collapsing.