The MSP roll-up was fully built. The demo just never had a client to show it

Every mechanism behind CMDash's MSP/vCISO edition already worked: the cross-client roll-up, the "N of M included" partner console, the managed-workspace volume bands, the white-labelled board pack. None of it was missing. What was missing was a single row of data — nothing outside the create-client-workspace API had ever actually written a client workspace, so the roll-up screen rendered empty in every demo and in front of every prospect. The MSP marketing page described the capability in prose, because there was no screenshot to take of a feature that had nothing to show.

This is the same failure shape as most of the bugs worth writing about: not a crash, not an error in a log, just an honestly-rendered empty state that looked exactly like "nothing here yet" instead of "the pipe upstream was never connected." A trial-emails timer that fires a year too late and a roll-up screen with zero clients both pass every test that only checks "did this throw."

What changed

The demo seed now carries a full vCISO practice with eight managed clients — five inside the included band, three in overage, so the volume-based billing story is demonstrable rather than hypothetical. The roll-up screen now leads the MSP walkthrough on /for/msps, and it appears in the multi-client user guide with a real screenshot instead of a description of what the empty state used to look like.

The lesson, generalised

A feature is not "done" when every mechanism behind it has a test. It is done when something — anything — writes the row that makes the mechanism visible. The full record is in CHANGELOG.md under 7.1.7; if you run an MSP practice and have never seen this screen with real clients in it, that screenshot is now on the persona page linked above.