The Architecture of Trust

Finance teaches how organizations determine what is worth investing in. Hospitality teaches something finance textbooks leave out: that the best experiences come from genuinely caring about the person in front of you, understanding what they need before they say it. Psychology bridges the two — explaining the real drivers of commitment and trust beneath the surface of every business case.

My plan was behavioral finance. What I couldn't have predicted was that "Solution Engineer" would turn out to be exactly that curriculum in practice.

The Hartford's Finance Leadership Development Program was structured to produce people who understood insurance as a living operating system — not one function, but the whole thing. I rotated across IT Financial Analysis, Small Commercial Financial Modeling, and Personal Lines Strategy & Competitive Intelligence, going genuinely deep in each while running structured coursework across underwriting, claims, risk, actuarial, and operations in parallel.

That combination of breadth, depth, and cross-functional exposure is uncommon at the start of a career — and it's directly why I can speak the language of an insurance executive today, not just a technology buyer.

In my Strategy & Competitive Intelligence rotation, I was studying which companies were winning in financial services — and the answer was almost always driven by technology. That insight is what put Salesforce on my radar. I then deliberately built my way onto The Hartford's internal Salesforce team as a Business Consultant — gaining the customer's seat: configuring solutions, managing release cycles, and leading offshore development. Being accountable for whether the technology actually worked for the people using it is still the most grounding thing I bring to every customer conversation.

At PwC I led a large-scale Agency Management System implementation for a major insurance carrier — advising leadership on Salesforce ecosystem strategy and roadmap at the intersection of implementation and management consulting. This gave me the SI's seat: accountable for architecture decisions, managing stakeholder expectations, and living with the gap between what was promised and what was possible.

It also showed me clearly that the strategic, visionary questions consistently lived on the Salesforce side of the table. So I decided to cross it.

When I joined Salesforce, I brought all three perspectives: the customer who has lived inside a large-scale implementation, the SI accountable for delivery, and now the SE helping customers build the vision. That triangulated view is what allows me to meet customers where they actually are.

What I learned in this chapter wasn't in any training: that in an account this complex, the SE's most important output is not the demo. It is trust — built through presence, follow-through, and the willingness to be wrong in front of the customer and come back with a better answer.

Promotion to Principal was a signal to go bigger — not just on the account, but across the organization. The shift wasn't about doing more. It was about doing things that multiplied: architectures that opened entire verticals, assets every SE after me could stand on, AI wins that seeded federation-wide pipeline.

Total ACV contribution: $44M+. Presidents Club 2026.

The past year has been defined by work that reaches further than any single account — a Dreamforce stage, a Tiger Team building a practice from nothing, industry CABs where customer feedback shaped product roadmaps. Not because I was chasing scale for its own sake, but because I kept saying yes to the hardest, newest, most uncertain things — and each one compounded into something bigger than the last.

Cambridge, MIT, every Agentforce badge from Innovator to Legend — a real belief that the moment you stop learning in this industry is the moment you start falling behind.