I left Verizon to spend seven years as Executive Director of O'Dwyer Retreat Center. Every technology decision ultimately came through me. We had no CIO, no IT department, and no procurement function. I was accountable for whether a purchase advanced the mission or consumed money and staff capacity we could not spare. That chapter did not replace my enterprise sales background. It handed me the buyer's responsibility for the financial, operational, and technical consequences of change.
Large organizations distribute technology decisions across specialists. At O'Dwyer, the financial, operational, and technical questions all converged on one desk. A system that failed, a contract that confused, an implementation that fell short, or a vendor that stopped responding became my organization's problem to absorb. With no internal IT team and limited capacity, a clear owner and reliable support were not service preferences. They were buying criteria.
A $50,000 security decision inside a $1.5 million operating budget, and two very different ways of approaching it.
He arrived with an impressive live demonstration of a platform well outside our budget. He never asked how the current system was performing, what we were considering, or what our team could realistically support.
No further opportunityHe started with how we operated, then recommended an option with fewer features because it was the one his team could support reliably. He took on the work we could not staff: remote management and a commitment to be on the property within 24 hours when remote support was not enough.
Won the workA feature request is often shorthand for an operating constraint.
I raised $250,000 to expand what the organization could offer, and the visible structure was the smallest part of the work.
Zoning, environmental review, legal and architectural planning, safety, insurance, staff training, and contractor timing all had to align before anyone could use it. The lower bids handed those responsibilities back to an organization with no capacity to absorb them. The contractor I chose answered each one with a concrete plan rather than a caveat.
I chose the highest-priced proposal because it was the only one that addressed the full execution risk.
The seller needed to understand the organization's real operating constraint before recommending a solution.
Price mattered, but so did implementation capacity, support, adoption, risk, and the effect on the people using the solution.
The strongest partner made the organization more capable without leaving it to absorb responsibilities it could not reasonably support.
That experience sharpened my Outcome Orchestration method: understanding what each stakeholder needs a change to accomplish and shaping a solution that works across those priorities.
I'm focused on senior enterprise sales roles in AI and enterprise technology where understanding the buyer's operating reality matters. If that perspective is useful to what you are building, a direct note is the fastest way to reach me.
A product that creates meaningful new capacity or capability for clients.
A sales organization where experienced sellers are expected to make the whole team better.
A company that listens to the people closest to the client.