Positioning Cloud and On-Premises Deployment Options in an Enterprise Sale

How would you approach selling an on-premises deployment versus a cloud service to a customer, and how would your pitch differ between the two? ```hint Start from why they lean one way Before pitching either option, find out what sits behind the customer's preference and who in their organization has to approve the purchase. The pitch changes with each answer. ``` ### Clarifying Questions - Does the company offer both a self-hosted version and a cloud service, or is it cloud-only, so the real task is winning over a customer who wants to keep the product on their own servers? - Who is the customer: a regulated organization (a bank, a government body, a hospital group) with data-residency rules, or a company that already runs most of its systems in a public cloud? - Am I supporting a sales team on one deal, or setting the overall positioning and pricing for the two options? - Is there a hard requirement such as an air-gapped network, where no data may leave the site at all? ### What a Strong Answer Covers - Discovery of the customer's drivers and of the buying group (security, finance, infrastructure, end users) before any pitch. - A value case for each option tied to those drivers, using total cost of ownership rather than list price. - Specific handling of the usual objections: data security and residency, control, cost predictability and reliability. - A recommended path (proof of concept, hybrid, staged move) and a clear view of when not to push the cloud. - How the PM measures whether the positioning works and feeds lost-deal reasons back into the product. ### Follow-up Questions - The customer's security team says no data may leave their network, and you only sell a cloud service. What do you do? - The CFO says the cloud bill is unpredictable because pricing depends on usage. How do you respond? - After several deals are lost to self-hosted competitors, would you build an on-premises edition? What would you need to know first?