Stupid Customer Tricks
Feb. 10th, 2022 09:26 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
canyonwalkerThis afternoon a prospective customer we've been trying to schedule a meeting with for several weeks finally responded to us. He sent an email at 4:54pm proposing 9am tomorrow as his first choice. 9am tomorrow. He suggested tomorrow 2pm or Monday afternoon if that didn't work.
'Mr. 4:54pm would like a demo first thing tomorrow," I teased my colleague, Todd, via Slack. Todd is the account executive in charge of the opportunity.
Normally we want more preparation for the demo. We've been chasing Mr. 4:54pm for weeks not just to schedule a time but to align on what his needs are— so we can address them accurately in our presentation. But in this case Todd and agreed, "Fuck it, let's shoot from the hip." We figured if we didn't take the shot we'd lose another several weeks with this opportunity. Todd confirmed the 9-10a slot and sent a calendar invitation.
Here's where it gets really stupid.
Mr 4:54pm fires back an email minutes later. "WhY iS tHeRe A mEeTiNg ToMoRrOw?!?!"
...Well, he didn't write it in camel case like that, but that's what the tone of his message seemed like. He seemed genuinely surprised, like he was completely unaware that he just proposed a Friday morning meeting—as his first choice, no less— and we accepted.
Todd emailed him briefly mentioning the whole propose/accept dynamic.
Then it got even stupider.
"We couldn't pOsSiBlY have a mEeTiNg that sOoN!" Mr 4:54scolds us. He points out the huuuuge number of people he forwarded the invitation to (which he did without telling us, until now) and implies we're fools for thinking we can coordinate such a meeting on such short notice. BTW the huge number of secret invitees rang alarm bells for me; more on that in a moment.
At this point I figure there are two likelihoods here. 1) Mr 4:54pm is incompetent. He's a senior director of software in a highly successful technology company. "Knows how to schedule a meeting" should be well within his wheelhouse. 2) He's deliberately setting us up to fail. He proposes difficult meetings times hoping we'll decline; then he can blame us for being uncooperative. Or if we accept them (like we did) he faults us for being unrealistic (like he did).
Then there's the thing about the huuuge number of people he forwarded the invite to. Huuuuge demo meetings rarely go well. They require strong leadership— exactly the kind of thing Mr. 4:54pm is not providing. Another point for incompetence... or malice... or both.
Update: Friday afternoon Mr. 4:54pm asks us if we could tell him who's attending the meeting because he doesn't remember who he forwarded it to!
'Mr. 4:54pm would like a demo first thing tomorrow," I teased my colleague, Todd, via Slack. Todd is the account executive in charge of the opportunity.
Normally we want more preparation for the demo. We've been chasing Mr. 4:54pm for weeks not just to schedule a time but to align on what his needs are— so we can address them accurately in our presentation. But in this case Todd and agreed, "Fuck it, let's shoot from the hip." We figured if we didn't take the shot we'd lose another several weeks with this opportunity. Todd confirmed the 9-10a slot and sent a calendar invitation.
Here's where it gets really stupid.
Mr 4:54pm fires back an email minutes later. "WhY iS tHeRe A mEeTiNg ToMoRrOw?!?!"
...Well, he didn't write it in camel case like that, but that's what the tone of his message seemed like. He seemed genuinely surprised, like he was completely unaware that he just proposed a Friday morning meeting—as his first choice, no less— and we accepted.
Todd emailed him briefly mentioning the whole propose/accept dynamic.
Then it got even stupider.
"We couldn't pOsSiBlY have a mEeTiNg that sOoN!" Mr 4:54scolds us. He points out the huuuuge number of people he forwarded the invitation to (which he did without telling us, until now) and implies we're fools for thinking we can coordinate such a meeting on such short notice. BTW the huge number of secret invitees rang alarm bells for me; more on that in a moment.
At this point I figure there are two likelihoods here. 1) Mr 4:54pm is incompetent. He's a senior director of software in a highly successful technology company. "Knows how to schedule a meeting" should be well within his wheelhouse. 2) He's deliberately setting us up to fail. He proposes difficult meetings times hoping we'll decline; then he can blame us for being uncooperative. Or if we accept them (like we did) he faults us for being unrealistic (like he did).
Then there's the thing about the huuuge number of people he forwarded the invite to. Huuuuge demo meetings rarely go well. They require strong leadership— exactly the kind of thing Mr. 4:54pm is not providing. Another point for incompetence... or malice... or both.
Update: Friday afternoon Mr. 4:54pm asks us if we could tell him who's attending the meeting because he doesn't remember who he forwarded it to!
