"Vibe coding" jokes land in engineering chats. We've seen finance teams ship the same vibe inside spreadsheets—and pay for it later.
What broke
Forecast models that doubled as only documentation. Macros nobody could unwind. Imports from CRM that silently changed definitions between quarters.
What we coached instead
Treat models like /repos: named owners, versioning, immutable month closes, reconciliation notes in-line—not in email.
RULE: Before a new KPI ships to the board, it needs:
- Definition (formula + source tables)
- Owner + change log entry
Pairing engineers with finance analysts
Small scripts for imports and checks, not unmaintained “wizard” sheets. Alerts when thresholds drift—not colour-only conditional formatting nobody screenshots.
Where this breaks down
When quarter pressure skips documentation. When tools block git-style workflows outright.
Our read
Finance needs engineering hygiene inside their stack. Velocity without traceability becomes risk faster than you'd think—investors ask questions quietly at first.