This one tripped me up more than I expected.
Acknowledge the client's request while making it clear you cannot commit to a date for an undefined feature. Explain that you need to align with engineering and design to assess feasibility and scope before providing any timeline. Then propose a concrete next step, such as a discovery session, to move the conversation forward collaboratively.
Pro tip: Never say 'no' outright—say 'not yet' and immediately offer a path to 'yes' by proposing a time-boxed discovery. This shows you're client-focused while protecting your team from unrealistic commitments.
Thank the client for their interest and validate the importance of the feature to their needs. This builds trust and shows you're listening.
Clearly state that because the feature hasn't been discussed internally, you cannot provide a reliable delivery date yet. Avoid guessing or overpromising.
Briefly outline the steps needed to assess feasibility: gathering requirements, technical scoping, and prioritization with engineering and design.
Suggest a specific action, like a discovery workshop or a follow-up meeting, to gather requirements and involve the right stakeholders.
Commit to a timeline for when you'll get back to them with a more informed estimate, and clarify that any date will be contingent on internal alignment.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.