CLIENT · LATE-STAGE SAAS · ~520 PEOPLE · REDACTED
A field rename in the CRM would have broken the board's pipeline report. Held.
REPORTS BROKEN · 12mo
0
CHANGES HELD
64
DRIFTS CAUGHT
64
ESCALATIONS
2
// 01
WHAT WE WALKED INTO
WHAT WE WALKED INTO
Twenty-three downstream reports depended on a CRM that anybody with admin access could rename a field on. The reports were brittle in a way nobody had time to fix.
Quarter-end always brought a "the pipeline report is empty" Slack message. Nobody knew which change had broken which report. Everybody had a hunch.
// 02
THE WATCH · 22 MONTHS
THE WATCH · 22 MONTHS
MONTH 1
Mapped
Every CRM field used by every downstream report. 23 reports, 412 dependencies.
MONTH 4
Held
First field rename held until reviewed. Renamed in a way the report could follow. Admin's reaction: 'oh.'
MONTH 22
Verified
64 changes held, 64 changes shipped. Zero broken reports in the last 12 months.
// 03
WHAT IT MEANS
WHAT IT MEANS
“I haven't gotten a 'pipeline report is empty' message in a year. I miss it the way you miss a toothache.”
— VP RevOps · LATE-STAGE SAAS · ~520 PEOPLE · NAME REDACTED
Your numbers are probably also three different numbers.
We can tell you which one is the real one. Usually within a week.
Start the watch →We can tell you which one is the real one. Usually within a week.