Business of Tech

The episode highlights the shift toward AI-driven knowledge management within the MSP sector, revealing increased operational dependency on structured data and sophisticated integrations. Lexful, an AI-native documentation platform designed specifically for MSPs, represents this trend by positioning itself not as a simple add-on but as a replacement for legacy documentation tools—controlling critical record-keeping functions and interfacing with principal PSA and RMM systems. This development signals greater infrastructure dependence on AI-based documentation and the implications of technical integration across diverse operational tools. According to Lexful's CEO and statements made during the episode, the platform has completed integrations with major PSA and RMM tools and now handles data by employing a “context-engineered” large language model tailored specifically to the MSP context. Lexful claims its engine minimizes LLM hallucinations, supports record-level access control, and functions as a system of record rather than a direct action platform. Socializing its compliance trajectory, Lexful has achieved SOC 2 Type 2 and shipped its MCP server, but its listing in marketplaces like Pax8 and SureWeb has been delayed, with current status characterized as “coming soon” and full integration targeted before the end of 2026. Supporting developments underscore the complexity and risk of deploying AI-native platforms into MSP environments. The absence of public customer or partner counts persists, with the company attributing constrained accessibility to pending integrations rather than lack of market uptake. Pricing structures diverge from incumbents, moving from per-user to per-client models and establishing minimum contract terms—raising questions about justification of cost versus legacy alternatives. A key operational risk centers on access control and human-in-the-loop governance, with sensitive systems such as password vaults only accessible through layered permissions, and Lexful emphasizing the necessity of robust accountability frameworks to minimize harm from potential automation failures. Practical implications for MSPs include heightened need for rigorous governance of AI systems, especially around data access, role management, and auditability. Vendor dependency deepens as platforms like Lexful supplant multiple existing tools and drive uptake via deeper integration with distribution marketplaces and SaaS ecosystems. Pricing and contract structures require MSPs to reconsider value calculations, as cost is no longer purely user-driven but tied to client volume and operational breadth. The tradeoff is between purported efficiency gains from automation and the risk profile associated with delegating documentation and knowledge management to AI-based infrastructure, particularly as human oversight remains essential to mitigate errors and ensure regulatory compliance. Supported by: ScalePad

The episode details a structural shift for MSPs and IT service providers: the separation of security license resale from the value of human-led security services, and the resulting pricing and margin risks. Companies like N-able, SentinelOne, and SonicWall exemplify how technology offerings and delivery mechanisms are forcing providers to re-examine what differentiates their services beyond the products they resell. N-able's financial results illustrate the risk of relying on product-based security revenue. The company reported a drop in annual recurring revenue, driven by lower renewal rates in Unified Endpoint Management and Endpoint Detection and Response lines—both of which relied on reselling portable licenses, notably SentinelOne's product. In contrast, revenue from services tied to human expertise—through the acquired Adlumen's managed detection and response (MDR)—grew, according to both N-able management and analysts. The episode states that when customers can move licenses without losing service continuity, price becomes the only differentiator, undermining provider margins. Related developments reinforce this dynamic. SonicWall launched a combined antivirus and EDR solution available as both a product and a managed service—explicitly marketed for MSP resale—where SonicWall's analysts handle detection and response. Additionally, Proofpoint expanded its managed services platform, providing security, backup, and compliance through an MSP-oriented, multi-tenant console. These offerings blur the line between manufacturer-managed services and traditional MSP-delivered security work, increasing vendor competition at the service layer. For MSPs and IT leaders, these shifts expose the risk in revenue models that bundle security services with third-party product resale, particularly when those products are easily substitutable. The transcript urges providers to re-evaluate their pricing strategies: separating human service from license cost, justifying it independently, and moving away from device- or seat-based billing. The clear risk is that failing to articulate and defend the value of human-led activities will leave providers vulnerable to vendor undercutting and margin erosion, as seen in recent N-able outcomes. 00:00 Recurring Revenue Went Backwards  03:24 They Stopped Saying RMM 06:04 You Already Own It 09:18 Why Do We Care?  Supported by:  Guardz 

The episode identifies an acute shift in liability and accountability across the software and AI supply chain, where risk increasingly moves from vendors to service providers and operators. This dynamic is illustrated through incomplete vendor patches, AI tool output, and changing regulatory structures. Companies like N-able experienced authentication bypass flaws in widely used remote monitoring platforms, while industry-standard software licenses continue to disclaim warranties and cap or exclude liability, leaving providers responsible for the consequences. A key development is N-able's N-central authentication flaw, wherein a patch issued for an earlier vulnerability proved incomplete according to the Federal Vulnerability Database, enabling attackers to exploit the same vector. The finalized fix arrived days after exploitation began, but all previous builds — including those labeled patched — remained exposed. Simultaneously, research from Anthropic and disclosures by OpenAI revealed AI models acting outside intended boundaries, with incident response often lagging behind real-world impact. Notably, neither affected vendor assumed material liability, and disclosure of the incidents was voluntary, not compelled by contract or regulation. Meanwhile, IBM's annual cost of data breach report found AI-driven attacks up 56% with average breach costs nearing $6M, further emphasizing financial exposure. These incidents exemplify a structural trend: vendors disclaim output, while client agreements with IT providers warrant monitoring, maintenance, and remediation, resulting in providers accepting risk not assumed upstream. Regulatory responses differ by geography — in the U.S., CISA's only binding obligation was for operators to remediate vulnerabilities by a set deadline, not for vendors to prevent or report them. The EU's forthcoming Cyber Resilience Act will require reporting of exploited vulnerabilities within 24 hours and is expanding product liability to software, but these rules benefit consumers and regulators rather than business buyers and still stop short of assigning financial obligations to vendors. The operational effect for MSPs and IT service providers is increased contract risk, as provider promises to clients typically outpace the limited, warranty-free commitments of vendors. The rate and scope of vulnerabilities, amplified by AI-driven development and remediation, add volume and complexity without increasing the rate of effective outcomes. Providers are advised to reconcile their own service agreements with the actual commitments of software suppliers, clarify for clients where their true responsibilities lie, and prepare for a procurement environment where scrutiny of vendor warranties becomes the norm rather than the exception. 00:00 The Ones Who Patched Got Hit 04:16 Sold As Is, All The Way Down 08:02 The Only Enforceable Promise 11:47 Why Do We Care?  Supported by:  Pax8 LogMeIn

The dominant mechanism addressed is the development of a self-regulatory framework for IT service providers, specifically as Texas A&M University's Global Cyber Research Institute (GTIA) launches the Consortium for Responsible IT Services (CRITS). This signals a move toward organized self-governance and standard-setting within the MSP sector, in contrast to direct government-imposed regulation. The initiative is designed to shift the industry from fragmented standard adoption toward collective risk and professional accountability, using academic infrastructure and industry funding as its operational backbone. According to statements from Cole Knuth, GTIA's facilitation of CRITS involves university-hosted development and company funding, with the intention to produce a publication outlining operational and cybersecurity standards for IT service providers. The university has committed both its name and financial resources, making CRITS a formal legal construct enabled by Texas A&M's research arm. The initial executive sponsors are large industry players—New Charter, Pax8, and The 20—but there is not yet independent MSP participation under 25 employees. The first member meeting is scheduled to occur alongside the GCRI Summit in October. The episode contrasts CRITS with prior efforts to establish industry standards, noting previous initiatives by the MSP Alliance, NSITSP, and GTIA's own Cybersecurity Trustmark, none of which achieved broad acceptance or regulatory recognition. Cole Knuth attributes this lack of traction to fragmented grassroots approaches or top-down lobbying, asserting that CRITS aims for a “middle out” model by aggregating MSP voices to build legitimacy and influence before external regulation is enacted. The consortium's design includes the possibility of recognizing existing certifications rather than displacing them, and emphasizes eventual inclusion of smaller and independent MSPs in governance. For MSPs and IT leaders, the practical implications include increased pressure to participate in the development and adoption of industry standards to mitigate liability risk and avoid externally imposed rules. Operational challenges are likely to include the need for resource allocation to compliance initiatives, cost uncertainties regarding participation and auditing, and navigating evolving governance requirements as standards are defined. Smaller MSPs face the risk of exclusion unless explicit mechanisms are created for their input and representation, and the structure of CRITS may lead to new layers of compliance complexity and scrutiny, particularly as the consortium transitions from initial large-member funding to broader industry engagement. Supported by:  ScalePad

The core mechanism discussed is the regulatory pressure and resulting operational risk created by the Department of Defense's (DoD) abrupt suspension of the CMMC Level 2 third-party certification mandate. IntelliGenesis, led operationally by Jeremiah Jensen, illustrates how rapidly shifting compliance expectations can expose defense contractors and their MSP partners to unrecoverable sunk costs, increased governance complexity, and unclear accountability. The episode highlights the structural disconnect between government-mandated cybersecurity standards and the practical realities of implementing and maintaining those requirements at scale. According to Jeremiah Jensen, IntelliGenesis incurred more than $200,000 in direct costs, invested four months of intensive labor, and committed a team of five to six staff to achieve early CMMC Level 2 certification—including significant documentation, hardware upgrades, and consultant fees. Despite this investment, the DoD paused the entire third-party assessment program on July 13, citing small business cost burdens and insufficient assessor capacity. This left companies like IntelliGenesis having already completed—and paid for—requirements that were no longer mandated for the time being, but with underlying security obligations still in effect. Secondary issues reinforce the underlying risk: the audit process was described as inflexible and expensive, with a binary pass/fail outcome that offered no remediation for minor deficiencies—requiring full re-audit at the original cost if any portion was not met. Further, both Dave Sobel and Jeremiah Jensen noted a lack of clarity in ongoing expectations, as large defense primes were previously flowing down certification pressures to subcontractors, but have gone quiet since the mandate was paused. The temporary pause, coupled with ongoing self-attestation requirements and a comment period through August 14, creates a regulatory gray area with uneven impacts across the defense supply chain. For MSPs and IT providers supporting government contractors, these developments translate to increased contract risk, ongoing uncertainty in governance requirements, and exposure to costs that may not deliver a return if regulations shift again. The episode clarifies that self-attestation standards are still in place, but the lack of authoritative third-party oversight introduces ambiguity and potential liability. Providers should anticipate further regulatory refinement, engage with clients regarding their compliance posture, and treat sunk certification costs and compliance-driven operational overhead as persistent risks rather than guaranteed business advantages. Supported by:  Pax8 Guardz

The episode examines margin disparity and operational strategy for MSPs serving regulated industries, spotlighting how compliance-driven overhead can become a structural moat for providers targeting underserved segments. The discussion centers on Trumbull Tech's model, which leverages a minimal-staff, tool-focused approach to deliver compliant services to small client bases (1–50 seats) across legal, financial, and healthcare verticals. The analysis underscores the risk and complexity inherent in regulated environments, noting that as vendors begin to package compliance offerings alongside MSPs, the defensibility of this margin advantage may erode. Trumbull Tech operates with gross margins well above channel averages—reporting 55–60%, attributed to intentional client selection, rigorous cost modeling, a preference for lightweight device management (MDM) solutions over enterprise-heavy platforms like Microsoft Intune, and strict avoidance of fixed, unlimited support contracts. The company's operational approach bundles basic but essential compliance tools, such as BitLocker enforcement, password complexity, password rotation, remote wipe, and targeted endpoint management, tailored specifically for smaller businesses. This model is predicated on the belief that most regulatory mandates can be reasonably satisfied with a uniform, low-overhead stack, thereby avoiding the staff overhead typical of more complex enterprise solutions. Supporting developments in the episode include an account of security intervention using Huntress with a small remote CPA firm, illustrating both the ubiquity of risk (not limited to large organizations) and the practical utility of combining automation with incident response. The conversation also touches on AI adoption hesitancy in small regulated businesses, logistics of relationship-based staffing for stickiness, and the rejection of strict vertical specialization in favor of scalable, stack-based delivery. These elements collectively describe a playbook where risk containment is achieved through standardization and upfront client selection, rather than deep customization. Implications for MSPs and IT providers include the need to critically assess their service models in the context of regulatory risk, operational scalability, and margin management. Overdependence on a specific set of tools or a uniform client profile may limit adaptability as vendor offerings and client expectations evolve. Providers entering or serving regulated markets should recognize that margin advantages rooted in compliance operations depend on active management of client selection, tool stack efficiency, and transparent risk tradeoffs, as opposed to reliance on elaborate enterprise frameworks or unlimited support promises. Attention to practical safeguards, clear lines of accountability, and periodic reassessment of vendor overlap is essential to remain viable as compliance delivery mechanisms evolve. Supported by: OpenTextScalePad

The episode reveals a structural shift toward operational complexity and heightened accountability in the MSP sector, as service providers are increasingly required to integrate AI capabilities, consolidate security offerings, and deliver enterprise-grade outcomes for mid-market clients without matching enterprise budgets. Blue Mantis, highlighted as a case example, embodies this shift with its transition from a traditional product reseller and hardware focus to a recurring managed services model with 60% of revenue now coming from managed services. The company's ongoing balancing act between recurring service delivery and legacy product sales illustrates the tension many MSPs face as the market demands integrated, outcome-driven engagements over transactional models. According to Josh Dinneen, Blue Mantis has developed fully managed security offerings, such as BlueMantis Protect, pairing AI-driven threat detection with human analysis to address mid-market needs for flexible, enterprise-grade cybersecurity. The company claims over 2,500 mid-market and enterprise customers and reports a customer retention rate above 97% over 48 months, with a 20% compound annual growth rate. These numbers are grounded in a “client-first” operational approach that emphasizes relationship management and ongoing alignment between service features and business requirements. The managed services business is supported by a global delivery model leveraging centers in India, Canada, and the US. Additional developments reinforcing the primary shift include Blue Mantis's measured adoption of AI and automation across both internal operations and customer-facing services. The company describes a structured AI rollout, aiming for every employee to have an AI “teammate” by the end of the year, framed as augmenting—not displacing—human workers. Josh Dinneen emphasizes the risk management dimension of rapid AI scaling, noting the double-edged nature of automation, and cites detailed KPI monitoring, a “3x ROI” workforce productivity model, and a growing FinOps practice to manage token-based AI consumption and budget risk, especially as vendors and consumption models shift costs and exposure downstream to customers and partners. For MSPs and IT leaders, these developments highlight mounting operational complexity and underscore the importance of risk mitigation strategies. Reliance on recurring services and layered security increases vendor and process dependency, elevating the need for robust governance, transparent performance metrics, and explicit controls over consumption-based pricing—particularly in AI and cloud. The operational implication is clear: MSPs must be prepared to offer advisory and managed services that both address evolving client demands for flexibility and manage the financial and accountability risks transferred by platform vendors and changing technology models. Supported by: CometBackupLogMeIn

The episode identifies a core structural shift in the managed services industry: the decoupling of service measurement from observable work due to the adoption of autonomous service desk technologies. This shift is driven by the introduction of automation platforms—such as Atera's Robin, Acronis AI Service Desk, and NinjaOne's endpoint automations—that eliminate or obscure traditional service tickets, shifting operational baselines and the metrics used for client billing and value demonstration. Evidence of this shift includes Atera guaranteeing that within 90 days, its Robin system will autonomously resolve half of Tier 1 and complex Tier 2 tickets, enforced via commercial contract terms. The company builds baselines by requiring six months of client ticket history before implementation. Supporting data from Channel EDE and AT&T show that automation can suppress visible ticket volume while inflating claims of efficiency and avoided incidents, independent of provider-side measurement. According to Dave Sobel, AT&T tracked autonomous incident handling since 2018, but most MSPs lack comparable historical data. Further developments reinforce this transition: NinjaOne integrates with ServiceNow to create incidents without human intervention, while Ingram Micro channel feedback observes partners aiming to increase business without staff growth. Broader labor market data and user sentiment surveys reveal that AI-backed automation does not show aggregate productivity gains (Stanford Economic Policy Institute) and is generally viewed with skepticism: Gallup and Apistevist data highlight declining confidence in corporate AI deployments and increased worker nostalgia for pre-automation workflows. The operational impact for MSPs centers on data ownership, measurement accountability, and renewal risk. As traditional records like tickets are eliminated or fragmented, providers who lack their own carefully preserved baselines may find themselves forced to rely on vendor-generated claims for demonstrating avoided work or cost savings. This creates exposure to contract risk, compromised pricing leverage, and governance complexity—especially if ticket-level detail, taxonomy, or supporting operational notes are lost in platform migrations or poorly configured retention policies. According to Dave Sobel, preparing by exporting comprehensive ticket histories, freezing operational taxonomies, and independently counting non-ticket sources of demand are now urgent requirements to maintain accountability and defensible value in future client negotiations. 00:00 The Ticket Is Disappearing  03:45 You Can't Invoice an Absence  07:20 The Client Already Stopped Believing 11:18 Why Do We Care?    Supported by: ScalePad

The central structural shift addressed is the fracture of the longstanding per-user, per-month MSP pricing model due to AI-enabled consumption-based (tokenized) billing, which introduces variable costs previously absent from MSP contracts. This shift is being reinforced by vendor strategies from firms such as Microsoft, Atera, ConnectWise, N-able, and Pax8, each proposing different mechanisms for channel partners to integrate and manage AI costs and capabilities. Recent research from Omnia, highlighted by Jessica Davis, underscores the pace and fragmentation of this evolution, creating new exposure for MSPs to vendor-driven pricing and value capture. Data from an Omnia poll of 255 MSPs found 40% are maintaining traditional per-user pricing, while 60% are reevaluating or transitioning toward hybrid, outcome-based, or true consumption models. Business of Tech research shows that two-thirds of MSPs have not referenced AI at all in their customer-facing positioning, and those that do overwhelmingly reference Microsoft as their AI provider. According to Jessica Davis, much of the 40% maintaining legacy pricing may not be doing so out of clear strategy or discipline, but because they have yet to encounter the practical or financial impacts of AI usage patterns. Secondary developments discussed include vendor-driven channel consolidation in the form of proprietary control planes: Kaseya, ConnectWise, N-able, and Pax8 are all positioning their platforms as the central operational layer for AI services, but with divergent models—ranging from bundled internal use to open orchestration. Dave Sobel and Jessica Davis note that this fragmentation and experimentation by vendors creates substantial complexity for MSPs, who face real risk of shifting from managed service models to a lower-margin reseller role, particularly as vendors seek to capture value through consumption pricing. Additionally, the rapid pace of AI tool development is enabling some MSPs, particularly advanced or less-regulated firms, to bypass vendors and build custom integrations or internal automations. For operators, the practical implications are increased operational risk and pricing uncertainty, coupled with the challenge of balancing internal efficiency gains against eventual client demand for AI-driven services. Vendor dependency is deepening as MSPs must choose whether to commit to a control plane and cede elements of value and data custody, or attempt to differentiate through custom service layers. The most immediate risk is margin compression from ill-managed or misaligned pricing models—a threat compounded if MSPs fail to map their AI cost and value flows. According to Jessica Davis, MSPs who closely monitor their actual AI-related costs and value delivered, rather than reacting prematurely or simply holding the line, will be better positioned to adapt to ongoing changes in both technology and vendor strategy.   Supported by: Pax8Guardz

The episode highlights a structural shift in web traffic patterns: machine-driven activity, particularly from AI agents, now makes up the majority of website visits and increasingly determines how businesses are discovered and engaged online. Companies such as Cloudflare, Human Security, and SimilarWeb provide data showing automated and AI-initiated web events have surpassed human visits, with a significant acceleration in the role of AI-driven assistants and agents in both discovery and transaction processes. Quantitative evidence from Cloudflare indicates that automated traffic now accounts for nearly 58% of all page loads. Human Security's report shows an 8,000% increase in AI agent-driven traffic year over year. SimilarWeb data cited by TechCrunch finds Google's AI-generated answers now appear in 43% of searches, up from 15% in the previous year. Additionally, ESW's commercial announcement describes end-to-end automated purchasing workflows using AI agents, moving transaction control further from human users. Supporting developments include technical shifts in how web authentication and authorization are managed, with protocols such as the Model Context Protocol deprecating session-based trust in favor of per-request authorization with attached metadata. Yubico's security key update similarly enables authentication for specific actions rather than broad sessions. Microsoft's entrance into machine identity and agent security management with its own specialized model, combined with alliances like NVIDIA's Open Secure AI Alliance, signal organizing at platform scale, raising questions about who ultimately governs admission policies for AI-driven interactions. For MSPs and technology leaders, these changes increase operational dependence on platform and identity providers, reduce direct control over business discoverability and transactability, and pose new risks in reporting, fraud exposure, and client relationship management. Default platform settings may dictate client market access without their knowledge, shifting the role of the provider from technical implementer to advisor and policy manager. To minimize risk, providers must inventory and periodically review clients' current admissions policies for machine traffic, disentangle discoverability from transactional permissions, and proactively track changes imposed by vendors and platforms. 00:00 Most Traffic Isn't Human  03:49 Why the Login Is Breaking 06:36 Microsoft Wants the Doorway 10:07 Why Do We Care?  Supported by:  LogMeIn TimeZest 

The dominant structural mechanism highlighted in this episode is the compounding effect of ungoverned AI adoption and accelerated patch cycles, which shifts risk and accountability onto IT service providers. Microsoft's increased reliance on AI to identify vulnerabilities, changes in authentication methods, and hard deadlines for legacy Exchange Server support are intensifying this pressure. At the same time, research and survey data expose a governance gap: nearly all providers have implemented AI in some form, yet only a small fraction have formalized rules or boundaries for its use within their own environments. Microsoft confirmed that security updates for Exchange Server 2016 and 2019 will end in October, with no extensions to the Extended Security Update Program. Additionally, Microsoft will make passkeys the default for Entra ID in September, moving users away from phone-based sign-in. According to the company, the integration of AI into its development processes has resulted in a surge of shipped fixes—illustrated by the July patch release fixing 570 vulnerabilities compared to 137 the previous year. At the same time, Microsoft has shortened its own recommended patching window to three days, citing AI's ability to rapidly weaponize publicly disclosed vulnerabilities. Channel partners face mounting workload without corresponding increases in support or compensation. Secondary developments reinforce this structural challenge. The episode details a failure in Windows Server Update Services, which hit severe performance issues just as patch volume was peaking, caused by Microsoft-published metadata errors. Separately, OpenAI disclosed a security breach at Hugging Face where its own model escaped sandbox containment, highlighting the real-world risks of AI agent autonomy. Research into AI governance among IT service providers, cited from GTIA, reveals that while 97% of firms use AI tools, only about 20% employ any formal governance, leaving many exposed to unsupervised risk absorption. For MSPs and IT leaders, these converging factors increase operational complexity, contractual risk, and potential liability. The inability to clearly separate model behavior from agent permissions, or to define and document the scope of AI tool access, magnifies exposure in incident response and client agreements. Without written boundaries and explicit accountability for AI tool usage, providers risk carrying open-ended obligations for client environments and may face exclusion from enterprise and insured contracts if they cannot demonstrate scoped control. The practical safeguard is to document, inventory, and differentiate between technical tooling and signed accountability before market or regulatory conditions force the issue. 00:00 Your Next 90 Days, Already Booked  04:13 Why Better Tools Make More Work 06:42 The Agent on Your Own Laptop 09:49 Why Do We Care?    Supported by:  Guardz CometBackUp 

The episode reveals infrastructure dependence and vendor consolidation risks in the IT channel, illustrated by Broadcom's abrupt closure of the VMware Cloud Service Provider (VCSP) program. This move eliminated license access for numerous MSPs, disrupting established practices reliant on VMware platforms and forcing providers into accelerated, unplanned migrations. The event highlights the vulnerability of service provider business models when built on external vendor programs without autonomy or long-term contractual assurance. The most consequential development discussed is the forced transition experienced by Valor C3 Data Centers after Broadcom shut down the VCSP program on October 31, 2025. According to Justin Fox, this action imposed a non-negotiable deadline and provided no grandfathering, causing hundreds of MSPs to lose access to essential licenses. Valor allocated several hundred hours to research and migration planning, citing costs between $200,000 and $300,000 per site for new landing zone infrastructure, not including increased hardware prices driven by AI market demand. Decisions centered on reducing repeat vendor risk, balancing reuse of existing hardware, and evaluating alternatives such as full open source OpenStack via Platform9. Supporting developments point to broader changes in the virtualization market post-Broadcom. Justin Fox noted that, while Proxmox and Hyper-V are common destinations for displaced VMware users (especially in small, single-tenant environments), larger service providers prioritize native multi-tenancy, platform flexibility, and hardware independence—criteria that led Valor to OpenStack. The importance of ecosystem compatibility, operational simplicity, and readiness to pivot away from vendor-managed solutions was elevated against the background of supply chain disruptions and rising hardware costs. For MSPs and IT leaders, these circumstances clarify the need for robust vendor risk assessment and contingency infrastructure strategies. Reliance on proprietary vendor programs presents exposure to sudden policy changes, price escalations, and contract terminations. Transitioning to open platforms can reduce repeat risks, but does not eliminate dependency—especially when managed open source solutions have their own governance and continuity considerations. Clear communication with customers, careful management of migration costs, and ongoing evaluation of vendor relationships are required to avoid operational shocks and revenue disruption in an increasingly consolidated channel environment. Supported by: Pax8 ScalePad

The dominant structural shift highlighted is the migration from flat-rate software subscriptions to usage-based billing models within AI and cloud services. Notably, vendors such as Anthropic, OpenAI, and GitHub have transitioned services off fixed-rate subscriptions toward consumption-based pricing, while Microsoft has introduced new premium tiers that embed AI and security features above the base offering. This shift introduces hidden metering within per-seat pricing, creating less transparency for small- and mid-sized clients regarding actual AI consumption and cost accountability, as documented in research referenced by Forrester. A consequential finding is that budgets for software and AI are reportedly rising by 80% among business and technology decision-makers surveyed by Forrester, yet most organizations are only at the early stages of genuine AI integration. According to IDC research sponsored by SAS, only 9% of small- and midsize businesses (SMBs) have fully embedded AI in daily operations, while about 70% remain in pilot or opportunistic phases. Moreover, a Gallup survey found that 52% of American workers now use AI on the job, but depth of adoption remains limited, with many implementations running only at a superficial level. Supporting developments include mounting evidence that cloud computing's historical promise of near-infinite capacity is eroding. Computer Weekly reports that Microsoft's cloud elasticity is encountering real-world constraints, leading to capacity limits and service rollbacks. Further, regulatory intervention is escalating: New York state has implemented a moratorium on new large-scale data center permits, reflecting mounting political resistance and public distrust toward large technology providers. Meanwhile, increased capital spending by AI vendors is pressuring margins and potentially driving future price adjustments or investment cutbacks across the sector. For MSPs and IT leaders, these trends increase operational complexity and expose gaps in spend governance and accountability. As metered AI and hybrid pricing models proliferate, tracking real usage and managing associated costs becomes more challenging, especially when AI charges are masked within bundled per-user pricing. Providers must develop discovery and reporting practices to quantify hidden AI spend, inventory usage meters within client stacks, and establish pricing models that properly segment one-time discovery from ongoing measurement. Failure to implement these controls exposes both MSPs and clients to unplanned overages, margin loss, and audit risk as consumption scales invisibly under the current invoice structure. 00:00 Your Subscription Became a Meter  04:14 Compute Ran Out of Room 06:51 Nine Percent Ever Finish 09:51 Why Do We Care?  Supported by:  Guardz ScalePad   

The episode identifies a significant structural shift in the technology sector where the adoption of AI is increasingly shifting costs and accountability from technology providers to individual users and their employing organizations, creating new governance and operational complexities. This shift is underscored by CompTIA's research, which indicates a projected growth in tech jobs despite past contractions, alongside a strong intention among companies to increase AI investment and training. However, the true impact is complicated by the distinction between the tech industry (vendors) and technology occupations across all sectors. CompTIA's latest IT Industry Outlook for 2026 reveals a generally optimistic sentiment among tech professionals, with 77% feeling positive about their organizations' prospects and 84% planning to increase AI investment. The report highlights five priorities for AI value: expanding cybersecurity, sharpening data practices, automating workflows, and rebuilding the workforce pipeline. Despite this positive outlook, a key finding is that many companies are still in the early stages of integrating AI into their technology stacks, suggesting that the projected growth may not yet fully reflect the downstream impacts of widespread AI implementation. Further analysis indicates that while AI is driving demand for specific skills like data management and cybersecurity, the development of AI fluency is uneven. Many MSP websites do not mention AI, and only a small fraction offer defined AI solutions, highlighting a potential gap in market readiness. The episode emphasizes that AI is not a standalone product but an enabler, with its cost and complexity necessitating a FinOps approach. This contrasts with the simpler per-user SaaS models, as AI's consumption-based nature and potential for machine-speed operation introduce unpredictable cost variables. For MSPs and IT leaders, this evolving landscape presents several operational implications. The increasing cost and complexity of AI implementation demand a focus on data governance and robust FinOps practices, traditionally handled by IT infrastructure teams but now extending to individual-level use cases. A lack of defined AI job roles and the inconsistent adoption of AI by service providers suggest an opportunity for MSPs to develop expertise in AI governance, enabling them to manage AI implementation, cost, and risk for their clients. Failure to address these governance and cost management aspects could lead to significant operational challenges and liability.   Supported by:  ScalePadGuardz

The dominant structural shift in the cybersecurity market is the relocation of value from security work to financial consequence management, driven by insurers moving directly into the managed services space. A cyber insurer's analysis of 100,000 policyholders revealed that those under constant security monitoring file 70% fewer claims. This data allows carriers to identify effective controls, leading them to offer bundled security services directly to clients and MSPs, as exemplified by Coalition's offerings for managed service providers. This shift is underscored by the commoditization of specialized security tasks. Capital One released Vulnhunter as open-source, an AI tool that finds exploitable software flaws, a function previously requiring dedicated specialists. Similarly, Deloitte is industrializing vulnerability remediation using AI, and Blackpoint Cyber deploys autonomous agents for rapid threat detection and containment. These developments signify that the "doing" of security is becoming automated and cost-effective, while the ultimate financial responsibility remains with those who bear the risk. Supporting this core shift, breaches are increasingly originating through third-party vendors, impacting numerous downstream organizations without direct attacker interaction. A software provider serving over 2,000 US hospitals experienced a breach that exposed data for thousands of its clients. This highlights how vendor security failures create cascading impacts, reinforcing the insurer's position as the party ultimately on the hook for losses and incentivizing them to directly manage or provide the preventative security. For MSPs and IT service providers, this dynamic presents a clear operational imperative. The "insurability floor"—the baseline security controls required by carriers—is rising and being set by insurers, not vendors or clients. MSPs must integrate these evolving carrier requirements into their standard operating procedures to ensure their clients remain insurable. Failure to do so risks making clients ineligible for coverage, creating liability for the MSP, and potentially leading to being bypassed by insurers who are bundling services directly. The value for MSPs now lies in operationalizing this rising floor consistently for all clients, rather than merely providing a static security stack. 00:00 They're Selling the Protection Now  03:24 Why "Secure" Stopped Being Yours  05:57 The Floor Keeps Rising 08:44 Why Do We Care?  Supported by:  Guardz ScalePad 

The episode reveals a fundamental structural shift in AI deployment: the deliberate decoupling of powerful AI capabilities from accountability and human oversight. This is exemplified by incidents such as a former Mayo Clinic safety lead being fired after flagging a hospital AI tool (Maya) with a significant error rate (up to 67%) and the replacement of nurses by AI for administrative tasks at Montefiore. The trend is further driven by the increasing availability of potent, open-source AI models, like Moonshot's Kimik 3.2, which remove the traditional vendor accountability that was once inherent in software delivery. This detachment is fueled by a desire for speed and cost savings, leading to a critical "governance gap" where AI operates without a robust control layer or "harness." A primary development highlighting this shift is the reported issue with OpenAI's GPT 4.56, which allegedly deleted user files, termed an "honest mistake" by the company. This underscores how AI, even from leading developers, can cause operational damage when unsupervised. The episode points out that historically, software delivery included both vendor liability and human oversight as inherent safeguards. However, the move towards commoditized, freely accessible AI models and open-source releases is intentionally eliminating these checks. Enterprises are also rationalizing this by shifting to local AI models, severing ties with vendors who were previously points of accountability. Supporting this central theme, the episode details how the increasing accessibility of advanced AI models, such as Kimik 3.2, means frontier capabilities are no longer confined to major labs. Furthermore, studies indicate that reliance on AI advice can paradoxically reduce human accuracy and increase overconfidence in incorrect outputs, making human review less effective if not properly structured. This suggests that even human oversight, if not independently rigorous, can be compromised by the very AI it's meant to check. The core value is shifting from the AI model itself to the "harness"—the accountable judgment layer that controls and validates AI actions. For MSPs and IT leaders, this structural shift creates significant operational implications. The erosion of vendor accountability and human oversight means the "harness" is often missing, creating a liability vacuum. Clients may deploy AI without adequate checks, leading to potential errors, data loss, and reputational damage. MSPs are presented with an opportunity to address this by becoming the named, accountable "check" or harness provider. This requires shifting client conversations from AI acquisition to AI accountability, mapping existing unsupervised AI deployments, and offering oversight services as a distinct, valuable offering to mitigate risks for clients and ensure trustworthy AI integration. 00:00 AI Went Free, the Checks Didn't  03:59 Forget the Model — Own the Harness 06:45 You Can't Just Watch It Anymore 10:19 Why Do We Care?  Supported by: Pax8

Most MSPs can already tell you which of their clients' Microsoft 365 environments are misconfigured. The harder question is why so few get fixed — and what it takes to turn security visibility into security operations at scale. Dave sits down with Nick Ross, CEO of Cloud Capsule and a three-time Microsoft MVP, to talk about the operational gap MSPs can't close with assessment tools alone, and how his team is trying to close the distance between finding problems and remediating them across dozens of client tenants at once. Nick launched Cloud Capsule's Manage tier in May to move partners beyond assessment into remediation. He argues the biggest challenge in M365 security isn't visibility — it's execution: the knowledge gap around how to architect a policy, plus the manual hours to deploy it one tenant at a time. He walks through how the platform templatizes baselines, enforces desired state configuration so controls can't be quietly tampered with, and gives technicians the context to know whether flipping a control from red to green will flood the help desk with tickets. The conversation also digs into the harder business questions: whether pushing security work down to junior techs lowers the skill floor and introduces risk, how to prioritize 250+ controls without drowning in red, and the economic reality that many MSPs already know clients are misconfigured but can't get them to pay for the fix. Nick's answer leans on newer levers — the AI-readiness conversation, Copilot data governance, and cyber insurance renewals — to reframe security as table stakes rather than a hard sell. Supported by: Guardz  

The core structural shift identified is budget reallocation within technology spending, as funds are redirected from legacy software, hardware refreshes, and higher-cost labor toward AI infrastructure, automation, and junior-level hiring. This resource substitution is not additive but redistributive, with spending on AI solutions and related tools coming directly from reductions in traditional IT line items. IBM's $70 billion market valuation loss and delays in large deals signal that even established vendors are affected by this reallocation, with money leaving areas they once dominated. The primary evidence is IBM's issuance of its first profit warning since the early 2000s, attributed to missed large contracts and delayed deals, which triggered a 25% drop in share value, equating to $70 billion in market cap loss. According to Dave Sobel citing Semafor, this reduction was not due to an overall decrease in technology budgets but resulted from enterprise customers reallocating funds toward hardware and AI-related infrastructure. Omnia reported a 3.6% decline in global PC shipments during the second quarter, which was also attributed to rising hardware component costs driven by AI buildouts, causing delays and cancellations in endpoint refresh cycles. Supporting developments include Ramp and Revelio Labs research showing that organizations intensively adopting AI increased headcount by 10% and entry-level hiring by 12% over two years, while CompTIA found IT unemployment fell below 3% even as tech firms cut staff. Futurism cited further labor market reshuffling, with older workers in AI-exposed roles exiting the workforce and younger, cheaper hires being amplified by automation. ConnectWise's rollout of an AI-native platform and KPMG's survey highlighting the importance of leadership accountability in AI projects reinforce that resource allocation is shifting to tools and personnel accountable for AI operation and outcomes. Operationally, this reallocation puts pricing pressure on providers focused on legacy revenue lines such as per-seat licenses, break-fix, and hardware refresh, as these budget categories are shrinking. Evidence from Service Leadership's profitability report shows providers who adopted service desk automation earlier are now earning more per wage dollar, compounding their advantage. The practical implication for MSPs and IT service providers is to identify which client budget categories are “filling” and adjust offerings toward data readiness, AI deployment, and managed accountability, rather than defending legacy categories now facing structural decline. Failure to adapt exposes firms to revenue erosion and intensifies competitive risk from providers aligned with relocated client spend.   00:00 Watch the Money Move  04:37 AI Spend Is Funded by Substitution  07:19 Your Revenue Mix Is the Bet 10:24 Why Do We Care?  Supported by:  Guardz ScalePad 

The episode highlights a shift from technology selection to operational risk management in the AI landscape for MSPs. Service providers are being forced to navigate the fast-changing interplay between AI models, the harness software that mediates their deployment, and the financial realities of consumption-based billing. The rapid proliferation of open-source and open-weight AI models, alongside market behaviors from closed vendors and regulatory interventions, is introducing volatility and uncertainty in both cost structures and client offerings. This dynamic creates structural challenges related to margin maintenance, vendor dependency, and responsibility for AI-driven decisions. The discussion cites the release of GLM 5.2, an open-weight model from Z AI, which now rivals expensive closed models on key benchmarks at a fraction of the cost. At the same time, large-scale investments by commercial AI vendors have yet to deliver returns on expectations, with reports indicating businesses that adopted AI are not seeing projected value. Specific attention is given to operational constraints such as compute scarcity, token consumption variability, and export policy restrictions impacting AI availability. The episode notes that these pressures are driving both vendors and MSPs to reconsider the viability of reliance on expensive, closed offerings versus investigating open alternatives. Supportive examples include the proliferation of AI “harnesses” (middleware layers like Perplexity, Claude Code, and Cowork) that sit between service providers and underlying AI models, increasing both choice and complexity. Token billing models are highlighted as a source of unpredictability for MSPs, with vendors like Atera and ConnectWise experimenting with different abstractions to shield or pass through token risk to service providers. The potential for on-premises AI deployments using smaller language models is discussed as a cost-mitigation strategy, though this raises further questions about data privacy, infrastructure burden, and long-term vendor roles. Additionally, uncertainty is flagged around sustainability of leading vendors, with projections that at least one major AI player may exit or be acquired within a year due to financial vulnerability. For MSPs and IT service leaders, these structural and supporting developments translate into increased operational and financial complexity. There is a pressing need to evaluate not just which AI technologies to adopt, but how to architect solutions that can withstand rapid vendor movement, cost swings, and evolving regulatory requirements. Practical safeguards include testing open-source AI models alongside commercial offerings, exercising caution in vendor selection, and closely monitoring evolving consumption billing models. Preparing staff and clients for adaptive, process-oriented approaches—rather than fixed solutions—is positioned as a necessary step to maintain resilience as the AI adoption cycle continues to correct course. Supported by:Pax8CometBackupGuardz

Contemporary technology governance has shifted from rule-based regulation to a landscape defined by administrative leverage and directive-driven decisions. This dynamic is seen in both the cybersecurity and AI sectors, where agencies such as the U.S. Department of Defense and companies including OpenAI and Anthropic navigate obligations and approvals through administrative action rather than statutory change. As a result, MSPs and IT service providers must recognize that the durability of their offerings and client architectures increasingly hinges on how they respond to rapid, unpredictable shifts in the governing environment rather than on fixed compliance deadlines or product release dates. A notable example of this mechanism is the Department of Defense's suspension of the rollout of Phase Two of the Cybersecurity Maturity Model Certification (CMMC), as reported by Federal News Network. About 80,000 companies had been preparing for new third-party assessment requirements, but these assessments have been paused pending a 60-day review. Despite the pause, the underlying data protection requirements for defense contractors remain in force, demonstrating that while compliance deadlines can disappear overnight, fundamental security obligations persist. Additional cases amplify the trend toward directive-based governance. The U.S. Commerce Department lifted export restrictions on Anthropic's Fable 5 and Mythos 5 AI models after new safeguards were implemented, following the same pattern previously used to impose those restrictions. Similarly, OpenAI's GPT 5.6 model was released to the public only after a voluntary government review concluded, illustrating that administrative reviews, not boardroom decisions, can dictate technology availability. Concurrently, other governments such as China are employing similar tactics, with Reuters reporting that Chinese authorities have met with local AI firms to discuss restricting overseas access to advanced models. These parallel moves across geopolitical boundaries indicate a structural reliance on executive discretion rather than legislative clarity. The operational impact for MSPs, IT service providers, and technology leaders is a heightened exposure to contract risk and pricing volatility. Service commitments anchored to deadlines, default settings, or product availability are susceptible to abrupt policy reversals or administrative interventions, translating to sudden revenue shortfalls and reactive client management. The recommended response is to audit current commitments, identify those pegged to mutable triggers rather than enduring obligations, and systematically re-anchor contract language and client communication to core outcomes and standing requirements. This preparation mitigates the risk of unpaid work, scope renegotiation, and unplanned operational disruption when another directive-driven policy shift occurs. 00:00 Three Government Switches in Three Weeks  04:07 Why AI Is Governed by Leverage, Not Law 06:46 CMMC Paused — Your Obligations Didn't 09:27 Why Do We Care?  Supported by:  Pax8 Guardz   

The episode highlights a structural shift in cybersecurity risk, moving from a reliance on human skill as both the source of attack and defense to a landscape shaped by autonomous AI agents acting as privileged entities inside client environments. This pivot is illustrated by Sysdig's discovery of an agentic ransomware attack (“Jade Puffer”) where AI software—not a human operator—managed intrusion end-to-end, adapting in real time without manual intervention. The key structural effect is a drastic reduction in the cost and skill required to mount effective attacks, while simultaneously introducing unmanaged access points in the form of AI agents with human-equivalent credentials. Supporting this shift, Sysdig found that the AI-driven “Jade Puffer” attack executed more than 600 payloads, automatically adjusted after failures, and required minimal human oversight. ZDNet reported Apple's unusually rapid patch cycle, attributed by the company to the speed of AI-driven exploit development. According to IT Pro, attackers typically remain inside networks for about two and a half weeks before detection, with nearly half of breaches only discovered after data loss. The U.S. cybersecurity agency CISA admitted to lacking an incident response playbook, improvising during a breach. These developments collectively indicate that existing human-centric security models are being outpaced by autonomous threats. Further reinforcing this thesis, The New Stack emphasized a governance gap: most organizations lack standards for assigning identity or scoping access for AI agents, which today operate using human credentials without effective monitoring or control. AvePoint's research, as cited by Dave Sobel, suggests the number of unseen AI tools inside organizations has nearly tripled, while about half of employees now use AI agents frequently. While agent-based automation expands operational efficiency, the inability to monitor or restrict these agents exposes a widening attack surface and undermines traditional governance. For MSPs and IT service leaders, the operational ramifications include increased accountability for identifying, inventorying, and scoping AI agents as privileged identities within client environments. Continuing to rely on human-centric security and pricing models risks misalignment with actual exposure. The analysis suggests treating AI agent identity management as a distinct, recurring service line—akin to user identity and multifactor authentication—with pricing linked to risk rather than labor hours. Failure to proactively address this governance gap may result in unaccounted incidents and reactive, non-strategic service delivery that affects renewal cycles and liability positions. 00:00 5 Security Alarms Ringing at Once  04:22 Why Hacking No Longer Takes Skill  06:40 Your Agents Became the New Insiders 09:14 Why Do We Care?  Supported by: ScalePad 

The episode highlights a structural weakness in the current cybersecurity product ecosystem, where the process of certification and lab-based product validation often fails to ensure meaningful security. The episode focuses specifically on how regulatory and certification frameworks—such as those linked to device and software security—are largely decoupled from true technical evaluation, enabling both vendors and labs to use certification badges as symbolic rather than substantive assurances of security. According to Adwait Nadkarni, this decoupling allows manufacturers to treat compliance as a liability shield, rather than as a measure of robust risk mitigation. The most consequential finding, as articulated by Adwait Nadkarni, is that many certified security products can deliberately evade both automated and human review processes, with vulnerabilities designed to look secure while quietly exposing risk. The episode references certification structures such as SOC 2 and detailed research into IoT device certification, finding that certification labs often compete on speed and convenience instead of technical rigor. This creates a situation where certified products may still contain basic, decades-old flaws, with operators and MSPs left without practical recourse when technology fails. Other related developments reinforce the risk transfer created by certification mechanisms. Vendors frequently utilize broad liability disclaimers in end-user licensing agreements, explicitly or implicitly excluding themselves from responsibility for product failures—even in scenarios involving harm or downtime. Adwait Nadkarni points to practices where smoke detectors and other security products use ambiguous language about acceptable use and warranty, further reducing vendor accountability. Labs themselves generally disclaim any responsibility for the certified products' behavior once deployed, emphasizing a system with diffuse or absent accountability. For MSPs and IT leaders, these developments underscore the need to move beyond reliance on certifications and vendor marketing. Operators should critically assess the actual language and protections embedded in contracts, focusing on enforceable liability rather than assuming technical validation from a certification badge. Absent regulatory reform or industry-wide consortia to create and uphold real minimum standards, the practical task for service providers is to minimize exposure to legal and operational risk by scrutinizing the fine print of contracts, seeking clear remedies for technology failures, and tempering trust in vendor assurances that cannot be independently verified. Supported by: GuardzCometBackup

A structural shift is occurring as employees and customers increasingly bypass sanctioned IT systems in favor of faster, unsanctioned "shadow" tools that offer comparable or "good enough" functionality with less friction. This shift is highlighted through evidence from Gartner, SparkToro, Microsoft, and reports from Altran Digital Business, which collectively show sanctioned internal and customer-facing systems losing relevance as users opt for alternative solutions that optimize convenience and efficiency over formal governance. The most consequential development referenced is Microsoft's move to replace premium OpenAI and Anthropic models in core applications like Excel and Outlook with lower-cost in-house models, as reported by Bloomberg and Channel Insider. Microsoft claims these new models offer similar accuracy with increased efficiency, reflecting a broader market trend toward solutions that meet minimal functional thresholds at drastically reduced costs. This mirrors broader enterprise behavior, where cost and sufficiency now outweigh premium features, driving a reconsideration of value in AI provisioning. Supporting developments include a Gartner survey showing consumers are about three times more likely to use general AI tools like ChatGPT than corporate chatbots, and a report from Altran Digital Business revealing that over half of employees rely on personal devices or unauthorized tools for work, with nearly a third ceasing to report IT problems entirely. Clickstream data shows that more than two-thirds of Google searches end without a click as users accept AI summary answers, bypassing source links altogether. Vendors such as N-Able and Okta are responding with new products aimed at identifying and gating shadow tool usage, but these approaches often add operational friction without actually closing governance gaps, as Kaseya data indicates most SaaS accounts remain unmanaged despite existing controls. For MSPs and IT leaders, the key implication is that additional controls and "lockdown" measures are likely to increase friction without effectively steering users back to sanctioned processes. Current market tools that focus on visibility and gating of shadow IT may exacerbate the problem by making official workflows less attractive. The practical recommendation is to map where users have already abandoned sanctioned paths and focus on improving those official workflows until they are easily usable and competitive with shadow alternatives. The effectiveness of service delivery should be measured not by control metrics, but by whether users actively choose sanctioned systems for their work.   00:00 The quiet walkout  03:49 Even Microsoft picked good-enough 06:22 Why more control backfires 09:00 Why Do We Care?  Supported by:  Pax8   

The dominant structural shift examined is the erosion of channel-driven value creation in AI offerings, marked by the rapid commoditization of resold AI technologies and a pivot toward consumption-based pricing models. Microsoft Copilot is cited as the most commonly resold AI product by MSPs, with market data showing that 84% of productized AI services among “AI forward” firms rely on this single vendor. The resulting model accelerates value capture at the vendor level, narrowing room for differentiated service or margin at the partner level. This consolidation pressures MSPs to shift from traditional product resale to enablement and operational integration or risk disintermediation. The primary development highlighted is the widespread lack of substantive AI go-to-market offerings among MSPs. According to analyzed web positioning data, 61% of MSPs do not mention AI offerings on their sites, and among those that do, the majority use vague or unscoped “AI solutions” language without concrete services behind them. Only a small subset offers named, productized AI services. Of these, the overwhelming reliance on Microsoft Copilot underscores a lack of channel-developed solutions and points to a market structure where vendors, rather than partners, capture much of the economic value. Supporting developments reinforce both the risk and inertia present within the channel. Ryan Morris outlines that true differentiation will require MSPs to develop packaged offerings around governance, financial controls, and vertical-specific business outcomes, yet early market activity shows little movement in these directions. The discussion emphasizes the potential for cost overrun through uncontrolled AI consumption, echoing past cycles from telecommunications to cloud. Efforts by large vendors to staff direct AI engineering resources are framed as a threat only to the top enterprise tier, with the bulk of SMB delivery left to service providers—albeit within a model now driven heavily by consumption volume and efficiency calculations. Operational implications for MSPs and IT leaders include increased pricing pressure and possible margin erosion as customers optimize consumption and as vendors streamline direct monetization of AI. There is a growing need for internal and customer-facing governance structures to manage data use, financial exposure, and compliance. Channel partners that limit themselves to product resale risk commoditization, while those able to package and deliver business-integrated AI services may find more durable value. The episode underscores the urgency for MSPs to clarify and productize their AI engagement—not simply as a differentiator, but as a defensive strategy against margin compression and vendor dependency.

The core structural shift affecting MSPs and IT service providers is a market bifurcation, where the traditional middle-ground offering—an undifferentiated blend of hardware and support—no longer matches client buying behavior. Dave Sobel referenced research from Techisle, which underscores a split between buyers seeking high-touch, managed outcomes and those opting for low-cost, self-serve technology tools. This division is further exacerbated by increasing component costs and external pressures on hardware pricing, particularly the rapidly escalating prices for memory and storage. Supporting data comes from a recent analysis of approximately 3,000 MSP websites conducted by Business of Tech. The scan found that 68% of MSPs make no mention of AI in their public-facing materials, with only about 1 in 7 offering a defined AI service. Simultaneously, reporting from both Business Insider and E2E reveals that 90% of businesses already have employees using AI tools—primarily adopted independently rather than through formal provider channels. This disconnect highlights a lag in MSP market positioning relative to how technology is actually being acquired and implemented by clients. Additional market stresses are introduced by rising hardware costs linked directly to shortages in memory and storage components. Apple's price increases for Macs and iPads serve as a tangible example, justified by upstream cost spikes in DRAM, which CNBC reported has increased nearly 9x—from approximately $35 to $300 per module. Further, AI data center buildouts are projected to divert up to 20% of consumer memory manufacturing by 2027, suggesting ongoing and intensifying cost pressures for MSPs still reliant on hardware-centric business models. Most providers, as observed by Dave Sobel, remain silent or default to restating the value of external AI platforms like Microsoft Copilot. The practical implication for MSPs and IT service providers is a pressing need to reassess positioning and operational models. Providers embedded in the undifferentiated middle face rising cost risk, declining differentiation, and potential margin erosion. Viable paths require declaring and operationalizing a clear service model, either by transparently externalizing hardware and component pricing risk, or by committing to outcome-based, managed offerings where the provider takes on measurable accountability. Those who adapt agreements and marketing to clarify their role—particularly by documenting internal AI-driven efficiencies—will be better equipped to sustain margin and client relevance as market forces continue to widen the gap. 00:00 Two-Thirds of MSPs Are Silent  04:37 The Memory Shock Splitting the Market 07:05 No Buyer Left in the Middle 10:41 Why Do We Care?  Supported by:  CometBackup ScalePad   

The episode identifies a structural decoupling of software value from licensing units, driven by the rise of agentic AI platforms that automate tasks previously executed by human users within applications. This shift is evidenced by vendors realigning away from per-seat software economics toward service and outcome-based models. Companies such as Microsoft, Amazon, and OpenAI are redirecting resources into consulting and certification initiatives, responding to changing customer usage patterns and eroding profitability of traditional license models. According to Gartner, agentic AI could impact 20% of enterprise SaaS spend by 2030, redefining how businesses allocate budgets for software and services. A notable development illustrating this shift is Notion's decision to discontinue its Notion Mail application, not for lack of adoption, but because automated AI agents had largely replaced the need for a human-operated inbox. Microsoft has committed $2.5 billion and hired 6,000 consultants to embed AI solutions directly within client environments, bypassing traditional software seat sales. OpenAI has announced a global partner program aiming for 300,000 certified consultants within a year, while Amazon is embedding similar models into its offerings. Financial disclosures reveal that OpenAI's cost structure remains unsustainable under typical software unit economics, spending $1.60 for every $1 earned as of the most recent annual report. These developments reinforce the displacement of the per-seat licensing model. Gartner's cited mechanism is arbitrage, where agentic AI completes cross-system tasks without users actively working within apps, detaching business value from app usage. Traditional consulting's move away from hourly billing, as reported by the Wall Street Journal, echoes the software industry's realignment, emphasizing fixed-fee and outcome-based pricing over labor hours. The combination of end-client optimization efforts, vendor migration to services, and changes in consulting economics demonstrates a market-wide move toward operational accountability over software resale. For MSPs and IT providers, these changes pose direct challenges to legacy revenue assumptions and operational models. Per-user or license-based pricing faces mounting contract risk as agentic agents reduce seat counts. Service providers will be evaluated on their ability to manage this transition—internally and for their clients—by documenting workflow changes, auditing tool stacks, and adapting to new consumption and outcome-based vendor models. Early adoption of these practices within one's own business is becoming a credibility benchmark, as prospective clients scrutinize whether providers have successfully navigated the same seat retirement and cost reallocation they are expected to deliver. 00:00 Software Giants Go Human  04:26 Agents Don't Buy Seats  06:58 Squeezed From Both Ends 10;12 Why Do We Care?  Supported by: Guardz Pax8 

The dominant structural mechanism explored in this episode centers on governance gaps in access management and the resulting liability transfer to MSPs. The discussion highlights how fragmented identity stacks, unmanaged access, and reliance on manual tracking expose MSPs to growing contractual, operational, and legal risk. Companies and technologies referenced include Microsoft 365, Google Workspace, Okta, ConnectWise, and specific access governance solutions targeting the channel. The ConnectWise 2026 Threat Report identifies credential abuse as a core attack vector, underscoring how unaddressed authorization and access drift remain a structural exposure area. The episode cites multiple indicators and supporting data. According to the ConnectWise 2026 Threat Report, credential abuse is now the primary attack vector, with attackers commonly exploiting active and orphaned accounts left unmanaged in client environments. Fragmented identity stacks complicate the onboarding and offboarding process, with onboarding often requiring 45 minutes per client as technicians navigate numerous access portals. The prevalence of shadow IT, orphaned accounts, and missed deprovisioning windows was discussed as persistent drivers of both operational overhead and increased incident risk. Supporting developments include community-documented scenarios where multi-factor authentication (MFA) was present but insufficient to prevent breaches, particularly when privilege escalation or temporary exclusions remain unaddressed. Examples such as the Reddit phishing event and Microsoft's handling of MFA via VOIP demonstrate how authentication is distinct from governance, and that temporary access or exceptions frequently become permanent, heightening exposure. Regulatory environments—including healthcare, finance, and government—were cited as adding further requirements for explicit governance controls and auditable access policies, while manual spreadsheet tracking often fails to meet these demands. The operational implications for MSPs include the need to move beyond basic practice such as MFA and endpoint protection, toward purpose-built tools and processes that provide continual visibility, auditable controls, and policy enforcement for client access. Without this, MSPs face increased administrative burden, billing discrepancies, contractual liability, and reputational risk. As regulatory audits become more demanding and clients demand clearer evidence of governance, service providers must reconcile the tradeoffs between increased process complexity and the need for automated, enforceable identity governance. This shift challenges existing pricing models, requiring MSPs to justify and potentially repackage their service offerings in the context of risk management and operational maturity.

The episode examines the ongoing shift in the IT services market from traditional managed services to “managed intelligence,” as vendors like PAX8 and ConnectWise attempt to reposition their offerings around artificial intelligence (AI). This structural change introduces increased operational complexity for MSPs who are being urged to adopt new AI-driven models, while facing evolving expectations regarding service delivery, pricing, and accountability. The mechanism at play is the transfer of risk and uncertainty from vendors to MSPs, especially as AI and usage-based billing models upend established business practices. One significant development highlighted is PAX8's call for MSPs to become “managed intelligence providers”; however, according to PAX8's own head of AI adoption, only 17 out of 600 interviewed partners currently meet that standard, up from 13 a year prior. In response to this slow uptake, PAX8 has introduced bridge services and a Managed Intelligence Program to support partners through the transition, including white-labeled AI services and a platform for tracking usage called the agent gateway. These efforts underscore that the managed intelligence model presents a steep learning curve for most MSPs, with few having yet achieved operational maturity in this area. Related market activity further illustrates these dynamics. ConnectWise has restructured its platform around an AI core, introducing predictive intelligence and shifting to ticket-based billing rather than traditional per-seat models. According to ConnectWise, this shift reduces L1-L2 ticket escalations by 86% and increases technician productivity by 30%. Meanwhile, concerns remain about data ownership and the scope of actionable information, with companies like Lexful and Enable pushing for greater integration across siloed applications. There is also ongoing debate on whether system-of-record vendors or independent AI-native platforms will ultimately control operational workflows and client relationships. For MSPs and IT service providers, these developments translate into practical concerns around vendor dependency, variable cost exposure, and pricing pressure. The move to consumption-driven models and token economics increases unpredictability, forcing providers to absorb or carefully manage AI usage costs or risk compressed margins. There are also governance and accountability questions related to client relationships, especially as more AI service layers are introduced by upstream vendors. The operational implication is a need for heightened financial diligence, risk assessment, and a clear strategy for maintaining client trust and service differentiation in an increasingly intermediated service landscape. Sponsored by: Pax8 ScalePadABC SolutionsRythmz

The dominant structural shift outlined is a transfer of liability and accountability for AI-generated errors from vendors to the entities deploying these systems—primarily MSPs and their clients. While vendors aggressively promote scalable AI tools and urge rapid adoption, the legal and operational burden of verifying and standing behind AI output falls on deployers, not on the tool providers. Recent court rulings and shifting buyer expectations are accelerating this transfer, fundamentally altering the MSP business model around AI services. Primary evidence for this shift comes from both industry behavior and legal precedent. Kaseya urged MSPs to quickly embrace AI services while revealing that only about 13% of providers are seeing significant revenue from AI, despite roughly half of clients requesting these solutions. Compounding the structural gap is a low conversion rate from proof-of-concept to production (only 20% success, per Kaseya), and high failure rates in AI-generated code—Forbes reported security and logic errors appear far more frequently in machine-produced output than in human code. Notably, courts in Germany and Canada have ruled that organizations are legally responsible for the statements and errors created by their AI, not the vendors providing the underlying tools. Supporting developments reinforce the risk and accountability mismatch. Research cited from Gartner indicates over 70% of CEOs and 75% of CIOs believe current IT operating models are unfit for the demands of the AI era, highlighting a recognized governance gap. Consumer surveys show that over half hold company leadership personally responsible for AI failures. The recurring vendor emphasis on selling tools, combined with product features that prioritize scale over individualized accountability, deepens the structural challenge for service providers. For MSPs and IT service organizations, the primary practical implication is that competitive differentiation and risk mitigation will depend less on which AI products are resold and more on documented processes for reviewing, annotating, and standing behind AI-generated output. Vendors' tools are pervasive and quickly commoditized, so market separation arises from the ability to provide tangible accountability standards—proof of human review, defined sign-off authority, and clear records for client audits and legal defense. Pricing strategies that reflect the cost of accountability, rather than simply product markup, are likely to become more sustainable as client focus shifts from features to liability management in AI adoption. 00:00 The 13% Problem  03:29 The Tool vs. The Work 05:43 The Wrong Answer's New Address 08:37 Why Do We Care?  Supported by:  CometBackup TimeZest   

The dominant structural shift underlined in this episode is the removal of the pricing floor for undifferentiated, repeatable IT work due to agentic AI adoption, especially in IT services and MSP operations. As described by Dave Sobel, this shift is not about wholesale job elimination but about AI absorbing routine, predictable execution, leaving human operators responsible for judgment and oversight. This change is illustrated by organizations such as OpenAI, where 97.9% of employees use AI agents, and by sector-wide hiring data tracked by SignalFire, revealing that software engineers—previously considered vulnerable—remain the largest share of new hires. The most consequential development is the clear division between executional work and judgment-based roles. Data from SignalFire shows that software engineers make up 55% of new tech hires, contrary to predictions of their displacement by AI. Similarly, ISC2's Cybersecurity Workforce Survey, reported by Dark Reading, finds entry-level cybersecurity roles are evolving rather than disappearing, with AI taking over routine triage and increasing demand for higher-level judgment skills. OpenAI's near-universal internal AI adoption supports the notion that employees are adapting their roles rather than being replaced outright. Further supporting developments include evidence from SplashTop, which measured that 53% of IT team capacity is spent on endpoint maintenance and repetitive tasks, areas highly susceptible to automation. The effect is heightened by macro trends—cited from Axios Macro and the NFIB—showing small businesses are actively reducing hiring plans and seeking solutions that remove the need for headcount growth. New MSP offerings, such as managed support teams available within 30 days, are scrutinized for repackaging traditional labor models vulnerable to rapid automation. For MSPs and IT service providers, the operational implication is the urgent need to reevaluate service lines, staffing, and pricing models. Services based on predictable, repeatable execution now face competition from AI-driven agentic work that operates with negligible marginal cost, eroding the business case for labor arbitrage and body-shopping models. The path to defensibility shifts toward services that require human judgment, oversight, and outcome-based delivery, with increased risk for firms reliant on commoditized execution. Sorting offerings by their exposure to automation and focusing investment in non-automatable, judgment-driven roles becomes a practical risk mitigation approach. 00:00 The Most-Hired Casualty  04:19 Which Half It Eats 07:06 The Rent-a-Team Trap 09:47 Why Do We Care?  Supported by:  Pax8  Sign up for the SMB Online Conference: www.smbonlineconference.com

The dominant structural shift addressed is the increasing operational dependency on Microsoft Intune for endpoint management across organizations of all sizes, which is exposing gaps between Microsoft's native capabilities and the practical needs of managed environments. This shift is creating new pressure points for service margins, as IT service providers find themselves compensating for visibility limitations and inconsistencies in Intune's deployment mechanisms. Vendors such as Recast Software have positioned themselves as companions that address these shortfalls, acknowledging that Microsoft routinely incorporates previously “companion” features into its own ecosystem. The primary evidence cited is the identified lack of comprehensive fleet visibility and inconsistent application deployment within Microsoft Intune environments. According to Recast Software's Chief Product Officer, Jake Mosey, customer feedback repeatedly points to insufficient information about device states—especially during hybrid or co-managed transitions from Microsoft Configuration Manager to Intune—and challenges with application deployment timing, patching, and third-party app management. These operational gaps create environments in which service providers must employ supplemental tools to maintain efficiency and consistency across client environments. Supporting developments include lessons learned from similar dynamics in the Apple-Jamf ecosystem, where continual vendor evolution (“Sherlocking”) forced channel vendors to focus on speed, specialization, and building direct community relationships. Jake Mosey emphasized that effective community-driven product development relies on discerning the needs of the wider user base, not just the loudest voices, and maintaining a focused strategy. The discussion also highlighted persistent fragmentation in multi-platform environments, meaning MSPs must often manage diverse device fleets with varying visibility and control requirements—a complexity heightened during prolonged hybrid migration states. Operationally, MSPs and IT leaders face practical implications including increased vendor dependency, the need for multifaceted visibility tools, and a requirement to plan for ongoing hybrid environments rather than clean migration end-states. Service providers are urged to prioritize automation where possible but must also recognize that full migration to a single endpoint platform remains impractical for many. Failure to address these gaps increases risk to client productivity and end-user satisfaction, particularly when patching, application deployment, or security controls are inconsistently applied. The expectation is that meaningful improvements will depend more on inventory and visibility capabilities than solely on automation or AI.

The dominant structural shift highlighted is margin pressure and business model viability for MSPs due to workforce reduction driven by AI automation. This is exemplified by Microsoft's introduction of Agent365—an enterprise product licensing AI agents rather than human users—and industry reports forecasting that 30–50% of white-collar jobs may be replaced by AI technologies, according to publication summaries referenced during discussion. The shift fundamentally threatens the per-seat managed services pricing model that has anchored MSP revenue. Evidence of mounting financial risk is provided by the scenario where clients may halve their seat counts within a two-to-three-year window. As stated, this adjustment would immediately cut monthly recurring revenue (MMR) for MSPs. The discussion connects this trend to Microsoft's evolving licensing model and notes an industry-wide consensus reflected in a Capterra survey, which found all surveyed MSPs in 2024 facing significant increases in local competition. The implication is that margin pressure from both automation and intensifying competition is occurring simultaneously. Additional developments reinforce the risks to stability. Security complexity and associated liability are increasing, as non-specialist teams—originally tasked with legacy IT functions—are now expected to take responsibility for security operations without adequate expertise. This burden is heightened by the emergence of unmanaged AI adoption at client organizations, creating new avenues for data exposure and regulatory risk. Surveyed business owners are considering exit or consolidation, citing inability or unwillingness to restructure business models to accommodate these changes. Peer group participation is recognized as widespread but not a direct countermeasure to these structural challenges. For MSPs and IT service providers, the practical implications are clear: reliance on the per-seat model is a growing contract risk, with revenue volatility linked to workforce automation outpacing both the speed of traditional service adaptation and client technology adoption. Accountabilities around AI risk, security governance, and compliance are expanding—often without a corresponding increase in compensable scope or staff capability. Operators must assess vendor dependency (especially in rapidly shifting software licensing models), realign service portfolios towards advisory, compliance, and security, and prepare for sustained market turbulence marked by shrinking margins and rising operational complexity. Supported by:  Small Biz Thoughts Community Sign up for the SMB Online Conference: www.smbonlineconference.com

A structural repricing of memory and silicon components is forcing a shift in the economics of hardware resale for managed service providers (MSPs) and IT service providers. This shift is driven by concentrated demand for memory components from AI infrastructure build-outs, as evidenced by data from IDC and remarks from companies including Apple, Micron, SK Hynix, and Samsung. The episode highlights that memory costs have quadrupled in a year, and that both endpoint devices and servers are experiencing durable price inflation due to component scarcity and intensified competition for supply. The most consequential development cited is Apple's acknowledgment—confirmed by Tim Cook to the Wall Street Journal—that device price increases are now “unavoidable” because the cost of memory can no longer be absorbed. Memory manufacturers' share prices rallied on this signal, reinforcing an investor consensus that higher component costs will persist. IDC data showed AI-focused, non-x86 servers using Nvidia's ARM chips generated $58.7 billion—or nearly 48% of all server revenue—up 107% year over year, while x86 server revenue declined due to DRAM and NAND shortages. This dynamic indicates that AI infrastructure is bidding up component costs at the expense of standard business hardware. Secondary developments further reinforce this mechanism. The market's response to U.S. government announcements regarding Intel chip capacity expansion demonstrates that relief from the silicon crunch remains years away, not months. Channel partners—according to industry reporting—were already pivoting from hardware resale to services prior to these price shocks, with thinning hardware margins preceding the current pressure. The combination of fixed-fee hardware contracts and rising component costs now places providers in a position where they are “short silicon,” having unknowingly absorbed inflation risk they cannot pass on under existing contractual terms. For MSPs and IT leaders, the principal operational implications center on contract structure, exposure to component price volatility, and diminished hardware margins. Providers with fixed monthly agreements or hardware-as-a-service contracts based on last year's component costs are at an increasing risk of margin erosion, as their ability to reprice is contractually limited. Practical mitigation steps include auditing all fixed-fee agreements for exposure, amending contracts to include component index or price adjustment clauses, and separating hardware as a transparent, pass-through line item. Failing to adapt contract terms or refresh timing may compound both financial risk and the security profile of client endpoints. 00:00 Not the Tokens  03:31 An Auction for the Parts 05:46 Short Silicon 07:44 Why Do We Care?   Supported by: Pax8 ScalePad    Sign up for the SMB Online Conference: www.smbonlineconference.com

The episode reveals a structural shift where “AI powered” has moved from a selling point to a source of liability and customer distrust. Surveys from WordPress VIP, the Pew Research Center, and Carnegie Mellon University indicate that both consumers and professionals increasingly see visible AI in products and services as a negative attribute, eroding trust rather than adding perceived value. This trend impacts MSPs directly, as their role in advising clients on technology adoption now brings increased accountability for customer experience outcomes tied to AI-driven automation. According to a WordPress VIP survey, 60% of US consumers are deterred by the term “AI” in brand marketing, and 86% do not fully trust AI-delivered information, preferring original sources. The Pew Research Center found that, while 49% of US adults now use AI chatbots, 40% believe AI will worsen society and 67% distrust regulatory oversight. A Carnegie Mellon study of working visual artists reported 99% disapproving of generative AI and 85% refusing to use it. These quantified findings underscore a broad disconnect between AI adoption and public trust. Additional research reinforces this skepticism and clarifies operational risks. AnswerConnect's survey of 6,000 consumers across the US, UK, and Canada found that 85% prefer human service over bot interactions, 57% lose trust in brands using AI for support, and 73% exhibit greater loyalty to businesses maintaining human involvement. Data from Fractal and Search Engine Land shows that the share of consumers who say heavy AI use would decrease their trust in a brand nearly doubled in a year, rising from 20% to 39%. Furthermore, 84% desire businesses to disclose AI use, yet only 20% of businesses consistently do so. These patterns suggest tangible declines in customer loyalty and increased expectation for transparency surrounding AI deployment. For MSPs and IT service providers, visible AI in customer-facing areas introduces pricing risk and trust liabilities. Delegating key customer interactions to AI without clear disclosure can erode brand equity and disrupt client retention metrics. The operational recommendation is to segment human-in-the-loop service as the standard premium offering, with fully automated AI positioned as a disclosed, lower-tier alternative. Writing these distinctions explicitly into contracts and statements of work—pairing them with actual client retention data—enables more defensible pricing and clarifies accountability, helping avoid unintended consequences tied to silent automation. 00:00 The Turn-Off  03:39 Reading the Motive 05:25 The Loyalty Account 08:35 Why Do We Care?    Supported by:  Pax8  ScalePad    Sign up for the SMB Online Conference: www.smbonlineconference.com

Vendor channel consolidation, specifically through peer and family-owned acquisitions, is driving a fundamental shift in the operational landscape for MSPs. This episode analyzes the case of NetSciences, an MSP based in New Mexico, which was acquired by Qual IT—a family-owned operator with over two decades in the space. The MSP market now includes multiple buyer categories: peer acquisitions, roll-ups, and private equity (PE) players, each with distinct approaches to valuation, integration, and operational continuity. The transition of NetSciences to Qual IT illustrates that smaller MSPs increasingly face decisions about optimal sale pathways. According to Joshua Liberman, roll-up buyers and PE investors often introduce rapid shifts in deal terms and operational models, with PE offers described as subject to abrupt valuation changes (drops up to 67% noted by Liberman), creating a higher risk profile for sellers seeking stability and legacy preservation. By contrast, the peer acquisition model (as executed through platforms such as ASCII's peer-to-peer review process) is allowing some MSPs to complete sales with greater continuity and cultural alignment, though post-sale integration often defaults to the acquirer's systems and standards rather than blending best practices. Secondary developments reinforcing this shift include persistent market focus on monthly recurring revenue (MRR) metrics and the operational tradeoffs of pursuing high MRR percentages. Liberman maintained a 50–60% MRR intentionally, arguing that chasing 80%+ MRR metrics can distort business health and does not universally suit all MSP models. Discussion of cybersecurity underscores the need to reposition technical services as business outcomes—security is described as foundational, permeating every operational and client decision, yet is often misunderstood or negotiated away to the detriment of risk posture. Operationally, these trends imply that MSPs must be highly selective about both client and acquirer fit, balancing growth trajectories against risk aggregation and cultural alignment. Attempts to homogenize client environments and enforce consistent security baselines are necessary but limit scale and acquisition appeal. Failure to assess how integration will shift toolsets, processes, and staff autonomy can result in loss of operational maturity and control post-sale. Additionally, the unchecked adoption of tools such as AI—without oversight or documented process—exemplifies emerging areas of governance risk that technology leaders cannot overlook. Supported by: ScalePadTimeZest Sign up for the SMB Online Conference: www.smbonlineconference.com

The episode highlights a structural shift in IT and security governance driven by the proliferation of autonomous AI agents inside enterprise environments. This shift is characterized by a mismatch between the visibility and control frameworks that organizations possess versus the scale and autonomy of AI deployments. Microsoft's introduction of Agent365—a control plane designed for agent governance—and policy statements from its security leadership illustrate the growing gap between the number of AI agents and the traditional IT administrators tasked with managing them, raising questions about the effectiveness and scalability of legacy governance mechanisms. A consequential development described is the growing risk stemming from AI agents operating with inherited credentials and unrestricted lateral access, often without comprehensive oversight or tracking. Both Microsoft and Zero Networks are referenced as addressing this problem but propose different architectural solutions. Microsoft's model emphasizes governance at the identity and endpoint layers, exemplified by Agent365, while Zero Networks promotes network-layer enforcement. The latter approach seeks to restrict lateral movement before it leads to a breach. Data points referenced include insider reports of numerous agents running undetected in enterprise workflows, and observations that most organizations lack accurate inventories or controls corresponding to their AI agent exposure. Supporting stories reinforce the structural shift and associated risk, with Chris Boehm emphasizing the speed and scope of AI agent deployment compared to previous technology waves such as mobile and cloud. The emergence of agents capable of rapidly scanning and connecting across systems further complicates standard prevention and detection postures. Credential governance is described as insufficient on its own, since privileges and exceptions tend to accumulate and enable unaudited access, particularly as agent proliferation accelerates. The episode also references the challenge of building reliable behavioral baselines due to the dynamic, ephemeral nature of modern agents, making static or manual approaches impractical. For MSPs and IT service providers, the operational implications include increased risk associated with governance gaps, margin pressure from the need to adopt new security layers, and greater complexity in maintaining policy enforcement. Existing security stacks are often fragmented, with consolidation complicated by the addition of new solutions that promise automation and scalability but also require integration into varying infrastructure maturity levels. Effective containment of breaches is increasingly tied to minimizing lateral movement rather than relying solely on detection speed. As agent-driven access becomes ubiquitous, the ability to dynamically segment and restrict access based on observed behavior, rather than static credentials alone, is highlighted as a practical safeguard in limiting breach impact and maintaining service continuity. Supported by:Zero Networks https://zeronetworks.com/

The episode centers on persistent margin pressure and operational discipline as the dominant structural mechanisms in the managed services sector. Data from the Service Leadership Index (SLI), managed by ConnectWise under Peter Kujawa, reveals that best-in-class MSPs continue to target aggressive profit growth—specifically, a 34% increase in profit dollars on only 10.6% revenue growth—despite already sustaining a six-year average of 19% adjusted EBITDA. The discussion highlights that achieving these targets relies less on rapid revenue growth and more on cost control, particularly around SG&A (Selling, General and Administrative Expenses), and highlights the influence of financial discipline often seen in private equity-backed firms. The analysis is grounded in quantitative benchmarking. According to the SLI's 2026 profitability report, while best-in-class EBITDA performance has been sustained, recent years show a widening gap between budget targets and attainment. Specifically, in 2023, MSPs overshot their profit budget by 31%, but in 2024 and 2025, performance dropped to 81.9% and 89.4% of budget respectively. The report explicitly calls current profit targets “ambitious,” given recent misses. Scale thresholds were also referenced, notably the operational risks between $6M and $10M in annual revenue, with Peter Kujawa citing stalls in growth and compressed margins as common in that band. The episode further introduces the first iteration of an Automation Index intended to quantify financial and operational impact of AI adoption on MSPs. Metrics such as service multiple of wages, revenue per employee, and service gross margin are emphasized, but findings show that automation is not delivering uniform benefit. Top-tier MSPs increase efficiency and retain pricing discipline, while bottom quartile firms see little or no improvement in core metrics. The report also notes that private equity-backed providers are investing significantly in AI, though organic growth and acquisition costs remain similar across provider types. Operational implications for MSPs include heightened accountability for realistic forecasting and disciplined budgeting. Failure to match projections with operational realities risks unnecessary cost expansion, especially around headcount and tool adoption. For firms in key scale thresholds, owner delegation and leadership investment are essential to avoid stagnation and margin erosion. Additionally, automation and AI adoption provide efficiency opportunities but deliver benefit only to those with strong management practices; undisciplined adoption or margin givebacks through pricing discounts negate potential gains. MSPs must therefore focus on data-driven decision-making, careful cost control, and ongoing evaluation of both financial and operational KPIs to navigate increasing complexity, vendor dependency, and persistent margin pressures.

The core structural shift highlighted in this episode is the commoditization of AI model platforms and concurrent consolidation at the vendor and platform layer, forcing Managed Service Providers (MSPs) to move their value proposition above reselling models to orchestrating, governing, and verifying AI outputs. The discussion references the rising concentration and valuation of platforms such as NinjaOne—a founder-led, profitable RMM platform with a $12.3 billion valuation and 70% year-over-year growth—and Pax8 building business toolkits that draw more operational functions onto their rails. At the same time, major AI developers like OpenAI are entering the channel more directly by launching partner programs aimed at MSPs and consultants. The most consequential development is the confirmed shift from reselling AI models to managing their outputs and risks. Glean surveyed 6,000 digital workers and found that while AI delivers approximately 11 hours of weekly time savings, nearly 6.4 hours are reclaimed by “bot sitting”—the human intervention required to supply context, verify, and correct AI outputs. This hidden labor raises a risk scenario: two-thirds of workers admit to releasing unchecked AI outputs, and Ivanti found that only 42% of IT environments actually have a named owner for each AI agent, despite 85% claiming so—a 43-point gap in accountability. Asana and Deloitte further reinforce the issue, reporting frequent cost overruns and unmanaged autonomous AI deployments among enterprise and SMB environments. Supporting developments underscore this governance and accountability gap. TechCrunch cited that ChatGPT's AI market share has dropped below 50% as the field becomes more interchangeable and less differentiated by underlying model. Vendors such as Anthropic and OpenAI, recognizing model commoditization, are seeking revenue through high-volume partner channels, blurring the lines between vendor and channel competitor. According to Asana, more than 80% of UK IT leaders encountered unplanned AI costs, and over half reported business harm from autonomous AI actions, shifting operational and liability risks squarely onto MSPs and IT service providers. Operationally, these trends compel MSPs to take explicit ownership of the orchestration and governance layer, rather than relying on tool reselling. The transcript advises mapping every AI-driven decision or output that reaches client endpoints and identifying who verifies these outputs before customer exposure. Failing to address these governance blanks does not avoid work but shifts it to unbilled, post-incident cleanup, often with financial, legal, or compliance consequences. Effective MSPs will need to price, document, and regularly review their verification, orchestration, and risk assumption, positioning these as standalone, billable services to manage risk and maintain margin as AI platforms commoditize and vendor dependencies rise. 00:00 Bigger Platforms, Unwatched AI 03:44 The Vendor Walks Into the Channel 05:56 Govern It or Absorb It 08:52 Why Do We Care?  Supported by:  ScalePad  Sign up for the SMB Online Conference: www.smbonlineconference.com

A pronounced infrastructure dependence on third-party AI models has emerged across the MSP ecosystem, largely due to the rapid adoption and integration of AI-powered features within vendor products. This structural shift is increasingly opaque, as providers are sold features rather than transparent access to underlying models, leaving MSPs exposed to changes in technologies and policies enacted upstream by vendors or regulators. The episode highlights how this dependency extends to delivery teams and end clients, with operational continuity tightly linked to decisions and actions outside the MSP's direct control. The most consequential development referenced is Anthropic's release and rapid withdrawal of its Fable 5 AI model following a directive from the U.S. Commerce Department, which ordered a cutoff of model access to foreign nationals within 72 hours of public launch. According to published benchmarks, Fable 5 surpassed GPT 5.5 in performance, but the government-mandated suspension exposed how quickly model access can be rescinded. The policy move immediately impacted any MSP or client with offshore or nearshore staff relying on AI features invisibly powered by that model. Further supporting the central theme, companies such as PAX8, Enforcer, and CloudRadio are embedding AI capabilities into platforms used by MSPs to manage Microsoft 365 environments, automate ticketing, and support scalable client operations. In parallel, vendors like Proofpoint are integrating compliance solutions directly with AI model APIs, further entwining risk management tools with the same core AI infrastructures. A Netrio survey cited in the episode found that while 82% of mid-market IT leaders have AI in production, only 26% report organization-wide governance, highlighting an accountability and visibility gap. Operationally, MSPs face heightened contract and vendor risk. Most lack an accurate inventory of which AI models underpin their services and how rapidly these dependencies can be affected by regulatory directives or vendor shifts. The discussion underscores the need for explicit procurement protocols, delivery mapping, and outage runbooks that account for opaque model dependencies. As clients seek greater transparency and contractual assurances regarding model use and continuity, MSPs who anticipate and document these dependencies may be positioned to reduce exposure and establish clearer accountability. 00:00 Switched Off  03:19 Painted Over 05:20 Govern or Absorb 08:41 Why Do We Care?  Supported by: Pax8 Sign up for the SMB Online Conference: www.smbonlineconference.com

The episode highlights a structural shift from automation that suggests actions to automation that executes actions autonomously, thereby transferring substantial operational risk and accountability to technology vendors and their AI-driven platforms. This transition is exemplified by Atera's deployment of their autonomous AI agent, Robin, which is positioned to handle a significant proportion of Tier 1 and complex Tier 2 IT tickets for managed service providers (MSPs). The company's commercial strategy, including performance guarantees, signals an increased expectation that AI can assume core IT operational responsibilities that were traditionally reserved for human engineers. Atera has introduced a policy wherein Robin is guaranteed to autonomously close at least 50% of all Tier 1 and complex Tier 2 tickets within 90 days of onboarding, or fees are waived. According to Atera, this commitment is supported by a backend analysis of MSP tickets and live demonstrations using historical data. The company asserts that Robin's mean time to repair is approximately 120 seconds, that onboarding is managed collaboratively, and that the rollout is more akin to hiring and training a human engineer than a standard software deployment. This approach is backed by patent filings and a business model integrating AI as the foundation rather than an add-on. The episode further examines the implications of mandatory AI bundling in Atera's redefined RMM and PSA platform offering. The company has faced pushback from segments of the MSP community dissatisfied with bundled AI services and associated pricing changes, particularly from those wishing to maintain control over their technology stack. Atera responds by describing a re-conceptualization of their platform as inherently AI-driven, distinguishing between “platform AI” and the autonomous Robin agent, and clarifying that preexisting AI users would not incur additional costs. There is also discussion around the impact of automation on human roles and the need for new approaches to training and accountability, particularly for junior staff. For MSPs and IT service providers, these developments signal an increase in infrastructure dependency on vendor-managed AI agents, as well as new layers of contract risk linked to performance guarantees and platform integration. The operational reality described involves a significant reduction in required headcount, a shift in staff responsibilities from routine incident response to higher-order business and security tasks, and the necessity for designated internal management of AI tools. There remain unresolved concerns about skill degradation and the long-term risks of over-automation, including the narrower pathways through which junior personnel may acquire foundational experience. Sponsored by:  ScalePad https://scalepad.com/dave/ Nerdio https://nerdio.co/MSP-Radio Sign up for the SMB Online Conference: www.smbonlineconference.com

Vendors supplying AI-driven technologies are experiencing sustained margin pressure from high operational costs and underwhelming business-level returns, leading to the rapid creation of new product categories that are pushed into the MSP channel. Companies such as Atomic Work, Silverfort, and Guards are releasing governance tools for managing AI agents, while Connect Secure is offering patch management products targeted at MSPs. These launches are not indicators of competitive differentiation, but of structural cost challenges being passed from vendors to their partners.   Business media reports and internal industry data reveal that while individual productivity from AI implementations increases—for example, by accelerating engineer output—the promised business-level gains in productivity, revenue, and profit have not materialized to the extent vendors projected. According to analysis cited by Dave Sobel, high operational costs are forcing large firms like Microsoft, Google, Amazon, and Uber to restrict or cap AI usage internally, reflecting an industry-wide retreat from premium pricing models due to an unclear return on investment at the organizational level.   Additional developments reinforce this margin-driven shift. The federal Cybersecurity and Infrastructure Security Agency (CISA) has mandated 72-hour patching of high-risk vulnerabilities, underscoring heightened compliance requirements. Simultaneously, vendors are accelerating the rollout of governance, identity, and patch velocity tools. However, a study analyzing over 13,000 US MSPs found that those surpassing $1 million in revenue are distinguished by market positioning, online visibility, and business maturity, not by the breadth or novelty of their toolsets.   For operators, the implication is clear: stacking up new vendor products is now a baseline requirement rather than a path to competitive advantage. Firms that rely solely on vendor frameworks and toolsets risk absorbing more complexity without improving margin or differentiation. Practical separation will come from owning the "judgment layer"—defining, governing, and pricing how AI functions within client environments—rather than reselling tools. Positioning, documented governance, and clear operational standards will be more defensible than investing exclusively in vendor-driven offerings. 00:00 Manufactured Urgency  03:58 The Cost Confession 06:09 Out-Buy vs. Out-Position 08:35 Why Do We Care?    Supported by:  Nerdio  Sign up for the SMB Online Conference:  www.smbonlineconference.com

Vendor channel consolidation continues to restructure the MSP landscape, with private equity-backed rollups driving both market concentration at the top and increased deal volume. This episode centers on the sale of Worksighted, a 25-year-old, $27 million revenue MSP with strong vertical focus in healthcare and construction, to Thrive in a 35-day close. The structural mechanism at play is an increasing market segmentation where larger MSPs systematically acquire or merge with similarly sized providers, often leaving a gap for smaller operators as larger entities move upmarket. Primary evidence for this consolidation includes direct transaction data and workflow. According to Abraham Garver, his team handled 132 vetted buyer candidates for Worksighted, resulting in eight competitive offers after 76 signed NDAs. Thrive, having completed 27 MSP acquisitions, was able to accelerate the deal's timeline due to deep experience and preparation by both buyer and seller. The trend is further supported by Q2 market updates indicating 22 U.S. MSPs likely to come to market in 2026 and over 120 M&A transactions in Q1 alone, as reported by Drake Star. Related developments highlight the bifurcation of deal opportunities by provider size and the associated liquidity for MSPs. Private equity buyers increasingly favor acquisitions with a minimum of $3 million in revenue and $500,000 in EBITDA, while smaller MSPs are more commonly left to pursue peer-to-peer mergers or organic growth strategies. The episode also addresses the operational pitfalls of optimizing solely for high recurring revenue percentages, with evidence suggesting buyers offer premiums for organic growth and new client acquisition rather than rigid recurring revenue thresholds. For operators, these dynamics generate clear tradeoffs and risks. Larger MSPs face the challenge of integrating acquired firms and potentially divesting smaller clients who do not meet their revised minimums. Smaller MSPs may find opportunity by acquiring divested clients or targeting niche segments that fall beneath larger consolidators' thresholds. For all providers, the importance of thorough preparation, clean financials, and strategic clarity on post-transaction roles emerges as a key safeguard against value loss and disruption. Rigid adherence to target metrics not grounded in buyer behavior—such as focusing excessively on monthly recurring revenue—carries the risk of reduced flexibility and diminished exit prospects. Sponsored by:ScalePad ABCS Sloutions LLC

Platform vendors are transferring liability and delivery responsibility for AI services onto MSPs by building structured AI practice frameworks, training programs, and service delivery methodologies. This approach is motivated by mounting economic pressures on vendors, as seen with large-scale infrastructure investments and the need for sustainable revenue models. PAX8, Ingram Micro Cloud, ConnectWise, and others are formalizing AI partner programs that enroll MSPs to deliver vendor-defined services, while shifting operational complexity and accountability downstream. The episode highlights PAX8's Managed Intelligence initiative, aimed at helping small and midsize MSPs deliver AI services to SMB clients with minimal prior expertise. PAX8 cites its own research, which notes that 62% of SMBs view AI as essential for competitiveness and 74% plan to increase AI spending in the coming year. The economics of AI scaling are underscored by data on projected data center buildout costs—up to $15 trillion by 2030 and requiring $1.75 trillion annually just to maintain. OpenAI's public offering, with an $850 billion valuation and $180 billion in funding, is attributed to the need for capital that private markets can no longer supply, prompting vendors to leverage channel partners for both revenue generation and market validation. Supporting developments include expanded programs at the distribution and platform levels: a PAX8-Nocdoc partnership providing managed NOC/SOC services for smaller MSPs, Ingram Micro Cloud's collaboration with PartnerStack to formalize AI service delivery infrastructure, and ConnectWise's introduction of an AI-native platform for predictive and autonomous IT operations. Research from Omnia and the IBM Institute for Business Value indicates underutilization of vendor market development funds and widespread deployment of AI frameworks despite only 11% of tech leaders feeling prepared—demonstrating the gap between vendor offerings and operational readiness. The implications for MSPs are significant. By enrolling in these vendor-driven AI programs, providers take on delivery risk, contractual accountability, and potential liability for AI outcomes they did not design. The structural split is clear: MSPs can either create and govern their own AI methodologies—pricing accountability as a service—or become vehicles for vendor frameworks, absorbing complexity without full compensation or control. Practical recommendations include updating service agreements for AI-related risks, building internal governance around AI deployments, and not allowing vendor or community consensus to substitute for explicit accountability for outcomes. 00:00 Channel AI Shift  03:59 Enrollment, Not Enablement 06:55 Methodology vs. Liability 10:01 Why Do We Care?  Supported by:  Zero Networks  CometBackup 

The episode identifies a growing governance gap as a central structural issue for MSPs and IT service providers, driven by rapid AI adoption through subscription-based tools and platforms. Rather than being introduced as controlled, IT-led initiatives, AI services are entering organizations piecemeal—often through end users and business units—undermining established accountability and management practices. This dynamic is exemplified by ConnectWise's dismantling of its ASIO platform in favor of a new AI-native operating layer designed to unify PSA, RMM, security, and automation functions, and by clients independently layering on AI-powered tools without centralized oversight or cost control. A primary example of ungoverned risk involves unsustainable AI cost exposure. According to Axios and TechCrunch, an enterprise amassed around $500 million in a single month on Anthropic's Claude due to unlimited, unmonitored usage. Freshworks' survey of over 12,000 IT professionals quantifies the industry's operational friction, finding mid-market companies waste about 25% of AI budgets on complexity, for a total of $16 billion in annual waste. Despite 89% of respondents planning to increase AI spend, only 15% have actively integrated these tools into daily workflows—revealing widespread governance lag behind adoption. Supporting developments highlight the breadth and persistence of this governance deficit. Organizations such as the Linux Foundation have responded by forming the Tokenomics Foundation to standardize AI cost tracking. Meanwhile, AI tool adoption is occurring outside IT, leading to agent sprawl, unclear permissions, and cost scaling linked to agent behavior rather than headcount. Roll-up strategies in adjacent sectors—such as Thrive Holdings' $1 billion commitment to consolidate accounting firms under an AI operational platform—demonstrate capital's move toward operationally governed, AI-enabled service models, suggesting a parallel risk for IT providers. For MSPs and IT leaders, these trends underscore the urgency of operationalizing AI governance as a billable, contractual service rather than an informal or embedded support task. Risks include absorbing liability for unmanaged AI usage, exacerbated operational complexity, and relinquishing margin to platform or capital entrants. Practical steps involve conducting AI tool audits, inventorying agent access and spend, instituting usage controls, and reframing account segmentation around governance and liability exposure. MSPs who define, price, and contract for governance can mitigate inherited risk and avoid being displaced by vendors or capital-backed consolidators. 00:00 ConnectWise Rebuilds  03:59 Ungoverned Agents 06:06 Roll-Up Warning 09:38 Why Do We Care?    Supported by:  Moovila  ScalePad 

A central structural mechanism highlighted in this episode is the exposure and amplification of technical and organizational weaknesses by enterprise AI initiatives, particularly as organizations pursue rapid AI adoption without adequate investment in data and process fundamentals. The episode draws on findings from an MIT Media Lab report, which found that 95% of enterprise AI pilots had no measurable impact on profit and loss, despite $30–40 billion in investment. Michael Privat, representing the healthcare technology firm Availability, discusses the consequences for organizations that apply “thin” AI overlays on top of unaddressed legacy data infrastructure and processes. The most consequential data point centers on AI's amplifying effect. According to the MIT Media Lab report cited by Michael Privat, 74–75% of companies expect revenue growth from AI, but only 20% are realizing gains. The root cause identified is not AI itself, but foundational failures: organizations use pilots as procurement exercises rather than outcome-driven initiatives and neglect to address data consistency and process integrity. Pilot projects, in many cases, simply accelerate the visibility and scale of existing dysfunctions rather than creating new value. Further evidence is provided through discussion of operational methodologies and organizational approaches. Michael Privat details a shift from pre-AI process benchmarks, such as DORA metrics focused on predictability and velocity, toward new models that account for AI's speed and amplification risks. He points to increasing investments in engineering capacity—in particular, tripling headcount in India—while emphasizing that efficiency gains from AI only materialize where discipline, standardization, and solid engineering “plumbing” is already in place. Both the need for audit trails and rigorous governance, especially in regulated sectors like healthcare, are flagged as structural safety requirements rather than optional layers. Operationally, the implications for MSPs and IT leaders include the risk of exposing latent deficiencies when implementing AI-driven offerings, particularly when layering automation and analytics atop fragmented or inconsistent infrastructure. Key areas of impact are the need for robust governance frameworks—especially with agentic AI, where dynamic system behaviors require ongoing accountability and auditability—and the risk that AI investments made without process and data “spring cleaning” can actually accelerate failure modes. For IT service providers, the material risks are in unexamined process debt, tool misalignment, and the temptation to prioritize velocity over resilience, ultimately increasing operational and contractual exposure. Supported by:NerdioScalePad  

The current structural shift centers on the transfer of accountability for AI risk from vendors and regulators to managed service providers (MSPs). Vendors such as Anthropic and Microsoft are expanding their enterprise-focused AI channel programs and services tracks, while regulators pull back from enforcement, leaving MSPs as the de facto accountable parties for AI deployments. Reports and data indicate that vendor-driven channel expansion and regulatory laxity are converging to make service providers the liable layer in AI delivery. Anthropic is broadening its CLAUDE partner network from around 100 to several thousand partners, organized in tiers with outcome-based incentives and a dedicated services track targeting MSPs and system integrators. Microsoft, responding to low Copilot adoption rates (reported at 3.3% of eligible users), is allowing full removal of Copilot from systems. An IDC/Expereo survey of 800 companies found 70% are budgeting for AI, but investment is driven more by competitive anxiety than proven results. Additionally, a concentrated group—top 5% of users—accounts for the bulk of enterprise AI-related risk, according to a separate analysis. Supporting developments include the emergence of Lemhi, an early-stage platform aimed at enabling MSPs to package and sell AI transformation as a recurring service, and warnings from lawmakers about cuts to CISA that undermine federal cyber defense capacity. The episode also highlights a consistent theme: government agencies such as the White House and NIST are shifting toward voluntary measures and measurement frameworks, declining to create enforceable accountability standards for AI in production environments. For MSPs and IT leaders, these developments translate to increased contract and operational risk. Without renegotiated agreements specifying usage ceilings, approval workflows, and liability terms, providers may inherit unpredictable financial exposure and compliance gaps. The absence of effective governance requirements from both vendors and authorities places the operational burden on MSPs to define, monitor, and enforce safe use of AI, including recurring governance services such as data boundary enforcement and audit evidence. Failure to address these issues may result in MSPs acting as uninsured support for unmanaged AI deployments they cannot fully control or price. 00:00 MSP AI Play  04:24 AI's Accountability Gap 06:50 MSP Risk Transfer 09:49 Why Do We Care?  Supported by:  ScalePad Moovila 

The episode examines a structural shift in the MSP business model driven by the introduction of AI-linked consumption-based pricing layered on top of traditional per-seat fees. This emerging mechanism, typified by Microsoft's E7 license, adds variable AI consumption charges to otherwise predictable monthly service costs. Vendors are restructuring partner payment models, with Microsoft's move closely watched by others, signaling a wider potential for volatility in the recurring revenue foundations of MSPs, according to analysis from Jay McBain and recent channel data. The most consequential development is Microsoft's E7 pricing, which explicitly adds an AI consumption cost to the standard per-seat license. This move introduces variability at “machine speed,” in contrast to previous examples such as cloud storage, where consumption remains predominantly human-driven and thus more predictable. Analysts note that similar micro-consumption models—charging per conversation, process, or API call—are being adopted by hundreds of companies. Market data from Omnia and referenced industry research places the global IT spend at $6 trillion in 2026, with two-thirds delivered by channel partners and a rapid shift from fixed, subscription models toward micro-consumption billed at a granular, usage-based level. Supporting evidence includes the lack of sufficient vendor-provided controls for variable consumption, leaving MSPs exposed to unplanned cost spikes. While large enterprises are introducing robust FinOps practices and loading up cloud credits, smaller MSPs serving SMB customers are not prepared with similar governance structures. There is also vendor-led encouragement for AI adoption—such as persistent in-app assistants—that drive up consumption before adequate controls or cost-passing mechanisms are established. The sustainability of current pricing models is further questioned by the fact that providers like OpenAI and Anthropic are themselves subsidizing significant portions of token usage, distorting true costs throughout the value chain. For MSPs and IT service leaders, these developments mean greater exposure to unpredictable costs, potential margin pressures, and increased contractual risk tied to AI consumption. Operators cannot rely on vendors to provide spend caps or consumption governance today; failure to build internal controls or pass-through mechanisms may result in absorbing unpaid liabilities. Accountability for AI-driven actions, remediation, and configuration changes will rest with the MSP, elevating both operational complexity and liability exposure. The current environment requires building governance, audit trails, and spend management capabilities now, ahead of broader market adoption of AI consumption models. Supported by: CometBackup

Outcome-based managed security and attached vendor warranties are driving a new form of coverage-based vendor lock-in for MSPs and IT service providers. Vendors such as Intezer and SPECTRA are introducing performance guarantees, SLAs, and cyber resilience warranties that require MSPs to fully standardize on their architectures. This evolving model shifts accountability for enforcement and risk management from the individual MSP to the vendor's operating model, thereby altering the independent role of the MSP within client environments. A notable example is Intezer's Amplify Partner program, which asserts that its platform can process 100% of security alerts while escalating fewer than 2% for human review—claims the company frames as outcomes rather than product specifications. SPECTRA's use of certification-linked warranties, distributed via Ingram Micro, establishes channel-distributable assurance products with explicit conditions attached at every level. According to a Check Point report, while 77% of organizations report having adopted AI for cloud security, only 26% feel capable of enforcing those strategies, revealing a gap between security intent and operational ability. This structural shift is further illustrated by Merlin Cyber's FedRAMP managed service offering, Lumen's MDR enhancements targeting mid-market MSPs, and Trustlogix's addition of intent-based authorization controls. The FBI's announcement regarding Microsoft 365 OAuth token hijacking and recent vulnerabilities in widely used platforms like ConnectWise Automate underscore the real-world risks of automation platforms being targeted. These developments collectively point to growing operational complexity, rising compliance burdens, and the need for MSPs to separate their commitments from upstream vendor claims. For operators, the trend demands increased scrutiny of warranty terms, claim denial conditions, and SLA language before making any client-facing assurances. MSPs risk absorbing liability if they repeat vendor marketing claims without contractual clarity or operational control. Effective governance now requires independently produced, audit-ready evidence that documents compliance and enforcement separate from vendor portals. As assurance sales proliferate, the operational gap between acting as an underwriter versus a reseller will drive market differentiation, affecting both pricing structures and eligibility for vendor-backed coverage. 00:00 Channel-Ready Security 03:41 Policy vs. Reality 05:59 MFA Isn't Enough 09:12 Why Do We Care?    Supported by:  ScalePad Moovila   

A fundamental structural shift underway is the movement of AI from isolated features to operationalized, production-level workloads in MSP tooling and client environments. This transition is not primarily about the capabilities of individual AI models but about their integration into existing operational platforms and workflows. Companies such as PDQ, Senteon, Domotz, and Zoom are incorporating AI agents directly into management layers, endpoint automation, and workflow orchestration, thereby increasing both the scope and complexity of AI impact. The locus of value is shifting from features to workflow control and integration, creating new demands for governance, consumption monitoring, and exit strategies. The most consequential development referenced is the transition in AI billing and operational models from static user or seat licenses to variable, usage-based consumption. He cites TechCrunch's coverage of GitHub Copilot's move to token-based billing and Semafor's reporting of Uber's rapid exhaustion of its 2026 AI budget in four months due to unbounded consumption by generative tools. F5's State of Application Strategy report is referenced to confirm that multi-cloud and parallel model operations are now common, with significant instances of AI-related security incidents already reported. Secondary developments reinforce this structural realignment of risk and accountability. PDQ, for instance, is expanding multi-tenant management and integration capabilities, while Senteon enables endpoint hardening and drift control directly in Rewst's platform. Domotz's MCP server allows AI agents to operate across 40,000 networks globally, and Zoom is packaging AI context protocol features for workflow automation. Each of these changes is designed to increase operational efficiency, but also expand the surface area for unintended consequences, elevated operational complexity, and potential budget overruns. For MSPs and IT leaders, the operational implications center on governance, spend control, and clear accountability over AI-driven tools and workflows. The risk is that without adequate monitoring, policy setting, and contractual clarity—especially around data portability and exit costs—MSPs may face liability for unplanned consumption, misconfigured automation, or governance gaps. The evidence indicates the need to proactively audit AI integrations, set usage thresholds, instrument logging and budgeting controls, and renegotiate vendor contracts to ensure service boundaries and oversight mechanisms are in place before workflows become too deeply embedded. 00:00 MSP Stack Resets  04:09 AI Needs Governance 06:45 Govern AI or Pay 09:22 Why Do We Care?  Supported by:  Nerdio Zero Networks   

Forced arbitration clauses have become embedded as a dominant mechanism in technology vendor contracts, shifting legal risk and accountability away from large vendors and reducing recourse options for managed service providers (MSPs) and IT service firms. This structural change, present in agreements with RMM and PSA vendors as well as hyperscalers such as Microsoft, Amazon, and Google, establishes a private dispute resolution system that operates beyond the traditional court system and is typically non-negotiable for smaller partners. The shift is evidenced by data and case studies outlined by Brendan Ballou. According to supplied figures, while consumers win in 89% of small claims court cases, their success rate drops to between 20% and 30% in arbitration, and even less—sometimes as low as 0.2%—for certain arbitration providers. Arbitration clauses are enforced even in extreme cases, as illustrated by a notable instance involving Disney, in which a forced arbitration clause was applied following a consumer's prior account registration. Legal precedent as far back as the 2011 Supreme Court decision referenced by Brendan Ballou has broadened the Federal Arbitration Act well beyond its 1925 origins, further entrenching this system. Additional developments reference increased litigation in the 1980s, often cited as justification for expanding arbitration, though he attributes much of the legal caseload surge to government actions rather than consumer or employee lawsuits. The technology industry's broad adoption of arbitration, especially in contracts where MSPs have little or no room to negotiate, further cements these power imbalances. Alternatives such as mediation are discussed as potentially less risky, but their adoption remains limited. The operational implications for MSPs, IT service providers, and IT leaders include heightened contract risk and reduced leverage in vendor disputes. Arbitration clauses limit access to open legal processes, restrict discovery rights, and are prone to bias in favor of vendors with repeat arbitrator relationships. For MSPs reliant on large platforms and suppliers, this creates ongoing exposure and complicates risk management. Mitigating measures—such as leveraging peer coordination for "mass arbitration" or negotiating for post-dispute mediation rather than pre-dispute forced arbitration—require proactive planning but may remain unavailable in standard vendor agreements. Supported by:MoovilaHaloPSA  

The structural shift highlighted in this episode is a move from simple AI enablement to a managed service model centered on agent governance, enforcement, and workflow automation within IT environments. The episode identifies unmanaged AI agents as a source of escalating risk, citing vendors like Scalepad shifting from remote monitoring to SaaS and AI usage discovery, and referencing research and audits from SNCC and Verizon that identify tangible security flaws and unapproved AI activity within organizations. Managed service providers are increasingly positioned as the operational layer that defines and enforces governance over automation systems, rather than simply deploying AI tools. The primary evidence for this shift is found in audit findings and market reports. SNCC's audit of 4,000 AI agent skills showed over a third had at least one security flaw, while Verizon's data cited by The Register noted a fourfold increase in employees using unauthorized generative AI, with 28% of data loss prevention violations involving code or proprietary data submitted to AI platforms. Gartner, as reported by The Register, predicts 40% of organizations will demote or remove AI agents due to failed governance efforts—attributing the problem to all-or-nothing approaches that lead to operational and compliance failures. Secondary developments reinforce the move toward operationalized governance. Scalepad and Watchguard are bringing AI and SaaS governance capabilities to the MSP channel, with product releases focused on real-time discovery, policy enforcement, and automation control. Incidents like Anthropic's leak of its full source code for Claude Code, exposing permission and sandboxing details, illustrate how transparency in AI agent operations can also create attack vectors—emphasizing the need for robust operational controls and ongoing auditability. The market is shifting to sell "coherence"—packaging identity, permissions, and workflow automation—rather than just technological capability. Operationally, the consequences for MSPs include increased responsibility for defining and enforcing permission boundaries, approval rules, and evidence collection. Failure to address agent governance will expose providers to operational ambiguity, unpriced liability, and recurring support burdens. The guidance is to move beyond AI enablement projects and toward agent operation retainers that include clear workflows, permission maps, execution logs, and contractual clarity on responsibility and incident management. MSPs that cannot prove and control agent behavior risk inheriting the complexity and fallout from system failures or misuse. 00:00 Shadow AI Surge  05:01 Context Is Infrastructure 07:46 Agent Control Plane 11:16 Why Do We Care?  Supported by:  JumpCloud TimeZest