Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't mean to be rude but this idea that there's some decisive, authoritative data vs. sketchy anecdotal claims kind of drives me up the wall.

What data would or could exist in this case beyond the hundreds of calls the author is apparently basing their observations on? That seems like a reasonable qualitative data set to me.

On the other hand, what you're asking for doesn't make much sense. Any push/pull strategy difference is going to change who takes a call in the first place. You're not doing a RCT on a random sampling of the population.

The point is simply that you're going to have a better time doing sales if your supply matches some pre-existing demand. You don't need a quantitative study to understand why that may well be the case.

It's the same reason that, despite being bombarded with advertisements, we don't all go out and buy 16 meals a day or 10 cars a year simply because someone tried to sell those things to us. We act when we have a need, and founders need to understand that as a physical reality when trying to sell their products.



Your comment hits on a broader tension I see a lot, not just here but in business strategy in general. It's the divide between compelling, experience-based narratives and empirical evidence. I think both are essential.

The author has presented a fantastic and intuitive narrative with the "BUYER-PULL" model. Your analogy is spot-on: you can't sell 16 meals a day to someone who only needs three. The qualitative insight is powerful.

My request for data comes from the next step. How do we know this narrative is not just a "just-so story"? How much does this effect matter on the margin? In the complex world of B2B sales, where needs aren't always as clear as hunger, can "push" tactics sometimes be effective at helping a buyer crystallize a latent need?

Asking for metrics like close rates isn't meant to demand an impossible standard of scientific proof. Instead, it's an attempt to test the boundaries of this framework and understand its real-world impact. Great insights often come from quantifying the effects of a powerful story.


Please don’t pollute HN with AI slop.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: