Sure, you can claim it's not really work in the narrow definition of work, but if you go down that path, you will end up at "it's only really work if it's physical work".
However, it's disingenuous to compare them with plowing a field, laying bricks, welding steel bars, driving a bus, serving meals or even fixing software bugs.
What may seem like "eating and drinking" for sales and biz dev folks is a game requiring thinking on your feet, subtle negotiation, reading social cues, and constant strategy changes.
Trying to influence a potential client to close a multi-million dollar software contract is anything but close to 'normal' activities. It's very demanding intellectually and emotionally.
I really encourage you to learn more about what sales folks actually do when having dinner with a big prospective client. They aren't just eating.
That shit is difficult, tyring and definitely requires certain skills to do it right. I definitely would put it up there with developing complex Software architectures.
Or the candidate may have just failed another interview hours ago because he said he enjoyed working 8 or 12 hours a day, and lose the faith of humanity all together.
You'll never know why they've generated that answer if you don't ask a follow up question.
I've seen hundreds of wantrepreneurs who call networking "work" and yet haven't shipped anything, haven't sold anything, and are just wasting everyone's time.
Yes, all of them.
I know them because I either worked for them or worked with their companies.
Things got a lot better post launch when he had more actual work to do, but I think his work weeks probably consolidated to something close to 50 hours.
Don't want to be too hard on him, since he was very good at his primary role, namely pitching the company to the investors.