An implementation contractor made a change in a production CRM they weren’t authorized to make. It touched lead scoring, and on a morning when marketing hadn’t launched anything, it fired more than eight thousand bad MQL notifications at the sales team. The change itself took about four seconds. Finding it took most of a day, because the evidence was sitting in an audit log, and an audit log is a thing nobody opens until something is already on fire.
This talk is about closing that gap. Not by preventing the change, since controls that depend on a busy person remembering them tend to fail quietly, but by shortening the time between something happening and somebody knowing it mattered. The platform already records the events. What’s missing is triage. So the build is three boxes: the audit log you already have, a small reasoning layer that reads each change and rates it against a rubric I wrote, and a message that fires only for the risky ones, into a channel the team already sits in. Next to it runs a dumber, deterministic backstop that ignores causes entirely and just watches volume. The build notes below are the whole thing, flow by flow, including the gotchas that cost me real hours.