I worked with many sales people who got CEOs later, because they made big sales, but most of them, because they sold stuff they didn't had, because they didn't really know the customers.
In extreme cases, this leads to overworked devs and rich sales people, when the devs are good and the features aren't that hard to implement. If the features are too hard, it leads to angry customers and the company losing much money.
LOL, how much have you sold in your career? Because really, it seems like you've never had a sales meeting at all.
Practically though, if you've worked in sales, you'll know that what the OP is talking about isn't just something that happens often, but is basically the life-blood of some rather large companies.
Now, I dislike it because it puts the impetus on the developers to deal with it if it goes wrong, and that sort of crunch-time stress is just crazy, but it's also not something that the OP has come up with on his own...
I'm sure there are more ways of doing that too, though, so these are just my observations. And yeah, don't trust the sales guys :)
But if I ever learned that a business partner were so dishonest with me, I'd drop them in a heartbeat. Business relations are all about trust and integrity.
That's fun new word for "lies".
Obviously, he's a liar to his business partners, his customers, and his employees. But right now, he isn't a liar to us quite yet.
So he has gained some personal growth from this event. All's well in the long run, but its difficult to make up for broken trust.
I'm not OP, but you still don't get what's wrong here. You're still lying. Why not say "Not yet, but we have a great dev team and we would gladly add this feature in for you before launch." It's honest, and frankly sounds more impressive to the client.