CRM: divisions as accounts

Four accounts
one picture

BOS is a CRM. The accounts are not customers. They are divisions, and each one carries a health score, an owner, its active initiatives and the timestamp of its last real update. A division that stops updating stops looking healthy, which is the point.

The accounts

Each card carries a status mix: one bar per active initiative, coloured by status. The bar chart is CSS only, there is no charting library anywhere on this site.

What each field means

Field	What it holds	Why David reads it
Health score	0 to 100, moving with real updates, slips and unresolved dependencies.	Which division needs attention before it asks for any.
Owner	One named person per division, accountable for its update reaching the graph.	It removes the question of who to ping when something slips.
Active initiatives	Every initiative currently claimed as live by the division.	The distance between a plan and a division's own list.
Last real update	The timestamp of the last change that came from a live feed, not a written summary.	A stale timestamp is itself a signal, and the honest one.