The Revenue Integrity Gap

In this episode, David sits down with John Holcombe from JH Leadership, https://jhleadership.com/ - a certified executive coach and author of Creating Value Faster: The Leadership Guide to Customer Insight-Driven Innovation who has spent decades watching what happens when leadership judgment fails to travel into rooms the leader is not in - to unpack what AI actually demands of the people who lead. Moving beyond the pressure of "just deploy AI," the conversation explores why AI is less a technology problem than a leadership one - exposing organizational fault lines, eroding trust, and forcing a reckoning with how deliberate leadership either extends the loop or exposes it.Key topics covered:AI as the fourth answer: Leaders have spent entire careers solving one question - how do you carry your judgment into rooms you are not in? Management layers, playbooks, and training were partial answers. AI is the fourth. It either extends the loop or exposes it. This episode frames why AI magnifies whatever is already broken beneath the surface of the organization.The blurred North Star: AI does not move the North Star. It blurs it. Leaders inundated with information and forced to accelerate decision-making without a well-designed organization underneath them find that AI only magnifies the cracks. The C-suite can walk away from a congenial meeting thinking everyone understood the same picture - and be wrong.The leadership arc of identity, altitude, and influence: John outlines the evolution from subject matter expert to conflicted doer-leader to architect and commercial operator. Each turn requires self-awareness, courage, commitment, and follow-through. Skipping the turns is what produces leaders who command instead of influence - and AI is exposing them faster than any prior technology cycle.The influence gap where AI does the most damage: When AI surfaces problems teams were not aware of, untrained leaders attack the team instead of the problem. Copilot gets rolled out to everyone, governance is absent, and the gap between authority and influence widens. Command-and-control leaders are flushed out immediately - AI accelerates the discontent that was already there.Delegating authorship to a machine: David shares a firsthand observation - functional leaders submitting AI-generated reports with polished visuals but uncorrelated data, telling the leader "you did a good job" without ever reading the output. The result: trust erodes from "trust and verify" to "trust and validate," and the leader becomes the inspector of work they should not have to inspect.The magnifying glass and the loop: In a moment of parallel emergence between host and guest, John names what he calls "the cycle loop" - the connective tissue between leadership judgment, organizational execution, feedback, and adjustment. AI can either harness the loop or break it. Without maintaining what John calls "organizational integrity, for lack of a better term," AI accelerates the fracture faster than the leader can see the breakdown.Job theory and the McDonald's milkshake: Borrowing from Clay Christensen, John reframes the AI question as a "job to be done" question. Before deploying AI, leaders must understand what the actual job is - for the customer, for the team, for the process. AI trained on meaningless data produces meaningless results. AI trained on real operational understanding becomes powerful.Anthropic as a business coach: John shares the anecdote of a young executive using Anthropic as a business coach - a specific pattern showing how AI is already stepping into roles humans thought were uniquely theirs, and what it means for what leaders should actually be doing.The dilution of authority: A leader's authority naturally dilutes over time as the organization watches their feet. When AI steps into that dilution without governance, breakage accelerates. David and John unpack where the breakage happens first - at the day-to-day task level, when tools are introduced without buy-in, guardrails, or clarity about how work changes.Technical debt and stovepipes: Siloed functions that do not understand how they impact each other create conflict at every organizational layer. John argues that servant leadership - humility, cross-functional dialogue, and understanding how my function impacts yours - is the antidote to the stovepipes that AI makes even more dangerous.The one decision for the next 90 days: When a leader feels the loop breaking, the answer is not strategy - it is one decision: go talk to your teams. Engage cross-functionally, find where things are breaking, empower people to bring concerns and solutions, and ask the null hypothesis question: what happens if we do this, and what happens if we do not? Set guardrails at the top, but make sure they extend all the way down to the individual.You get what you walk by: The episode closes with John's core message - the best leaders are not sitting at their desks. They are walking the floor, talking to customers, understanding workarounds, and building the relationships that make AI an amplifier of good design rather than an amplifier of brokenness. Or as John puts it plainly: when your hammer, everything looks like a nail - and with AI, most systems do not need the hammer, they need the loop.www.prime-timesystems.com

In this episode, David sits down with Nicole Miller from Nordis Technologies (www.nordistechnologies.com)-a product-minded operational leader who spent eight years rebuilding the technology substrate of a 30-year-old company before ever pointing AI at it, to unpack what disciplined AI transformation actually looks like inside a legacy enterprise. Moving beyond the pressure to "just put AI on it," the conversation explores why intentional data architecture — not model selection — is the real prerequisite for AI ROI.Key topics covered:**The substrate-first approach:** While most companies rush to deploy AI on top of fragmented systems, Nicole spent years simplifying architecture, rewriting the intent of the technology stack, and building a patented platform before AI was ever in the picture. Her logic: you can't point AI at data that doesn't tell a story.AI-enabled vs. AI-centric vs. AI-native: A framework for understanding where your organization actually sits. Nicole argues there's no getting to AI-native in a thirty-year-old company without first being AI-enabled — and most leaders skip that step entirely.Technical debt as a strategic decision: Rather than chasing legacy debt indefinitely, Nicole made the hard call to draw a line — telling her technical team "we're not looking back" — and centered the organization on a new foundation built around data that tells a story (Espresso Hub).Data lakes as landfills: Without intentionality, data warehouses become dumping grounds of duplicative, incongruent information. Nicole's cautionary tale of a CTO who built a data warehouse under pressure — only to have it dismantled — illustrates what happens when governance and intent are absent.The falsehood of AI: AI alone won't solve anything. Without documented processes, defined systems of truth, and clear data definitions, AI just costs money and frustration. The real discipline is patience — understanding the business and the right data before letting AI work for you.Measuring ROI in people power: Nicole translated AI impact into FTE terms the leadership team could understand — "when AI is working for us, we don't increase the employee population by one, but we feel the lift of twenty." Concrete examples include coding productivity (every two engineers now contribute like three and a half) and customer service response times cut from 80 minutes to 10 via their AI agent, Ask Coral.The multi-year journey: A phased operational strategy — One Team One Dream → Ready Set Grow → Be the Spark → Aligned Execution → Unleashed Potential → New Frontiers → Intelligence Into Action — showing how bringing 180 people along takes longer but ensures longevity.Bringing the whole team: The hardest part wasn't the technology — it was educating the entire leadership team on AI. Nicole stresses that you can go anywhere fast by yourself, but taking an organization with you requires patience, inclusion, and a shared vision.The one decision: Define your outcome. Without a clearly defined outcome, the investment becomes impossible to measure and the measurement against it becomes impossible to track.The episode closes with Nicole's core message: AI on its own is not enough. You have to think about AI for your business — where you are in the story, then think about where AI fits. Discipline, patience, and intentionality are what separate organizations that build lasting AI capability from those that end up in the pilot graveyard.

In this episode, David sits down with Ajay Chankramath, head of Platform Engineering Consulting (the advisory arm of platformengineering.org), to unpack the real operational risks of AI adoption inside enterprises. Moving beyond the hype-versus-reality divide, the conversation explores where AI governance actually belongs — not at the model layer, but embedded in the workflow.Key topics covered:The integrity gap: AI is being deployed on top of fragmented operating models, accelerating existing cracks rather than fixing them. Decision velocity is rising exponentially while trust infrastructure lags behind.Signal vs. noise: Executives are distracted by model benchmark races and AGI timelines (noise) while missing ungoverned AI already running inside their own developer workflows (signal).Real-world cautionary tales: From the OpenAI sandbox escape incident to a founder who vibe-coded an entire SaaS product only to suffer security breaches within three weeks — illustrating what happens when governance is absent.Shadow AI as a demand signal: Rather than a discipline problem, shadow AI reveals that sanctioned paths aren't meeting developer needs. The "paved paths" approach (80/20 rule) offers a framework for balancing standardization with flexibility.Five governance mechanisms: Identity for every agent, scoped permissions (least privilege), budgets/cost caps, verification before work counts as done, and full observability/logging.AI that watches vs. AI that works: Advisory AI (dashboards, summaries, copilots) requires lighter governance, while autonomous AI acting on systems of record demands a significantly higher governance bar.Model types and governance differences: Closed models (OpenAI, Anthropic), open weights, and open source each carry distinct governance implications around data sovereignty, audit trails, and supply chain risk.The 90-day action plan for CIOs: A concrete month-by-month roadmap — inventory AI usage (days 1–30), apply least-privilege scoping (days 31–60), and implement budgets, logging, and weekly agent activity reports (days 61–90).The one decision: No agent should run anonymous. Give every AI agent an identity, the way every employee and service already has one.The episode closes with Ajay's core message: trust scales when verification is structural — and making verification the condition for "done" on any delegated work is the single highest-leverage operational change a leader can make.

Every revenue leader is trying to figure out what AI actually means for how they run the business. Lance has an answer — but it's not the one most people expect.In this episode of The Integrity Gap, David Figueroa sits down with Lance Hodgson, a Chief Revenue Officer who's spent the last several years watching companies deploy AI into revenue organizations that weren't ready for it. His argument is direct: AI doesn't create leverage on its own. It amplifies what's already documented, architected, and governed. Companies with a real operating system underneath the AI are pulling away. Everyone else is getting more chaos, faster.The conversation reshapes what a modern CRO seat actually looks like — less closer and coach, more systems architect. The person who's designing how people, tools, and agents work together, not just hitting a quota. It's a prescriptive episode for revenue leaders wrestling with what to do about AI while their operating model is still catching up.What You'll HearLance walks through three pillars that reshape how the modern CRO role actually works — and why the operating system underneath the revenue organization now determines whether AI creates leverage or exposure.Pillar 1 — Lift the Floor, Not Just the CeilingMost revenue organizations obsess over their top performers. Lance argues the real leverage is somewhere else entirely. The competitive advantage in a modern revenue org isn't found in the top 10% — it's found in engineering the process so mid-performers can access what top performers do intuitively. That's what a real operating system does. It codifies instinct into something everyone can execute.Pillar 2 — Document Before You AutomateEvery conversation about AI in revenue starts with the tools. Lance flips it. Without an operating system underneath, there's nothing to feed the agents. No playbook, no framework, no governance layer. And AI without any of that doesn't create leverage — it accelerates the mess. This is the pillar that reframes how CROs should be thinking about their AI investments right now.Pillar 3 — The CRO Is Becoming a Systems ArchitectThe old CRO seat was about closing deals and coaching the team. Lance describes a role that's shifted underneath most people's feet — the modern CRO thinks in layers now. People, tools, agents, playbooks, feedback loops, all designed to work together. It's less a sales leadership role and more an operating design role. And the CROs who make that shift are the ones running the businesses that are pulling ahead.

Welcome back to the Revenue Integrity Gap. I'm David Figueroa. Today's episode should resonate with many founders, CEOs, or leaders who are currently experiencing challenge around scale. And in today's day and age, there are many businesses that are encouraged to grow because technology and the new era of AI have influenced so much that we can do. And so today I'm joined by Geoff Toffetti, and he's come here today with a lot of great insights, and I believe that there's substance about what we're about to converse about today, to give executives conversations around what Some people talk about it. A lot of leaders talk about growth and scale, but Geoff has actually lived through it. Scaling multiple businesses through many stages through their cycle, and looking at operating models and seeing the shift in operating models and how sometimes scale has the weight where the operating model breaks.

What happens when the board asks, "What's our AI strategy?"In this episode, David Figueroa explores one of the most common challenges facing executive teams today. As pressure to adopt AI continues to grow, many organizations find themselves launching pilots, testing tools, and chasing activity without a clear operating model behind it.David breaks down why AI adoption and AI strategy are not the same thing, how board-level conversations often create urgency before a diagnosis exists, and why governance matters more than simply adding more technology.In this episode:• The difference between an AI mandate and an AI strategy• Why pilots don't always lead to progress• The risks of adopting AI without governance• How leaders can shift the conversation from tools to outcomes• Building an operating model that scales with AIThis episode concludes the Prelude Series of The Revenue Integrity Gap and lays the foundation for Season One, where David sits down with executive leaders to explore the intersection of revenue, leadership, governance, and AI.If this conversation sparked a new question, share it with someone searching for better answers. Subscribe so you never miss what's next.

Most companies are great at tracking activity.They know how many calls were made, how many emails were sent, and how many deals closed. But there's one thing sitting between activity and results that often gets overlooked: behavior.In this episode, David Figueroa explores how technology is changing the way organizations understand human behavior. AI is no longer just helping teams work faster. It's starting to influence decisions, recommend actions, and shape how people work every day.The challenge is that most organizations still focus on activities and outcomes while missing the behaviors that actually drive performance.David breaks down the difference between activity, outcomes, and behavior, why behavior has historically been difficult to measure, and how AI is creating new opportunities—and new risks, for revenue leaders.In this episode:• Why activity, outcomes, and behavior are not the same thing• How AI is influencing decisions behind the scenes• The hidden impact of AI-generated habits• Why behavior may be a stronger predictor than traditional metrics• The difference between correlation and causality• How behavior-based insights can improve forecasting and coaching• A simple question leaders should ask their teams this weekThis is the second prelude episode of The Revenue Integrity Gap, a series exploring the intersection of revenue leadership, governance, behavioral intelligence, and AI.If this conversation sparked a new question, share it with someone searching for better answers. Subscribe so you never miss what's next.

A year ago, every boardroom conversation centered on AI adoption. Today, the conversation has shifted. AI has already been deployed across sales, marketing, finance, and operations, yet many organizations struggle to answer a simple question: what has actually changed?In this opening prelude episode of The Revenue Integrity Gap, David Figueroa explores a growing challenge facing modern businesses: AI sprawl. What begins as individual teams adopting AI tools to improve productivity can quickly evolve into fragmented systems, disconnected decision-making, and a loss of organizational visibility.Drawing from his work with CEOs, CROs, CFOs, and executive teams inside fast-growing companies, David explains why AI sprawl is not merely a technology problem. It is a governance problem. As different departments adopt different AI tools, organizations risk creating multiple versions of truth, weakening forecast integrity, fragmenting institutional knowledge, and eroding trust between teams.This episode examines why AI sprawl is accelerating faster than traditional software sprawl, how hidden AI adoption impacts business operations, and what leaders can do to regain control before fragmented AI systems begin shaping critical business decisions without oversight.In this episode, David discusses:• What AI sprawl actually looks like inside growing organizations• Why AI sprawl is different from traditional tool sprawl• How fragmented AI systems create multiple versions of truth• The impact of AI on forecast integrity and executive decision-making• Why institutional knowledge is becoming increasingly vulnerable• How AI-driven reporting can unintentionally erode trust across departments• The governance challenges most organizations are overlooking• A practical exercise leaders can use to identify AI sprawl across their businessThis episode is the first installment in a three-part prelude series leading into the inaugural season of The Revenue Integrity Gap, where revenue leadership, governance, and AI intersect.If this conversation sparked a new question, share it with someone searching for better answers. Subscribe so you never miss what's next.