Your three biggest enterprise accounts have a combined ACV of $1.5M. Together, they've requested 40 features over the past year. Building most of them would require 6 months of engineering time and would result in a product that works very well for these three accounts and less well for the other 500 accounts you serve.
This is the best customer request trap. And most SaaS product teams walk into it repeatedly.
The analysis that determines when to say yes vs. no:
Will this feature serve the needs of 20%+ of your current customer base? If the request addresses a need shared broadly across your ICP, build it. If it addresses a workflow specific to one customer's business process, don't.
Does this feature advance your product strategy, or does it create a detour? Some enterprise requests are directionally aligned with where you're taking the product — you would have built this eventually, the customer is just giving you timing and requirements. Build it. Some requests are orthogonal to your strategy — they'd solve a problem for this customer without advancing your product toward its intended position. Don't build it.
Is this request about improving a core workflow or adding a new workflow? Improving core workflows (making existing features faster, more accurate, more integrated) is almost always the right investment. Adding new workflows that don't exist in the core product adds complexity without necessarily deepening value.
When you say no:
Be clear, respectful, and explain the reasoning. "We're not building this because it doesn't serve our broader customer base" is better than vague deferral.
Offer an alternative path. Can they solve the need through the API? Through a third-party integration? Through a configuration of existing features?
Stay firm under renewal pressure. The threat to not renew if a feature isn't built is a negotiation tactic. The right response is a calm explanation of what you're building and why it's the right investment for the product's future.
The best customers are the ones who want you to succeed long-term. They can handle an honest no.