How SafeChange AI came to be
The idea didn't start on a whiteboard — it came out of a real ticket.
I recently assigned a field deletion request to one of my teammates: a simple-sounding task, "remove this custom field, it's no longer needed." What should have been a five-minute change turned into hours of manual detective work. Before the field could be safely deleted, they had to track down every place it was referenced — page layouts, list views, reports tucked away in folders no one had opened in months, flows, validation rules, Apex classes and triggers, and any lookup or master-detail relationships hanging off it. Miss even one, and the deletion either fails outright or, worse, silently breaks something downstream that nobody notices until a report stops running or a flow throws an error in production.
Watching that unfold, I felt the pain point firsthand: Salesforce gives you almost no guardrails here. There's no single view that says "here's everything that depends on this field, and here's what happens if you remove it." Admins and developers are left grepping through metadata by hand, cross-referencing report folders, and hoping they didn't miss a reference — and then, on top of that, the actual removal has to go out as a destructive change deployment, promoted carefully through sandboxes into higher environments, with real risk if anything was missed along the way.
That experience is what pushed me to build SafeChange AI. Instead of an admin manually hunting through every layout, report, flow, validation rule, and Apex reference, the tool does that dependency mapping automatically — then uses AI to generate the exact diffs needed to cleanly remove those references, shows them for human review before anything runs, and only proceeds with explicit approval. Full metadata backup and rollback are built in, so even the destructive deployment step — the part that used to keep me cautious about promoting these changes to higher environments — has a safety net.
It's a tool born directly out of watching a teammate struggle with something that should never have been this risky or this manual.
Log in or sign up for Devpost to join the conversation.