Four Assets, One Practice

This playbook is one of four pieces that work together. Here’s what each one is, and when to reach for it as you move from building belief → modeling the practice → running engagements → earning ecosystem recognition.

This playbook is built around two ideas that work together and, once you see them as a pair, reframe everything else that follows.

The first is that Copilot adoption — real, sustained, habitual adoption — is not a technology problem. It’s a coaching problem. Get a senior leader or a room of decision-makers in front of Copilot doing something genuinely useful for their own work, and they don’t need to be sold. They need to be shown. One hour. One live demonstration. One moment where they stop evaluating and start imagining. That’s the hook. It works every time — when it’s done right.

The second is that adoption is not the destination — it’s the starting line. Once your customers are using Copilot, building personal agents, and asking “can it connect to our CRM?” — that’s when the real practice begins. The ongoing work of keeping those agents accurate, governed, and generating value is what this playbook calls AgentOps. It’s the managed service layer that turns a one-time deployment into a permanent, compounding monthly revenue stream. Every agent you help a customer build creates an obligation to manage it. That obligation is your retainer. It never ends — because the agents never stop running.

Before you read the proof of concept below, be clear about what it is — and what it isn’t. We are not the partner in this story. We are not delivering AgentOps, managed services, or a retainer to this customer. We didn’t sell them a license or scope a professional services engagement. What you’re looking at is proof of something much simpler, and much more important to you: this conversation works.

It’s easy to walk into a customer and ask, “What’s your AI strategy?” (they’ve never heard anyone ask them that before) and then start throwing darts — trying to sell a pro-services engagement to build their first agent. That’s not where this journey starts. The journey starts with storytelling — a live hour, a senior leader doing real work, a moment where they stop evaluating and start imagining. That’s what moves a customer from wanting AI to requiring the capabilities this playbook describes. Once they require it, your work begins — installing and implementing the rest of this solution to keep their AI investment safe, secure, properly grounded, and running like a top. The POC below proves the conversation. The rest of the playbook is the operating manual for everything that happens after a customer says “yes.”

Our Cloud Engineering team designed and delivered a structured Copilot adoption workshop for a Fortune 100 enterprise client — 200+ senior leaders. The session was titled exactly as you see above. That title alone changed the dynamic in the room: before a single slide was shown, every leader was leaning in. What followed was the same three-step Show & Tell motion described later in this playbook, built around a deliberate coaching model and the agent maturity arc. The mandate from senior leadership was clear: this organization will be AI-fluent. What changed the outcome wasn’t the license rollout — it was bringing our team in at the leadership offsite, running hands-on sessions rather than pointing people to a portal, and naming the workshop in a way that made the value impossible to ignore. The numbers below are what happened in the first 90 days. Nothing modeled or estimated.

Introducing AgentOps — The Practice This Playbook Is Built On

A name for the thing the channel is building but hasn’t named yet.

The ideas in this playbook are grounded in research, channel data, and a straightforward question: If I were still running a partner practice today, what would I actually do?

That question matters because the data is clear but the path forward isn’t obvious. The AI managed services opportunity is real, it is accelerating faster than most of the channel is prepared for, and the partners capturing recurring revenue around it are not necessarily the ones with the biggest teams or the deepest technical bench. They are the ones who made an early decision about the kind of business they wanted to build — before the market made that decision for them.

I’ve spent three decades watching this industry from a lot of different angles — technical and leadership roles at SMB-focused Microsoft partners, practice manager for one of the largest national SIs in the Microsoft ecosystem, more than ten years as a Technical Strategist inside Microsoft’s partner organization helping partners retool their entire services model as perpetual licensing gave way to subscription, then building services practices with VMware’s top 50 partners, and now leading the cloud engineering team at TD SYNNEX. What that experience teaches you is pattern recognition: the window for being early in a new category is always shorter than it looks.

I want to be upfront about what this playbook is: it’s not a step-by-step guide based on a methodology I’ve field-tested with a hundred partners. Nobody has that yet — this space is too new. What it is, is a framework. A way of thinking about the AI managed services opportunity from someone who’s watched this exact transition happen before in different forms. Take what fits your practice. Leave what doesn’t resonate. The goal is simple: get you thinking differently about this next wave before the window closes — and give you enough of a head start that when your customers start asking the question, you already have an answer.

In my first thirty minutes inside a partner practice, I wouldn’t look at the pitch deck or the pricing sheet. I’d pull up the PSA and ask four questions. Not because I don’t already know the answers — because the owner needs to hear themselves say them out loud.

Partners licensed Copilot for customers who then barely used it. Renewal conversations turned uncomfortable. The product wasn’t the problem — the delivery model was.

Leading with the “plumbing” — permissions, Purview, MFA remediation — before the customer sees Copilot do something remarkable is the fastest way to stall a deal. Show the magic first. Then sell the protection.

These gaps are not unique to your practice — they’re the defining challenge of this moment across the channel.

Microsoft’s Adoption Workshop framework identifies four roles that determine whether a Copilot deployment succeeds or stalls:

Before your first training session, identify one person in each role. The partner who does this in Week 1 has a fundamentally different engagement than the one who just turns on licenses and hopes for adoption. AI support questions (prompt errors, agent misbehavior, permission questions) are inevitable — build a simple internal AI Support Runbook so your team handles them consistently. This is also billable scope if you formalize it.

The most common deal-killer in the SMB Copilot motion. The conversation goes like this:

Partners are provisioning Copilot the same way they provision Exchange Online — as a transaction. That’s the wrong mental model entirely.

Copilot is not an infrastructure project with a go-live date. It’s a practice-building engagement. Partners who treat it as the former will win the license and lose the renewal.

Even partners who run a pilot often sabotage it before it starts. Two failure patterns dominate:

This is the “set it and forget it” failure mode — and it’s rampant in the SMB channel.

What happened was predictable: employees didn’t know they had access, didn’t know how to use it, and no one gave them a reason to try. AI doesn’t transform an organization by being purchased. It transforms when people know how to apply it.

Walking into a customer meeting and leading with “AI is transforming the way businesses work” is not a pitch — it’s a TED Talk. SMB owners don’t buy categories. They buy solutions to problems they feel every day.

Even at $21/user/month, partners who can’t quantify ROI before the customer does their own math are walking into a losing conversation. That math needs to be pre-empted with a business case, not countered after objection.

Microsoft’s rapid expansion of the “Copilot” brand across dozens of SKUs created genuine marketplace confusion — and too many partners absorbed that confusion and transmitted it straight to customers. Customers can feel uncertainty in a sales conversation. When the partner doesn’t fully understand what they’re selling, trust evaporates.

Partners who can’t confidently navigate these distinctions are creating the exact hesitation that kills deals.

This playbook isn’t a perspective. It’s a remedy guide for problems the industry has named.

An MSP audit listed eight reasons SMB rollouts fail. Microsoft’s own field guidance corroborates them. Every one is a service line you can sell — and every one is already mapped to a motion in the pages you’re holding.

The most successful partners have abandoned slide decks entirely when selling Copilot. They run a three-step “Show and Tell” motion that makes the value undeniable — and it closes faster than any deck ever will. The sequence is everything: show first, prove second, protect third.

These aren’t rehearsed presentations. They’re real scenarios you can pull out cold in any conversation — on a phone, in a lobby, at a QBR. Each one demonstrates something the customer wishes they were doing today.

Once Demo C lands, a natural question surfaces: “Can it pull from our CRM?” or “Can we connect it to ServiceNow?” That question is the moment Step 2 begins — and for you as a partner, it’s the most important moment in the entire sales call.

Every dollar in the Revenue Runway falls into one of three buckets. Name them once, here, and every later section — Early Work, Outcome-Based, AgentOps tiers, the bank scenario — slots into a known home. Project / SOW, Managed AgentOps, and Outcome-Based are the only three revenue shapes you need to hold in your head.

Most of your early work with a new Copilot customer is pro-bono or at-cost — workshops, discovery sessions, prompt coaching, agent clinics — done to earn trust and uncover the first paid project. This block is the inventory of what that free work actually looks like, how it converts into paid work, and how it eventually rolls into the hybrid retainer that becomes your Tier 1 AgentCare baseline.

A Copilot deployment that’s been handed to a customer and left alone leaks money three ways: oversharing incidents, inactive licenses (Microsoft’s own data shows 40–60% of seats go dark within 90 days), and user frustration that kills the renewal conversation. The work that fixes all three is mostly not initially billable — it’s clinics, office hours, playbook drops, oversharing scans — and every hour of it is an audition for the paid project that comes next. Below is the full menu of that early work, grouped by what it produces: enablement, governance, adoption, and discovery.

Flat per-user pricing collapses under expanded service menus. Pure hours-bank retainers kill margin and bury the partner in scope fights. The hybrid is what actually sells:

300-seat SMB math: $3,300 base + $1,200 bundle + average 2 new hires/mo = ~$4,500/mo. Blended, that’s still $15/user — but the customer can see what it buys.

Contrast with SOW fatigue — every AI vendor promises, none measure. Outcome-based turns a cost line into an investment the CFO can actually defend.

The partner’s fee is tied to the champion’s goal too. That alignment is what kills the usual scope-creep fight and makes the champion the partner’s loudest advocate internally.

The partner brought the baseline and the measurement plan. IT gets to focus on tenant hygiene, security, and data access — not on building a business case they were never staffed to build.

• Customer can name one number that matters and is measurable today.
• Baseline data is accessible before you quote.
• Executive sponsor cares about the KPI personally and can clear friction.
• Pre-agreed MRR conversion path the customer will sign pre-sprint.

• No baseline and no time to establish one.
• KPI depends on variables you don’t control (seasonality, another vendor).
• Sponsor is a director or below — no authority to protect the KPI.
• It’s ongoing managed services — those are retainer, not outcome-priced.

AgentOps is the ongoing managed service practice of keeping your customers’ AI agents accurate, secure, and generating measurable value — month after month, without a defined end date.

Traditional MSP revenue is tied to seats and devices — static infrastructure that doesn’t grow on its own. AgentOps changes that equation. Every Copilot Studio agent your team builds and deploys creates a new, permanent managed service obligation: the agent must be tuned as usage patterns evolve, its grounding data audited as SharePoint sources change, its token consumption monitored for cost efficiency, and its security posture reviewed as Microsoft ships model and connector updates. That work never ends because the agent never stops running. That dependency is your retainer.

The AgentOps model structures this work into three monetizable components — a per-user governance base, a per-agent management fee (AgentCare), and an Azure consumption markup (Credit Wrap) — that stack together into a recurring revenue engine. A partner who has built and handed over six agents across three customers is already running an AgentOps practice. The question is whether that work is named, scoped, and priced — or whether it’s being given away as part of a flat managed services agreement that was written before agents existed.

The Stacked Default model invoices all four components as separate line items. The Flat-Tier Alternative bundles them into a single per-user rate — same economics, simpler invoice, lower visible margin.

Four dials. Every tier is a different mix of these four lines — and nothing else. Read them before the model cards below and the tier math on the next page lands in a single pass.

What it is: The full three-component model — Per-User Base + AgentCare + Credit Wrap — invoiced as separate line items. This is the recommended starting point for any partner building a durable AgentOps practice. It maximizes margin, creates explicit value visibility for the customer, and scales naturally as agent count grows: every new agent deployment adds revenue automatically without a contract renegotiation.

Use this when: your customer understands the value of each service layer, you have at least one deployed agent under management, and your team can track per-agent time. The transparent invoice is also a QBR asset — it makes value concrete and visible every month.

What it is: A single all-inclusive per-user rate that bundles the Per-User Base, AgentCare, and Credit Wrap into one invoice line. The customer sees one number; the complexity is absorbed internally. This is how most traditional MSPs already price — it removes friction from the sales conversation and makes renewals frictionless.

Use this when: you're earlier in your practice build and want to keep billing simple, when your customer base is cost-sensitive and detailed line items create friction, or when you're managing fewer than 3 agents per customer and the math still works at the bundled rate. The tradeoff is margin compression as agent count grows — at 6+ agents per customer, the Stacked model outperforms meaningfully.

To model flat-tier pricing: set agents/customer = 0 in the CPB Workbook Tab 2. The four-stage structure is identical.

What it is: AgentCare priced as a standalone offering — no per-user base, no Credit Wrap — just a monthly managed service fee per deployed agent. This is not the same as the AgentCare component within the Stacked model. As a standalone, it's designed for a specific scenario: a customer whose tenant is already under MSP management by someone else (or by their own IT team), but who has deployed Copilot Studio agents that need professional oversight.

Use this when: you inherit an agent someone else built, when a customer wants to separate AI services from their existing MSP contract, or when you're entering a new account through an agent build and want a recurring revenue bridge while you work toward full managed services. It's also the right model for partners who are pure Copilot Studio builders — strong on build, not yet running full managed services.

Critical rule: Agent builds are always scoped and billed separately as project engagements ($3,500–$8,000+ per agent). The AgentCare retainer covers ongoing management of deployed agents — never new construction. This boundary must be explicit in your SOW and renewal language.

What it is: A standalone or add-on offering where you purchase pooled Azure compute (Copilot Studio message credits, Azure OpenAI tokens, Power Automate flow runs) at CSP cost and bill the customer at a 25–35% markup. You're not just reselling credits — you're managing the consumption pool, optimizing credit allocation across agents, monitoring for unexpected spikes, and ensuring no agent runs out of budget mid-month. That management overhead justifies the markup.

Use this when: any customer is running Copilot Studio agents at meaningful volume. Credit Wrap is always additive — it stacks on top of either the Stacked Default or Flat-Tier model. The only question is whether you surface it as a visible line item (Stacked) or absorb it into your flat rate (Flat-Tier). At Tier 2 the dollar amounts are modest; at Tier 3 with 6+ agents on Azure AI Foundry, it becomes a meaningful margin layer.

GM: ~85% — essentially pure margin once you've set up the pooling mechanism. Small on its own — but across a 50-customer base at Tier 3, Credit Wrap adds $75K–$90K annually with no incremental labor. Never leave it on the table.

You’re likely ready to claim if you meet all four of these:

Why channel economics — not model quality — is the right frame for the Copilot conversation. And why that frame actually wins.

Handle the “we already use ChatGPT” objection with a business model argument — no FUD, no bashing, no comparison of benchmark scores.

Don’t argue model quality. Argue data gravity, governance inheritance, and channel economics.

Anthropic’s Claude Partner Network launched March 2026 ($100M). OpenAI’s SMB Services Program named its first partner in Nov 2025. Rosters are short. Local SMB partners can credibly self-position as the regional AI services partner today.

CRN XChange Security 2025 calls unsanctioned AI “the biggest invisible threat.” MSSP Alert (Apr 2026) names AI governance as the 2026 security-services differentiator. Governance spans all AI, not just Copilot.

Accenture took 30,000 Anthropic practitioners. PwC is OpenAI’s named reseller. Both are chasing enterprise. The sub-200-seat customer is open ground for the partner who shows up with a governed multi-AI story.

The tool you enter your numbers into. Tabs 1–5 build a defensible P&L and stress-test practice design. Tabs 6–7 handle engagement mechanics and sprint scoping. Tabs 8–9 are live project trackers you run during delivery.

The manual behind the model. Explains the why of every gate and phase on Tabs 8–9, maps real Microsoft customer stories to each checkpoint, and cites the Microsoft guidance and MSP field research the frameworks are built on.

Enter your current customer base, seats, revenue streams, headcount, and overhead. A live P&L builds as you type — gross profit, EBITDA, and six metrics benchmarked against Service Leadership and Worklyn Partners data.

The core practice-design tool. Enter target customer counts and pricing per tier — the practice P&L builds automatically. Models Stacked Default and flat-tier pricing, AgentCare, Credit Wrap, Agent 365, project fees, and AI Specialist hire ROI.

Side-by-side P&L — today vs. a fully designed Copilot practice. Every line item flows from Tabs 1–2 automatically. Includes a 3-year revenue projection and benchmark comparison. The tab you share with leadership.

A print-ready one-page summary that pulls every key metric from Tabs 1–3 automatically. Business snapshot, P&L comparison, benchmark metrics, and a 90-day action plan pre-populated with the highest-leverage moves.

Bear / Base / Bull modeling across five variables: close rate, Tier 1→2 progression, AI Specialist utilization, labor inflation, and logo churn. Outputs recalculate as you adjust inputs. Hire-decision framework built in.

The four AI/LLM non-negotiables checklist, RACI deal-prep reference, and a live kicker math calculator. Open this tab before scoping any outcome-based engagement — before you quote a base fee or discuss a kicker.

The full Tier 1 service menu (16 items across Enablement, Governance, Adoption, and Discovery) plus three outcome sprint templates: Activation Sprint (T1), Workflow Sprint (T2), and QBIC (T3). Reference during scoping conversations.

Phase-gated checklist for a Tier 1 Copilot Activation Sprint — 50+ tasks from Pre-Engagement through the five gates and into ongoing Tier 1 MRR. One person owns it. Every item gets a status. Run it as a live tracker, not a reference.

Five-phase worklist for any Copilot Studio agent build — Discovery Workshop through Design, Build & Test, Deploy & Train, and Phase 5 AgentOps. Covers simple agents ($3,500–$8,000) and complex builds ($12,000–$28,000). Includes the AgentCare / Credit Wrap reference table.

The evidence base. Summarizes the Microsoft Copilot adoption guidance, Partner Center playbooks, and MSP field research that shaped every phase and gate in Tabs 8–9. Cite this when a partner asks "why this framework and not something else."

Gate-by-gate walkthrough of Tab 8. What each gate is checking for, what "ready to advance" actually looks like, the common failure modes, and the soft signals that tell you to pause a deployment before Gate N+1.

Phase-by-phase walkthrough of Tab 9. Discovery through AgentOps, where simple and complex builds diverge, typical time budgets, and what Phase 5 recurring work actually buys the customer — the answer to "what am I paying AgentCare for?"

Published Microsoft customer stories mapped to specific Tab 8 and Tab 9 line items, plus the full citation list behind every external claim in the CPB — Microsoft guidance, SLI, Worklyn, and MSP field research. Narrative weight for the checklists, and primary sources for the skeptics.

Open the Workbook. Fill Tab 1 with your baseline, design on Tab 2, stress-test on Tab 5, and walk Tab 3 into leadership.

The Ops Guide sits on the shelf during this phase — it isn't needed yet.

Send the Ops Guide first. Context before tool. Once they understand why the gates and phases exist, Tabs 8 and 9 become legible instead of intimidating.

Then hand over the Workbook and point them to Tabs 8–9.

Keep the Workbook open on Tab 8 or Tab 9 as your tracker. When a gate decision stalls, pop the Ops Guide open to the matching section.

Tool drives the day-to-day; guide resolves the judgment calls.

Industry benchmarks often cite ~8–12% EBITDA for well-run SMB Microsoft partners. That figure is real — but it represents a steady-state operating model, not a transition year.

The P&L examples in this playbook intentionally land lower, at approximately 5–6% EBITDA, to reflect a more realistic moment in a partner’s journey:

• A second seller has recently been added
• A new Copilot practice is being built and productized
• Specialized skills are being hired and enabled
• Platform costs and delivery friction are real and present
• The business is prioritizing sustainability over short-term margin maximization

Reaching benchmark EBITDA does not require a different customer base, higher license margins, or aggressive pricing. It comes from operational maturity:

• Utilization normalization as delivery becomes repeatable
• SG&A leverage as revenue grows faster than overhead
• Practice maturity shifting Copilot work from projects to retainers
• Reduced delivery friction and less pre-sales burden

These changes occur naturally over 12–24 months once a practice is established — particularly for packaged, recurring services.

“TD SYNNEX has been a true extension of our team as we expand our Microsoft practice by simplifying all engagements, from onboarding and enablement to selling and scaling solutions for our end customers. The Frontier Distributor designation is meaningful validation from Microsoft of TD SYNNEX’s capabilities.”

No partner is expected to have a fully built AI managed services practice on day one. ServiceSolv exists precisely for the gap between “I want to sell this” and “I can deliver this.”

You close the engagement. ServiceSolv handles the technical delivery. You keep the customer relationship and the recurring revenue.

A food company, a law firm, a health agency, and a creative shop. Four different industries. One story.

None of them waited for a perfect data environment. None ran a six-month readiness assessment. They started with a real problem, showed their team what Copilot could do, and let adoption grow from there. The partners winning in the SMB AI market are the ones helping customers take that first step — and then building the services practice around what comes next. That first step is always available. The question is whether you take it with them.

Introduces the Microsoft Agent Pre-Purchase Plan (P3) — access to 32 Microsoft services through a single pool of funds to simplify procurement across complex AI builds.

Unified program covering incentives, benefits, and co-sell support for software development partners. Currently in preview with full availability expected in 2026.

New specialization for partners implementing sovereign-cloud strategies across Azure, Microsoft 365, and Security — a growing requirement in regulated markets.

New designation for partners meeting strict customer satisfaction and service quality thresholds — a differentiator for partners building managed AI service practices.