The announcement always ends the same way: dashboard live, old system switched off, everyone smiling for the photo. What almost never gets told is what happens for the next two quarters, the parallel processes that aren't supposed to still exist, the numbers nobody quite trusts yet, the same question landing from three different departments about whether the new system is actually right or just wrong in a way nobody's caught. This keynote goes looking for that part of the story. A controller who's actually lived through a system replatform on what it took to get the team trusting the numbers again, and the one decision they'd make differently if they had it to do over. Key takeaways: - What to actually budget for after go-live, since it's rarely in the original project timeline - How to rebuild a team's trust in numbers once the system has already given them a reason to doubt it - The one call they'd reverse if they had the decision to make again