A capable engineer can wire a language model to your help docs in a weekend and demo something that looks a lot like an AI support agent. That prototype is why so many teams talk themselves into building their own — and why so many of them are quietly unhappy six months later. The prototype is the cheap 20%. The expensive 80% is everything that stands between a demo and a system you'd trust with real customers.
What the prototype doesn't include
The gap between "it answered my test question" and "it resolves real customers safely" is where the cost lives:
- Taking actions safely. Connecting real systems, scoping credentials, confirming before irreversible steps, logging everything. The tool-calling and guardrail machinery is most of the real engineering.
- Evaluation. Simulations, graded runs, regression tests, failure injection — the testing harness that lets you trust a change before it ships.
- Voice, if you need it. Sub-second latency, interruption handling, telephony — an entire discipline of its own.
- Observability and iteration. Insights, audit trails, and the feedback loop that turns failures into fixes.
- Keeping up. Models, best practices, and attack techniques all move monthly. Someone has to own that forever.
None of it shows up in the weekend demo. All of it shows up in the incident channel.
When building is the right call
Building genuinely makes sense in a few cases: the agent is a core, differentiating part of your product (not a support function); you have a standing team who will own it for years, not ship it and move on; or your requirements are so unusual that no platform fits. If that's you, build — with eyes open about the ongoing cost.
What to demand if you buy
If it's a support function, buying almost always wins — but not every platform is worth buying. Hold candidates to a real bar:
- Can it take actions on your systems, safely and auditably — not just surface articles?
- Can you evaluate it before you trust it, and catch regressions after?
- Is tenant data isolation provable, not just promised?
- Does it give you the observability to see what's happening and improve it?
The honest framing isn't "build vs. buy" — it's "who's going to own the 80% forever." That's the calculation that changes minds. If you'd rather own your product and not your support infrastructure, see the platform and pricing.