
Architecting Amid Regulations in Finance
Key topics Does regulation shape cloud architecture from the start, or get applied after the fact? What percentage of enterprise cloud spend goes to waste? How does a hybrid estate complicate zero trust and entitlement management? Where is AI actually useful inside a regulated architecture team? What happens when you stop letting an AI assistant simply agree with you? Regulation comes first. Seb's team only builds on cloud services that have already cleared a rigorous compliance review, then designs around what's approved rather than retrofitting compliance onto a finished architecture. That same discipline covers data and AI sovereignty: jurisdiction, data center location, and backup zones are core to the design, not overhead bolted on afterward. On cost: roughly 30% of all cloud spend is waste, according to Seb, mostly from over-provisioning rather than unused services. His team runs an annual OKR specifically to find and cut that waste. On AI: Seb treats it as a second opinion, not a replacement for his team. He uses it to pressure-test architecture documents, prompt for edge cases, and even diagnose a broken home CCTV system from raw log files. Emily and Seb also compare notes on what changes when you stop letting an AI assistant simply agree with you, after Emily's own experiment asking Claude to drop the sycophancy and get blunt. The throughline: in a heavily regulated environment, guardrails and good architecture patterns move faster than ad hoc decisions, and the same discipline that keeps regulators satisfied is what makes room for AI experimentation without losing control.




