I wrote the forecast change note to `output/drivers-note.md`. The script's figures are in `output/drivers.json`. The script reconciled: the six driver deltas sum to the EBITDA change exactly.

**Headline:** Current EBITDA is $303K against $452K in Prior, a change of ($149K), or (32.9%).

Three of the six drivers changed:

| Driver | Prior | Current | Months changed | EBITDA delta |
| --- | --- | --- | --- | --- |
| Active customers | 46 | 44 | 12 | ($133K) |
| Gross margin | 26.2% | 26.6% | 12 | $39K |
| Headcount | 23.00 | 23.75 | 9 | ($54K) |

Revenue per customer, Cost per head and Other opex did not change. Their deltas are $0.

Active customers carries the EBITDA move. It cut revenue by ($509K). The higher gross margin offset part of that, and the added headcount made the fall worse.

The data shows how much each driver moved EBITDA, but not why it moved. The note's Review section asks each driver's owner which documented assumption supports the change. It asks in particular why headcount rose while customers fell.

The input was `drivers_fy2026.csv`, 144 rows, sha256 `704c929028e8`.