I disagree, hard.

There’s a 3rd option. It’s probably the most obvious, and the most common:

3) What’s involved in building this feature and how long would that take?

When somebody asks a developer if it’s “possible” to add xyz feature — well, that’s no different to me asking my plumber if it’s “possible” to install a new shower in my bathroom. He/she will turn round to me and say, “Yes, it’s possible. I would install this by doing abc. The time for doing that work is X. Therefore, it will cost you Y”. He/she wouldn’t ask me an abstract question about what it’s worth to me (“What’s a shower every day worth? How do I put a figure on that?”). Or whether I would consider having no bathtub, in lieu.

Why is there the assumption that when a non-technical person asks a developer “Is it possible to…” that this question has a veiled agenda? Why is there the assumption that all non-technical staff are out to ‘get one over’ on developers, that every query is a chance to pull the wool over their eyes?

The real problem here is that the development department within a company is quite often viewed from afar — with fear or bemusement. Arguing over semantics makes developers even less accessible and integrated than they were already. Walking up to the “Rockstar” developer to discuss a new feature can already be intimidating enough for non-technical staff — let’s not make it more so.