Prioritizing a Deal-Blocking Enterprise Request Against a Committed Roadmap

You are a product manager for an enterprise software product. Your sales team comes to you with a \$100M deal that will not close unless the product gains a capability it lacks today; the customer treats that gap as a deal stopper. At the same time, your engineering team is fully committed to a different key feature for the rest of the year. How would you prioritize between the two requests? Walk through what you would want to learn first, the options you would consider, the recommendation you would make, and how you would bring sales, engineering and leadership to a decision. ```hint Test both claims first Neither request is as fixed as it sounds. Before ranking them, find out how firm the deal's value and the "deal stopper" label really are, and what delaying the feature the team is building would actually cost. ``` ### Clarifying Questions - Is the \$100M the yearly value or the total over a multi-year contract, and how likely is the deal to close once the gap is filled? - Do other customers or prospects need the missing capability, or would it be a customization for this one account? - Who depends on the feature already in progress: customers who were promised it, a public launch date, or an internal strategic goal? - Do I have levers beyond my own team, such as borrowed engineers, partners or professional services, or a customer willing to sign against a committed delivery date? ### What a Strong Answer Covers - Verifying both sides before choosing: the deal's real value, odds and deadline, and the true cost of delaying the in-progress feature - Judging whether the capability fits the product strategy and serves more than one customer, instead of treating it as a one-off revenue grab - Options beyond either/or (reduced scope, sequencing, added capacity, a partner or services workaround, a dated commitment), compared on value, cost, risk and the precedent they set - A clear recommendation, the conditions that would change it, and who owns the final call - Communication to sales, engineering, leadership and the customers waiting on the current feature ### Follow-up Questions - The CEO tells you to win the deal whatever it takes. How do you respond, and what do you insist on protecting? - After the team starts building, the customer keeps pushing the signature back. What do you do now, and what would you change next time? - How would you set up a process so that large sales requests like this one stop arriving as emergencies?