Tech Talks Daily

What can private companies learn from government caseworkers about adopting automation and using data more effectively?
In this episode of Tech Talks Daily, I speak with David Turner, General Manager and Senior Vice President of Government Services at Equifax Workforce Solutions, about public sector automation, data modernization, and the people responsible for delivering social services.
The conversation begins with a surprising finding from an Equifax Government Services study of over 500 U.S. government employees. Every respondent expected efficiency to improve during the following year, while 95% believed automation would free time for higher value, human centered work.
David explains why government employees may be more receptive to modernization than many people assume. Caseworkers operate under rising demand, staffing pressures, changing policy, and limited budgets. When technology removes repetitive administration or supplies information faster, they can see an immediate connection between the tool and the person waiting for support.
We discuss how the meaning of automation has changed inside social services. A few years ago, it might have meant entering information into an online portal. Today, integrated connections can search data sources behind the scenes and return verified information during the caseworker's existing process.
David describes continuous evaluation, which can identify when circumstances within a caseload have changed. Instead of searching every case for a possible update, a worker can direct attention toward the people whose income, address, or employment data indicates that further review may be needed.
Income verification provides another example. Equifax says it can return income information in under one second, helping prevent the delays created when an applicant must leave the process to find a document. Those pauses matter when an eligibility decision already involves several stages and numerous external systems.
The gig economy makes this work harder. Applicants may receive income from employment, contract work, digital platforms, and several side projects. Agencies need access to a fuller income picture without sending people back toward paper forms and manual verification.
David also shares what Equifax has learned through its Day in the Life program. The team spends time with caseworkers to understand their processes, policy restrictions, and information constraints. He believes public sector leadership can remain closely connected to employees in the field because many agency executives previously performed those roles themselves.
AI introduces further possibilities. David discusses how data and AI could eventually identify signs that someone who has left an assistance program may be experiencing financial difficulty again. Community groups, food banks, or other services could potentially offer support before that person returns to crisis. Such a system would also require careful decisions around consent, privacy, accuracy, and responsibility.
The central lesson is refreshingly human. Technology creates value when it removes administrative pauses and gives experienced caseworkers additional time to understand someone's circumstances.
Could public sector automation teach private companies how to connect technology investment with human outcomes? Listen to the episode and share your thoughts with me.

What happens when an AI experiment becomes a production service that your employees, customers, and daily operations depend upon?
In this episode of Tech Talks Daily, I speak with Brian Klingbeil, Chief Strategy Officer at Ensono, about AI infrastructure resilience, operational dependency, FinOps, legacy modernization, and the growing pressure to prove that enterprise AI investments are producing meaningful returns.
Brian has been speaking with major enterprises through Ensono's Executive Advisory Council. Three years ago, many participants were experimenting with proofs of concept. Today, they are being asked to present AI projects that are already in production, approaching production, or demonstrating a clear return through productivity, lower risk, service quality, or financial results.
That progression creates a new problem. When an AI model begins supporting product delivery, customer service, logistics, software development, or internal operations, it becomes part of the company's operating infrastructure. Leaders must then ask familiar IT questions about availability, monitoring, security, incident response, disaster recovery, ownership, and cost.
Brian believes FinOps often provides the first warning. Token consumption can be difficult for CFOs and business leaders to interpret, particularly when hundreds of agents are operating across different models. Ensono's internal platform has produced around 1,000 agents, prompting questions about which are effective, which are expensive, and who should carry the cost.
We discuss why chargeback and showback could change employee behavior. When AI spending is absorbed by a central corporate budget, teams may have little reason to question whether an expensive model is suitable for a routine task. When the cost reaches their departmental budget, the decision can look very different.
Architecture also matters. Brian recommends systems that are loosely coupled and tightly integrated. Companies should be able to replace a model, provider, FinOps tool, or service as the market changes, while still connecting each component closely enough to deliver useful business outcomes.
That creates a genuine tradeoff. Providers such as Microsoft, Amazon, Google, OpenAI, and Anthropic can offer specialist capabilities that businesses may want to use. Avoiding every provider specific feature can limit what the technology delivers, while becoming too dependent on one provider can make future change expensive and disruptive.
The conversation then turns toward legacy technology. Brian argues that many systems described as outdated still process airline reservations, banking transactions, insurance claims, government services, and other high volume workloads. Turning them off without suitable replacements would create far bigger problems than the word "legacy" suggests.
AI can change the modernization decision. Ensono worked with Markerstudy Group to analyze six million lines of RPG code running on an IBM i platform. The resulting plan identified applications that should move elsewhere while preserving workloads that still benefited from the platform's reliability and transaction processing capabilities.
Brian treats migration as one possible part of modernization. AI tools can document old code, support modern development environments, and allow younger developers to work with established platforms without immediately beginning a lengthy and expensive replacement program.
We also discuss Ensono's use of AI operations. Brian says the company reduced mean time to repair by 50% while processing approximately 50,000 tickets each month. The example shows how AI value can be measured through service quality and operational performance rather than relying entirely on direct revenue.
The result is a balanced conversation about moving quickly while building enough control to keep AI dependable. Organizations need space for experimentation, but production services also require ownership, budgets, recovery planning, and people who know what to do when something fails.
If one AI model or provider disappeared tomorrow, how much of your business would stop working? Listen to the episode and share your thoughts with me.

What happens when an autonomous AI agent makes a financial decision using inaccurate, outdated, or poorly synchronized data?
In this episode of Tech Talks Daily, I speak with Marcin Kaźmierczak, cofounder of RedStone Oracles and Credora Ratings, about why verifiable data is becoming so important to financial AI agents. RedStone originally developed its oracle infrastructure to supply smart contracts with reliable information from hundreds of sources. The same principles are now being applied as AI agents begin analyzing markets, recommending allocations, processing payments, and executing trades.
Marcin explains what a blockchain oracle does and why smart contracts cannot independently access real world information. RedStone aggregates, cleans, and distributes financial data, including asset prices, liquidity, volatility, and market capitalization. According to Marcin, its network currently secures over $10 billion in total value locked and has operated for six years without a mispricing or downtime event.
The discussion then moves into agent driven finance. AI agents can process information and act at considerable speed, but that speed introduces problems when the underlying information is delayed or the model hallucinates. Marcin describes the synchronization challenge created when an oracle updates every five seconds while an agent makes decisions every second.
One example captures the risk. An AI trading agent reportedly generated $200,000 over three months before losing $250,000 in two transactions. Marcin explains how Credora Ratings can add financial risk context by rating assets and strategies from D to A. Companies can then instruct an agent to operate only within an approved risk range.
We also discuss tokenized assets, the growing interest from major financial institutions, and why blockchain networks offer an attractive operating environment for autonomous finance. Marcin shares practical advice for leaders, including speaking with experienced implementers, testing agents in closed environments, identifying likely failure scenarios, and creating response policies before introducing real money.
What evidence would you require before trusting an AI agent with a financial decision? Listen to the episode and share your answer with me.

What if a restaurant could identify a margin problem while the ingredients were still being unloaded, rather than discovering it several weeks later?
In this episode of Tech Talks Daily, I speak with David Cantu, CEO of Craftable, about AI restaurant back-office technology, margin intelligence, inventory management, purchasing, invoice automation, and the continuing importance of human hospitality.
David has spent decades working in restaurants and technology. He describes an industry dealing with staffing difficulties, rising leases, food inflation, lower traffic, and relentless margin pressure. David cites a National Restaurant Association study indicating that 40% of restaurateurs were not profitable during the previous year.
Craftable connects purchasing, recipe management, inventory, accounting, sales data, and analytics. The company says its platform is used by over 10,000 restaurants, hotels, and venues.
David argues that useful hospitality AI should automate the work that keeps managers, chefs, and operators away from guests. This includes producing sales forecasts, suggesting orders, planning preparation, identifying invoice anomalies, and comparing projected labor with actual requirements.
The conversation becomes particularly practical when David describes a restaurant receiving a ribeye that has increased in price by 20%. If the dish is a popular, high-margin menu item, that vendor increase can quickly reduce its profitability.
Craftable's Invoice AI can detect the change when the invoice is received. The operator can then consider running a higher-priced chef's special, promoting another steak, reviewing the menu price, or adjusting future orders. Waiting until month-end reconciliation would explain the lost margin but leave no opportunity to recover it during service.
We also discuss the difference between AI intelligence and operator knowledge. AI can examine large volumes of information, but an experienced restaurateur understands the atmosphere, the team, the guests, and what is happening at that particular moment.
David believes AI recommendations need to show their work. Managers should be able to inspect how a sales forecast, suggested order, staffing plan, or trend was calculated. Transparency helps people assess the recommendation without forcing them to search through another large analytics report.
Craftable is also testing how to measure whether a recommended action produced a result. If a manager coaches a server with unusually high complimentary items or promotes a menu category with falling attachment rates, the platform can examine whether that action affected sales or margins.
David is skeptical of hospitality AI added as a promotional layer without being built into the daily workflow. At industry conferences, he has seen vendors attach language models to existing products while offering little operational value.
His hope for restaurant AI is highly human. He wants technology reducing administrative pressure while employees welcome guests, serve meals, develop their teams, and create the warm experiences that define hospitality.
Which restaurant decision could protect profitability if the operator received the right information before the next service began? Listen to the episode and share your thoughts with me.

Why do so many enterprise AI initiatives begin with impressive demonstrations but struggle to produce measurable business value?
In this episode of Tech Talks Daily, I speak with Dom Selvon, CTO and value partner at Valliance, about enterprise AI ROI, outcome-based consulting, build versus buy decisions, proprietary data, ontologies, and governance.
Valliance is an AI-native consultancy that charges against client outcomes rather than hours worked. Dom explains why his "value partner" title is deliberate. The company begins by identifying the financial or operational result a client wants and connects its own compensation with achieving that result.
Dom argues that many AI initiatives begin without a clear definition of success. The pressure to adopt AI is real, but companies frequently select technology before agreeing on the business problem, desired outcome, or measurement.
He identifies three recurring mistakes. The first is framing the project around AI rather than the business need. The second is failing to establish a metric and baseline before work begins. The third is using a consulting model that rewards billable time without connecting payment to the client's result.
We also discuss how generative AI is changing traditional build versus buy decisions. Companies historically bought software because custom development was slow, expensive, and difficult to maintain. Coding agents can now reduce the time and cost required to create software for specific internal needs.
Dom does not believe SaaS will simply disappear. However, vendors selling convenience, workflow wrappers, or integration glue face new competition from customers who can create similar capabilities themselves. He argues that stronger SaaS positions will depend on assets a model cannot easily regenerate, including proprietary data, networks, regulatory standing, and deep workflow adoption.
This leads to a wider discussion about competitive advantage. When companies have access to similar models, generated code begins to converge. Dom believes lasting differentiation comes from company data, institutional knowledge, connected systems, employee experience, and the semantic context surrounding that information.
Dom explains why ontologies matter to enterprise AI. Raw data tells an agent what is stored in a particular field. An ontology describes the customers, orders, contracts, payments, relationships, and business rules represented by that data. This context allows people and agents to reason about information in a way that reflects how the company actually works.
Governance also needs to be designed from the beginning. Dom argues that security, permissions, accountability, and compliance allow successful pilots to expand without forcing the business to rebuild everything later.
How can leaders tell when AI is genuinely being adopted? Dom offers a surprisingly simple signal: people stop talking about AI. The technology becomes part of ordinary Monday morning work, and employees focus on completing the task rather than explaining the tool.
Has your company defined the business result, measurement, proprietary context, and governance required to turn AI enthusiasm into operational value? Listen to the episode and share your thoughts with me.