June 17, 2026

The Monthly AI Council: A 60-Minute Format for SMB Leadership Decisions

This article has been written by Tim Hickle

The Monthly AI Council is a 60-minute standing leadership meeting facilitated by the VCAIO and chaired by the client's executive sponsor. It is the room where AI decisions land. The Council is a working session — not a status review. Six segments, fixed timing, named owners, decisions documented. Every TaaS engagement above ~50 employees runs a full Council; smaller engagements run the Compass Module instead. 


Why the Monthly AI Council Anchors the MSP AI Practice 

For MSPs, the Council is the part of the TaaS motion that separates a practice from a project. A project ends. A Council is a calendar event that recurs forever — which is exactly what makes the retainer defensible. 


The 60-minute format is six segments. 


  1. Welcome (5 minutes). Executive sponsor opens. Agenda confirmed. Any urgent escalations surfaced. 
  2. Measurement Review (15 minutes). Three layers of measurement reviewed: training completion, AI observability (active users, sessions, agent invocations), and survey signal (employee sentiment, friction reports, shadow AI signals). 
  3. Use Case Spotlight (15 minutes). Two to three use cases reviewed — one from the active pipeline, one new candidate, one retrospective. The VCAIO presents the recommendation; the Council decides go/no-go. 
  4. Roadmap & Decisions (15 minutes). AI Maturity Score movement. Roadmap milestones tracked. AUP updates. Governance changes. Decisions documented with owners. 
  5. Q&A (5 minutes). Open floor for the sponsor and department heads. 
  6. Actions (5 minutes). Named owners and dates for everything decided. Documented and circulated within 24 hours. 

What's not in the Council: status reports, technical deep dives, vendor demos, and individual employee reviews. Those happen elsewhere. The Council exists to make decisions and assign owners. 


The reason the format matters is that AI Council failure is usually a format failure. When the Council drifts into status review, leadership disengages. When it drifts into technical detail, decisions slip. When it drifts into vendor demos, the sponsor stops attending. The 60-minute discipline is what keeps the Council alive at month 14. 


How the Monthly AI Council Turns AI Strategy into SMB Leadership Decisions 

For SMB leadership, the Council is the structural mechanism that turns AI from a topic into a discipline. The single best predictor of AI adoption success, according to Prosci's 25-year change-management benchmarking study, is active and visible executive sponsorship. BCG found employee AI positivity rises from 15% to 55% with active leadership support. None of those statistics describe a one-time kickoff meeting. They describe a recurring rhythm. 


For your executive team, the Council is a 60-minute monthly commitment. In exchange you get: 


  • A single room where every AI decision lands — instead of decisions happening in IT tickets, email threads, and hallway conversations. 
  • A consistent record of what was decided, by whom, with which evidence. Removes the "I thought we agreed to" pattern. 
  • A working forum where department heads commit owners — which is what turns Council decisions into Monday-morning action. 
  • A predictable cadence so AI stays on the leadership agenda even when other priorities are loud. 

The Council should be on your calendar at TaaS kickoff. If it isn't, your AI program does not have a decision forum — and the absence of a forum is the most common reason AI programs stall after Phase 3. 


How Lemhi Automates Monthly AI Council Prep for VCAIOs 

Lemhi makes the Council a sellable, repeatable artifact — not a custom motion the MSP reinvents at every client. 


  • Standardized 60-minute agenda template. The six-segment format is built into the platform. The VCAIO walks in with the agenda pre-populated. 
  • Automated Measurement Review pulls. Training reports, observability dashboards, and survey signal are curated by the platform before the meeting. The VCAIO reviews and selects what to surface; they don't assemble from scratch. 
  • Use case pipeline scoring. The platform pre-scores use cases on fit, effort, and impact. The VCAIO selects which two or three to bring to the Council each month. 
  • Decisions log integration. Decisions are captured in the platform and roll into the QBR AI Segment and the AI Maturity Score updates. 
  • Compass Module alternative. For clients too small for a full Council, the 30-minute Compass format is built in. Same VCAIO, lighter cadence, same decision discipline. 
  • 

The Council works because the platform makes the prep tractable. Without automation, the VCAIO drowns in prep work and the Council quality degrades. With Lemhi, the VCAIO can carry 12–18 Council clients sustainably. 


Field Notes

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.

AI Transformation as a Service VCAIO playbooks MSP-ready sales motions
Subscribe to Field Notes

For MSP leaders building the next recurring revenue category.

Frequently Asked Questions

Monthly AI Council FAQ

Practical answers for MSPs running the Monthly AI Council as the decision forum for AI adoption, governance, use cases, measurement, and executive sponsorship.

What is the Monthly AI Council?

The Monthly AI Council is a 60-minute standing leadership meeting facilitated by the VCAIO and chaired by the client's executive sponsor. It is the room where AI decisions get made.

How long is the Council?

The Council is 60 minutes, monthly. It has six segments: Welcome, Measurement Review, Use Case Spotlight, Roadmap & Decisions, Q&A, and Actions.

Who should be in the Council?

The Council should include the executive sponsor as chair, department heads, the IT lead, AI Champions, and the VCAIO as facilitator. It is typically 6–10 people.

What's the difference between the Council and a QBR?

The Council is monthly, operational, and decision-making. The QBR is quarterly, strategic, and review-oriented. The QBR AI Segment is a 10–15 minute block inside the existing QBR.

What's not on the Council agenda?

Status reports, technical deep dives, vendor demos, and individual employee reviews are not on the Council agenda. Those happen elsewhere. The Council is for decisions.

How does the VCAIO prepare for the Council?

The VCAIO prepares using Lemhi platform automation. Observability pulls, training reports, AI Maturity Score updates, and use case pre-scoring are curated; the VCAIO reviews and selects what to surface.

What if the client is too small for a Council?

Use the Compass Module. A 30-minute working session with the owner or executive sponsor replaces the multi-stakeholder Council. Same VCAIO, lighter operating rhythm.

What happens if the executive sponsor doesn't show up?

The motion breaks. Active executive sponsorship is the single strongest predictor of adoption success. The VCAIO escalates and may recommend pausing the engagement.

How are Council decisions documented?

Council decisions are documented in the platform's decisions log. Each decision has an owner, a date, and a follow-up cadence. Decisions roll into the QBR AI Segment.

What's reviewed in the Measurement Review segment?

The Measurement Review segment covers three layers: training completion, AI observability such as active users, sessions, and agent invocations, and survey signal. The Council reviews all three to triangulate adoption reality.

How does the Use Case Spotlight work?

Two to three use cases are reviewed monthly. The VCAIO presents the recommendation; the Council decides go or no-go and names owners.

Does the Council have authority to commit budget?

The Council can approve roadmap changes inside the existing retainer. New spend outside the retainer escalates to the executive sponsor.

How does the Council relate to the AUP?

The AUP is reviewed at every Council. New tool categories, shadow AI findings, and employee questions feed the next AUP revision.

What is the "Transformation Paradox"?

The Transformation Paradox is the pattern that AI moves faster than organizational decision cycles. The Council exists to compress the decision cycle to monthly, fast enough to keep up.

Can the same Council cover multiple AI tools?

Yes. The Council reviews AI activity across all approved tools and surfaces shadow AI usage of unapproved tools.

What's the right ratio of Council clients per VCAIO?

The right ratio is 12–18 clients running full Councils, 25–35 on the Compass Module, or 18–24 for mixed books. Tooling automation is what makes those numbers achievable.

Where can I learn more?

Lemhi publishes the Council agenda, Compass Module format, and decisions-log structure as part of the TaaS practice. Sign up for Field Notes to get the weekly playbook.

The MAGIC Framework

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.

Map the opportunity Align the business Govern the rollout Implement the roadmap Continuously prove value
See the MAGIC Framework

For MSPs ready to turn AI demand into a managed service motion.