AI Practice vs. AI Program: The Distinction That Makes MSPs Profitable
This article has been written by Tim Hickle
AI Practice vs. AI Program: The Distinction That Makes MSPs Profitable
The AI Practice is the commercial offering an MSP sells — the packaged, repeatable service the MSP delivers across its client book. The AI Program is the portfolio of AI work, owners, outcomes, and policies that the client runs internally. The MSP's AI Practice supports the client's AI Program. Lemhi's vocabulary deliberately separates the two because mixing them is the most common cause of scope creep, margin erosion, and accountability confusion in MSP AI work.
How the AI Practice vs. AI Program Distinction Protects MSP Margin
For MSPs, the Practice/Program distinction is a survival tool. Without it, every client conversation drifts into questions like "can you also help us with this internal initiative" — and the MSP either says yes and loses margin or says no and damages the relationship. With it, the boundary is clear: the MSP delivers the Practice, the client owns the Program, and the VCAIO is the connective tissue.
What the Practice owns:
- The commercial structure. Pricing, scope, SLAs, escalation paths.
- The named role. The VCAIO who carries the relationship.
- The recurring artifacts. Monthly AI Council, QBR AI Segment, AI Maturity Score, AUP, Continuous Scanner output, training rollout.
- The standardized playbook. Phase 0–3 onboarding, ongoing cadence, exit criteria.
What the Program owns:
- The strategic intent. Why the client is investing in AI, what outcomes they want, what risks they will not accept.
- The internal owners. The executive sponsor, the department heads, the AI Champions inside the client.
- The decisions. What the Council decides goes into the Program — but the Program is what executes against those decisions.
- The accountability. When AI helps or hurts the business, the Program is where the consequences land.
The VCAIO is accountable to the MSP for delivering the Practice and accountable to the client for advancing the Program. Both lines of accountability are visible in the Monthly AI Council and the QBR AI Segment.
Where MSPs lose money: when they accept Program-side work (custom agent builds, departmental AI projects, internal change-management initiatives) inside the Practice retainer without re-scoping. The fix is not refusing the work — it is expanding the retainer or selling a separate project alongside the Practice.
What SMB Leaders Should Know About AI Practice vs. AI Program Ownership
For SMB executives, the distinction is the answer to a question your team is probably asking quietly: *who owns AI here, us or the MSP?* The answer is: you own the Program, the MSP runs the Practice that supports it. Both roles are real.
What this means concretely:
- You own the strategic outcomes. AI is your investment, your risk, your competitive advantage. Your executive sponsor signs the budget; your department heads commit owners; your employees do the work.
- The MSP owns the operating discipline. The VCAIO shows up every month. The Council convenes. The QBR reports ROI. The AUP gets revised. The Continuous Scanner runs. The training ships.
- The handshake is the Monthly AI Council. That is where the Practice and the Program meet — where the MSP's standardized motion produces decisions the client's leadership team commits to.
If your AI relationship feels confused — if you can't tell whether you or the MSP "owns" a particular decision — the fix is to articulate the boundary in the next Council. Most ambiguity disappears once Practice and Program are named separately.
How Lemhi Enforces the AI Practice and Program Boundary in MSP Delivery
Lemhi enforces the Practice/Program distinction inside the platform — which keeps MSPs profitable and clients aligned.
- Standardized Practice artifacts. The Council agenda, the QBR AI Segment slides, the Maturity Score rubric, the AUP template — all standardized so every Practice ships the same way.
- Engagement charter. Phase 0 produces a written charter that names the boundary between Practice and Program. Owners on both sides are documented at kickoff.
- VCAIO authority levels. Operational, tactical, and strategic decisions are pre-delegated or escalated based on the charter — so the VCAIO never has to negotiate authority mid-conversation.
- Scope-creep guardrails. When Program-side work emerges (custom agent builds, large training initiatives, departmental projects), the platform flags it as outside Practice scope and prompts a re-scope conversation.
- Compass Module for the Practice/Program edge case. At very small clients, the Practice/Program distinction collapses into the owner-operator. The Compass Module is designed for that reality.
The distinction is not pedantic. It is the operating discipline that makes the difference between an MSP that scales AI revenue and one that bleeds margin on every engagement.
Build the AI service line your clients are already asking for.
Every week, we send practical guidance for MSPs turning AI from scattered conversations into a repeatable managed service. No hype. No generic AI takes. Just the operating playbook.
For MSP leaders building the next recurring revenue category.
AI Practice vs. AI Program FAQ
Practical answers for MSPs defining the boundary between the commercial AI service they sell and the internal AI operating system their clients run.
What's the difference between an AI Practice and an AI Program?
The Practice is what the MSP sells: the packaged commercial offering. The Program is what the client runs internally: the portfolio of AI work, owners, and outcomes. The Practice supports the Program; the Program executes the strategy.
Who runs the AI Practice?
The MSP runs the AI Practice. The Practice is the MSP's commercial offering: TaaS, the VCAIO role, the Monthly AI Council, the QBR AI Segment, all standardized into a repeatable service.
Who runs the AI Program?
The client runs the AI Program. The Program is the internal portfolio of AI work, owners, outcomes, and policies. The executive sponsor leads it, and department heads own pieces of it.
How does the VCAIO connect the two?
The VCAIO is accountable to the MSP for delivering the Practice and accountable to the client for advancing the Program. Both lines run through the Monthly AI Council and the QBR AI Segment.
Why does the distinction matter?
Without the distinction, MSPs accept Program-side work, such as custom builds and departmental projects, inside the Practice retainer and lose margin. Clients drift into expecting the MSP to own the strategy, which is not what the Practice is for.
What happens when Program-side work emerges inside an engagement?
When Program-side work emerges, the MSP should re-scope the retainer to include it or sell a separate project alongside the Practice. The platform flags out-of-scope work for the VCAIO to address.
Is the AI Practice the same as TaaS?
TaaS is the specific managed-service shape Lemhi defines for the AI Practice. Practice is the broader category term. TaaS is the canonical Lemhi instantiation.
Does this distinction apply to small clients?
At very small clients, such as owner-operator firms, the Practice and Program effectively collapse into the same person. The Compass Module is designed for that reality.
How does the AI Practice differ from an AI consulting engagement?
Consulting bills for the readiness work and then disengages. The Practice runs every month. The Practice is the recurring shape of the work.
Where do training and enablement live: Practice or Program?
Training delivery lives in the Practice. The VCAIO runs Copilot 101, 102, 201, and 202. Training adoption lives in the Program. The client's department heads ensure their teams complete it.
Where does the AUP live: Practice or Program?
The AUP is drafted by the Practice and adopted by the Program. The VCAIO writes it, the executive sponsor signs it, and the Council reviews it monthly.
How is the boundary documented?
The boundary is documented in the engagement charter produced in Phase 0. Both Practice and Program owners are named, authority levels are documented, and the boundary is reviewed at the start of every annual retainer renewal.
How does the QBR AI Segment treat the Practice/Program distinction?
The QBR reports on Practice deliverables, meaning what the MSP shipped, and Program outcomes, meaning what the client achieved. Both are visible to leadership.
Does the distinction matter for AI risk and incident response?
Yes. The Practice handles AI-specific governance, including AUP, shadow AI, and the Continuous Scanner. The Program handles incident decisions, regulatory response, and customer communication. The VCAIO coordinates with the client's legal and HR contacts.
How does this distinction relate to the vCIO and vCISO motions?
The vCIO and vCISO use similar Practice/Program logic for IT and security. The VCAIO motion mirrors the same operating discipline for AI.
Where can I learn more?
Lemhi publishes the engagement charter template, VCAIO authority levels, and Practice/Program boundary guidance as part of the TaaS framework. Sign up for Field Notes to get the weekly playbook.
Scale AI transformation across your entire book of business.
Most MSPs are stuck selling AI as scattered projects, Copilot rollouts, or one-off workshops. The MAGIC Framework gives you a repeatable path to package, sell, deliver, and manage AI Transformation as a Service across your client base.
For MSPs ready to turn AI demand into a managed service motion.
