2000 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. - 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 calendar sync with AI and GitHub Actions to do that one job. We also talk about the habits software can't do for you, such as telling people when the day goes off plan or finding a way to be mentally present when you walk out of the office. David makes a case for remote work as the default for knowledge workers while making room for time together in person.
Our conversation turns to what businesses can simplify before introducing an agent. David describes teams using several tools to move information from one place to another, even when a smaller connection between tools would do the job. He brings that idea to life with his own podcast. His system prepares the edit, clips, transcript, and show notes, then asks him to review the result before scheduling it. David estimates his hands-on work after recording fell to about 15 minutes for that workflow. It's his account of his own setup, and the review step is part of it.
I keep coming back to the places David chooses to leave automation out. His team has a Friday call with no AI note taker so people can talk without wondering where the conversation will end up. For me, that belongs in the same discussion as the calendar script and the podcast workflow. The tools are useful when you know what you want them to make room for. Please share your thoughts. Which part of your working day would you simplify with AI, and what would you protect from it? - 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 recorded their conversation so she could give him her attention. I liked the example because the benefit, as he experienced it, was a better conversation. We put it alongside a very different setting: a warehouse, where people may see a robot arrive and wonder how the work, the staffing, or their own role might change. Both examples make me want to ask who gets to say whether the technology has made the job better.
We also discuss the gap between a conference announcement about a new digital workforce and the details a manager needs to get right before deploying an agent. Who trains the people expected to use it? Who checks the work? What does the company do when an automated system makes a mistake? Jon connects those questions with his reporting on AI policy and the lessons he draws from the response to social media. For an employer, the immediate question is who takes responsibility for the system in practice.
Jon says he finished the book more optimistic than he was when he began. He's found AI useful for some of the tasks he least enjoyed as a reporter, and he encourages people to try it and ask their managers for training instead of being left to figure it out alone. I'd love to hear what you've seen in your own workplace. Where has AI given you time for work you care about, and what support would make it easier to use well? Please share your thoughts. - 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 on individual use cases. An inventory of product names can tell you what a business has purchased, but it may tell you very little about what those products are allowed to do. We discuss why an organization needs to connect its AI assets with approved activities, named owners, and continuing evidence of how they operate. The same platform can create very different risks depending on the information it handles and the decisions it supports.
We also look at vendor assurance. Adding AI questions to a supplier questionnaire is a reasonable start, but the answers need evidence behind them. Alex describes AI Score research involving approximately 250 organizations using AI. He says 92% were beyond pilots, while only 16% had an inventory. These are company-reported findings, and the conversation does not establish the survey methodology. They provide a starting point for a practical question rather than a universal measure of enterprise readiness. Can your supplier explain what AI it uses, for which activities, and how it knows when that picture changes?
AI agents add another challenge. Existing identity, permission, and network controls remain relevant, while autonomous behavior creates a need to notice changes after deployment. Alex discusses monitoring whether an agent starts accessing external information when its approved use was limited to internal sources. We talk about the people responsible for those systems and how operational accountability should connect with board oversight.
There is also a commercial argument for governance. Alex sees it as a way to pursue business objectives within an understood risk appetite. Controls still need to justify the work they create, and the interview does not provide a measured customer return or a product demonstration. The useful lesson for listeners is to ask whether governance is helping a business make better decisions as its AI usage changes.
We close with the company's growth following the $5.4 million seed round referenced in the supplied guest notes and our conversation. Alex describes the challenge of keeping pace with customer needs and a rapidly changing market. For listeners responsible for AI adoption, security, procurement, or board reporting, the episode offers a practical way to connect written rules with observable activity.
I'd like to hear your thoughts. What would help your organization keep its AI approvals, ownership, and day-to-day use aligned as the technology changes? - 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 reasonable goals, but they lead to different projects and different ways of measuring success. Tim describes how he used company filings to study patterns in what businesses say about AI over time. The filings can show how the story changes. They can't tell us on their own whether a quiet company abandoned a project or simply stopped talking about it.
I also asked Tim what a CFO should expect to see before approving an AI budget. His answer includes a baseline, a comparison with simpler options and the costs that appear once a pilot is running across the business, including model usage, maintenance and retraining. We discuss his idea of "latte time," a reminder that saving a few minutes for each employee leaves a separate question about what the business or its customers gain from the time saved.
The conversation turns to AI agents and what meaningful human control looks like. Tim argues that leaders should decide where an agent can act, which cases should be escalated and who has enough time and information to intervene. We finish with three decisions a team can make before its next funding meeting: define the problem, name the person responsible and decide what will happen after launch. I'd love to hear your experience. Which of those decisions has made the biggest difference to an AI project in your business?
More News podcasts
Trending News podcasts
About Tech Talks Daily
If every company is now a tech company and digital transformation is a journey rather than a destination, how do you keep up with the relentless pace of technological change?
Every day, Tech Talks Daily brings you insights from the brightest minds in tech, business, and innovation, breaking down complex ideas into clear, actionable takeaways.
Hosted by Neil C. Hughes, Tech Talks Daily explores how emerging technologies such as AI, cybersecurity, cloud computing, fintech, quantum computing, Web3, and more are shaping industries and solving real-world challenges in modern businesses.
Through candid conversations with industry leaders, CEOs, Fortune 500 executives, startup founders, and even the occasional celebrity, Tech Talks Daily uncovers the trends driving digital transformation and the strategies behind successful tech adoption. But this isn't just about buzzwords.
We go beyond the hype to demystify the biggest tech trends and determine their real-world impact. From cybersecurity and blockchain to AI sovereignty, robotics, and post-quantum cryptography, we explore the measurable difference these innovations can make.
Whether improving security, enhancing customer experiences, or driving business growth, we also investigate the ROI of cutting-edge tech projects, asking the tough questions about what works, what doesn't, and how businesses can maximize their investments.
Whether you're a business leader, IT professional, or simply curious about technology's role in our lives, you'll find engaging discussions that challenge perspectives, share diverse viewpoints, and spark new ideas.
New episodes are released daily, 365 days a year, breaking down complex ideas into clear, actionable takeaways around technology and the future of business.
Podcast websiteListen to Tech Talks Daily, Global News Podcast and many other podcasts from around the world with the radio.net app

Get the free radio.net app
- Stations and podcasts to bookmark
- Stream via Wi-Fi or Bluetooth
- Supports Carplay & Android Auto
- Many other app features
Tech Talks Daily: Podcasts in Family





























