15+
Years selling it
Verizon, National Account Manager and then Senior Client Partner. Fortune 500, regulated and nationally distributed accounts. Multi-year negotiation, competitive takeaways, and partner ecosystems assembled around problems the customer had not yet scoped.
7
Years on the other side
Executive Director of a $1.5M organization serving 6,000+ people a year across 125+ groups. I owned the P&L, the vendor conversations and every technology decision. Participation grew 42% over five years and revenue grew 20%+ in a single year.
The CFO
What happens if it doesn't pay for itself?
Cost, savings, revenue impact, risk and return. A CFO is not asking what the thing does. They are asking what it costs, what it returns, and what happens to them if it fails. Answer the first question well and ignore the last one, and the deal quietly stalls at final approval with no explanation.
What I ask themWhat would this need to return before signing it stops being a risk?
The COO
What happens the day it breaks?
Capacity, speed, reliability, and what happens the day something breaks. Operations does not care about the platform. They care whether the job gets faster and more dependable, whether their people can absorb the change, and whether the thing holds up in the field rather than in the demo.
What I ask themWhere is the current process costing you the most time?
The CIO
Who is still supporting this in three years?
Security, scale, and fit with everything that already exists. Technology leaders inherit the decision long after everyone else has moved on to the next thing. They are asking whether it integrates, whether it is defensible, and whether it still works at ten times the volume.
What I ask themWhat would make this impossible for your team to support?