Discussion about this post

User's avatar
Kevin Shea's avatar

I think there's a lot of vagueness on both sides (mostly unintentional). The vendor doesn't want to pigeonhole their product and limit potential customer base. They also may not have portions of it fleshed out yet and hope that interactions with customers will help with that. And they probably have limited resources to provide pilots/sandboxes for potential customers to kick the tires. On the customer side, the interest in a product may be serious and well-thought out. Or, it could be just someone looking around with a general idea of what they need. I've found mostly the latter - that the customer's actual need for a new system is often unclear. There's uncertainty about cost constraints, expected ROI, what works and does not work in the current system, current workflows that are not nailed down or documented, and the requirements for a new system are not fleshed out. When you layer on the realities of change management, validation, updated process and control docs, logistics and impact of the transition/go-live to a new system, etc., the limitations discussed in the article can be seen as expected.

Expand full comment
JaMo's avatar

Having seen the sales and implementation side, I think there is a lack of trust that the customer knows how to evaluate the product. This "high touch" approach (Agreed not malicious or intentionally manipulative) can be to ensure each customer converts to a deal.

Parallels this great overview on how Atlassian sells product: https://www.intercom.com/blog/podcasts/scale-how-atlassian-built-a-20-billion-dollar-company-with-no-sales-team/.

Expand full comment
10 more comments...

No posts