For most of this series I wrote like a consultant pitching a business case. I want to drop that for the last part and be straight with you.
UKConnect isn't a real company. I made it up. I built this system to learn, and to show how the pieces actually fit together — not for a paying client. So there are no real customers, and there is no real ROI. I'm not going to invent one.
Why this post used to have numbers in it
The first version of this post quoted a "60% cost reduction" and a tidy per-agent saving. I put those there because I thought they'd get clicks, and they probably would. But a confident ROI figure for a fictional company is exactly the kind of thing that falls apart the moment someone asks a real question — and it's the opposite of why I write any of this. So I took it out. This is the honest version.
What I can actually stand behind
Plenty, just not a savings percentage. The system is real and it works. The architecture genuinely gives you consistency, round-the-clock availability, scaling without new headcount, and a logged record of every conversation — those are properties of the design, not numbers I made up. I also know what it costs to run, because I run it: a Gemini API bill and some cheap infrastructure, not a salaried team.
What I can't tell you is what it would save your support desk, because I've never pointed it at a real one. Anyone who quotes you a clean percentage off a demo is guessing.
How you'd find the real number
If you did deploy something like this, the honest way to learn its worth is to measure it, not to trust a slide. Take a baseline first — what a resolved contact costs you today. Then run the system on a slice of real traffic and watch cost per resolved contact, how many contacts it handles without a human, escalation rate, and customer satisfaction. The ROI is whatever those numbers say after a couple of months. It'll be specific to you, and it might be great — but it's earned, not assumed.
One thing I'd say with confidence: it won't take your team to zero. You still want people for the hard, sensitive, and angry cases, and someone watching the system. The realistic shape is "handle the bulk, escalate the rest."
The proof is the system, not a stat
So here's what I'll claim instead of a number: it's a complete, working, open-source build that you can read, run, and pull apart yourself. That's the actual evidence I can offer — more honest than any figure I could put on a fictional company, and more useful too.
That's the series
Over eight parts I've built a real customer support system — the architecture, the data layer, the Policy Agent, the Ticket Agent, the orchestration, the location handling, and the testing. It's all open source, and there's a LangGraph version too if you're choosing a framework.
If I had one piece of advice: start with a pilot, measure everything against a real baseline, and expand on proven value rather than a slide deck.
If you want a system like this built for your business — and rolled out without breaking your support team — that's what I do at twentytwotensors. Get in touch.