[nickjj]

As a customer who has been on a number of these calls, the thing I dislike the most is getting "yes" for every question I have. Just be honest with me.

Realistically I'm on the call with your business because I've put in a huge amount of research about your product or service, I likely narrowed things down to your service and maybe 1 or 2 others. I know a lot about the individual technical features of your service and your main competitors but didn't spend enough time to put it all together to solve every use case I might have -- only that your service so far looks promising.

I can't count the number of times where I'll bring something up and the person on the call (usually a business sales along with someone who is more technical) will flat out lie to us about something (even in a group call scenario), in which case I'll politely question that and reference their docs about it. They try to save grace by saying "oh yeah, our documentation must be out of date, sorry about that" or they directly lie about their competitors often saying so and so can't do xyz when they can and the easy out there is "oh, perhaps they added that recently".

It happens way too often to always have outdated documentation or information. Even after a 15 minute remote call you can get to know someone's mannerisms and the cadence of how they speak. It's not hard to tell when someone is lying or has much less confidence in what they're saying. I've gone with competitors for nearly 6 figure annual contracts because of these things multiple times when the decision has been pretty close.

If you're planning to be a customer, it's worth doing your due diligence to research things in a solid amount of detail before going into these calls. All it takes is maybe 2-3 full days of hardcore research to be super prepared. That's time very well spent to understand if a product looks like it will work for you as a first pass, especially so if you plan to bring other devs or a CTO into a future call to get contracts prepared and signed.

[throwaway432897]

> As a customer who has been on a number of these calls, the thing I dislike the most is getting "yes" for every question I have. Just be honest with me.

Joke: what’s the difference between a used car dealer and a software salesperson? The used car dealer knows when he’s lying to you.

Having been in B2B sales for a while now, if I was on the buying side I would never listen to an answer about a product feature/function from an account manager (the “business sales” person in your example) — only their sales engineer (the “someone who is more technical”.) If the SE lied, I’d never buy anything from their company for any reason.

Now, that said, documentation is sometimes out of date (although a better way of answering in those scenarios is for the SE to say something like “we didn’t do that until version x.y which came out/will come out last week/next month, etc. and our documentation isn’t up to date.” And, sometimes, prospective customers do “2-3 full days of hardcore research” and aren’t nearly as “super prepared” or knowledgeable as they think they are.

So, I guess be open to the idea that your SE understands their product better than you do, but if they really are slinging BS, run. Expect the account manager to be wrong about the details of their product (there is a reason SEs exist, and it isn’t because tech companies enjoy an artificially high cost of sales.) so don’t listen to much they have to say about product features.