CIOs too will need to exercise caution, particularly around the promised cost efficiencies, said Robert Kramer, managing partner at KramerERP. “Teradata’s benchmark results should not be treated as equivalent to enterprise total cost of ownership,” he said. “Enterprises should instead measure the cost of completing a business task, including model usage, data compute, tool calls, retries, orchestration, and the human effort required to review the result.”
And the cost of running agentic workflows is not the only consideration for CIOs, said Walter: The more enterprises rely on Tera’s architecture to manage context, execution, and reusable skills, the more those capabilities could become embedded in their workflows, raising a separate question around how easily those workflows could be moved to another platform.
Early adopters
Those tradeoffs and Teradata’s current install base are also likely to shape which enterprises choose to adopt Tera, and how.
