Scope is a feature, not a constraint
The most valuable thing a good team gives you is a confident, well-argued no.
Every feature you add is a feature you maintain, debug, explain, and eventually regret if it wasn't earning its place. Teams that say yes to everything aren't being generous. They're deferring the cost of their indecision onto your codebase.
A no is a design decision
When we push back on scope, it's not to do less work. It's because the version with fewer things in it is usually the better product. Restraint is the part of the craft that doesn't show up in a feature list, which is exactly why it's worth paying for.
The product people love is rarely the one with the most in it.
So we argue about scope, early and in the open. You'll always get the reasoning, and the final call is yours. But you're hiring us partly for the judgment about what to leave out — and we'd be doing the job badly if we kept that opinion to ourselves.