loader from loading.io

Measuring the True Cost of AI With Front

Tech Talks Daily

Release Date: 11/17/2026

 IGEL Reaches Unicorn Status and Why Endpoint Resilience Matters Now show art IGEL Reaches Unicorn Status and Why Endpoint Resilience Matters Now

Tech Talks Daily

What does IGEL reaching unicorn status mean for the customers and people behind the company? It was lovely to welcome my friend Klaus back to Tech Talks Daily for a conversation that felt like a catch-up with some particularly good news. We’ve spoken many times over the years, from Frankfurt to Miami, and this time we began with IGEL’s valuation above one billion dollars and the arrival of Vitruvian Partners alongside TA Associates. Klaus describes what the milestone means to a team that has spent years building the business. We also talk about the company’s reported annual recurring...

info_outline
How to Verify AI Research Before Acting with AlphaSense show art How to Verify AI Research Before Acting with AlphaSense

Tech Talks Daily

Would you put an AI answer in front of your board if you couldn’t tell which source supported its most important claim? On Tech Talks Daily, I’m joined by Julia Lecocq, who leads corporate sales in Europe and Asia-Pacific for AlphaSense. Julia works with teams making decisions about acquisitions, new markets, and competitive threats. We discuss why having access to thousands of documents can still leave someone with the hardest part of the job: working out which evidence applies to the decision in front of them. Julia uses earnings call preparation to explain the difference between finding...

info_outline
From Security Alert to Verified Fix with Cogent Security show art From Security Alert to Verified Fix with Cogent Security

Tech Talks Daily

How much time passes between discovering a vulnerability and getting the right person to fix it? On Tech Talks Daily, I’m joined by Vineet Edupuganti, co-founder and CEO of Cogent Security, to talk about the work that takes place after a scanner finds a problem.  Vineet describes it as an assembly line: someone has to find the affected systems, work out where they’re exposed, identify the owner, and get the fix completed. Each handoff gives a ticket somewhere to get stuck. One of the simplest examples Vineet gives is a vulnerability sent to the wrong person. The agent may have...

info_outline
Measuring the True Cost of AI With Front show art Measuring the True Cost of AI With Front

Tech Talks Daily

What does AI really cost when a cheap model fails, retries the task, hands the work to a person, and leaves the customer returning with the same problem? In this episode of Tech Talks Daily, I welcome back Dan O’Connell, CEO of Front, to discuss AI tokenomics and why token consumption is a poor substitute for business value. Our previous conversation focused on Bring Your Own Agent and the need for companies to choose the agents that fit their customer experience. This time, we turn to the economics behind those decisions. Dan describes tokens as the new cloud bill. As businesses deploy...

info_outline
Making Time For Real Work With AI and lilAgents show art Making Time For Real Work With AI and lilAgents

Tech Talks Daily

When AI saves you time, who gets to decide what happens to the time you get back? On Tech Talks Daily, I welcome back David V. Kimball, co-founder and CEO of lilAgents. David started working remotely in 2018, after most of his marketing department moved to another city. We talk about what he gained from working in a space set up for him and what became harder when the office and family life shared an address. David explains how he uses time blocking with his family and why a private appointment can show up as “busy” on a work calendar without giving away what he’s doing. He built a small...

info_outline
My Coworker Is a Robot and What AI Means For Your Job show art My Coworker Is a Robot and What AI Means For Your Job

Tech Talks Daily

How would you feel if your employer told you that an AI system would be doing part of your job next month? On Tech Talks Daily, I’m joined by technology journalist Jon Swartz, author of My Coworker Is a Robot, to talk about what workers are hearing from management and what they’re telling him in return. Some can picture a working day with fewer repetitive tasks. They can also see the uncertainty in front of them, especially when they’re asked to adopt new tools without the time or support to learn how they work. Jon gives me a personal example from a doctor’s appointment. His doctor...

info_outline
Closing the AI Governance Reality Gap With AI Score show art Closing the AI Governance Reality Gap With AI Score

Tech Talks Daily

How do you govern AI when the technology, its users, and the work it performs keep changing after you approve it? On Tech Talks Daily, I'm joined by Alex Harland, co-founder and CEO of AI Score, to discuss the distance between an AI policy and the reality of everyday operations. A company may approve a platform and complete its initial review, yet employees discover new applications, vendors introduce features, and agents begin working with different information. Alex argues that governance has to keep following those changes if it is going to remain useful. What interested me was his emphasis...

info_outline
Prevail: What Leaders Must Do Now Because Machines Can't Manage show art Prevail: What Leaders Must Do Now Because Machines Can't Manage

Tech Talks Daily

If an AI pilot works, what evidence would persuade you to fund it across the business? Three years after our conversation about Digital Transformation Payday, I welcome Tim Bottke back to Tech Talks Daily to discuss PREVAIL, his book on the decisions leaders make before anyone selects a model. Tim's argument is that by the time a project disappoints, the questions that might have changed its direction can be months behind it. We talk about what happens when the CTO wants room to experiment, the commercial team wants a better customer experience, and the CFO expects lower costs. Those are all...

info_outline
Using AI to Support Human Skills With Taskrabbit show art Using AI to Support Human Skills With Taskrabbit

Tech Talks Daily

What does useful AI look like when the work still needs someone to arrive at your home with the right skills and tools? In this episode of Tech Talks Daily, I speak with Ania Smith, CEO of Taskrabbit, about the relationship between digital technology and practical work. We discuss furniture assembly, TV mounting, and the decisions involved in connecting a customer with someone who can complete the job. For Ania, the opportunity is to make that connection easier while keeping the people doing the work central to the experience. A TV mounting request sounds straightforward until you consider the...

info_outline
How Deloitte Measures the Cost of Enterprise AI show art How Deloitte Measures the Cost of Enterprise AI

Tech Talks Daily

Could you explain why your AI bill rose and what the business got in return? I asked Jim Rowan, US Head of AI at Deloitte, because a total spend figure tells a finance team how much it paid, but gives it little help deciding which work to expand. In Deloitte's State of AI in the Enterprise survey, 71 percent tracked total AI interface and API spend, 51 percent tracked token volume, and 44 percent tracked the cost per unit. Jim suggests looking at what it costs to finish a task to an acceptable standard. We talk about what surrounds the model: the tools it can call, the information it can...

info_outline
 
More Episodes

What does AI really cost when a cheap model fails, retries the task, hands the work to a person, and leaves the customer returning with the same problem?

In this episode of Tech Talks Daily, I welcome back Dan O’Connell, CEO of Front, to discuss AI tokenomics and why token consumption is a poor substitute for business value. Our previous conversation focused on Bring Your Own Agent and the need for companies to choose the agents that fit their customer experience. This time, we turn to the economics behind those decisions.

Dan describes tokens as the new cloud bill. As businesses deploy agents across a growing number of customer interactions, usage-based charges can rise quickly. That number may show activity, but it does not explain whether the work created a useful result. A high token count can represent productive automation, repeated attempts, unnecessary complexity, or a task that eventually required human intervention.

His preferred measure is the total cost per successful outcome. In customer support, that means looking beyond the model’s headline price and accounting for every part of the journey. Model retries, agentic retries, human review, handoffs, coordination, response time, and the final customer result all affect the true cost to serve.

The idea matters because lower model prices can be misleading. A cheaper model may save money on the first attempt while increasing the number of retries or transfers. A larger model may cost extra per request while completing a difficult task with fewer steps. Leaders therefore need to compare operating results rather than price lists.

Dan explains how model routing can help. Simpler tasks may be directed to smaller models, while difficult work can be sent to models with greater capability. The choice depends on the task and the tradeoffs the business is willing to accept. Dan frames those tradeoffs through three dimensions: quality, speed, and cost. In many cases, a company can optimize two while accepting a compromise on the third.

That does not mean every basic task should automatically use the cheapest option. A slower response may be acceptable for internal analysis but frustrating during a live customer conversation. A small reduction in accuracy may carry little risk in one workflow and create expensive repeat contacts in another. The orchestration layer needs rules informed by the customer experience, the complexity of the request, and the cost of failure.

Customer service gives companies a useful environment for measuring those results because many of the existing measurements already connect work with outcomes. Cost to serve, time to resolution, deflection, accuracy, customer satisfaction, and repeat contact rates can all reveal whether AI is helping. Dan argues that agent performance should be evaluated alongside human performance using comparable standards.

Resolution is particularly important. If an AI system provides an answer and the customer returns an hour, a day, or a week later with the same issue, the task was not resolved. The first interaction may look successful in an activity report while creating extra work, frustration, and cost later. Measuring only initial response or deflection can therefore reward the wrong behavior.

The conversation also considers what automation means for the people working around customers. Front’s research, as discussed in the interview, found that 54 percent of surveyed leaders see issue resolution as support’s main purpose today, while 40 percent believe it should remain the main purpose. Dan interprets that difference as an opportunity to automate lower-level work while allowing employees to spend additional time building customer relationships.

The research also reports that 75 percent expect support, customer success, and account management to become increasingly unified. Dan believes this will affect team structures and the platforms companies choose. Customers do not think in internal departmental boundaries. They expect one company to remember their history and coordinate the response, whether the work passes between an agent, a support specialist, customer success, or account management.

Shared context and coordination therefore become part of the AI cost equation. A handoff without the customer’s history can force someone to repeat the problem, reducing satisfaction and extending resolution time. The technical cost of the interaction may appear low while the operational and customer costs continue to grow.

Dan recommends treating AI autonomy as a dial. Companies can begin with a person reviewing recommendations, maintain audit logs showing why the system acted, and increase autonomy as evidence builds. The same outcome measurements applied to employees should also apply to agents, including whether the customer received an accurate answer, achieved a lasting resolution, and had a good experience.

The larger message is that AI economics cannot be separated from service design. A model, router, agent, or platform earns its place by contributing to an outcome the business and customer value. Usage may help explain the bill, but it cannot prove the result.

Should companies continue celebrating rising AI usage, or start asking what each successful outcome cost and whether the customer would agree it was successful? Listen to the episode and share your thoughts.