Performance Narrative: Oct - Apr

The defining work of this half was platform displacement: moving customers off fragmented third-party stacks and onto a Microsoft security platform they could actually operate. The biggest of those was an eight-figure-TCV E5 step-up at a regional health system, where the play reframed the deal around operational efficiency, cost overlap, and security outcomes we could prove. Two more followed the same pattern. A mid six-figure Defender Experts for Hunting expansion at a multi-state health system, anchored in their SOC transformation roadmap. And a seven-figure Entra ID Governance opportunity in a regulated environment, where I led stakeholder alignment to displace a legacy IAM tool with a lifecycle management, Verified ID, and workflow-integrated identity vision.

Underneath the deals was a Perform motion that earned the right to those conversations: landing the E5 step-up, executing competitive CIR/DART wins across several large health systems, and delivering an on-the-fly ESA during a renewal pressure cycle. The Transform side compounded it. My flagship contribution this half was the ATS Security Enablement series. It started as an idea about driving a sales campaign toward ACR and grew into an executive-sponsored program that helps account teams turn Microsoft's security and AI story into practical customer conversations, especially around agentic AI, identity, governance, and risk. The sessions are forums for translating complex platform capabilities into language a customer can act on. The motivation is simple: make security an accelerator for AI adoption instead of a blocker. Alongside it I authored and delivered the AI Red Teaming workshop that two regional user groups picked up and ran with their own communities.

The "how" is where I want this to land. None of these were solo wins. The E5 step-up took months of weekly co-selling with the account team, and the DEX expansion only worked because I got out of the way and let the customer's SOC leader carry the narrative back to their own executives. I leaned hard on the work of others, too. I built on the Sentinel data lake strategy coming out of product and field leadership to support a competitive takeout that doubled a customer's ingestion commitment, and I partnered on a bi-weekly cadence with GBBs, CxEs, and CSU to translate frontier-customer incubation signals into field execution. I also joined the HLS Momentum Program this half to develop deeper sales acumen and grow my network with AEs, SSPs, and executives, because the long-term version of this role is bigger than the deals I close myself; it is shaping the motions others close. The pattern I am most proud of: every deal above has at least one named teammate whose contribution is load-bearing, and every enablement asset I shipped is something another SE can run without me in the room.

My biggest setback this year was a motivation one. I was assigned a 24-account quota, but I stepped in to help across roughly 60 once I picked up coverage for three additional sellers. I was pivotal on several of the largest closes of the year. The verbal credit was there. The comp credit was not, because I was running an overlay motion. That is a hard rhythm to keep up. Showing up at the same intensity for deals you are not getting paid on is a real motivation test, and there were stretches this half where I felt it. I also understand that org coverage changes, things stay flexible, and the help was the right call every time. I grew, because sixty accounts gives you sixty at-bats. I got exposure to deal shapes, customer archetypes, and SE peers I would not have seen on a 24-account year.

My H2 goal is to graduate from "the SE who closes the deal" to "the SE who shapes the motion others close." That means three concrete behavior shifts. First, write earlier and write publicly. The one-pager habit from the setback above becomes the default operating mode - every customer engagement starts with a written position, and the strongest of those become Tech Community posts or GitHub assets that other teams can run. Second, multiply through enablement, not heroics. The AI Red Teaming workshop and the security enablement series both proved that a single well-shaped asset reaches more customers than a calendar full of 1:1 calls; H2 is about making more of those, with co-authors, and instrumenting which ones actually move pipeline.