- Like
- SHARE
- Digg
- Del
- Tumblr
- VKontakte
- Flattr
- Buffer
- Love This
- Save
- Odnoklassniki
- Meneame
- Blogger
- Amazon
- Yahoo Mail
- Gmail
- AOL
- Newsvine
- HackerNews
- Evernote
- MySpace
- Mail.ru
- Viadeo
- Line
- Comments
- Yummly
- SMS
- Viber
- Telegram
- JOIN
- Skype
- Facebook Messenger
- Kakao
- LiveJournal
- Yammer
- Edgar
- Fintel
- Mix
- Instapaper
- Copy Link
We’ve talked a lot on SaaStr about how to make that critical hire: the VP Sales. I’ve done it right, and I’ve done it wrong. When it’s good … it’s just so good. It all clicks. But when you make a mis-hire, it’s about the worst mis-hire you can make. Because you’ll lose not just some incremental revenue, but potentially far more. All the second-order revenue you could have had (6x the initial lost revenue). You’ll end up with a crummy sales team under a mis-hire. And you’ll get lost. You can end up in a Year of Hell.
So I’ve tried to help here. We’ve posted a script to use when interviewing a VP Sales. A guideline to what phase and type to hire. And lessons learned on what a VP Sales really does.
And yet …
Even with all that …
You may screw it up. In fact, the majority of first VP Sales in SaaS companies don’t make it 12 months. Recently, the team at Salesforce asked me to present at Dreamforce on not just how to hire a VP Sales — but also how to fire one. Which got me thinking about key ways to figure it out — fast. You can see some of my slides below (you’ll have to come to Dreamforce to hear it all). So let’s dig in on how to know when you’ve made that mis-hire.
So let me tell you how you can figure it out — fast. People will disagree, especially those without a background in managing a great VP Sales. Your Board and investors may challenge this. Your colleagues may as well. But bear with me … you’ll see I’m right. That you’ll know in 30 days.
How is this possible?
First, let’s step back to our checklist of what a Great VP, Sales really does. Job #1 is Recruiting. Bringing in an amazing team that can sell under him or her. And constantly recruiting. Because you’ll need 2 more reps, then 4 more, then 8 and 16 and 64 more reps … to hit your compounding revenue plan. You’ll need the heads. And the Great VP, Sales all know this from experience.
So here’s Test #1: Did Your VP Sales Bring In At Least 1-2 Great Reps in the First 30 Days?
If not … it isn’t going to work out. I’m sorry, it’s just not. At least, not that well.
Why? Because all the great ones not only know this is job #1, but because they know it — they are always cultivating a few great reps to bring with them. In fact, the Great VPs of Sales often show up with a few great reps in tow for this very reason.
And if they haven’t for some reason (a bit of a fail right there) — they know that’s job 1 on Day 1, to get two more great reps in ASAP. So one way or another, they’ll bring in at least 2 Great Reps in the First 30 Days.
And Here’s Test #2: Did Your VP Sales Get Rid of the Worst Rep You Have in the First 30 Days?
Flip side of the same coin. It’s just a huge waste having an underperforming rep or two in the early days. Because leads are so precious in the early days. The Great VPs of Sales know you can’t route the Good Leads to a Mediocre/Crummy Rep. So they stop doing it immediately. And usually, manage out the worst of the bunch almost immediately.
You know what the mediocre VPs of Sales do? They tell you they need every warm body. That they can’t afford to get rid of Can’t Close Bob, as bad as his numbers are.
And it’s true. The mediocre VPs of Sales can’t afford to get rid of Can’t Close Bob. But the great ones don’t need Can’t Close Bob — at all. They immediately show him the door.
OK so those are the tests for Job 1 – Recruiting and Team Building.
——-
Next Up are the Tests for Job #2: Backfilling and Improving the Team.
The bottom line is you can figure out if your VP Sales is good enough based on revenue in about 90 days — It’s True. How? 90 Days Isn’t Enough to build up the pipeline, you say. Fair enough. 90 Days Isn’t Enough to See the Results of My Fancy New Processes? True, to some extent. But the thing is, it’s plenty of time to do Better Than We Were Doing Before.
When your VP Sales comes in, hopefully, you have something in the pipeline, some in-bound leads, some sort of mini-engine. Maybe it’s just a sputtering 1 cylinder engine … but something. Something to improve.
So a Great VP Sales will, if nothing else, tune the engine she inherits immediately, and so you’ll see faster revenue growth in just Half a Sales Cycle — and materially faster growth in Just One Sales Cycle (so this one might take 90 days to know for sure). You’ll see momentum, more deals in demos, more draft contracts going out, halfway through your sales cycle. And by the end of Just One Sales Cycle (say 90 days) … you should see real revenue improvements. Quantitative improvements of more deals closed. And more deals about to close.
It almost has to happen that way, if the VP Sales has made the people improvements we talked about above.
My Real VP Sales doubled sales in 90 days for this reason.
You shouldn’t expect quite those results. But, you should see real revenue progress in Number of Days = Average Sales Cycle. Or faster.
Otherwise, Houston, We Have a Problem. If you hear “I need more time” — something is Wrong. If you hear Pipeline, Pipeline, Pipeline … but there are no improvements in revenue and growth rates in One Sales Cycle — something is Wrong. It’s not my opinion. It doesn’t matter what your VP Sales even says, or what his or her past experience was. It’s just a fact.
And don’t listen to your Board or Advisors either — if they haven’t done it themselves. They’ll tell you to give it more time. And they will be very, very wrong.
Cut Bait, Don’t Fish, fire this VP Sales, and find your Real VP Sales. Fire this VP Sales in 90 days, and you may be OK. Give him or her 6-9+ months … to see how it plays out … and you’ll end up with a lost year. Don’t do it.
Because if it isn’t working in 30 days, then you haven’t really hired your true VP Sales. Find her or him. It was the best hire I ever made.
(note: an updated SaaStr Classic post)