The answer is probably NO.
I guess we have all seen a somewhat “strange” requirement and wondered why the client had such a specific and odd requirement. In some cases the reason is that the client is legally obliged to place the project in an open bid. To ensure they get the system they’ve already decided they want, they might “tweak” the specs and thereby severely limiting the number of bidders.
You can try and provide a half-assed “solution” to meet the spec, and hope that the client will change their mind in the nick of time (how often does that happen?). But why chase these clients, and poison your platform with a bunch of poorly executed features? If you focus – REALLY focus, on the user experience and add meaningful thoughtful features then people will alter the spec to support your platform instead.
The trick is to understand when a spec is really a useful request, or if it is there just to fence you out of the bid. If people don’t want your product, it is not because you do not support the Apple Newton, but because the rest of your application is simply too shitty to compete. Instead of adding more shit to your already shitty app, you should consider improving and cleaning up the mess.
If your app stinks, it is difficult to instill a sense of pride in the product in the team. If there is no pride, there is no motivation, and with no motivation there is no productivity.
An amazing application with fever features will always beat a shitty app with a million features.