Getting to No: The Key to Startup Selling
sequoiacap.com
sequoiacap.com
Also, a good sales call needs to have some structure. For example, a good portion of the qualifying questions should focus on customer pain.
Does the prospect have the pain you solve?
Does the prospect already solve/address the pain? If so, how? With whom? What is good about the current solution? What's wrong with it?
Does the prospect have budget to solve the pain? How much? How is budget allocated and when? What is the budget process?
Who makes decisions about this pain? Who decides which solution to use? Who approves the budget, and who can influence a purchase decision?
And so on.
With regard to endlessly calling people...if it works then stick with it. I've been amazed over the years at what works for different sales people. There are definitely practices that work for one person's personality that would be horrific with a different sales person.
However, I think the OP's advice is to remember your ABCs of selling (Always Be C/Selling).
I've definitely found the transition to salesperson from developer one of the hardest things about running a company.
I'm a fan of Jeff Thull's "Diagnostic Business Development" approach, and in his book Mastering The Complex Sale he makes a similar point. And think about it: If this customer is not going to buy your product (because they don't need it, don't like you, or because of your skin color, whatever) the sooner you find out, the better... because now you can divert that energy and attention to a different prospect who may be more likely to buy.
I'm still trying to learn to be a salesman after 20 some odd years of being a coder first and foremost, so a lot of this still feels foreign to me, but at least some of it is starting to make sense. Hopefully salesmen can be "made" and don't have to be "born".
The name of the book is: Go For No http://www.amazon.com/Yes-Destination-How-You-There/dp/09663...
It's a great book.
That said it's a technique that works really well.
Leads would throw out lots of vague reasons why they couldn't say 'yes' (usually because they were too polite / guarded to say the real reason), CEO/CTO would promise to resolve all of them, and then send the engineering team on a wild goose chase of trying to develop new features or new products that didn't make any sense. But really, it was usually a regulatory problem and they couldn't buy the product even if it sprouted golden unicorns from its AC bus because their regulator just wouldn't authorize non-essential equipment.
So I like this advice a lot. If someone is not going to buy the product I want to know as soon as possible. Your product direction shouldn't consist of the last 5 things potential leads told you while giving you a soft 'no', especially when you're building a product that takes months to years of testing and validation and failure analysis and certification before it can go to market.
Now thousands of people reading this ridiculous blog post will copycat. FACEPALM.
Please. Stop. this. nonsense.
> No reply after several attempts is a NO
If that was true, people wouldn't do it. It's not, though.This entire story is about selfish people spamming prospects with no respect for anyone else's time but their own.
Disgraceful.
Context: I was writing a book and needed it finished before final exams my senior year. I had to get people to say yes or no, but no responses were just wasting time. Not a single person was offended when I used this trick.
This was a great read to me, because now I know that I've been doing it right for the last few years. Before my "2013 startup year" I worked on a philanthropy advisory non-profit. 80% of my job was selling to wealthy individuals our service of being a guide to better donations. So I was basically a salesperson selling a service that almost nobody in Brazil consider a real need or problem - btw that's one difference between cause driven non-profits and market driven startups, you don't pivot if the market doesn't need your service, you persist. Mainly because the people you are solving a problem and the people giving you money are two separate stakeholders usually. That's kind of inevitable, because the social problem wouldn't be there to begin with if the market/society were really bothered by it. I can't imagine Watsi pivoting because people do not want to pay for medical anymore, but they would be willing to pay for a exotic tourism service to where the people they aid are from. They might get more money this way, but social tourism is another cause, solves another problem (maybe). It is not an acceptable pivot for a non-profit.
Back on topic, I learned to be persistent to get to a no. People hate saying no to something that the society consider the right thing to do, even if they have no intention of actually doing it, so this was crutial to my job - get a "no" was always my objective.
But I disagree with a reason to do it is getting feedback. I never got real feedback for why people were saying no - maybe because of what I was selling, there is a stigma in saying "I won't donate because I earned it by myself and I am antitled to spend on whatever I want, and giving them away to other people's benefit is not my idea of a money well spent".
Persistence is an admirable trait of any good salesperson though I would never recommend irritating an answer out of someone.
Most people think: Failure --> Success
It is actually: Failure --> Failure --> Failure --> Success
I think most guys (and possibly girls) eventually learn (sometimes through painful experience) that getting a quick rejection is better than being friend-zoned. Fail faster! Talk to that interesting person who intrigue you!
Pretty sure I understood what he is getting at but I'm not sure this advice will work or is recommended for all industries.