The vCIO Loses a Week Each Quarter to QBR Decks. Claude Cowork Hands Back the Packet Overnight.

You tried this in 2024. You exported a ticket summary out of ConnectWise, pasted it into a chat box, and asked for a quarterly business review. What came back was three paragraphs of adjectives about "strong performance" and a bullet list you would have been embarrassed to put in front of a client. You closed the tab and went back to building the deck yourself. That reaction was correct at the time. It is no longer correct, and the reason is worth ten minutes of your attention.

Two products changed the shape of this job. Claude Cowork landed on 12 January 2026 and expanded to web and mobile in July. ChatGPT Work landed on 9 July 2026 running on GPT-5.6. Both do the same fundamentally different thing: you hand over a goal, they connect to your files and applications, break the work into steps themselves, run for hours without you, and hand back a finished artifact. Not an answer — a deck, a filled spreadsheet, a document set. Both were built for people who do not write code, which in your shop means your vCIO and your account manager.

Count what a QBR packet really costs you

A proper quarterly business review packet for one managed services client is not a deck. It is an assembly job across six or seven systems:

• Ticket volume, type mix and response times out of ConnectWise PSA or Autotask, trended against the prior three quarters.
• Patch compliance and reboot-pending counts out of Datto RMM, NinjaOne or Kaseya.
• Backup success and last successful restore test out of Veeam or the BCDR appliance.
• Microsoft Secure Score, multi-factor coverage and risky sign-ins out of the 365 admin center.
• Warranty expiration and age profile for every workstation and server on the agreement.
• Network gear approaching end of support out of Auvik or your own inventory.
• A budget worksheet for the next two quarters, and the roadmap items you promised last time.

Call it four to six hours of vCIO time per client, per quarter. Twelve clients on a quarterly cadence and eighteen on semiannual is somewhere north of 300 hours a year of your most expensive non-owner's time, spent copying numbers between screens. And when the quarter gets busy, the QBRs slip — which is exactly when a client starts wondering what they pay you for.

Give it the goal, not the fourteen steps

The change worth understanding: you no longer write out the fourteen steps of building a QBR packet. You state the finished thing you want, point it at the systems, and it works out the steps and comes back with the packet.

The instruction looks more like a note to a competent new hire than anything technical: "Build the Q3 packet for these twelve clients. Use the standing template. Pull tickets and agreements from the PSA, patching and backup results from the RMM, licensing from the Pax8 invoice. Flag every device out of warranty before 31 March. Compare billed seats to actual seats and list the differences. Leave the recommendation slide blank."

That last sentence is the important one, and we will come back to it.

flowchart TB
  A["vCIO states the goal: Q3 packet, 12 clients"] --> B["Pull tickets and agreement terms from the PSA"]
  A --> C["Pull patch and backup results from the RMM"]
  A --> D["Pull the Pax8 invoice and compare to billed seats"]
  B --> E["Draft deck, one-page summary, refresh budget sheet"]
  C --> E
  D --> E
  E --> F["vCIO rewrites the recommendation slide"]
  F --> G["Account manager sends it and books the meeting"]

Tuesday night, twelve packets

Your vCIO writes the goal at 5:40 on a Tuesday and goes home. Overnight it works client by client. Wednesday morning there are twelve folders. Each contains an eighteen-slide deck on your template, a one-page executive summary written in the plain language your template uses, and a spreadsheet with three tabs: asset refresh budget, warranty expirations by month, and license variance.

She spends about forty minutes per client instead of five hours. That forty minutes is spent on the thing that actually earns the fee: reading the numbers, deciding what to recommend, and rewriting the recommendation slide in her own words. Nine of the twelve packets are correct as produced. Three have something wrong — a client whose agreement has an unusual after-hours term, a site that was sold in May and still shows in the asset list, a backup job that reports success but covers a server that was decommissioned. She fixes those, and she notes that all three are documentation problems in her own systems, not errors in the packet.

The money is on the license variance tab

The hours are the obvious saving. The unglamorous one is bigger. Seats drift. A client hires four people in August, your technicians provision four Business Premium licenses in the 365 tenant that same week, and nobody updates the ConnectWise agreement. You pay the distributor for four licenses every month from then on and you bill for zero of them. Nobody catches it, because catching it means reconciling a distributor invoice against thirty agreements by hand every month, and nobody has ever had time to do that in a normal month.

Two things about that table. First, the 3% drift figure is an illustration — run your own comparison for one month before you believe any number, and be prepared for it to be higher than 3% if you have grown fast. Second, the recovered licensing is real money in a way the recovered hours are not: your vCIO does not become 206 hours cheaper, she becomes 206 hours more available for the roadmap work that clients actually buy.

What you have to change about how you assign work

This is where most owners stall, and it has nothing to do with software. Your shop assigns work as task lists, because that is how you manage technicians. "Pull the ticket report, build the trend chart, update slides 4 through 9." Handing over a goal requires you to have written down, somewhere, what "done" looks like. Three things have to exist first:

• A real template. Not "the deck Jim uses." An actual standing packet definition with fixed sections, so that "use the standing template" means something.
• A definition of correct. Which number is authoritative when the PSA and the RMM disagree on device count? Today that lives in your vCIO's head and she resolves it silently. Write it down.
• A review step with a name on it. Somebody signs off on every packet before it leaves the building, and that somebody is not the person who wrote the goal in a hurry at 5:40 p.m.

The shops that get value out of this are the ones that treat it as a documentation exercise first. The shops that fail are the ones that expect it to invent standards they never set.

What must stay in the vCIO's mouth

Leave the recommendation slide blank on purpose. The packet can tell a client that 34 workstations pass their warranty date in the first quarter of next year. It cannot tell them that the right move is to replace 20 now and defer 14, because that decision depends on the client's fiscal year, the conversation you had with their CFO in June about a building lease, and your read on whether their operations manager is about to retire. That is judgment, it is what the client pays a vCIO for, and it should never be produced overnight by anything.

Also keep a human on anything that goes to a client under a compliance obligation you attest to — CMMC Level 2, HIPAA, PCI — where the packet becomes evidence. And keep a human on any slide that says a number went the wrong way. Bad news delivered in a template is a client-relationship problem; bad news delivered by your vCIO with a plan attached is a renewal.

Frequently asked questions

Do I need to connect it to my PSA directly?

Not to start, and I would not. Begin with exports — the reports you already run — dropped into a folder. You will learn what "done" looks like on your own packets before you give anything read access to live client systems, and the exports version works well enough to prove the value.

What about client data leaving my control?

Take this seriously. Your agreements and your cyber insurance application both make statements about where client data goes. Get in writing what is retained and where processing happens, put it in your written policies and your own vendor list, and tell your clients before the first packet goes out rather than after. If any of your clients touch EU users, the transparency obligations with a 2 August 2026 compliance date are a conversation for your attorney.

How long does a run actually take?

Long enough that you start it and leave. That is the point — it is not a chat where you sit and wait. Twelve client packets overnight is a realistic expectation; the first one will take longer because you will be correcting the template.

Could I use this for anything besides QBRs?

The same shape fits any recurring assembly job in a managed service provider: the monthly agreement true-up, the annual cyber insurance questionnaire renewal, the client-facing incident summary after a security event, and the new-client onboarding packet. Pick the one that recurs on a calendar and produces a document, because those are the ones where "done" is easiest to define.

A note on the phones

None of this touches the part of your week that actually interrupts you, which is the phone. CallSphere builds AI voice and chat agents that answer business phone lines and web chat, take the details, book the appointment, and capture the lead 24/7 — useful in a shop where the vCIO doing the QBR work is also the person the front desk transfers a prospect to at 3:15 on a Thursday.