I left Verizon to serve 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. A poor decision would consume scarce dollars and staff attention that could have advanced the mission elsewhere.
That seven-year chapter did not take me away from enterprise selling. It put me inside the decision. I was no longer asking someone else to absorb the financial, operational, and technical consequences of change. I was responsible for them.
Large organizations distribute technology decisions across specialists. At O'Dwyer, the same financial, operational, and technical questions converged on one desk. When a system failed, I was accountable for getting it fixed. When a vendor stopped responding, I was the one following up after hours.
Before a vendor quoted me, I explained our operating reality: we had no internal IT team and limited capacity to absorb another system. If something went wrong, I needed a clear owner, a prompt response, and a realistic resolution timeline. That was not an added service preference. It was part of the buying criteria.
For an organization our size, that was a consequential investment. We evaluated the options carefully and selected equipment from a leading camera manufacturer. The manufacturer's representative and the integrator approached the same opportunity in completely different ways.
He knew a grant had funded part of our original installation and roughly when another application window would open. He arrived with an impressive live demonstration of a platform far outside our budget. He never asked how the current system was performing, what we were considering, or what our team could realistically support.
There was no sale to lose that day. What he lost was the next opportunity, and he probably never knew it.
No further opportunityHe started by understanding how we operated. He knew the product category well enough to recommend an option with fewer features because it was the one his own team could support reliably.
More important, he took responsibility for the work we could not staff. His team would manage the system remotely, handle routine reporting and upgrades, and be on-site within 24 hours when remote support was not enough. He told me clearly what he could customize and where his limits were.
I had told every vendor the same thing: we did not have the capacity to manage another system after installation. Most heard it as context. He treated it as the buying criterion.
Won the workA feature request is often shorthand for an operating constraint.
I asked for a "set it and forget it" system. On the surface, that sounded like a feature preference. In reality, it described my scarcest resource: staff attention. The best proposal was the one that removed the most ongoing operational burden without creating new risk.
Before becoming Executive Director, I chaired an ad hoc strategic planning committee. We needed to decide what the organization should build next, so we surveyed current and former customers rather than answer the question internally. The same need surfaced repeatedly: outdoor learning and adventure programming, including a ropes course and zip lines.
I raised $250,000 for the project. The visible structure was only part of the work. Zoning, environmental review, land surveys and boundary questions, legal review, architectural planning, and contractor timing all had to align.
I chose the highest-priced proposal because it was the only one that addressed the full execution risk.
The contractor had the deepest experience and answered each concern with a concrete plan rather than a caveat. He understood that once the course was built, our small team could not spend its time managing an unstable installation. I had raised the money from people who trusted me to use it well. The proposal I could not afford was the one most likely to create delays, rework, or an unfinished project.
In both purchases, the winning vendor was not the cheapest. It was the one that understood the operating constraint and reduced the risk after the sale. Owning the budget and the outcome made the consequences immediate.
I already believed in discovery, operational fit, and accountability after the sale. Running O'Dwyer put me on the receiving end of all three. A vendor's assumptions became my budget problem. A weak implementation became my team's workload. Poor follow-through came back to my desk.
The principle I now call Outcome Orchestration mattered just as much when I was buying as when I was selling. The decision only worked if the financial, operational, and technical outcomes aligned for the people who had to fund it, support it, and use it.
My facilities manager and I both thought the manufacturer's representative gave a strong presentation. I also knew he had skipped the questions that mattered. The issue was not presentation quality. It was that the recommendation had not been shaped by our budget, staffing, support needs, or operating reality.
I told vendors plainly that we had no internal IT team and limited capacity to manage another system. The integrator who won the work did not uncover some hidden need. He listened to the constraint I had already stated and designed around it.
A solution could have more features and still be the worse choice if it created too much work for the people responsible for supporting it. From the buyer's chair, ease of operation, responsiveness, and ownership after implementation were part of the product itself.
The vendors who earned my business were not the ones who taught me what good selling looked like. They were the ones who practiced it.
A buyer in the position I was in can now use AI to clarify constraints before a vendor ever enters the room. That changes how requirements are written, how RFPs are scoped, and how teams estimate what a new initiative will take to operate.
The easy conclusion is that this reduces the seller's role. I think it raises the standard. When a buyer arrives with a clearer problem statement, a seller who leads with a generic demonstration and no questions is more exposed, not less. The gap between what the buyer asked and what the seller brought becomes easier to see.
AI would not have rescued the manufacturer's representative. My constraint was available to anyone willing to ask. He never did.
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 customers.
A sales organization where experienced sellers are expected to make the whole team better.
A company that listens to the people closest to the customer.