In a similar vein, enterprise customers tend to want different things than smaller customers do. This means that the features the teams have to work on will change, and some people may not be as interested in working on stuff they have no interest in using themselves.
A million times this. I currently work at an enterprise software firm, and this is exactly what happens with each new client.
In addition to the compressed timelines and ridiculous feature requests that must be honored... in terms of the product itself, you have to do one of the following: 1) Maintain separate codebases for each client, or 2) Build the application so it can handle different features for each client, since each client will want different things.
Neither course of action is nearly as pleasant as having products that are the same for all customers.
CEO: "$$$!!!"
B.D.: "Pivot!"
Engineers: "There goes our sprint"
Product Managers: "I'll be updating my resume..."
Maybe this is a trope from the 90s and 2000s or from a Scott Adams cartoon, but I disagree this is representative of most enterprise sales these days. Maybe I'm just spoiled, but every company I've worked at the past decade has had a knowledgeable sales force. I've been asked plenty of times, "can you add this feature for a huge customer?" and been able to say "no, that is not realistic for us to complete in a reasonable amount of time."
Every sale matters when you don't have customers, and if it means a little back-breaking work to get that first bit of revenue, I know very few companies with the fortitude to say 'No'.
Once the product has established a foothold, reputation, or repeatable sales process that works, product managers get an idea of exactly what it is that customers want, and across more than one data point. From that, they're able to communicate the exact value they provide to the sales team, and that sales team is able to approach customers with an actual, legitimate, proven value proposition.
It isn't until the product team really knows what they have that those requests become easier to turn down.
(Or at least, that's been my experience.)
They weren't promising Ferarris when we were building Maseratis, but they were definitely throwing in the undercoating and floor mats. Even now when I'm building and selling my own software products I do it. I literally do it to myself. In the end it helps evolve the product if you make a responsible claim you can get to.
It's the same old story: OS/2 was superior to DOS, Netscape was better than IE, Dreamcast was amazing, Amiga was ahead of its time, etc.
It's not just software. Shakespeare wasn't a popular playwright in his time, but now he's considered an icon. Were his plays therefore not great because, at the time they were written, no one wanted them?
Many good things are not popular or well-known. They are no less good.
In my experience, this happens because sales people come to the engineers and say "can we do [mad thing]?" and, engineers being engineers, go "yeah, sure, [possibly adding detail and constraints but the sales people stopped listening at 'yeah']". I've seen this many, many times.
Default answer out of any engineer's mouth should be "No." with optional coda of "But if you can tell me more about it, we might get to maybe."
Good thing this isn't some voluntary project but a massively funded commercial company. Since when must employees love every little thing they're doing?
This kind of BS culture is what runs companies into the ground the moment they need to actually build something that isn't "fun".
The 'brogrammers' just carry on as normal and some of their work is now adding features to help support enterprise requirements. Unless your sitting a cold calling sales rep next to my desk then who cares? Someone has to pay for that foosball table and fridge full of beers, let the sales people on a different floor do their job.