The integration tax nobody prices in
By Lewis Crook ·
Most voice AI business cases price the platform, the per-minute cost, and the implementation services. Almost none price the integration depth required to make the platform useful — which is the line item that decides whether the deployment can write a record, schedule a callback, or take a payment without an engineer in the loop.
The pattern is consistent. A pilot is scoped against a read-only API surface because read-only is what the vendor can stand up quickly. The pilot demonstrates that the AI can answer balance and status questions. Stakeholders are pleased. The production gate exposes that resolving a real intent requires write access against a system of record that has authentication, idempotency, and audit requirements the pilot never tested.
By the time that surfaces, the budget has been spent on the platform, not on the integration work. The programme either delays for another quarter to do the integration properly, or it ships a read-only deployment that is technically a voice AI but functionally a self-service lookup.
Price the integration depth from week one. Treat the API surface, the identity layer, the write-side idempotency, and the observability into integration failures as primary line items. The platform is the cheap part of a voice AI programme; the integration is where the resolution comes from.