
Brian J. Weiss: TechStack, Tenant Control, and Redefining PSA Ownership for MSPs
Business of Tech: Daily MSP News & IT Services AnalysisShow Notes
The episode highlights a structural shift toward MSPs considering custom-built operational core systems on enterprise platforms, rather than relying purely on traditional packaged PSA (Professional Services Automation) vendors. This approach is illustrated by ITECH Solutions’ decision to migrate from a legacy PSA system—augmented by multiple third-party tools—to a platform built on Microsoft Dynamics, leveraging TechStack as a custom layer for MSP functionality. A key development discussed is ITECH Solutions’ experience with the limitations of existing PSAs. According to Brian J. Weiss, the lack of mature APIs and aging software architectures led to workflow inefficiencies and cumbersome tool proliferation. By selecting Microsoft Dynamics and partnering with TechStack, ITECH Solutions aimed to build a purpose-built, role-based system without maintaining a full in-house development team. Weiss described this as a hybrid model: Dynamics provides the core enterprise environment, TechStack develops the MSP-focused PSA features, and ITECH Solutions manages its own customizations, all within their own Microsoft tenant. Supporting details reinforce the complexity and risk profile of this approach. Customization introduces three operational layers: Microsoft’s base (with ongoing feature releases), TechStack’s PSA-specific additions, and further MSP-specific custom work, all requiring maintenance and version management. The cost structure relies on Microsoft partner licensing and as-yet-undetermined pricing for TechStack’s development and support. While automation and workflow adherence are key selling points, Weiss noted that operational maturity—including process standardization and thorough documentation—is a prerequisite for success with this model; smaller MSPs or those with incomplete processes may face difficulties replicating the approach. For MSPs and IT leaders, the implications revolve around vendor dependency, operational complexity, and governance oversight. Relying on multiple layers (Microsoft, TechStack, and in-house customization) adds resilience against single-vendor lock-in but shifts accountability for support, updates, and platform stability. Contractual risk increases as MSPs must track not just vendor but also tenant-layer modifications and integrations. While this structure offers customization and data control, it requires MSPs to have strong internal processes and governance frameworks to avoid operational drift or unintended consequences from layered system changes.
Supported by: ScalePad TimeZest NinjaOne On-Demand Webinar: https://go.businessof.tech/p/ninjaone-pod
About Business of Tech: The daily MSP news and analysis podcast for managed service providers and IT services leaders. Host Dave Sobel covers AI for MSPs, MSP pricing and profitability, MSP M&A and private equity, vendor partner programs, MSP cybersecurity and liability, and MSP operations — and answers the question every story raises: Why do we care? Produced by MSP Radio. 💼 All Our Sponsors MSP Radio is supported by our partners:
ABC Solutions · CometBackup · Firetail · Guardz · HaloPSA · LogMeIn · Mailprotector · Pax8 · Rythmz · ScalePad · TimeZest · Transit AI
Supporting the IT services community through insights, analysis, and transparency.
🚀 Join Business of Tech Plus Get exclusive access to investigative reports, vendor analysis, leadership briefings, and more. 👉 https://businessof.tech/plus
🎧 Subscribe to the Business of Tech Want the show on your favorite podcast app or prefer the written versions of each story? 📲 https://www.businessof.tech/subscribe
📰 Story Links & Sources Looking for the links from today’s stories? Every episode script — with full source links — is posted at: 🌐 https://www.businessof.tech
🎙 Want to Be a Guest? Pitch your story or appear on Business of Tech: Daily MSP News & IT Services Analysis 💬 https://www.podmatch.com/hostdetailpreview/businessoftech
🔗 Follow Business of Tech
LinkedIn: https://www.linkedi
More from Business of Tech: Daily MSP News & IT Services Analysis
This episode outlines a structural shift whereby accountability for AI results is increasingly being transferred from customer leadership to Managed Service Providers (MSPs) and IT service providers. This transfer is being accelerated by internal pressure on client organizations to report AI success while reliable performance metrics remain elusive. Evidence from Futurum Group’s “The New AI Workforce” report and actions by vendors such as Dell and Accenture demonstrate how responsibility and reporting for AI are consolidating under technical teams, often with insufficient checks and unclear governance boundaries. Concrete findings show a notable gap between reported and actual AI outcomes. Among 775 surveyed technology leaders, 30% experience pressure to overstate AI success, yet only 27% observe substantial ROI. Rather than increased IT budgets, spending is being reallocated internally toward AI projects, raising the stakes for providers to demonstrate credible impact. Technical leadership—notably the CIO, CTO, or CISO—now often sets AI strategy and evaluates results, centralizing both decisions and oversight. Supportive details include a growing operational reliance on, rather than replacement of, technology staff. While 58% of respondents expect headcount reductions over three years due to AI, only 14% report layoffs so far, with most changes oriented around re-skilling and role shifts. Only 4% rate their teams as fully prepared for AI-first environments. Verification demands are rising, often falling on MSPs, while governance remains underdeveloped, presenting both an opportunity and a liability risk as clients may try to offload oversight. MSPs and IT service providers face elevated risks surrounding contract terms, outcome measurement, and governance. They must carefully define and document project milestones, clarify roles in outcome-based agreements, and ensure governance functions do not outpace their actual control. Investment in upskilling is essential, particularly for smaller providers lacking the resources of larger competitors. Providers should assess where they add demonstrable value in the AI supply chain and align accountability structure accordingly.
The episode highlights a structural shift in vulnerability management, where accelerated discovery of software flaws—driven by AI—has outpaced the ability to remediate. Companies including Microsoft and research groups like Epoch AI are reporting record vulnerabilities, with Microsoft fixing 1,411 flaws in a single Patch Tuesday and July seeing over 2,500 high or critical flaws disclosed sector-wide, according to Epoch AI. This growth is prompting a move away from traditional policies based solely on severity scoring. Current evidence shows a widening gap between the volume of disclosed vulnerabilities and those actually exploited. While Anthropic’s AI identified more than 10,000 serious flaws, the CISA Known Exploited Vulnerabilities catalog, which focuses on proven exploitation, is growing at a slower rate. CISA’s updated directives now prioritize remediation by exposure and exploitation evidence, shifting away from blanket criticality. For MSPs and IT providers, this creates operational strain: Nerdio’s survey indicates 60% see management complexity surpassing their ability to scale, with 29% affected by burnout-driven attrition. Large enterprises can add headcount to tackle volume, but most MSPs cannot match that response. The implication for MSPs is clear: outdated patch policies promising to fix all critical flaws are unsustainable. Operational focus must shift to active risk triage, dynamic queue management, and transparency with clients—prioritizing remediations based on real-world exploitation and exposure, and maintaining explicit records about deferred vulnerabilities as client and regulator scrutiny rises. 00:00 Patch Tuesday Breaks a Record 03:52 Severity Stopped Sorting the Work 06:50 When the Queue Outgrows the Team 10:24 Why Do We Care?
The episode details an ongoing shift toward upstream platform control and infrastructure dependence in the managed IT services sector. Centralized platforms, such as Pax8’s 8OS and governance initiatives from the Channel Trade Association (GTIA), increasingly control AI, access rights, consent, and management tooling, concentrating privileged identities and access points within vendor environments rather than those of MSPs or clients. A key case highlighting the risk is the ConnectWise Cloud Backup incident, where one credential enabled access to 173 Microsoft 365 tenants in two hours. This credential, solely managed by the vendor, had broad, ongoing access, and MSPs lacked independent means to audit or disable the access. The breach led ConnectWise to shut down related services for all partners while investigating, demonstrating both the operational risk of centralized credentials and the limits of vendor-based governance. Supporting developments reinforce this centralization. Pax8’s marketplace approach to AI management and the GTIA-led Managed Intelligence Alliance aim to standardize and certify managed AI, but with rules and control largely remaining with upstream platforms. Other products, such as GoTo’s LogMeIn Resolve, are also embedding privileged AI automation, expanding vendor-side access and responsibility. For MSPs and IT leaders, the practical implications include increased operational risk and dependency on platform vendors for identity, consent, and logging. Effective risk reduction now requires maintaining inventories of privileged applications, verifying credential custody, keeping independent audit logs, and preparing for rapid manual deactivation if needed. Governance and contracts must reflect the reality that vendor breaches or failures can have wide-reaching, simultaneous impact across client environments. 00:00 Managed AI Moves Upstream 04:30 One Vendor Key, 173 Tenants 07:28 AI Agents Multiply the Keys 10:39 Why Do We Care?
A persistent governance gap is emerging in organizational AI implementations, especially among clients of MSPs. Despite the integration of AI in regulated sectors like wealth management and construction, most MSPs are neither engaged at project inception nor maintain oversight through formal policies or audit-ready documentation. Specific examples include deployments using technologies such as Claude, where neither roles for approving AI configurations nor processes for tracking data access are uniformly established. A key development is the insufficiency of existing evidence and controls around AI use. Fewer than 20% of current client projects have written AI policies, and among 53 surveyed family offices, 80% are using AI without documented policy guidance. Insurers have started to introduce generative AI exclusions (e.g., CG4047), shifting the liability and evidentiary burden onto clients and their MSPs. Auditors now require dated, traceable documentation demonstrating that controls align with enacted policy, especially when AI accesses sensitive platforms like Microsoft 365. Related discussions further illustrate the depth of this issue. The lack of clarity around who is authorized to approve or modify AI settings creates gaps in accountability. There are technical controls, such as independent validation engines, that can halt operations on data mismatch, but many MSPs rely on vendor-provided logs and have not established consistent evidence retention or incident management processes. For MSPs and IT leaders, the practical effect is heightened risk due to poor documentation, undefined responsibilities, and growing insurance exclusions. Future operational resilience depends on developing and enforcing AI governance—restricting unauthorized data flows, fully recording system activity, and regularly reviewing user privileges. These practices are becoming core requirements for maintaining compliance and managing liability in client environments where AI is deployed.
AI service pricing for managed IT services is increasingly unstable due to manufacturers’ ability to change subscription deliverables and costs unilaterally. OpenAI’s reduction of its $200 plan benefits and the shifting terms in leading AI offerings, noted by SemiAnalysis and Omdia’s analysts, exemplify how MSPs risk absorbing margin losses when vendor pricing changes are passed downstream with little notice or warning. SemiAnalysis found that leading AI subscription services are often subsidized, using more infrastructure than they generate in direct revenue, with Gartner projecting a $5 trillion gap between required AI infrastructure investment and realistic revenue through 2030. The sustainability of current AI pricing is questionable, and over 80% of smaller AI cloud providers are expected to lose independence in this period. These developments elevate margin and continuity risks throughout the services ecosystem. Market data from Omdia indicates only 20% of North American partners have the maturity to productively monetize AI services, while most AI work remains experimental or internally focused. Some MSPs have bundled AI into flat fees without contract triggers for cost changes, exacerbating the risk. Techaisle’s data shows buyers’ top frustration is “bill shock” as token-based AI pricing remains volatile and unpredictable. For MSPs and IT leaders, the implication is growing vendor dependency and contract risk. Flat-fee AI bundles expose service providers to sudden margin erosion if manufacturers alter price or service conditions. Practical risk mitigation includes writing re-opener clauses and escalation triggers into contracts, charging separately for data readiness, and avoiding open-ended pilots. The benchmark should focus on contractual flexibility and risk allocation, not initial price alone. 00:00 AI Services Grow, Prices Don’t Settle 03:38 Why Today’s AI Price Is Borrowed 06:43 Price It Now, Write It to Reopen 10:00 Why Do We Care? Supported by: Guardz ScalePad NinjaOne On-Demand Webinar: https://go.businessof.tech/p/ninjaone-pod