Every Customer-Facing Call Should Have an Engineer on It
bennadel.com
bennadel.com
If your standard operating procedure is to waste engineering time sitting in on customer meetings, and then not let the engineers fix the issues they heard about then your customer trust is going to drop.
Also there's a buzz when engineers start to meet customers, but once you've met your 5th customer you're pretty much done with that buzz - especially if you're breifed by the company that you're not allowed to commit to anything.
The CFO is always the most interesting: they rarely really have strong domain knowledge of the details of the company's product in the market (they know what goes into making it!) and learn a lot about how our customers think of our product.
As an engineer myself, I'm usually scoped way down in the weeds of a mass of technical problems. It's an expensive context switch to come all the way up to thinking about broad customer issues, and then get back down. OK to do on occasion, but not regularly.
And besides: Why do customers feel less "heard" without an engineer on the line? Why are all the others on these calls under- or over-committing, unless an engineer is there? It seems like the problem isn't with lack of engineering presence, but with what everyone else in the organization is doing.
It will work against you in large quantities or on-call though. Also, a lot of engineers are introverts, and some are "too honest" to be customer facing.
Elon Musk is the only one who could get away with talking about stone toadstools to customers.