Setting Customer Expectations With an Estimate Before Scope Is Clear

You are a product manager, and a customer asks you for an estimate on something they are waiting for, but the requirements behind the request are still thin: you know roughly what they want, not the details. How would you arrive at an estimate and present it to them? Cover what you would do before quoting anything, what you would actually tell the customer, and how you would manage the estimate as the requirements become clearer. ```hint Make the uncertainty usable Think about how to turn "we don't know enough yet" into something the customer can plan around, and what would let you tighten the number over time. ``` ### Clarifying Questions - What is being estimated: a delivery date, the engineering effort, or a cost to the customer? - Is the customer external, such as a business account waiting on a feature, or an internal team that depends on yours? - What will the customer do with the number: rough planning, or a commitment they will pass on to their own customers? - Is there a fixed external deadline, such as a contract or launch date, that the work has to meet? ### What a Strong Answer Covers - Concrete, time-boxed steps to reduce the biggest unknowns before quoting, including the customer's underlying need and engineering's input. - An estimate stated with its uncertainty: a range or confidence level, the assumptions it rests on, and what is in and out of scope. - Communication that protects trust: when the estimate will be refined, how changes will be flagged early, and no promises the team cannot keep. - Options that give the customer value sooner when the full scope is uncertain, such as a phased first release. - How the estimate is revisited as requirements firm up, and how a slip is handled. ### Follow-up Questions - Tell me about a time an estimate you gave turned out to be badly wrong. What did you do, and what changed afterward? - The customer insists on a single committed date for their own launch plans. How do you respond? - Engineering will not size anything until the specification is final. How do you get a number you can share?