2000 Episoden
- 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 a document and putting it to work. A search might turn up an earnings report. An investor relations team also needs to know what executives have said before, whether outside evidence supports the proposed message, and what analysts might ask next. Julia also describes an unnamed M&A team using AlphaSense's SuperAnalyst to identify gaps in its strategy and compare possible acquisition or partnership targets. The output gave the team a starting point for further research. The decision about which targets to pursue still belonged to the people responsible for the deal.
We talk about what happens when a confident answer contains an outdated figure or rests on an assumption that nobody checks. Julia says a mistake early in a multi-step research task can carry through to the final recommendation. A citation gives an analyst somewhere to start. They still need to open the source, check when it was published, see whether it supports the exact claim, and look for evidence that points in a different direction. Julia also raises a point for managers: when AI takes on the initial research, teams need to agree who checks the work and how analysts will continue developing their judgment.
I joked that technology had been promising me spare time since I was a boy, yet I still haven't made it to the cinema on a Wednesday afternoon. Julia's answer was to look beyond hours saved and ask whether the team identified a risk earlier or spotted an opportunity it might have missed. I'd love to hear how you measure this in your own work. Has AI helped your team make a better decision, and what evidence persuaded you? Please share your thoughts. - 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 identified a real problem, but the recipient can't act on it. The ticket goes back and forth while the system stays exposed. We talk about how Cogent brings together security and operational data to help agents determine who owns what, and why the quality of those records affects what you can ask an agent to do.
We also discuss what Vineet calls governed autonomy. He describes customers setting their own boundaries and starting in environments where the consequences of a mistake are easier to contain. A development system and a customer-facing production service may need different permissions. He makes the case for auditable actions and limits on what an agent can change. I ask where analysts still need to be involved, especially when a fix could interrupt the business or when someone has to weigh a security risk against the cost of downtime.
For anyone considering another security tool, Vineet suggests looking at measures such as time to remediate and how often teams fix issues within their agreed deadlines. We also discuss the trade-off between a broader platform and a specialist tool that may do one job better.
I'd love to hear what you're seeing in your own organization. Which handoff would you trust an agent to handle today, and where would you still want a person to make the call? Please share your thoughts. - 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.
Weitere Nachrichten Podcasts
Trending Nachrichten Podcasts
Über 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-WebsiteHöre Tech Talks Daily, RONZHEIMER. und viele andere Podcasts aus aller Welt mit der radio.at-App

Hol dir die kostenlose radio.at App
- Sender und Podcasts favorisieren
- Streamen via Wifi oder Bluetooth
- Unterstützt Carplay & Android Auto
- viele weitere App Funktionen
Tech Talks Daily: Zugehörige Podcasts































