Again I have come into contact with a priori requirements 'gathering'. It is worth a general rant because it is so prevalent out there.
Developing a system for end users out of the mind of systems experts alone causes confusion in the requirements process - and holds things up.
Instead, please find out what the stakeholders need and then use your reasoning to deduce an efficient way to achieve those needs. And use this to limit your scope to only what is really required - don't spend money on one additional feature. Justify every feature in writing. And do not, by any means, create a sophisticated state of the art system if it isn't necessary!
The world will be a lot better for it.