Biggest Customer Wants an Off-Roadmap Feature: How the PM Decides and Responds

Your biggest customer keeps pushing for a feature that your roadmap does not include. How do you handle it? ```hint Find the problem behind the ask Before deciding whether to build anything, work out what the customer is actually trying to accomplish and whether this account is the only one that needs it. ``` ### Clarifying Questions - How is the request reaching me: from the customer directly, through their account team, or escalated to engineering or leadership without going through me? - Has the customer already been told the feature is not planned, and is a renewal, contract term or deadline riding on it? - Roughly how much of our revenue does this one account represent? - Is the product sold mainly to large accounts that commonly negotiate features, or is this customer unusual for our base? ### What a Strong Answer Covers - Discovering the job the requested feature is meant to do, how severe the gap is, and whether an existing capability or workaround already covers it - Sizing both sides: revenue and churn risk for the account, how many other customers share the need, build and maintenance cost, and what would slip - Judging fit with the product strategy and current company goals instead of treating the biggest account's request as top priority by default - A clear decision among real options (build, build a generalized version, schedule later with a workaround, solve outside the core product, decline) and how each stakeholder hears it - Keeping the relationship and the prioritization process intact, so one escalation does not become the way the roadmap gets set ### Follow-up Questions - The account team takes the request straight to your engineering lead instead of to you. How do you respond? - The customer says they will not renew without this feature. What changes in your answer, and what would you verify first? - If you do build it, how do you keep it from turning into a custom variant that only one customer uses?