How to handle extra requests during project discovery
Your prospective client adds another feature or deliverable before you have agreed on the core scope.
What they might say
- “Maybe we add the events module too.”
- “That should be a quick addition.”
- “Can we include that in the same price?”
What's usually behind it
Your client may be thinking aloud rather than making a firm request. They may not see how the addition affects the work, cost, or delivery date.
What you can say
- Let’s capture that without committing to it yet.
- It could change the cost and timing.
- How does it rank against what you need for the first launch?
Try not to
- Agreeing before you understand the extra work.
- Treating every new idea as a demand.
How Earshot helps in the moment
Earshot listens live, shows one short card with a suggested line to clarify priorities, and nudges you on pace.
More for client discovery