Topic
Enterprise
15 essays tagged “Enterprise”.
- How to Run a Program Reset Without Losing the Customer
Enterprise deliveries go sideways. The reset conversation is the most important one an account team will have with a customer. Most handle it by generating optimism. The ones that work generate clarity.
- Write the Account Plan for the Account, Not the Forecast Call
Most account plans exist to satisfy an internal process. The ones that actually help the account team are built to answer a different set of questions, and they get rewritten when the account changes, not when the quarter ends.
- The Discovery Call Is a Diagnostic, Not an Interview
Most discovery calls are information extraction exercises: the AE asks a list of questions, the customer answers, and both sides leave with the same understanding they arrived with. The good ones work differently.
- The Deal You Have to Sell Twice
Enterprise AEs spend most of their time selling to customers. The deals that close also require selling internally: to resourcing, to leadership, to the partner team. This is the part that most account planning frameworks skip.
- Why the Biggest Q1 Deals Rarely Close in Q2
Every January has the same shape: a pipeline full of deals that feel transformative and a Q2 that looks increasingly familiar by March. The pattern is structural, not motivational.
- The Customer Who Will Expand and the One Who Will Not
The signals are visible in the first engagement. Most account teams are not looking for them because they are focused on closing, not on reading what the relationship is actually built on.
- How to Run a Proof-of-Concept That Moves a Deal Forward
Most PoCs stall deals rather than close them. The problem is almost never technical. A PoC that is designed to prove technology answers the wrong question.
- The Organizational Pattern Behind Every Platform Deal That Dies in Contracting
The technical win is real. The champion is genuine. The architecture team loved it. Then contracting starts and the deal goes quiet for ten weeks. This is not a contracting problem.
- What the Executives Who Build Durable Partnerships Do Differently
Some enterprise technology relationships last a decade and define how an organization competes. Most last three years and end in a procurement review. The difference is visible from the first meeting.
- Read the Annual Report Before the First Meeting
Most enterprise AEs use the annual report to find the CEO's name and the company's headcount. That's not what it's for.
- The Deals That Stall on Security Were Already Lost
Security reviews don't kill enterprise cloud deals. They surface problems that were already there. The difference is whether security was in the room in week two or week fourteen.
- Nine Languages, One Practice: Notes on Operating Multilingually
Running an enterprise consulting practice across nine languages and four time zones teaches you things about organizational design that monolingual environments cannot.
- The Meeting That Actually Closes Enterprise Cloud Deals
It's not the CFO presentation. It's not the commercial proposal. It's the architecture review, and most sales teams treat it as a technical formality.
- Predictive Maintenance at Fleet Scale with Sparse Failure Data
How a 25-person delivery team shipped a production ML platform for 6,000+ industrial companies when the thing everyone agreed was necessary (labelled failure data) barely existed.
- Enterprise AI Adoption: The Gap Between Demo and Production
Most enterprise AI initiatives stall not because of model quality, but because of data readiness, organizational resistance, and unclear ROI expectations.